You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Routing on foot/bicycle does not appear to handle access=destination properly. Ways marked like that (and no overriding foot=yes or bicycle=yes) seem to be ignored by the router in those modes. In vehicle mode it does appear to handle access=destination properly.
Routing on foot/bicycle does not appear to handle
access=destinationproperly. Ways marked like that (and no overridingfoot=yesorbicycle=yes) seem to be ignored by the router in those modes. In vehicle mode it does appear to handleaccess=destinationproperly.Broken example (foot)
In this example:
Route I
The expected route should use the
highway=footpaththe end-marker is placed on. That way is tagged like this:The way is not used, even though it qualifies.
Broken example (bicycle)
In this example:
Route II
The
highway=cyclewaythat provides the fastest route is tagged like this:No
bicycle=*, soaccess=destinationshould allow the route to end on that way.Working example (car)
In this example:
Route III
The routing properly uses the connected set of way tagged with
access=destination, and uses them if the start or end of the route lies within them.The text was updated successfully, but these errors were encountered: