Releasing GraphHopper 0.6

Today we are proud to release version 0.6 of our open source road routing engine GraphHopper. It includes many smaller improvements as well as a new alternative route calculation for the flexibility mode. In an ealier blog post we made some simple but yet powerful visualizations based on this. Get it now via maven or the zip package.

Alternative routes for the flexibility mode

A big thanks for this release goes to all of our contributors and translators! To become a contributor see our contributing guidelines and e.g. the good first issues. This release includes features sponsored by Geofabrik and Sidekix. Read here to see how to become a sponsor and how to benefit from our expertise or donate us.

Thanks a lot to all contributors and translators!

Here are the highlights for GraphHopper 0.6:

• alternative route calculation for the flexibility mode, included an updated UI
• speaking of the UI: HelgeKrueger helped us to make it more modular using npm and externalize configuration
• conditional tag parsing (OSM) by boldtrn
• several bug fixes by ratrun and improving of the duration parsing (OSM)
• Furthermore ratrun improved GPX export format as well as the UI
• devemux86 helped to keep the Android demo updated and improved I18N possibilities for street names.
• motorcycle improvements by boldtrn
• enable multiple weights for the speed mode, again by boldtrn
• HarelM made it possible to use elevation data regardless of the resolution
• An updated GraphHopper iOS port by clns
• The map matching component now includes a web API not only a CLI. Let us know if you want to create a nice and simple JavaScript UI based on it 🙂 !
• All changes and necessary refactorings are documented in the changelog and see here for all closed issues and pull requests.

Did you know that there is a new route planner motoroute.me for motorcyclist or new offline route planners based GraphHopper?

Have fun and let us know your requirements!

Discuss here.

Isochrone visualization build with the mini ui. Click to read more about this in a separate blog post.