[openstreetmap/openstreetmap-website] Turn on turn restriction support for graphhopper (#2695)

[Andi]

The reason we use `"ch.disable": vehicleType === "car"` is that this way we enforced another/slower algorithm that already supported turn restrictions. However this is broken at the moment because of a GH configuration issue (will be fixed soon) and on openstreetmap.org we get GraphHopper routing *without* turn restrictions support nonetheless.

There are two options:

1) `turn_costs=true&ch.disable=true`: This does not work at the moment but will be fixed soon. It will result in routing that does support turn restrictions but is a bit slower.

2) `turn_costs=true` (remove the `ch.disable` parameter): This already works and results in faster routing than the first option. The only drawback is the longer data update cycle @karussell mentioned.

To avoid confusion in the blog article maybe I should have written that turn costs were already supported before but only for `/route` (not `/matrix`) and only using a slower algorithm.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/2695#issuecomment-655655481
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20200708/7c1f433e/attachment-0001.htm>