2. EXECUTIVE SUMMARY 8 SECTION 1: Background 14 Transit Only and Single-Mode Trip Planners Multimodal Trip Planners Open Source Software Considerations Open Source Approach Selected for OTP SECTION 2: Project Overview 20 Kick-Off Workshop July 2009 Project Management Plan September 2009 Project Scope and Goals Project Plan and Milestones The Open Elements of the Open Trip Planner Open Source Development Method Open Source Software Open Architecture Open Data Implementation of Prototypes February 2010 Year One Anniversary July 2010 Progress in Year Two

3. SECTION 3: Developing a Routable Network in Open Street Map 32 Analyzing Routable Street Network Alternatives for OTP Open Street Map Improvement Process Geocoding Issues OpenStreetMap Conclusions SECTION 4: Evaluation Studies 38 Preliminary Transit Trip Testing in January 2011 Preliminary Bicycle Trip Testing June 2011 Preliminary Bicycle-to-Transit Trip Testing June 2011 SECTION 5: Next Steps43 Metro RTO Grant Phase II OTP Metro RTO Grant 2011-2013 Target Goals July 2011 Kick-Off Workshop OTP October Launch Continued OSM Improvements

4. APPENDICES 46 Appendix A – High Level System Requirements Appendix B – Map of Test Areas for Open Trip Planner Appendix C – OTP Bicycle Safety Weights Appendix D – Procedures for PDX-OSM Improvement Project 50 Part 1 – Groundwork and Preparation Part 2 – Evaluations and Results Part 3 – Detailed Editing Procedures Part 4 – Quality Control Process

5. S2 project overview Metro Regional Travel Options Grant July 1, 2009 – July 1, 2011

6. S2 project overview Project Kick-Off Workshop July 2009

7. S2 project overview OpenTripPlanner.org

8. S2 project overview Open Source Development Method

9. S2 project overview Shapefiles Oracle OSM OpenStreetMap Regional Data PostGIS Adapter Adapter Adapter Adapter Adapter Data API Geocoding Service Address Normalizer Service Etc. Routing Service Client Application Web Services API Open Architecture

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

11. S2 project overview Progress in Year 1 (July 2009 – July 2010) Worldwide interest and participation

12. S2 project overview Progress in Year 1 Support and maintenance options

13. S2 project overview Demos Released Granada, Spain July 2010 Pune, India October 2010 Smartrip Transport for Dublin Journey Planner January 2011 Ottawa Canada Green Trip Planner January 2011 Tampa, Florida May 2011 Gipuzkoa Transit Android App May 2011 TeleAviv, Israel Budapest, Hungary July 2011 Translations into: French, Gaelic, Hungarian, Italian, Marathi, Polish, Spanish, Hebrew In-Kind Code Development Code quality improvements Improved wheelchair accessibility Graph reloading Speed improvements Memory usage improvements Code 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 Nominatimgeocoder 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 Progress in Year 2 July 2010 – July 2011

14. S3 routable network for OTP Street Map Data Options Why OSM? Investment in community product for shared benefits

15. S3 routable network for OTP Betsy Breyer Melelani Sax-Barnett PJ Houser Grant Humphries Portland State University Student Interns

16. S3 routable network for OTP

17. S3 routable network for OTP

18. S4 otptrip evaluation studies 15 trips Trips representative of suburban cyclists, downtown commuters Chosen to reveal OTP’s sensitivity to particular data Test Trips and Areas

19. S4 otptrip evaluation studies 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? Bicycle Routing Dependencies

21. Street type

22. User preferences Very competitive with other bicycle trip planners Bicycle Trip Planning Results

24. Street type

25. User preferences Minutes Bicycle-to-Transit Trip Planning Results

27. Street type

28. User preferences Arrival time All trips set to depart at/after 12:00 PM Bicycle-to-Transit Trip Planning Results

29. S4 otptrip evaluation studies Results OTP produced a significantly faster trip in all cases OTP trips also arrived earlier in all cases Bicycle Trip Planning Results

30. S4 otptrip evaluation studies 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 Trip Testing Conclusions

31. S4 otptrip evaluation studies Current version Earlier version Trip Itinerary Improvements

32. S5 next steps Metro Regional Travel Options Grant July 1, 2011 – July 1, 2013

33. S5 next steps

34. S5 next steps

35. New Features Introduced Target Release Date October 15, 2011