Hi, I found a wierd behaviour of the routing api :
This is the basic use case working fine, with start and arrival on each side on a bridge which has a foot/bike designated pathway.
Now, if I want to add a waypoint on the bridge, the waypoint is moved out of the bridge (the same thing happens with the start or end waypoint)
It seems to be the case on every bridge
Do you have an insight on this case ?
Best regards, Olivier
We recently changed the default values for snap_preventions from an empty list to [bridge, ferry, tunnel] to improve the routing for other cases, especially in the city.
You can submit snap_preventions:[] to fallback to the previous behaviour but I would not recommend it as a default behaviour.
Note, this change was only done for the /route and /matrix endpoint. Not e.g. the /match endpoint.
Thanks for the answer ! Could you please explain the use case fixed with that change ?
Regards, Olivier
Two very common use cases our API is used: for route planning or delivery management. In both cases you never have a stop at on a bridge, tunnel or ferry. E.g. assume you are looking up an address and the closest road is a tunnel like in the following example: GraphHopper Maps | Route Planner without the new snap prevention default the route would be via the “Lamar tunnel”:
There are similar problems when an address is near a bridge.
Ok, thanks for the explanation
