Traffic API Developer's Guide

Limitations

To reduce the size and increase the relevance of traffic data, the Traffic API allows you to limit the area and detail of traffic flow data and incident data that you can obtain via queries. In addition, the limitations listed below apply.

Note: The HERE Service Agreement applies for the limitations outlined below. For details on the HERE Service License Agreement, see the relevant documentation.

Traffic Flow Data Limitations

The API restricts the maximum size of a geographical filter used to retrieve traffic flow data. The following limitations apply to requests that specify a bounding box and proximity filters:
  • Maximum width and height of a bounding box: 2 degrees of longitude and latitude
  • Maximum permitted proximity radius: 100km
  • Maximum allowed corridor length: 500km
  • Maximum allowed corridor width: 10km

Although requests that specify very large spatial filters do not result in an error response, the response specifies a limited amount of data, as described above.

Traffic Incident and Zoom Level

Similar to the limitation of traffic flow data, the Traffic API has limitations on traffic incident information which prevent large response data transfers that are unsustainable:
  • No display of traffic incident information: zoom levels 0-7
  • Maximum bounding box width and height: 10 degrees of latitude and longitude
  • Maximum permitted size of the proximity radius: 100km
  • Maximum allowed corridor length: 500km
Note: Queries exceeding the limits in terms of zoom level or proximity radius result in an error response.