Open Street Map Improvement Project

RLIS Partner and Regional Street Centerline Meeting

Metro March 2, 2011

Presented by Bibiana McHugh, IT Manager of Spatial Technologies

Google Trends – Most Popular Searches by City

Single-Mode Trip Planners

Single-Mode Trip Planners

Single-Mode Trip Planners

Multi-Mode Trip Planners

Multi-Mode Trip Planners

Multi-Mode Trip Planners

Multi-Mode Trip Planners

Task 1. Project Management Plan

Project Initiation Workshop

July 15-17, 2009

Task 2. Develop and implement the software Jan 2011

Task 3. Evaluation Study May 2011

Task 4. Develop Final Report June 2011

Open Source Multi-Modal Trip Planner

OpenTripPlanner.org Project

Open Plans

Open Source Development Method

OpenTripPlanner.org

Open Source Development Method

Open Architecture

Client

Application

Geocoding

Service

Web Services

API

Address

Normalizer

Service

Etc.Routing

Service

Data API

Shapefiles Oracle OSMOpenStreetMap

Regional

DataPostGIS

Adapter Adapter Adapter Adapter Adapter

Open Data / Free Data

OTP Demos & Deployments

Elevation chart for bicycle trips

OSM Transit Trip Testing

TheIntertwine.org

The

Intertwine

Project

Implementation of

OTP for Intertwine

Planning of multi-

modal trips including

biking and walking

to explore Intertwine

Sharing of

information between

users and

community

Trails.shp developed

for Intertwine

Datasets used to build OTP graph

GTFS Data

Transit Trip Planning

USGS National

Elevation

Dataset

Street Data

Routing attributes required

OTP Street Data Options

Commercial

Products

TeleAtlas or Navtech

seamless coverage

worldwide

meets all requirements but

costly

RLIS Centerline

File

maintained by local

jurisdictions and

integrated for regional

distribution

3-county coverage area

designed for geocoding &

other regional

requirements, not routing

Open Street

Map

originally imported from

TIGER 2007 (without

addresses) and crowd-

sourced

seamless coverage

worldwide

designed for, and

supports, multi- modal

routing

no customization needed

for OTP,

not proprietary

Priority Phase I – Feb 18, 2011 thru Aug 18, 2011

1 Improve Geometry- make OSM linework coincident with RLIS

2Add 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

OSM PDX Google Group

On-line Google Doc

OSM Community

Portland wiki pagehttp://wiki.openstreetmap.org/wiki/Portland,_Oreg

on

Portland OpenStreetMap

grouphttp://www.meetup.com/OpenStreetMap-Portland/

Dave Hanson Local PDX user who imported Tiger data for US

OSM Mailing Lists

Talk

Imports

Routing

Announce

josm-dev

osmosis-dev

2011 PSU Student Interns

PJ Houser

Breyer, Betsy

Melelani

Sax-Barnett

Grant Humphries

(not Hugh Grant)

Shapefile OSM

Point, Line or Polygon FileEverything in one data model, more similar to

geodatabase

Point Node

Line Way

Polygon Closed Way (beg xy = end xy) or Relation

Attribute Tag

Layer 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

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 File

a. In ArcMap, create 10’ buffer @ all RLIS streets and dissolve

b. Query for all OSM ways that are inside the buffer

c. Reverse selection and export to new DIFF shapefile

d. Convert shapefile to OSM for use in JOSM (ArcMap 10 OSM Editor has

bugs)

2. Create Reclass File

Create a new RLIS file with OSM attributes

OSM Editing Procedures

RLIS Attribute OSM Key OSM Valueslocalid RLIS:localid

leftadd1 DELETE

leftadd2 DELETE

rgtadd1 DELETE

rgtadd2 DELETE

fdpre name_direction_prefix

fname name_base

ftype name_type

fdsuf name_direction_suffix

name "fdpre fname ftype fdsuf"

lzip zip_left

rzip zip_right

lcity DELETE

rcity DELETE

lcounty DELETE

rcounty DELETE

cfcc DELETE

class DELETE

drct 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 null

leadzero DELETE

quirk DELETE

side DELETE

source DELETE

struc DELETE

subarea DELETE

type highway see types

createdate DELETE

updatedate DELETE

lowner DELETE

rowner DELETE

Shape_Leng DELETE

Create Reclass File

Type Description OSM TagsKey 1 Value 1 Key 2 Value 2

1110 Freeway. highway motorway

1120 Ramps, interchanges and feeders. highway *_link oneway *

1121 On ramp (only). highway *_link oneway yes

1122 Off ramp (only). highway *_link oneway yes

1123 On/off ramp. highway *_link oneway no

5101 Freeway with rapid transit (i.e. MAX or streetcar). highway motorway railway light_rail

3100 Trail. highway footway

3200 Path. highway path

3210 Pedestrian walkway. highway pedestrian

3230 Stairway. highway steps

3250 Off street bikeway. highway cycleway cycleway track

1760

Private Road with NO Valid Address Range or Street Name. (Portland

only, subarea = 'P'). highway unclassified access private

1200 Highway. highway trunk

1221

Local street to freeway/highway on ramp (only) (Portland only, subarea =

'P'). highway motorway_link oneway yes

1222

Freeway/Highway to local street off ramp (only) (Portland only, subarea =

'P'). highway motorway_link oneway yes

1223

Freeway/Highway to local street on/off ramp (combination) (Portland only,

subarea = 'P'). highway motorway_link oneway no

1300 Primary arterial. highway primary

1400 Secondary arterial. highway secondary

1450 Major residential (cartographic). highway residential

1500 Minor residential (unclassified). highway residential

1521 Local street to local street connector (Portland only, subarea = 'P'). highway tertiary_link

1550

Minor residential street (unclassified), named but without addresses

(Clackamas Co. only, subarea = 'C') highway residential

1560

Minor 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 File

1. In ArcMap, create 10’ buffer @ all RLIS streets and dissolve

2. Query for all OSM ways that are inside the buffer

3. Reverse selection and export to new DIFF shapefile

4. Convert shapefile to OSM for use in JOSM (ArcMap 10 OSM Editor has bugs)

B. Create Reclass File

Create a new RLIS file with OSM attributes

C. Edit OSM File

In JOSM, bring in DIFF File, Reclass File, OSM File (1/4 County OSM files

downloaded nightly), and Aerials for reference

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

4. Delete old OSM feature geometry and DIFF geometry to track progress

5. Merge nodes in OSM

6. Upload corrections to OSM

OSM Editing Procedures

Mapping Layers in JOSM

Layer Name File

WashSE Diff.osmDiff 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

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 2011

Intertwine Project

Thank You!

CONTACT:

Bibiana McHugh

IT Manager of Spatial Technologies

McHughB@trimet.org

VISIT:opentripplanner.org

theintertwine.org

OSM-PDX Google Group