We are proud to release version 0.8 of our open source
GraphHopper routing engine! Here is the polished snap-to-road feature in two screenshots:
A big thanks goes to all of our contributors and translators!
To become a contributor see our
contributing guidelines and e.g. the good first issues. Read here to see how to become a sponsor and how to benefit from our expertise or donate us. Here are the highlights for GraphHopper 0.8:
new map matching algorithm based on hidden markov chains is finally integrated and gives us a big quality improvement, thanks to @michaz (GraphHopper) and @stefanholder (BMW Car IT). This feature was already deployed 2 months ago in our GraphHopper Directions API. Some improvements were done by @kodonnell. the osm import module is split from the core #
450 making Android and iOS integration cleaner there is a new overlay module #
781 allowing you to specify GeoJSON at import time to change properties like access and speed of the routing graph new ‘more standard’ code formatting for all repositories #
many UI fixes like upgrading to leaflet 1.0, thanks to @fbonzon ( Bikewithme) updated
the iOS port, thanks to Calin @clns travis build enhancements like running against jdk9 and deploying snapshots #
806, thanks to @mprins a new ‘on-demand’ weighting with a new data encoder #
730 elevation interpolation in tunnels&bridges #
713, thanks to @highsource (DB Systel) fixing time calculation for turn costs #
393 a new short_fastest weighting #
747 Several updates to Android build/sample from
@devemux86 ( talent) several bug fixes (incl. three major)
The changelog is
here – please read about the necessary changes to your config.properties and/or your Java code. Dowload the new version here. As the documentation has slightly improved we’d like your input here as well.
In the next release we expect bigger changes to come like one top secret 😉 and
this exciting work from @devemux86 which continues the work from VTM ( OpenScienceMap) and has OpenGL support, allows map rotation, iOS support and more, while keeping compatibility with the Mapsforge file format.
And if you like OpenStreetMap as we do, consider
supporting them via money.