Otp 2009 2011 rto grant final report

775 views
726 views

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
775
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • TriMet is the public transportation service provider in Portland, OR
  • Open Plans has experience developing communities around open source software and data. The objective is build a development community around the code and have Open Plans manage it so it’s a very viable alternative for agencies. 
  • collaborative method to software design, development, distribution with access to source code
  • Collaborative method of tracking work and voting on important decisions.
  • Open Plans has experience developing communities around open source software and data. The objective is build a development community around the code and have Open Plans manage it so it’s a very viable alternative for agencies. 
  • Project timeline July 2009- July 2011. TriMet received a grant to build an osmmtps.  The Open Planning Project (TOPP) http://topp.openplans.org/ is the primary contractor and the subs are David Emory/Five Points http://trip.atltransit.com/, Brandon Martin Anderson/GraphServer (Bus Monster) http://graphserver.sourceforge.net/, and TriMet (in-kind).  We're starting with David's code and building from there.  The objective is build a development community around the code and have TOPP/OpenGeo manage it so it’s a very viable alternative for agencies.  We have enough funding, but we need one other agency on board so its a collaborative effort to ensure continued success. In TOPP’s experience, the most successful os projects are collaborations, so this is critical. 
  • Project timeline July 2009- July 2011. TriMet received a grant to build an osmmtps.  The Open Planning Project (TOPP) http://topp.openplans.org/ is the primary contractor and the subs are David Emory/Five Points http://trip.atltransit.com/, Brandon Martin Anderson/GraphServer (Bus Monster) http://graphserver.sourceforge.net/, and TriMet (in-kind).  We're starting with David's code and building from there.  The objective is build a development community around the code and have TOPP/OpenGeo manage it so it’s a very viable alternative for agencies.  We have enough funding, but we need one other agency on board so its a collaborative effort to ensure continued success. In TOPP’s experience, the most successful os projects are collaborations, so this is critical. 
  • Otp 2009 2011 rto grant final report

    1. 1.
    2. 2. EXECUTIVE SUMMARY 8<br />SECTION 1: Background 14<br />Transit Only and Single-Mode Trip Planners<br />Multimodal Trip Planners <br />Open Source Software Considerations <br />Open Source Approach Selected for OTP<br />SECTION 2: Project Overview 20 <br />Kick-Off Workshop July 2009 <br />Project Management Plan September 2009 <br />Project Scope and Goals <br />Project Plan and Milestones <br />The Open Elements of the Open Trip Planner <br />Open Source Development Method <br />Open Source Software <br />Open Architecture <br />Open Data <br />Implementation of Prototypes February 2010 <br />Year One Anniversary July 2010 <br />Progress in Year Two <br />
    3. 3. SECTION 3: Developing a Routable Network in Open Street Map 32<br />Analyzing Routable Street Network Alternatives for OTP <br />Open Street Map Improvement Process<br />Geocoding Issues<br />OpenStreetMap Conclusions<br />SECTION 4: Evaluation Studies 38<br />Preliminary Transit Trip Testing in January 2011 <br />Preliminary Bicycle Trip Testing June 2011 <br />Preliminary Bicycle-to-Transit Trip Testing June 2011 <br />SECTION 5: Next Steps43<br />Metro RTO Grant Phase II<br />OTP Metro RTO Grant 2011-2013 Target Goals<br />July 2011 Kick-Off Workshop <br />OTP October Launch <br />Continued OSM Improvements<br />
    4. 4. APPENDICES 46<br />Appendix A – High Level System Requirements <br />Appendix B – Map of Test Areas for Open Trip Planner <br />Appendix C – OTP Bicycle Safety Weights <br />Appendix D – Procedures for PDX-OSM Improvement Project 50<br />Part 1 – Groundwork and Preparation <br />Part 2 – Evaluations and Results <br />Part 3 – Detailed Editing Procedures <br />Part 4 – Quality Control Process <br />
    5. 5. S2 project overview<br />Metro Regional Travel Options Grant <br />July 1, 2009 – July 1, 2011<br />
    6. 6. S2 project overview<br />Project Kick-Off Workshop <br />July 2009<br />
    7. 7. S2 project overview<br />OpenTripPlanner.org<br />
    8. 8. S2 project overview<br />Open Source Development Method<br />
    9. 9. S2 project overview<br />Shapefiles<br />Oracle<br />OSM<br />OpenStreetMap<br />Regional<br />Data<br />PostGIS<br />Adapter<br />Adapter<br />Adapter<br />Adapter<br />Adapter<br />Data API<br />Geocoding<br />Service<br />Address<br />Normalizer<br />Service<br />Etc.<br />Routing<br />Service<br />Client<br />Application<br />Web Services<br />API<br />Open Architecture<br />
    10. 10. S2 project overview<br />OTP uses open source datasets (GTFS, NED, and OSM) to build a routable graph.<br />
    11. 11. S2 project overview<br />Progress in Year 1 (July 2009 – July 2010)<br />Worldwide interest and participation<br />
    12. 12. S2 project overview<br />Progress in Year 1<br />Support and maintenance options<br />
    13. 13. S2 project overview<br />Demos Released<br />Granada, Spain July 2010<br />Pune, India October 2010<br />Smartrip Transport for Dublin Journey Planner January 2011<br />Ottawa Canada Green Trip Planner January 2011<br />Tampa, Florida May 2011<br />Gipuzkoa Transit Android App May 2011<br />TeleAviv, Israel <br />Budapest, Hungary July 2011 <br />Translations into: French, Gaelic, Hungarian, Italian, Marathi, Polish, Spanish, Hebrew <br />In-Kind Code Development<br />Code quality improvements <br />Improved wheelchair accessibility <br />Graph reloading <br />Speed improvements <br />Memory usage improvements<br />Code documentation <br />Tutorials and user guides <br />Intermediate stops in API <br />Better extensibility <br />Visualization improvements <br />Making bikes on transit optional <br />Kept up-to-date with changing technology <br />Edge notes <br />Nominatimgeocoder support <br />Cleaner max walk distance support <br />Support for certain common GTFS failure modes <br />Workarounds for OSM data issues (pedestrian islands) <br />Support loading OSM from Protocol Buffers format & bz2 xml <br />OSM future proofing <br />OSM permission bug fixes <br />Traffic circles / roundabouts <br />Much improved transfer support (min transfer times; transfers now routed on walking network) <br />Support for multiple route names on the same stop pattern (typically night buses) <br />Dozens of miscellaneous bug fixes <br />Gvsig visualization <br />Documentation for graph builder <br />Better names for some OSM ways <br />Better slope visualization <br />Slope override for bridges <br />Some integration with OneBusAway<br />Preferred/non-preferred/banned routes<br />Progress in Year 2 July 2010 – July 2011 <br />
    14. 14. S3 routable network for OTP<br />Street Map Data Options <br />Why OSM? Investment in community product for shared benefits<br />
    15. 15. S3 routable network for OTP<br />Betsy Breyer <br />Melelani <br />Sax-Barnett<br />PJ Houser<br />Grant Humphries <br />Portland State University Student Interns <br />
    16. 16. S3 routable network for OTP<br />
    17. 17. S3 routable network for OTP<br />
    18. 18. S4 otptrip evaluation studies<br />15 trips <br />Trips representative of suburban cyclists, downtown commuters<br />Chosen to reveal OTP’s sensitivity to particular data<br />Test Trips and Areas <br />
    19. 19. S4 otptrip evaluation studies<br />Where is the bicycle infrastructure?<br />How are data translated for the algorithm?<br />Configuration<br />How does the router determine the best path from A to B?<br />Bicycle Routing Dependencies <br />
    20. 20. S4 otptrip evaluation studies<br />Custom weights<br />Routes consider a variety of factors:<br /><ul><li>Bicycle infrastructure
    21. 21. Street type
    22. 22. User preferences </li></ul>Very competitive with other <br />bicycle trip planners<br />Bicycle Trip Planning Results<br />
    23. 23. S4 otptrip evaluation studies<br />Routes consider a variety of factors:<br /><ul><li>Bicycle infrastructure
    24. 24. Street type
    25. 25. User preferences </li></ul>Minutes<br />Bicycle-to-Transit Trip Planning Results<br />
    26. 26. S4 otptrip evaluation studies<br />Routes consider a variety of factors:<br /><ul><li>Bicycle infrastructure
    27. 27. Street type
    28. 28. User preferences </li></ul>Arrival time<br />All trips set to depart at/after 12:00 PM<br />Bicycle-to-Transit Trip Planning Results<br />
    29. 29. S4 otptrip evaluation studies<br />Results<br />OTP produced a significantly faster trip in all cases<br />OTP trips also arrived earlier in all cases<br />Bicycle Trip Planning Results<br />
    30. 30. S4 otptrip evaluation studies<br />OpenTripPlanner provides competitive transit and bicycle trip planning<br />Local knowledge has been critical for adding data in OpenStreetMap and evaluating results in OTP<br />Multimodal (bike-to-transit) trip planning offers significant trip time reductions<br />Trip Testing Conclusions<br />
    31. 31. S4 otptrip evaluation studies<br />Current version<br />Earlier version<br />Trip Itinerary Improvements <br />
    32. 32. S5 next steps<br />Metro Regional Travel Options Grant <br />July 1, 2011 – July 1, 2013<br />
    33. 33. S5 next steps<br />
    34. 34. S5 next steps<br />
    35. 35. New Features Introduced <br />Target Release Date October 15, 2011 <br />

    ×