OSM Improvements
description
Transcript of OSM Improvements
Priority Phase I – Feb 18, 2011 thru Aug 18, 2011 1 Improve Geometry- make OSM linework coincident with RLIS
2 Add Additional Linework: Trails.shp, bicycle.shp, pedestrian paths, major waterways
3 Verify Directionality for bicycle routing 4 Verify Turn Restrictions for bicycle routing
Priority Phase II 5 Turn restrictions – physical and legal for driving
Not Included Addresses Loc_Ids (only for segments we are editing, not all of them)
OSM Improvements
Shapefile OSM
Point, Line or Polygon File Everything in one data model, more similar to geodatabase
Point NodeLine WayPolygon Closed Way (beg xy = end xy) or RelationAttribute TagLayer file (point, line or poly) Relation (can include nodes and ways)Edit Session Change Set Copy of shapefile for editing Sandbox copy of OSM data for playing
Tools for Editing: ESRI ArcMap Tools for Editing: ESRI ArcMap, JOSM, Potlatch, Merkaartor, MapZen, Quantum GIS, Osmosis
Topology Tools Validation Tools (JOSM)
OSM Glossary
OSM PDX Google Group
On-line Google Doc
Procedures to create coincidence linework between OSM and RLIS and to bring in new linework including: streets, trails.shp, bicycle.shp, pedestrian paths, major waterways
1. Create a DIFF Filea. In ArcMap, create 10’ buffer @ all RLIS streets and dissolveb. Query for all OSM ways that are inside the bufferc. Reverse selection and export to new DIFF shapefiled. Convert shapefile to OSM for use in JOSM (ArcMap 10 OSM Editor has bugs)
2. Create Reclass FileCreate a new RLIS file with OSM attributes
OSM Editing Procedures
RLIS Attribute OSM Key OSM Valueslocalid RLIS:localidleftadd1 DELETEleftadd2 DELETErgtadd1 DELETErgtadd2 DELETEfdpre name_direction_prefixfname name_baseftype name_typefdsuf name_direction_suffix
name "fdpre fname ftype fdsuf"lzip zip_leftrzip zip_rightlcity DELETErcity DELETElcounty DELETErcounty DELETEcfcc DELETEclass DELETEdrct oneway yes if 2 or 3, no if 1, null if 0
flip_direction yes if drct was 3, no if drct was 2, otherwise nullleadzero DELETEquirk DELETEside DELETEsource DELETEstruc DELETEsubarea DELETEtype highway see typescreatedate DELETEupdatedate DELETElowner DELETErowner DELETEShape_Leng DELETE
Create Reclass File
Type Description OSM TagsKey 1 Value 1 Key 2 Value 2
1110 Freeway. highway motorway1120 Ramps, interchanges and feeders. highway *_link oneway *1121 On ramp (only). highway *_link oneway yes1122 Off ramp (only). highway *_link oneway yes1123 On/off ramp. highway *_link oneway no5101 Freeway with rapid transit (i.e. MAX or streetcar). highway motorway railway light_rail3100 Trail. highway footway3200 Path. highway path3210 Pedestrian walkway. highway pedestrian3230 Stairway. highway steps3250 Off street bikeway. highway cycleway cycleway track
1760Private Road with NO Valid Address Range or Street Name. (Portland only, subarea = 'P'). highway unclassified access private
1200 Highway. highway trunk1221 Local street to freeway/highway on ramp (only) (Portland only, subarea = 'P'). highway motorway_link oneway yes1222 Freeway/Highway to local street off ramp (only) (Portland only, subarea = 'P'). highway motorway_link oneway yes
1223Freeway/Highway to local street on/off ramp (combination) (Portland only, subarea = 'P'). highway motorway_link oneway no
1300 Primary arterial. highway primary1400 Secondary arterial. highway secondary1450 Major residential (cartographic). highway residential1500 Minor residential (unclassified). highway residential1521 Local street to local street connector (Portland only, subarea = 'P'). highway tertiary_link
1550Minor residential street (unclassified), named but without addresses (Clackamas Co. only, subarea = 'C') highway residential
1560Minor residential street (unclassified), unamed and without addresses (Clackamas Co. only, subarea = 'C') highway residential unnamed yes
Create Reclass File
Procedures to create coincidence linework between OSM and RLIS and to bring in new linework (including: streets, trails, bike & ped paths, waterways)
A. Create a DIFF File1. In ArcMap, create 10’ buffer @ all RLIS streets and dissolve2. Query for all OSM ways that are inside the buffer3. Reverse selection and export to new DIFF shapefile4. Convert shapefile to OSM for use in JOSM (ArcMap 10 OSM Editor has bugs)
B. Create Reclass FileCreate a new RLIS file with OSM attributes
C. Edit OSM FileIn JOSM, bring in DIFF File, Reclass File, OSM File (1/4 County OSM files downloaded nightly), and Aerials for reference1. Copy RLIS attributes into OSM using “paste tags” tool 2. Copy OSM tags back into RLIS attributes to capture complete set3. Copy RLIS feature and paste geometry (with attributes) into OSM File 4. Delete old OSM feature geometry and DIFF geometry to track progress5. Merge nodes in OSM6. Upload corrections to OSM
OSM Editing Procedures
Mapping Layers in JOSM
Layer Name File
WashSE Diff.osm Diff Layer (contains only streets and trails from OSM that have been identified as inaccurate)
All Str ReClass.som RLIS Streets Layer
Washington-SE.osm OSM Data Layer
Trails_Wash.osm RLIS Trails
TM Aerials Aerial Imagery
RLIS=Blue Diff File & OSM = Red
JOSM Editing Session
1. Copy RLIS attributes into OSM using “paste tags” tool 2. Copy OSM tags back into RLIS attributes to capture complete set
3. Copy RLIS feature and paste geometry (with attributes) into OSM File
Note that this way is now red indicating that it belongs to the OSM Data Layer
4. Delete old OSM feature geometry and DIFF geometry to track progress
5. Merge nodes: connect the newly added ways to the existing OSM node network
Phase I - TO DO LIST
Formalize and approve Tags for all RLIS features (Reclass Files)
Identify procedure for directionality and turn restrictions for bicycle routing
Recruit community to assist with importing waterways
OSM Mapping Parties to test bicycle data and trips - four this summer for each county
Formalize and document procedures to share with other jurisdictions
Prepare for OTP Beta release in Fall 2011Intertwine Project
OTP Project Tasks
Task 1Project Management Plan work with stakeholders to identify and prioritizerequirements and that can be delivered within the two-year timeframe and budget
September 2011
Task 2 Application Development of Features prioritized at July 2011 Workshop January 2011
Task 3 Evaluation Study May 2011
Task 4 Final Reports June 2011
Open Trip Planner Phase II
Metro Regional Travel Options Grant July 1, 2011 – July 1, 2013
Features Needed to Replace ATIS
1. Ability to print, email, and SMS output2. Fare calculations3. Return and prioritization of multiple trip itineraries4. Language translation 5. Graph/chart to easily change variables for trip plans6. Enhancements based on feedback from public beta release 7. Geocoder to locate addresses and landmarks 8. Administrative tools for staff to continue maintenance of the application and data,
including transfers. 9. Tools for Customer Service staff 10. Improve stability of the API for third-party developers11. Extend the availability of the service to mobile devices 12. Trip disability options
Open Trip Planner