Public Transport Routing Mode
- Estimated routing (
publicTransport) uses aggregated data to estimate a route. In this mode, precise departure and arrival times are not available. Specifying departure time is still important, as line availability and frequency can change throughout the day.
- Timetable routing (
publicTransportTimeTable) uses dynamic data to provide a more precise, detailed route. In this mode, departure and arrival times are available. The request must specify either an
departuretime (but not both).
When specifying an
departure time you can decide whether you need to append a timezone offset (see xs:dateTime for reference). The following will happen:
- If no timezone is specified the time will be considered local to the departure/arrival point (this is useful when you want to specify a time in a possibly unknown timezone of the departure/arrival point)
- If a timezone is specified the time will be considered as is. (This is useful, for example, if you want to specify the current time).
If timetable routing is requested, but timetable coverage is not available for the requested area, service will return a route using estimated data. If coverage is available, but no route is found, an error
NoRouteFound will be returned.
arrivaltime is not supported for the estimated Public Transport routing. Requesting will result in an error response.
getRouteservice (see Get Route) does not support Public Transport routing.
Please refer to the table below for key differences between Estimated Routing and Timetable Routing.
|Feature Name||Estimated Routing||Timetable Routing|
|Respects public transit access points||Yes||Yes*|
|Schematic transit line geometry||Yes||Yes*|
|Accurate time information||No||Yes|
|Company logo images||Yes||No|