EXECUTIVE SUMMARY 8

SECTION 1: Background 14Transit Only and Single-Mode Trip PlannersMultimodal Trip PlannersOpen Source Software ConsiderationsOpen Source Approach Selected for OTP

SECTION 2: Project Overview 20 Kick-Off Workshop July 2009Project Management Plan September 2009

Project Scope and GoalsProject Plan and Milestones

The Open Elements of the Open Trip PlannerOpen Source Development MethodOpen Source SoftwareOpen ArchitectureOpen Data

Implementation of Prototypes February 2010Year One Anniversary July 2010Progress in Year Two

SECTION 3: Developing a Routable Network in Open Street Map 32Analyzing Routable Street Network Alternatives for OTPOpen Street Map Improvement ProcessGeocoding IssuesOpenStreetMap Conclusions

SECTION 4: Evaluation Studies 38Preliminary Transit Trip Testing in January 2011

Preliminary Bicycle Trip Testing June 2011 Preliminary Bicycle-to-Transit Trip Testing June 2011

SECTION 5: Next Steps 43Metro RTO Grant Phase II

OTP Metro RTO Grant 2011-2013 Target GoalsJuly 2011 Kick-Off Workshop

OTP October Launch Continued OSM Improvements

APPENDICES 46 Appendix A – High Level System RequirementsAppendix B – Map of Test Areas for Open Trip PlannerAppendix C – OTP Bicycle Safety Weights Appendix D – Procedures for PDX-OSM Improvement Project50

Part 1 – Groundwork and PreparationPart 2 – Evaluations and ResultsPart 3 – Detailed Editing ProceduresPart 4 – Quality Control Process

Metro Regional Travel Options Grant July 1, 2009 – July 1, 2011

Project Tasks Estimated Completion Data Actual Completion Date

Project Management Plan September 2009 September 2009

Software development and implementation of working prototype

January 2011 February 2010

Evaluation studies for data efficacy and OTP planned trip results

May 2011 July 2010 – June 2011

Final Reports June 2011 June 2011 S2 p

roje

ct o

verv

iew

Project Kick-Off Workshop July 2009

S2 p

roje

ct o

verv

iew

OpenTripPlanner.org

S2 p

roje

ct o

verv

iew

Open Source Development Method

S2 p

roje

ct o

verv

iew

Open Architecture

ClientApplication

GeocodingService

Web ServicesAPI

AddressNormalizer

ServiceEtc.Routing

Service

Data API

Shapefiles Oracle OSMOpenStreetMap

RegionalDataPostGIS

Adapter Adapter Adapter Adapter Adapter

S2 p

roje

ct o

verv

iew

Street Data

OSM

USGS National Elevation Dataset

NED

Transit Data

GTFS

OTP uses open source datasets (GTFS, NED, and OSM) to build a routable graph.

S2 p

roje

ct o

verv

iew

Progress in Year 1 (July 2009 – July 2010)Worldwide interest and participation

S2 p

roje

ct o

verv

iew

Progress in Year 1Support and maintenance options

S2 p

roje

ct o

verv

iew

Progress in Year 2 July 2010 – July 2011

Demos Released

5. Granada, Spain July 20106. Pune, India October 20107. Smartrip Transport for Dublin Journey

Planner January 20118. Ottawa Canada Green Trip Planner

January 20119. Tampa, Florida May 201110. Gipuzkoa Transit Android App May

201111. TeleAviv, Israel 12. Budapest, Hungary July 2011

Translations into: French, Gaelic, Hungarian, Italian, Marathi, Polish, Spanish, Hebrew

