open trip planner status update may 2011
DESCRIPTION
otpTRANSCRIPT
bene
fits
of open data
resu
lts o
f collaboration
pow
er o
f open source software
Dec 2005 - Google Transit launched Portland, OR Dec 2010 - 448 participating cities worldwide
resu
lts o
f co
llabo
ratio
n
General Transit Feed Spec (GTFS) Initially for Google Transit
Now supports hundreds of apps
worldwide
resu
lts o
f co
llabo
ratio
n
bene
fits
of o
pen
data
40 apps developed by third parties using TriMet’s open data PDX Bus sends @ 100k requests/day for next arrival info
bene
fits
of o
pen
data
City of Portland resolution directs city government to open data and encourage adoption of open source solutions in technology procurement
bene
fits
of o
pen
data
Just look at the numbers:
7 Other nations establishing open data16 States now offering data sites9 Cities in America with open data236 New applications 253 Data contacts in Federal Agencies305,709 Datasets available on Data.gov
bene
fits
of o
pen
data
proprietary software
open source software
risk
low entry cost, shared costs
broad user & developer base (many
eyes)
fosters innovation and competition
risk
traditional business model, well understood
aligns with procurement
processes
more control
Understand and weigh your risks and advantagesNot all proprietary is the same, and not all oss is the same
p
ower
of
open
sou
rce
soft
war
e
Analyzed alternatives for internet mappingCompared open source alternatives with proprietary
p
ower
of
open
sou
rce
soft
war
e
TriMet Interactive System Map/Trip Planner maps.trimet.orgAll open source technologies including GeoServer, OpenLayers, PostGIS
p
ower
of
open
sou
rce
soft
war
e
TriMet Interactive System Map/Trip Planner maps.trimet.orgReal-Time Vehicle locations , Measure Distance Tool
p
ower
of
open
sou
rce
soft
war
e
Internal applications using same open source platformMobility map, Real-Time Vehicle Mapper, Stops and Amenities Application, Accident & Incident Application, Transit Mapper
p
ower
of
open
sou
rce
soft
war
e
Single-Mode Trip Planners
trip
pla
nnin
g
2009 Portland, OR
1. trimet trip planner
2. oregon unemployment claim
3. 95.5 the game
4. multnomah county jail
5. onpoint credit union
6. mypcc
7. pcc.edu
8. pdx.edu
9. workinginoregon.org
10. blazers edge
2010 Portland, OR
trip
pla
nnin
g
Timeline for Development of Open Source Multi-Modal Trip PlannerProject Management Plan September 2009
Software development and implementation of working prototype January 2011
Evaluation Study May 2011
Final Reports June 2011
Metro Regional Travel Options Grant July 1, 2009 – July 1, 2011
open
trip
pla
nner
(OTP
)
Project Kick-Off Workshop July 2009
open
trip
pla
nner
(OTP
)
OpenTripPlanner.org
open
trip
pla
nner
(OTP
)
Open Source Development Method
open
trip
pla
nner
(OTP
)
Open Architecture
ClientApplication
GeocodingService
Web ServicesAPI
AddressNormalizer
ServiceEtc.Routing
Service
Data API
Shapefiles Oracle OSMOpenStreetMap
RegionalDataPostGIS
Adapter Adapter Adapter Adapter Adapter
open
trip
pla
nner
(OTP
)
Street Data
OSM
Elevation Data
USGS
Transit Data
GTFS
Open Data
open
trip
pla
nner
(OTP
)
OTP Graph
What can OPEN deliver in 9 months?
open
trip
pla
nner
(OTP
)
What can OPEN deliver in 9 months?
open
trip
pla
nner
(OTP
)
Worldwide interest and participation
open
trip
pla
nner
(OTP
)
Support and maintenance options
open
trip
pla
nner
(OTP
)
Street Map Data Options Why OSM? Investment in community product for shared benefits
open
str
eet m
ap (O
SM)
Jurisdictional Data
• regional or local coverage
• not designed for routing
Commercial Products
• seamless worldwide coverage
• includes routing attributes
• costly annual license fees
OSM
• seamless worldwide coverage
• includes routing attributes
• collaboration with community
Portland State University Student Interns
open
str
eet m
ap (O
SM)
PJ Houser Betsy Breyer Melelani Sax-Barnett
Grant Humphries
Phase I – Feb 18, 2011 thru Aug 18, 2011 Improve existing geometry Add new linework: missing streets, trails, bicycle lanes , ped paths, waterways Add/correct attribution Verify directionality and add turn restrictions for bicycle routing
open
str
eet m
ap (O
SM)
Phase II –Aug 18, 2011 Verify directionality, add turn restrictions and speed limits for driving directions
Not Included Addresses & Loc_Ids (only for segments we are editing, not all of them)
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 playingTools for Editing: ESRI ArcMap
Tools for Editing: ESRI ArcMap, JOSM, Potlatch, Merkaartor, MapZen, Quantum GIS, Osmosis
Topology Tools Validation Tools (JOSM)
open
str
eet m
ap (O
SM)
open
str
eet m
ap (O
SM)
open
str
eet m
ap (O
SM)
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
On the Horizon
OTP Phase II Kick-off WorkshopJuly 2011
OTP TriMet Public Beta Release September 2011
OSM Data Improvements and further collaboration with community and jurisdictions for on-going maintenance
Code for America Program Innovative new program that provides real resources to advance open source software and data in government
bene
fits
of open data
resu
lts o
f collaboration
pow
er o
f open source software
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