Routing API Developer's Guide

Public Transport Routing Mode

Routing API calculates public transport routes in one of two different ways:
  • 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 arrival or departure time (but not both).

When specifying an arrival or 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.

Note: Specifying arrival time is not supported for the estimated Public Transport routing. Requesting will result in an error response.
Note: Always use the fastest Routing Mode Type when calculating Public Transport routes. See RoutingTypeType for more information.
Note: At the moment getRoute service (see Get Route) does not support Public Transport routing.

Please refer to the table below for key differences between Estimated Routing and Timetable Routing.

Table 1. Public Transport Routing Feature Availability Matrix
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
LinkId functionality Yes No
Note: Timetable Routing may be subject to premium pricing. For details please contact your sales representative.
Note: Certain geographic coverage carries contractual limitations for syndication to 3rd parties beyond HERE Owned and Operated applications. This coverage currently includes, but is not limited to, the following: Paris, France (STIF); Berlin, Germany (VBB); full coverage Germany (Deutsche Bahn); and Helsinki, Finland (HSL). These regions will carry a lesser scope by default as opposed to what may be additionally available pending contractual agreements and access entitlements. Contact your Sales, Marketing, or Product representative for additional details.
Note: Timetable Routing support for schematic transit line geometry and access points depends on data availability.

You cannot use this account to purchase a commercial plan on Developer Portal, as it is already associated to plans with different payment methods.

To purchase a commercial plan on Developer Portal, please register for or sign in with a different HERE Account.

Something took longer than expected.

The project should be available soon under your projects page.

Sorry, our services are not available in this region.

Something seems to have gone wrong. Please try again later.

We've detected that your account is set to Australian Dollars (AUD).
Unfortunately, we do not offer checkouts in AUD anymore.
You can continue using your current plan as normal, but to subscribe to one of our new plans,
please register for a new HERE account or contact us for billing questions on