- Routing for car, foot and bike
- Offline Routing for Smartphone Apps
- Roundtrip Routing
- Isochrones (beta)
- Ski-routing (beta)
bicycle routing and
The routing API currently covers Western Europe. The base network for the Routing API is the OpenStreetMap network of roads and ways. The bicycle routing is based on three layers of data: 1) road network, 2) digital elevation model, giving preference for routes with less vertical climb, 3) a route popularity heatmap of Europe, based on 3 million user provided bike routes, giving preference to more popular alternatives and thus covering “soft” factors such as surface quality, traffic or scenicness.
Please note that certain types of applications may require quality check and quality improvement of the specific OpenStreetMap area. (This most notably applies to ski routing in a specific area. For other routing types the network quality usually is excellent already.)
The API returns a specific route between two or more points plus meta data such as distance (which can be used to calculate a time estimate). The API also returns a complete road book / cue sheet for each route. The cue sheet can easily be translated in any language, current translations exist for English, German and Dutch.
The Routing API can be used in any application, including browsers and smartphone apps. See the chapter Maptoolkit UI Components for a deploy-ready route planning component for browsers that operates with the Routing API.
Optionally lift opening hours can be taken into account for selected ski resorts, and the routing can be packaged as an offline routing package (so it works without data connection). Note that usually the data quality of each ski resort needs to be checked prior to deployment.
The large Austrian ski resort Ski Amadé is already making use of our ski routing in their data goggles: