The Routing API has supported path details for 2 years, but had some limitations. E.g. the details like cycleway, or bridleway where missing, which is now returned instead of a generic “other” value. Also path details are now supported for the TomTom add-on. Before: Afterwards: If you want to see this feature in action on […]
One of the main purposes of our open-source routing engine is calculating the ideal route to get from one place to another. Using publicly available map data from OpenStreetMap it can calculate the optimal route for a given source-target pair for many different vehicles and flexible optimization criteria. However, such route calculations become considerably more […]
The Route Optimization API works via an HTTP endpoint and you POST a JSON document to https://graphhopper.com/api/1/vrp?key=[YOUR_KEY] This requires an API key that you can get here: login and go to API keys and generate an API key by clicking the Add API key button. Copy it and paste it to [YOUR_KEY]. Let us start […]
Lean back and read our fresh spring news: For the GraphHopper Directions API we are looking for an infrastructure engineer – feel free to contact us for more details. A few weeks ago we released the new version 0.12 of the GraphHopper open source routing engine. Read more about it here. Finally we are happy […]
A new release 0.12.0 of the open soure GraphHopper routing engine is available. The GraphHopper routing engine supported turn restrictions and turn costs only for a subset of its algorithms. After over a year of work on the edge-based routing for the speed mode (Contraction Hierarchy=CH) it is now possible to support turn costs for […]
We are happy to announce our new API docs. We specified our APIs in the OpenAPI specification language and moved the entire content of our old documentation to a single OpenApi 3.0 document. This has many advantages: There is only a single source for the documentation of new features, and for generating client code to […]
