HERE Map Tile Service

Overview

The HERE Map Tile service is a RESTful API that provides map tile images of the whole world. You can use these map tiles in front-end applications as backgrounds for the visualization of geospatial data.

This API provides all available parameters from the original HERE Map Tile API and allows custom display options, multiple tile resources, and color schemes.

Use the HERE Map Tile service to:

Access map tiles for interactive applications
Choose from many viewing schemes and display options
Specify the location, zoom level, and resolution of map tile images

Using the HERE Map Tile service for active routing and track and trace scenarios is not allowed.

API Reference

/tiles/{resource}/{mapId}/{scheme}/{zoom}/{column}/{row}/{size}/{format}

get

Return a map tile

Request
Response

URI Parameters

resource: required (string)
Defines the tile type. For example, maptile, basetile, or labeltile. Find a complete list of tile types in the HERE documentation: https://developer.here.com/rest-apis/documentation/enterprise-map-tile/topics/request-constructing.html
Example:
```
maptile
```
mapId: required (string)
Specifies the map version. It can be a version ID, 'newest' or a hash.
Example:
```
newest
```
scheme: required (string)
Defines the view scheme. For example, normal.day, normal.night, or hybrid.day. Find a complete list of view schemes in the HERE documentation: https://developer.here.com/rest-apis/documentation/enterprise-map-tile/topics/request-constructing.html
Example:
```
normal.day
```
zoom: required (integer)
Zoom level of the map image.
Example:
```
4
```
column: required (integer)
Tile column number.
Example:
```
8
```
row: required (integer)
Tile row number.
Example:
```
5
```
size: required (integer)
Size of the returned map tile in pixels per side. Available options:
- 256
- 512
Example:
```
256
```
format: required (string)
Defines the output format. Available options:
- png
- png8
- jpg
Example:
```
png
```

Headers

Authorization: required (string)
Used to send a valid OAuth2 access token.
Example:
```
Bearer access_token
```

HTTP status code 200

The request was successful, the response contains the requested image.

HTTP status code 400

The request is invalid.

Body

Type: text/xml

Example:

Bad request

HTTP status code 401

Given request is unauthorized. Bad or expired token. Reauthenticate the user. Any details will be provided within the response payload.

Body

Type: application/json

Schema:

{
  "$schema":"http://json-schema.org/draft-04/schema#",
  "title":"error",
  "description":"Schema for API specified errors.",
  "type":"object",
  "properties":
  {
    "status":
    {
      "type":"integer",
      "description":"original HTTP error code, should be consistent with the response HTTP code",
      "minimum":100,
      "maximum":599
    },
    "type":
    {
      "type":"string",
      "description":"classification of the error type, lower case with underscore eg validation_failure",
      "pattern":"[a-z]+[a-z_]*[a-z]+"
    },
    "message":
    {
      "type":"string",
      "description":"descriptive error message for debugging"
    },
    "moreInfo":
    {
      "type":"string",
      "format":"uri",
      "description":"link to documentation to investigate further and finding support"
    },
    "details":
    {
      "type":"array",
      "description":"list of problems causing this error",
      "items":
      {
        "$schema":"http://json-schema.org/draft-04/schema#",
        "title":"errorDetail",
        "description":"schema for specific error cause",
        "type":"object",
        "properties":
        {
          "field":
          {
            "type":"string",
            "description":"a bean notation expression specifying the element in request data causing the error, eg product.variants[3].name, this can be empty if violation was not field specific"
          },
          "type":
          {
            "type":"string",
            "description":"classification of the error detail type, lower case with underscore eg missing_value, this value must be always interpreted in context of the general error type.",
            "pattern":"[a-z]+[a-z_]*[a-z]+"
          },
          "message":
          {
            "type":"string",
            "description":"descriptive error detail message for debugging"
          },
          "moreInfo":
          {
            "type":"string",
            "format":"uri",
            "description":"link to documentation to investigate further and finding support for error detail"
          }
        },
        "required":["type"]
      }
    }
  },
  "required":["status" , "type" ]
}

Example:

{
  "status":401,
  "message":"Authorization: Unauthorized. Bearer TOKEN is invalid",
  "type":"insufficient_credentials",
  "moreInfo":"https://pattern.yaas.io/errortypes.html"
}

HTTP status code 403

Evaluated request scopes in access token are not sufficient and do not match required scopes.

Body

Type: application/json

Schema:

