GuidesAPI Reference
Guides
  1. HERE Map Attributes API v8 Developer Guide

Introduction to HERE Map Attributes API v8

HERE Map Attributes API v8 is based on and offers simple access to HERE map data and customers' private map data.

Overview

Features

  • 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 are easy to use - 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, and more).
    • Map objects have a permanent identifier and a flat set of attributes.
  • Support for plain tile retrieval, geographic filtering (rectangle, polyline corridor) and attribute value filtering (roads with more than two lanes).
  • Fast response times (milliseconds) for tile retrieval.
  • Caching retrieved map content in applications up to one month.

Pricing

The pricing differs slightly depending on the content used. Contact us for your use case and volumes. Evaluation and limited volumes are free of charge.

Self-hosting (on premise)

You can also run HERE Map Attributes API v8 in your own premises (self-hosted). Contact us for more information.

Request tracing

When submitting a bug report or asking for support, always provide the routing request URI, request identifiers and the corresponding error code, if any.

You can tag your requests with a request identifier using the non-standard HTTP header X-Request-ID. The service echoes this value in the response, be it success or failure. While you can use any string as the request identifier, using a universally unique identifier (UUID) to identify your requests is recommended.

Updated last month