(→Results: - some speed examples ...) |
|||
| Line 19: | Line 19: | ||
The other main option would seem to be using the [[Open Source Accessibility Toolkit]] code which seems to include OD routing capability by centroid of traffic zones. However this is probably not updated to work with the latest OTP. It does include some nice visualisation capabilities though, if we want to calculate things like modal accessibility difference between PT and car. | The other main option would seem to be using the [[Open Source Accessibility Toolkit]] code which seems to include OD routing capability by centroid of traffic zones. However this is probably not updated to work with the latest OTP. It does include some nice visualisation capabilities though, if we want to calculate things like modal accessibility difference between PT and car. | ||
=== OTP's performance for O-D routing via the PT network === | |||
From the OSAT manual, some indicative routing speed results from 2011 using OTP (capabilities of computer used not stated): | |||
"Trip calculations can range from <100ms to >2 seconds per trip. In the long run for DC, it comes out to be about 240ms per trip, or 4 minutes to calculate 1000 trips. For King County, which has a larger graph, it comes out to be about a second per trip. Runtime also depends on your processor." | |||
Revision as of 04:47, 8 August 2013
WP Essentials
This is a Work Package as part of the OSSTIP project.
Inputs: BZE’s Proposed updated network and frequency information, Working OSSTIP platform for display of existing PT timetable (OSSTIP/WP4), Network->timetable conversion tools (OSSTIP/WP5).
Outputs: Installed instance of OSSTIP with relevant GIS data uploaded, Created map-based analysis, and updated documentation.
Estimated Time: Medium
Requirements Summary
- Investigate OTP's Batch Analyst Mode routing capabilities/speed
- Investigate the Open Source Accessibility Toolkit extension to OTP for these types of calculations.
Results
(2013-08-08) - am trying to follow instructions of OTP's https://github.com/openplans/OpenTripPlanner/wiki/Batch-Analyst mode to see how good its capabilities are in this area. This seems to require installing and setting up a development environment for the project, based on Eclipse.
The other main option would seem to be using the Open Source Accessibility Toolkit code which seems to include OD routing capability by centroid of traffic zones. However this is probably not updated to work with the latest OTP. It does include some nice visualisation capabilities though, if we want to calculate things like modal accessibility difference between PT and car.
OTP's performance for O-D routing via the PT network
From the OSAT manual, some indicative routing speed results from 2011 using OTP (capabilities of computer used not stated):
"Trip calculations can range from <100ms to >2 seconds per trip. In the long run for DC, it comes out to be about 240ms per trip, or 4 minutes to calculate 1000 trips. For King County, which has a larger graph, it comes out to be about a second per trip. Runtime also depends on your processor."