Indoor routing backend service

This tutorial describes the information about indoor routing backend service and its usage via APIs.

The Indoor Routing backend service provides functionality to generate route within indoor map such as shopping mall, parking garages etc. Route can be generated across multiple levels within indoor map considering indoor attributes. Multimodal routes also can be requested which includes vehicle or combination of vehicle and pedestrian.

Pre-requisites

• Your organization must be onboarded to HERE Indoor Maps. For more information, see Prepare to use indoor maps.
• A HERE indoor map must be ordered for the building and opt for routing graph. For more information, see Order and update indoor maps.
• Any User or App which will be using the indoor routing service should be added as a member of Indoor maps project. To learn how to add users to the indoor maps project, please see Add new users to the Indoor Maps project.

Indoor routing API reference

• API reference

Features and tools

• Multilevel route calculation.
• Consideration of the space addressing i.e. Center point of a particular space in route calculation.
• Route calculation based on topology modality and directionality.
• Transport mode supported: pedestrian, car, taxi, scooter.
• Multimodal route with one vehicle at a time with or without pedestrian included depending on the availability of the route. Though we are expecting only one value in the transportMode, pedestrian will be considered by default as a secondary mode in case of any vehicle mode given.
• Customized route if user wants to start, end or have entire journey with the vehicle by providing vehicle-enable option in the parameters.
• Customized speed options for any transport mode with a defined range. Duration calculation will happed based on the given speed.
• If any of the route conditions requested by the user are not satisfied in the route, a notice will be given to the user. For example, if a user requested a car-based route and such a route is not present or available, an equivalent route will be given starting with pedestrian directions, and eventually transitioning to a car-based route, with a notice warning that the given condition is violated in the output route.
• Query parameters given in API to calculate the route based on requirement. i.e. if route needs to avoid features like stairs, escalators or ramp.
• Routing modes can be given as parameters, such as fast or short. fast will give fastest route based on duration and short will give shortest route based on distance.
• Additional intermediate waypoints can be inserted into the route by specifying one or more via waypoint parameters between actual origin and destination. The route will then visit those locations in the order they were specified in.