RTPO OVRDC Sidewalk Import

From OpenStreetMap Wiki
Jump to: navigation, search
Available languages — Import/Plan Outline
· Afrikaans · Alemannisch · aragonés · asturianu · azərbaycanca · Bahasa Indonesia · Bahasa Melayu · Bân-lâm-gú · Basa Jawa · Baso Minangkabau · bosanski · brezhoneg · català · čeština · dansk · Deutsch · eesti · English · español · Esperanto · estremeñu · euskara · français · Frysk · Gaeilge · Gàidhlig · galego · Hausa · hrvatski · Igbo · interlingua · Interlingue · isiXhosa · isiZulu · íslenska · italiano · Kiswahili · Kreyòl ayisyen · kréyòl gwadloupéyen · Kurdî · latviešu · Lëtzebuergesch · lietuvių · magyar · Malagasy · Malti · Nederlands · Nedersaksies · norsk bokmål · norsk nynorsk · occitan · Oromoo · oʻzbekcha/ўзбекча · Plattdüütsch · polski · português · português do Brasil · română · shqip · slovenčina · slovenščina · Soomaaliga · suomi · svenska · Tiếng Việt · Türkçe · Vahcuengh · vèneto · Wolof · Yorùbá · Zazaki · српски / srpski · беларуская · български · қазақша · македонски · монгол · русский · тоҷикӣ · українська · Ελληνικά · Հայերեն · ქართული · नेपाली · मराठी · हिन्दी · অসমীয়া · বাংলা · ਪੰਜਾਬੀ · ગુજરાતી · ଓଡ଼ିଆ · தமிழ் · తెలుగు · ಕನ್ನಡ · മലയാളം · සිංහල · ไทย · မြန်မာဘာသာ · ລາວ · ភាសាខ្មែរ · ⵜⴰⵎⴰⵣⵉⵖⵜ · አማርኛ · 한국어 · 日本語 · 中文(简体)‎ · 吴语 · 粵語 · 中文(繁體)‎ · ייִדיש · עברית · اردو · العربية · پښتو · سنڌي · فارسی · ދިވެހިބަސް

About

This import is in support of an initiative to widen the OSM-based pedestrian network to include cities within the area under the jurisdiction of the Regional transportation planning organisation (RTPO) known as Ohio Valley Regional Development Commission (OVRDC). The RTPO region includes 12 southern Ohio counties: Adams, Brown, Clermont, Fayette, Gallia, Highland, Jackson, Lawrence, Pike, Ross, Scioto and Vinton. You can read more about our program at our website [1].

Import Plan Outline

OVRDC will generally follow the outline as proposed here - Proposed features/sidewalk schema.

Goals

The goal is to improve the mapping of the pedestrian network within the RTPO region by importing sidewalk data collected by OVRDC. The data is high quality and covers such a large area that it would be extremely time-intensive to match through individual mapping.

Within the RTPO region there is a considerable need to import data due to the lack of data available within this region on OpenStreetMap. By importing OVRDC sidewalk data the map will improve significantly and encourage others within the RTPO region to contribute as well. This source containing sidewalk data would also be able to assist in the creation and development of routing tools to help assist those with limited mobility and needs for safe travel.

We plan to import pedestrian data, defined as: crosswalk, cycleway, and footway. The import data will be limited to the cities containing any crosswalks, cycleways, and footways within the RTPO region in order to address the lack of data available.

Schedule

We would like to complete the import by the end of January, 2017.

Import Data

Background

We will be working with data collected and maintained by OVRDC.

Data source site:https://www.ovrdc.org/apps/osm-sidewalk-project.html
Data license: Public Domain
Type of license (if applicable): Public Domain
Link to permission (if required):
OSM attribution (if required):
ODbL Compliance verified:

OSM Data Files

GeoJSON Format: https://www.ovrdc.org/apps/assets/data/sidewalk-study/sidewalks_wch_12_02_16.geojson

Import Type

JSOM.

Data Preparation

Data Reduction & Simplification

Shapefiles have been simplified to the extent that is possible to maintain validity.

Tagging Plans

highway=footway + footway=sidewalk

highway=crossingrailway=crossingcycleway=crossingfootway=crossing

surface=paved,paving_stones,fine_gravel,dirt

smoothness=good,intermediate,bad

Brick = "paving_stones"

Crushed Limestone = "fine_gravel"

Changeset Tags

Data Transformation

Describe the transformations you'll need to conduct, the tools you're using, and any specific configurations or code that will be used in the transformation.

We are converting to osm in JOSM and using the validation tools to look over any errors. Topology has been completed in ArcMap.

Data Transformation Results

Post a link to your OSM XML files.

??

Data Merge Workflow

Team Approach

We are working on this as a team of revolving interns under a Transportation Planning Coordinator at OVRDC in cooperation with the Ohio Department of Transportation (ODOT).

References

List all factors that will be evaluated in the import.

Workflow

Detail the steps you'll take during the actual import.

Information to include:

  • Collect sidewalks via ortho imagery (Ohio OSIP) and field collection
  • Create and validate topology using ArcMap
  • Consult with local officials on the results of the field/ortho mapping
  • Consult with OSM Community via listserv and web maps
  • Validate shapefiles to OSM using JOSM
  • Merge with OSM data using JOSM
  • Upload
  • Changeset size policy - none as of yet
  • Revert plans - none as of yet

Conflation

We would like to use NGA's Hootenany software, available here - https://github.com/ngageoint/hootenanny - but need to actually get it up and running first. A OSM hosted hootenany instance would be amazing! For now we are using JOSM and eliminating any conflicts on our side. For example, we decided not to include a bikepath we collected, as it is already in OSM, and conflating it would be too time consuming.