Traffic API Developer's Guide

Requesting a Traffic Pattern Tile

The API supports requests for a tile overlay showing the typical traffic pattern for a specific time point during the week. The time point is specified as a number of seconds from the beginning of the week (00:00 hours, Sunday, in local time).

Traffic Pattern, [Z]/[X]/[Y] Addressing

User Story

The user wants to obtain a map tile showing a traffic pattern, 5:40 PM, using the [Z]/[X]/[Y] addressing scheme:

Request Summary

The following list summarizes the elements required to create a request matching the user story and shows, in square brackets, how those elements are used in the request example below. Note that the request example also uses the authentication parameters.

Resource: tiles [tiles]
URL variables: {zoom}/{column}/{row} [8/134/86], the [Z]/[X]/[Y] (tile) addressing scheme, see also The Mercator Projection
  size [256], the resolution of the response image
  {format} [png32], the format of the response image
Parameters: pattern_time [pattern_time=150000], a value indicating the time point for which to obtain the traffic pattern overlay as a number of seconds from 00:00 on Sunday, in local time)

Request

A request matching the user story is formulated as follows:

https://tiles.traffic.cit.api.here.com/traffic/6.0/tiles/8/134/86/256/png32
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&pattern_time=150000

Response

The response to the requests for a traffic pattern tile overlay delivers the following PNG image:

Figure 1. Traffic pattern tile Traffic Pattern Tile for Frankfurt at 5:40 PM on Monday

Note that if you remove the parameter pattern_time, the returned map tile is identical to the one in the flow tile example (see also Figure 1):

Figure 2. Flow tile Real-time flow tile request for Frankfurt

Traffic Pattern, Quadkey Addressing

The same traffic tile request is shown below, but this time it uses the quadkey addressing scheme:

User Story

The user wants to obtain a map tile showing a traffic pattern, 5:40 PM, using the quadkey addressing scheme:

Request Summary

The following list summarizes the elements required to create a request matching the user story and shows, in square brackets, how those elements are used in the request example below. Note that the request example also uses the authentication parameters.

Resource: tiles [tiles]
URL variables: {quadkeytraffic} [quadkeytraffic], resource endpoint, indicating that a traffic tile overlay based identified by a quadkey is required
Parameters: quadkey [quadkey=12020330], ], map tile location specified as a single value, see also Quadkeys
  pattern_time [pattern_time=150000], a value indicating the time point for which to obtain the traffic pattern overlay as a number of seconds from 00:00 on Sunday, in local time)

Request

A request matching the user story is formulated as follows:

https://tiles.traffic.cit.api.here.com/traffic/6.0/tiles/quadkeytraffic
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&quadkey=12020330
&pattern_time=150000

Response

The result is an image as shown for the quadkey version of the request under Response

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 selfservesupport@here.com.