The HERE Map Attributes API REST API offers simple and fast access to the rich HERE Map Content, seamlessly extensible by your own map data.
Simplified access to the whole HERE map content.
Maps (catalogs) for different applications.
A map (catalog) contains thematic layers, optimized for typical use cases.
A layer is geographically tiled - tiling optimized for map display, driver warnings, map matching and routing use cases.
Tiles can be used easily - no referencing between tiles, tiling of roads and polygons optimized for the use cases.
Plain text or JSON response, flat lists of map objects (POIs, roads, carto lines, carto polygons, traffic signs...).
Map objects have a permanent identifier and a flat set of attributes.
In addition to plain tile retrieval, geographic filtering (rectangle, polyline corridor) and attribute value filtering (roads with more than 2 lanes) are supported.
Fast response times (milli seconds) for tile retrieval.
Upload your own map objects for customized map display, routing, search and driver warning (Bring Your Own Data).
Very simple upload, new / updated map content becomes instantly available.
Your map content stays private, it is just available for your applications through the HERE Location Services.
Retrieved map content can be cached within applications up to 1 month.
The per transaction or per asset based pricing differs slightly depending on the premium layer content used. Contact your account executive for your use case and volumes. Evauation and limited volumes are free of charge.
You can also run the HERE Map Attributes API in your own premises (self hosted). Contact your sales representative for more information.
For the terms and conditions covering this documentation, see the HERE Documentation License.
For the available authentication options, see the Identity & Access Management Developer Guide.
For information about how to get support, see the Developer Support FAQ.
When submitting a bug report or asking for support, always provide the routing request URI, request identifiers and the corresponding errorCode, if any.
You can tag your requests with a request identifier using the non-standard HTTP header X-Request-ID. The service will echo this value in the response, be it success or failure. While you can use any string as the request identifier, we recommend using a UUID to uniquely identify your requests.