In-Kind Code DevelopmentCode quality improvements Improved wheelchair accessibility Graph reloading Speed improvements Memory usage improvementsCode documentation Tutorials and user guides Intermediate stops in API Better extensibility Visualization improvements Making bikes on transit optional Kept up-to-date with changing technology Edge notes Nominatim geocoder support Cleaner max walk distance support Support for certain common GTFS failure modes Workarounds for OSM data issues (pedestrian islands) Support loading OSM from Protocol Buffers format & bz2 xml OSM future proofing OSM permission bug fixes Traffic circles / roundabouts Much improved transfer support (min transfer times; transfers now routed on walking network) Support for multiple route names on the same stop pattern (typically night buses) Dozens of miscellaneous bug fixes Gvsig visualization Documentation for graph builder Better names for some OSM ways Better slope visualization Slope override for bridges Some integration with OneBusAway Preferred/non-preferred/banned routes

S2 p

roje

ct o

verv

iew

Street Map Data Options Why OSM? Investment in community product for shared benefits

S3

rout

able

net

wor

k fo

r OTPJurisdictional

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

PJ Houser Betsy Breyer Melelani Sax-Barnett

Grant Humphries

S3

rout

able

net

wor

k fo

r OTP

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

Improve geometry

Add additional linework: missing streets, trails, bicycle lanes , pedestrian paths, major waterways

Add/correct attribution

Verify directionality and add turn restrictions for bicycle routing

S3

rout

able

net

wor

k fo

r OTP

S3

rout

able

net

wor

k fo

r OTP

S4

otp

trip

eva

luati

on s

tudi

es

Test Trips and Areas

15 trips

Trips representative of suburban cyclists, downtown commuters

Chosen to reveal OTP’s sensitivity to particular data

S4

otp

trip

eva

luati

on s

tudi

es

Bicycle Routing Dependencies

Algorithm

Data

Where is the bicycle infrastructure?

How are data translated for the algorithm? Configuration

How does the router determine the best path from A to B?

S4

otp

trip

eva

luati

on s

tudi

es

Bicycle Trip Planning Results

Very competitive with other bicycle trip planners

Custom weights Routes consider a variety of factors:

• Bicycle infrastructure• Street type• User preferences

S4

otp

trip

eva

luati

on s

tudi

es

Bicycle-to-Transit Trip Planning Results

Routes consider a variety of factors:

• Bicycle infrastructure• Street type• User preferences

PCC Sylva

nia to Gab

riel S

kate

Park

Beave

rton HS t

o Cedar

Hills Sh

opping Cen

ter

Lewis &

Clark C

ollege

to Pionee

r Square

SW Ed

gewood/H

untington to

Oreg

on Zoo En

trance

Portlan

d Centra

l Librar

y to SW

Virginia/

Nevad

a

SW Lu

radel/

25th to Sa

feway

at 8145 SW

Barbur

OHSU to

SW 10th &

Stark

SW 1st/

Ankeny t

o PSU Sm

ith Cen

ter

SW M

oody/Gain

es to Portl

and Ja

panese

Garden

Taylo

r/Cars

on to PCC Sy

lvania

Lake O

sweg

o Tran

sit Ctr

to Lusch

er Fa

rm

Marylhurst

Universi

ty to SW

57th/Josh

ua

SW 42nd/G

aleburn

to M

arylhurst

Universi

ty

SW 84th/B

rookri

dge to

Tuala

tin Hills St

ate Park

Riverp

lace A

thletic C

lub to SW

20th/Burn

side

13

5

24

16 17

811

6

18

45

13

3229

18

8

26

18

38

26

34 32

1915

57

83

35

95

52 51

24

x x

34

26

45

34

21

15

80

86

x

95

54

68

32

OTP Bike-to-Transit Google Transit ATISM

inut

es

S4

otp

trip

eva

luati

on s

tudi

es

Bicycle-to-Transit Trip Planning Results

Routes consider a variety of factors:

• Bicycle infrastructure• Street type• User preferences

PCC Sylva

nia to Gab

riel S

kate

Park

Beave

rton HS t

o Cedar

Hills Sh

opping Cen

ter

Lewis &

Clark C

ollege

to Pionee

r Square

SW Ed

gewood/H

untington to

Oreg

on Zoo En

trance

Portlan

d Centra

l Librar

y to SW

Virginia/

Nevad

a

SW Lu

radel/

25th to Sa

