RTPO OVRDC Sidewalk Import
- 1 About
- 2 Import Plan Outline
- 3 Goals
- 4 Schedule
- 5 Import Data
- 6 Data Preparation
- 7 Data Merge Workflow
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 .
Import Plan Outline
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.
Be sure to list the general timeframe of your project.
We will be working with data collected and maintained by OVRDC.
Data source site:http://www.ovrdc.org/rtpo/bike-ped
Data license: https://website.tld/license
Type of license (if applicable): e.g. CC-BY-SA, Public Domain, Public Domain with Attribution, etc.
Link to permission (if required): e.g. link to mail list reference url - http://lists.openstreetmap.org/pipermail/imports/2012-December/001617.html
OSM attribution (if required): http://wiki.openstreetmap.org/wiki/Contributors#yourdataprovider
ODbL Compliance verified: yes/no
OSM Data Files
Link to your source data files that you have prepared for the import - e.g. the .osm files you have derived from the data sources.
Identify if this is a one-time or recurring import and whether you'll be doing it with automated scripts, etc.
Identify what method will be used for entering the imported data into the OSM database - e.g. API, JOSM, upload.py, etc.
Data Reduction & Simplification
Describe your plans, if any, to reduce the amount of data you'll need to import.
Examples of this include removing information that is already contained in OSM or simplifying shapefiles.
Describe your plan for mapping source attributes to OSM tags.
Describe how you'll use changeset tags in the import.
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.
Data Transformation Results
Post a link to your OSM XML files.
Data Merge Workflow
Describe if you'll be doing this solo or as a team.
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).
List all factors that will be evaluated in the import.
Detail the steps you'll take during the actual import.
Information to include:
- Step by step instructions
- Changeset size policy
- Revert plans
Identify your approach to conflation here.