This documentation is for v1 of the Route Planning API.
This guide will help you get started with the Route Planning API. To start you will need a test-account or an access token. Get in touch, we will supply you with one asap.
The Route Planning API can:
We supply a few default routing profiles, Bicycle, Car and Pedestrian.
The bicycle profile has the following options:
comfort: A comfortable route preferring well-paved roads, smaller roads and a bit of scenery at the cost of speed.
fastest: A profile that prioritizes speed over everything else.
shortest: A profile that prioritizes speed over everything else.
safety: A defensive route shying away from big roads with lots of cars.
comfort_safety: A route which aims to be both safe and comfortable at the cost of speed.
comfort_safety_speed: A route which aims to be both safe and comfortable without sacrificing too much of speed.
networks: A recreative route following existing cycling networks. Might make longer detours.
node_network: A recreative route following existing cycle node networks. Might make longer detours.
cycle_highway: A functional route, preferring cycle_highways or the Brussels Mobility network. If none are availale, will favour speed.
commute: A functional route which is aimed to commuters. It is a mix of safety, comfort, a pinch of speed and cycle_highway.
The car profile has the following options:
fastest: The main metric is time, this focuses on getting somewhere as fast as possible.
shortest: The main metric is distance, calculates routes that are as short as possible.
classifications: This profile prefers roads with a higher classification.
The pedestrian profile is a special case. A pedestrians speed is pretty much constant so there is only one profile:
default: The shortest route.