Sample Request

https://indoor-routing.venue.maps.cit.api.here.com/venues/routing/v1
  ?app_id={YOUR_APP_ID}
  &app_code={YOUR_APP_CODE}
  &waypoint0={START_OF_ROUTE}&waypoint1={END_OF_ROUTE}&venueRouteOptions={VENUE_ROUTE_OPTIONS}&mode=fastest;pedestrian

For more information on supported outdoor routing attributes, see the related section in the Routing API Developer's Guide.

Waypoints

There can be only one start (waypoint0) and one destination (waypoint1) parameters in the request. The general syntax of the waypoint parameter is:

geo!{latitude}, {longitude},{level}

Example 1: waypoint0=geo!52.518807689845346,13.415577850623919,0

venueRouteOptions

Default values

Route options are optional. If no options are given, the defaults are used: fastest;allowAll

Response

The Venues routing service response follows the structure of the common outdoor routing service response. Some extensions described below were added to represent indoor specific information.

The response currently consists of single route containing necessary legs to represent all indoor and connecting outdoor legs to travel between start and destination waypoints. Each leg has type property defining whether leg is indoor or outdoor leg. The legs are always represented in logical order from start to destination in respect to provided start and destination waypoints. For indoor legs, only pedestrian routing is currently supported, and any parameters suggesting other routing modes will be ignored.

In addition to common outdoor response shape property, the response introduces a level property determining corresponding level (floor) for every coordinate pair represented in the shape property.

  For example:
…
    "shape": [
      52.519885791453724,
      13.414394522476186,
      52.51939683023066,
      13.415148150431241,
      52.51856395001506,
      13.416065256894697,
      52.518521265746585,
      13.416319253668194,
      52.51856775464091,
      13.416489715739772,
      52.518598064769954,
      13.416581861849192,
      52.51841526493865,
      13.416708111029038,
      52.51840558397678,
      13.416716257755013,
      52.518318792513625,
      13.416794671105707,
      52.518351603126355,
      13.41705527381896
    ],
    "level": [
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      1,
      1
    ],
...

  

The shape and level pair described above is available as both route and leg level attributes. So both routes as legs of a combined route can have shape-level pairs attached to them.

The maneuver element represents a position along a route on which the user is expected to perform a specific action such as entering or exiting a building or entering or exiting a connector between levels.

  For example:

[
  {
    "position": {
      "latitude": 52.51840558397678,
      "longitude": 13.416716257755013,
      "level": 0
    },
    "id": "V_7171Lv15001Ds2486074",
    "connectorType": "ESCALATOR",
    "actionType": "ENTER"
  },
  {
    "position": {
      "latitude": 52.518318792513625,
      "longitude": 13.416794671105707,
      "level": 1
    }
    "id": "V_7171Lv15002Ds2486091",
    "connectorType": "ESCALATOR",
    "actionType": "EXIT"
  }
]

  

For an example of a complete routing request and response, see Requesting a Venue Route.