{
  "$schema":"http://json-schema.org/draft-04/schema#",
  "title":"error",
  "description":"Schema for API specified errors.",
  "type":"object",
  "properties":
  {
    "status":
    {
      "type":"integer",
      "description":"original HTTP error code, should be consistent with the response HTTP code",
      "minimum":100,
      "maximum":599
    },
    "type":
    {
      "type":"string",
      "description":"classification of the error type, lower case with underscore eg validation_failure",
      "pattern":"[a-z]+[a-z_]*[a-z]+"
    },
    "message":
    {
      "type":"string",
      "description":"descriptive error message for debugging"
    },
    "moreInfo":
    {
      "type":"string",
      "format":"uri",
      "description":"link to documentation to investigate further and finding support"
    },
    "details":
    {
      "type":"array",
      "description":"list of problems causing this error",
      "items":
      {
        "$schema":"http://json-schema.org/draft-04/schema#",
        "title":"errorDetail",
        "description":"schema for specific error cause",
        "type":"object",
        "properties":
        {
          "field":
          {
            "type":"string",
            "description":"a bean notation expression specifying the element in request data causing the error, eg product.variants[3].name, this can be empty if violation was not field specific"
          },
          "type":
          {
            "type":"string",
            "description":"classification of the error detail type, lower case with underscore eg missing_value, this value must be always interpreted in context of the general error type.",
            "pattern":"[a-z]+[a-z_]*[a-z]+"
          },
          "message":
          {
            "type":"string",
            "description":"descriptive error detail message for debugging"
          },
          "moreInfo":
          {
            "type":"string",
            "format":"uri",
            "description":"link to documentation to investigate further and finding support for error detail"
          }
        },
        "required":["type"]
      }
    }
  },
  "required":["status" , "type" ]
}

Example:

{
  "status": 403,
  "message": "Given request does not have required scopes in access token. It is not authorized to perform this operation.",
  "type": "insufficient_permissions"
}

HTTP status code 500

A server error occured.

Body

Type: text/xml

Example:

Internal Server Error

/tiles/{resource}/{mapId}/{scheme}/{zoom}/{column}/{row}/{size}/{format}

Service Usage

The HERE Map Tile service provides multiple URI parameters to access map tiles. These tiles split a large world map into individual pieces that you can assemble to produce a continuous image. The zoom level defines the resolution per side of the overall map. Each zoom level has a fixed number of columns and rows, starting with 0 (zero).

In general, the recommended method for consuming the Map Tile service is through a front-end map library such as HERE Maps API for JavaScript.

Introduction

To use this tutorial, you must have a valid Bearer access token.

For more information about how to get an access token, see the /token endpoint of the OAuth2 service's API Reference.

All tutorials are designed in a way that you can use them at the same time with the cURL REST client. You can also use the API Console to try out the API.

Request map tiles

To test your access to the HERE Map Tile service and to understand the structure of the request URL, you can send manual requests for tile images.

Use the following URI to request a map tile on the smallest zoom parameter level, 0. Because zoom level 0 only provides a single tile, the column and row parameters are also set to 0 in the example URI.

  /tiles/basetile/newest/terrain.day/0/0/0/256/png

basetile on the smallest zoom level

Zooming in and adjusting the column and row values gives you a map of Germany and its neighboring countries. You can also increase the value of the size parameter to 512 to receive a larger image.

  /tiles/maptile/newest/normal.day/4/8/5/512/png

a maptile showing central Europe

You can adjust the scheme and resource URI parameters to change the style of the map.

Set the resource parameter to define the type of tile to use. For example, maptile, basetile, or labeltile. Find a complete list of tile types in the HERE Map Tile API documentation.

For a complete list of scheme parameter value options, see the scheme entry in the Map Tile section of the HERE Map Tile API documentation. The full list includes options for specifying the type of map, color scheme, and day or night modes.

  /tiles/basetile/newest/normal.day/4/8/5/512/png

a basetile showing central Europe

In addition to illustrated maps, you can also access satellite images.

  /tiles/maptile/newest/hybrid.grey.day/4/8/5/512/png

a maptile made of satellite images

Send feedback
If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.
Get Help
Use our private help channel. Receive updates over email and contact our specialists directly.
hybris Experts
If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.

Overview

API Reference

/tiles/{resource}/{mapId}/{scheme}/{zoom}/{column}/{row}/{size}/{format}

/tiles/{resource}/{mapId}/{scheme}/{zoom}/{column}/{row}/{size}/{format}

get /tiles/{resource}/{mapId}/{scheme}/{zoom}/{column}/{row}/{size}/{format}

URI Parameters

Headers

HTTP status code 200

HTTP status code 400

Body

HTTP status code 401

Body

HTTP status code 403

Body

HTTP status code 500

Body

Service Usage

Introduction

Request map tiles