Closed schenklklopfer closed 1 month ago
The bug has been reproduced. To reproduce this issue, choose the bicycle profile and attempt to create a route using the provided coordinates. Instead of following the bicycle path, the route takes a detour.
You can view this in the web version here.
Web version | OSM |
---|---|
Fixed. Penalties for traffic signals were slightly lowered. No new maps required.
now OsmAnd web routing is the same as on OSM
andoird | ios balanced | ios shortest routes |
---|---|---|
Describe the routing engine used (required)
Describe your routing Profile (required)
Routing Profile: bike, no restrictions
Describe your start and end points (required)
https://osmand.net/map/navigate/?start=48.370671,10.901020&end=48.369521,10.892373&profile=bicycle#17/48.37050/10.89544
I just want to cycle up the road. There is a nice cycleway on the whole road, but OSMand is planning a massive detour.
Describe the actual route (required)
Both the app and https://osmand.net/map planes a detour here![image](https://github.com/osmandapp/OsmAnd/assets/6595165/dc8e7ca6-1fd8-46ec-95d3-b0bffe7b2ce6)
![image](https://github.com/osmandapp/OsmAnd/assets/6595165/65bed8ee-a4d3-4618-b240-bb72874910ee)
Describe the expected route (required)
Route as the official openstreetmap.org page route, in all three engines:![image](https://github.com/osmandapp/OsmAnd/assets/6595165/1799f07f-120e-408f-83d8-9cb20903dad5)
https://www.openstreetmap.org/directions?engine=graphhopper_bicycle&route=48.37065%2C10.90094%3B48.36982%2C10.89318#map=18/48.37027/10.89709 https://www.openstreetmap.org/directions?engine=fossgis_valhalla_bicycle&route=48.37065%2C10.90094%3B48.36982%2C10.89318#map=18/48.37027/10.89712 https://www.openstreetmap.org/directions?engine=fossgis_osrm_bike&route=48.37065%2C10.90094%3B48.36982%2C10.89318#map=18/48.37030/10.89706
Describe what Maps you used (online or offline) (required)
Your Environment (required)
Anything else? (optional)
If I choose a more direct startpoint the routing is correct!
![image](https://github.com/osmandapp/OsmAnd/assets/6595165/258f9495-405c-4910-9610-3bdaa181a88d)
https://osmand.net/map/navigate/?start=48.370539,10.897890&end=48.369521,10.892373&profile=bicycle#18/48.36999/10.89403
I think this is related to a bus stop. This bus stop is directly on the cycleway. This is correctly mapped in OSM data with "cycleway:both=share_busway": https://www.openstreetmap.org/way/589530816
This Tag is correctly recognized in OSM, support has been added here: https://github.com/osmandapp/OsmAnd-resources/pull/861
So maybe this is an issue with "priority" of this Tag?
If the way is short and direct enough the way is used, if it is longer a detour is planned.