Thanks a lot for add-on.
My PR
https://github.com/asamm/locus-addon-graphhopper/pull/1 to update GH to 0.11.0-pre1 is merged, thanks (updated to 0.10 because it is latest release).
GH vs Brouter:
1) better routes (at least for racing bike).
2) much, much faster. Instant result (of course, if contraction hierarchies (CH) were prepared for routing data).
3) GH is everywhere - Komoot uses GH, Locus uses online GH API. So, you get nearly the same route regardless of online status.
@menion Could you please add note to first topic about recommended (I would say even required) options to build routing data:
```
graph.flag_encoders: bike2,racingbike,mtb,hike
graph.bytes_for_flags: 8
graph.elevation.provider: cgiar
```
(add `car|turn_costs=true` if need car routing)
(`prepare.ch.weightings: fastest` is set by default, should be not set to no)
I shared correct and up to date routing data for Germany+Austria+Switzerland (dach osm map) (keep in mind that GH
doesn't support multiple files, so, if you need to cross borders, you have to use not country routing data, but some merged) —
https://github.com/develar/gh-routing-data/blob/master/README.md#germany-austria-and-switzerlandRoute calculation time is instant even for large distance with prepared CH. But size of routing data... (e.g. shortcuts_fastest_bike2 for DASH 929MB). Maybe a new “
landmark algorithm” is an option, but "Still the speed of contraction hierarchies is ~10 times faster on average". In any case SD card is cheap and modern phones have enough internal space in any case.