Routing API v7 Developer's Guide

Public Transport Routing (Deprecated)

Important: This service is deprecated and is planned to be discontinued. Please use Transit API V8 instead.
The Routing API v7 calculates public transport routes in one of two ways:
  • Estimated Routing – uses aggregated data to estimate a route.
  • Timetable Routing – uses dynamic data to provide a more precise, detailed route.

The table below lists the differences between the two ways that the API calculates public transport routes.

Table 1. Public Transport Routing Feature Availability
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

When calculating public transport routes, we recommend to always use the fastest Routing Mode Type. See RoutingTypeType for more information.

Estimated Routing

You can enable this mode using the publicTransport parameter. In this mode, precise departure and arrival times are not available. However, specifying a departure time is still important, as line availability and frequency can change throughout the day. Specifying an arrival time is not supported for Estimated Routing. Such a request results in an error response.

Timetable Routing

Note: This feature may be subject to premium pricing. For details, contact your HERE customer representative.

You can enable this mode using the (publicTransportTimeTable) parameter. In this mode, departure and arrival times are available. The request must specify either an arrival or departure time; but not both.

If timetable routing is requested, but timetable coverage is not available for the requested area, the service returns a route using estimated data. If coverage is available, but no route is found, a NoRouteFound error is returned.

Timetable Routing support for schematic transit line geometry and access points depends on data availability.

Using Timezones in Public Transport Routing Requests

When you specify an arrival or departure time, you can decide whether you need to append a timezone offset.
  • If no timezone is specified – the time is 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 is considered as is. This is useful if you want to specify the current time.

For more information, see xs:dateTime.

Public Transport Coverage and Availability

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 may carry a lesser scope by default as opposed to what may be additionally available pending contractual agreements and access entitlements. Contact your HERE customer representative for additional details.

Note: Currently, the getRoute service does not support Public Transport routing. For more information, see Get Route.