wrong route offset
Closed this issue · 0 comments
E.g. this route seems to have an offset:
If we would use points_encoded: false
it would be fixed:
The problem is that on the server-side we use a too low precision of 1e5 (the reason for that is that this is the default for the Google polyline algorithm).
This server-side change will improve the situation and this specific example. But best would be a higher precision and as the default cannot be changed on the server-side without breaking other clients it would be nice to have the multiplier
as parameter to avoid loosing this simple but very important compression (roughly 3x smaller than responses with points_encoded=false).
Another example is this route:
But here another cause mixes in (graphhopper/graphhopper#2950)