Working with HERE Map Data
HERE map data includes a rich variety of attributes. Depending on your request, the response may include a number of attribute names, some of which you can use as identifiers.
The Platform Data Extension API divides the world up into a set of regions, which may have more than one release.
When you make a request to the Platform Data Extension API, the response includes the Released Permanent IDs, Tiled IDs, and Dynamic Reference Permanent IDs, unless suppressed in the request. Permanent IDs allow you to combine all HERE core map content and additional content within the same release. In addition, you can also identify the same map objects across releases. However, there are some known limitations such as link splits or POIs with POI categories that may have changed.
If your request does not specify a certain release, then the most up-to-date data is delivered. This data also contains the Permanent IDs, but a 100% match between other map objects is not guaranteed. If your application requires a 100% ID match, you must request exactly the same map release from the Platform Data Extension API as the other corresponding HERE APIs.
For major map objects like road links and POIs, there is an option to request dynamic reference IDs such as ULR, AGORA, TMC or street address. This way, you can combine map data across very different map releases, especially with applications that do not have the HERE Permanent IDs on board. However, these requests result in more data transfer and may need more expensive map matching on the application side.
A link is a piece of road with a fixed set of attributes. A link ends at an intersection, or when any of its attributes change, such as the speed limit.
A link has a node at each of its ends. The lower left node (lower latitude, or if equal then lower longitude, or if equal then lower z-level) is called a Reference Node. The other node is called a Non-Reference Node. A node can connect two links to attribute changes along the road, or multiple links when there's an intersection.
- ANTARC – Antartica
- APAC – Asia Pacific
- AUS – Australia
- EEU – Eastern Europe
- HKG – Hong Kong
- IND – India
- MEA – Middle East Africa
- NA – North America
- SAM – South America
- TWN – Taiwan
- WEU – Western Europe
Requests to the Platform Data Extension API can refer to one or more regions by using the
region parameter. However, the
region parameter is optional in most cases, except for when you use the
HERE releases its maps quarterly and weekly. By default, the Platform Data Extension API delivers the latest available map release for each map region. But the API also offers older map releases on demand, which you can select via the
Until the end of 2015, quarterly map releases are named using the YYYYQQ format. For example, in 2015Q4 – the 4 indicates that the map was released in the fourth quarter.
Starting in 2016, quarterly map releases are named using the YYQJN format. For example, in 161J0 – the 161 indicates that the underlying base release is 2016Q1 and the letter J increments with the quarterly releases since then. The last digit N increments if there is a repair reshipment.
Weekly releases are named according to the YYQXX format. For example, in 16133 – the 161 indicates the underlying base release and the number 33 increments with the weekly releases since then. For availability of certain older map releases, contact your HERE Representative or Technical Customer Support.
Typically, HERE APIs use the latest available release of HERE core map. However, the underlying core map release can slightly differ between the different APIs. Hence, Platform Data Extension API offers all recent map releases. This way, you can retrieve additional map data from the map release that corresponds to other HERE APIs. For an example of a map release information request, see Checking Available Maps.