Venue Maps API Developer's Guide

Venue Maps API Request

A typical request to the Venue Maps API includes the basic elements shown in the following table and, in addition, it may contain resource-specific parameters.

Table 1. Basic elements of request to Venue Maps API
Element	Value/Example	Description
Base URL	`http://static-{1-4}.venue.maps.api.here.com`	Production environment
Path	`0` or `1`	Feature access parameter `0` - provides access to standard feature in resource tiles-png, tiles-ia, tiles-ia-b64 `1` - provides access to premium features in resources models-poi, models-full
Resource	tiles-png tiles-ia tiles-ia-b64 models-poi models-full	GET only, specify request details via query parameters
Level	`L{n}`	`n` is the number value of the floor level specified for the requested venue. Only needed for: tiles-png tiles-ia tiles-ia-b64
Application Code	`&app_code={YOUR_APP_CODE}`	Substitute your own unique `app_code`
Application ID	`&app_id={YOUR_APP_ID}`	Substitute your own unique `app_id`
Signature	`Signature=<Signature-value>`	Substitute your unique Signature
Key-Pair-Id	`Key-Pair-Id=<Key-Pair-Id-value>`	Substitute your unique Key-Pair-Id
Policy	`Policy=<Policy-value>`	Substitute your unique Policy

For further information, see Examples.

The Venue Maps CDN Service

The Venue Maps API accesses a CDN service that is configured with load balanced server pools. Use a suffix between 1 and 4 to access the Venue Maps API which allows download in parallel. In order to get the optimal cache hit rates, use URL prefixes 1, 2, 3 and 4 for the rows and columns of the tiles distribution as follows:

1: even row and column numbers
2: even row numbers and odd column numbers
3: odd row numbers and even column numbers
4: odd row and column numbers

Generic Requests

Generic request to a Venue Maps API tile looks as follows

<Base URL>/<Access>/<Resource>/<Level>/<quadkey>.<filename extension>?<Application Id>&<Application Code>&<Policy>&<Signature>&<Key-Pair-Id>

Generic request to a Venue Maps API model looks as follows

<Base URL>/<Access>/<Resource>/<Venue Identifier>.<filename extension>?<Application Id>&<Application Code>&<Policy>&<Signature>&<Key-Pair-Id>

Examples

Tile Example:

http://static-3.venue.maps.api.here.com/0/tiles-png/L0/03022223103013033.png?
  Policy={YOUR_GENERATED_POLICY}
  &Signature={YOUR_GENERATED_SIGNATURE}
  &Key-Pair-Id={YOUR_GENERATED_KEY_PAIR_ID}
  &app_id={YOUR_APP_ID}
  &app_code={YOUR_APP_CODE}

Response:

For More Tile Examples, see Examples.

Model Example:

http://static-3.venue.maps.api.here.com/1/models-full/DM_7171.json?
  Policy={YOUR_GENERATED_POLICY}
  &Signature={YOUR_GENERATED_SIGNATURE}
  &Key-Pair-Id={YOUR_GENERATED_KEY_PAIR_ID}
  &app_id={YOUR_APP_ID}
  &app_code={YOUR_APP_CODE}

Response:

{"content":
  {"category":
    {
    "id":"shopping","nt":"6512"
    },
    
    "phoneNumber":"+49 (30) 2693400",
    "placeId":"",
    "names":{"GER":"Alexa Shopping Center"},
    "addresses":
      {"GER":{"postalCode":"10179",
      "countryCode":"DEU",
      "houseNumber":"20",
      "streetName":"Gruner strasse",
      "district":"DE","city":"Berlin"},
      "ENG":{"postalCode":"10179",
      "countryCode":"DEU",
      "houseNumber":"20",
      "streetName":"Gruner strasse",
      "district":"DE","city":"Berlin"}},
    "contentId":"814985"},
  
  "connectors":[{
    "destination2":"Lv15003Ds_2486040",
    "connectorClass":"ELEVATOR",
    "destination1":"Lv15004Ds_2486057"}, ... 
           == Content Truncated ==

For more Model Examples, see Examples.