feway

at 8145 SW

Barbur

OHSU to

SW 10th &

Stark

SW 1st/

Ankeny t

o PSU Sm

ith Cen

ter

SW M

oody/Gain

es to Portl

and Ja

panese

Garden

Taylo

r/Cars

on to PCC Sy

lvania

Lake O

sweg

o Tran

sit Ctr

to Lusch

er Fa

rm

Marylhurst

Universi

ty to SW

57th/Josh

ua

SW 42nd/G

aleburn

to M

arylhurst

Universi

ty

SW 84th/B

rookri

dge to

Tuala

tin Hills St

ate Park

Riverp

lace A

thletic C

lub to SW

20th/Burn

side

12:00 PM

12:20 PM

12:40 PM

1:00 PM

1:20 PM

1:40 PM

2:00 PM

2:20 PM

OTP Bike-to-Transit Google Transit ATIS

All trips set to depart at/after 12:00 PM

Arriv

al ti

me

S4

otp

trip

eva

luati

on s

tudi

es

Bicycle Trip Planning Results

Results

OTP produced a significantly faster trip in all cases

OTP trips also arrived earlier in all cases

S4

otp

trip

eva

luati

on s

tudi

es

Trip Testing Conclusions

OpenTripPlanner provides competitive transit and bicycle trip planning

Local knowledge has been critical for adding data in OpenStreetMap and evaluating results in OTP

Multimodal (bike-to-transit) trip planning offers significant trip time reductions

S4

otp

trip

eva

luati

on s

tudi

es

Trip Itinerary Improvements

Earlier version Current version

Metro Regional Travel Options Grant July 1, 2011 – July 1, 2013

Phase II Project Tasks Estimated Completion Data

Project Management Plan September 2011

Software development and implementation January 2013

Evaluation Studies Spring 2013

Final Reports June 2013

S5

next

ste

ps

OTP Metro RTO Grant 2011-2013 Target Goals

•Incorporation of Alerts into the planned trip itinerary •Ability to print output •Bike Preference Triangle•Improvements to the descriptive itinerary•Resolution of bug issues •Speed & performance improvements•Email and SMS output•Ability to calculate fare•Analytical tools and batch trip planning•Multiple language support beyond current translations •Return and prioritization of multiple itineraries•Extend the availability of the service to mobile devices•Trip disability options •Create administrative tools for staff to continue maintenance of the application and data. These include easy and well-documented installation, deployment, and data loading. Routing support for transit, walking and biking all implemented. Improve stability of the API. •Continue to document information such as lessons learned and feedback from participating partners, which will be useful for future government open source software collaborations.

S5

next

ste

ps

OTP Phase II Kick-off WorkshopJuly 2011

OTP TriMet Public Beta Release October 15, 2011

OSM Data Improvements and further collaboration with community and jurisdictions for on-going maintenance

2011-2013 Target Goals

S5

next

ste

ps

New Features Introduced Target Release Date October 15, 2011

OTP Benefits

1. OTP is cheaper than ATIS and is a superior product that utilizes current web and open source technologies.

2. OTP fosters innovation and introduces competition in the industry, which can lead to better products and competitive pricing.

3. Multi-modal functionality is highly requested feature that not even Google or other agencies can offer.

4. OTP is open source and can easily and cost effectively be implemented by other agencies, not just TriMet.

5. OTP has the capacity to be a regional trip planner: working on IGAs with C-Tran, SMART, and Salem-Keizer Transit Cherriots.

6. Worldwide developer community and broad user base has many advantages: more eyes on code and application, faster development cycles, more control, shared costs…

7. Open Street Map data was improved for OTP, however, it can be used for TriMet dispatch purposes, saving significant annual licensing fees for commercial products like Tele Atlas or Navteq.

8. OTP encourages sustainable transportation modes, potentially decreasing the number of drive-alone vehicle trips in the region.

9. OTP has the capacity to save significant travel time when using multi-modes in contrast to single-mode trip planners, like Google and ATIS.