Routing API Developer's Guide

Effect of elevation on bicycle speed

Our bicycle routing considers elevation change, when determining what speed should be used on the given road. When going up the hill, speed decreases, possibly down to the pedestrian speed. When going down the hill, speed increases. Exact values are not mentioned in the documentation, as those can change with every release. The speed profile can not match all the cyclist, multiple profiles might be introduced in the future.

Elevation affects both route choice and estimated time to traverse the route. Following example shows how the ETA changes, when going on same road in 2 different directions.

https://route.cit.api.here.com/routing/7.2/calculateroute.json
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&waypoint0=geo!47.16757543377595,7.262282020247881
&waypoint1=geo!47.17349788688307,7.268998271621172
&mode=fastest;bicycle
https://route.cit.api.here.com/routing/7.2/calculateroute.json
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&waypoint0=geo!47.17349788688307,7.268998271621172
&waypoint1=geo!47.16757543377595,7.262282020247881
&mode=fastest;bicycle

First route, which goes up the hill, should have significantly higher ETA than the one going down the hill. In the time of writing this example, it was 405 seconds versus 144 seconds.

Elevation can be also returned in the response. It will be returned as third coordinate of a shape point.

https://route.cit.api.here.com/routing/7.2/calculateroute.json
?app_id={YOUR_APP_ID}
&app_code={YOUR_APP_CODE}
&waypoint0=geo!47.4242219248006,7.226144573449801
&waypoint1=geo!47.46701586747927,7.265097544012576
&mode=fastest;bicycle
&routeattributes=sh
&returnelevation=true

This can then be displayed to the user, for example by colouring the route based on slope or by displaying elevation profile of the route.