osmandapp / OsmAnd

OsmAnd
https://osmand.net
Other
4.6k stars 1.01k forks source link

Temporary access restriction ignored #17048

Closed Peter0 closed 1 year ago

Peter0 commented 1 year ago

🐞 routing report

Routing engine

Routing Profile

Car

Start and end points

From 50.73360 7.08573 to 50.73430 7.08827.

Actual and expected routes

When routing with internal car router, a route via node https://www.openstreetmap.org/node/10830758587 is ignoring the temporary restriction on this node. When going from west to east along Endenicher Straße, i.e. against direction of way in OSM data, the router is going through the node.

Is this a regression?

OSMand 4.3.12 shows behaviour as well as OSMand 4.3.8. Therefore I think: No. ## 🌍 Your Environment **OsmAnd Version:**



4.3.12

Device and Android/iOS version: Samsung Galaxy J5. /e/OS equivalent to Android 9 Maps used (online or offline):

scaidermern commented 1 year ago

I think this tag belongs to a way, not to a node. If you add it to a node then probably some additional tag like barrier is required. Looks like a mapping error to me.

Zirochkabila commented 1 year ago

@Peter0 It looks like a mapping error (you can try to build a route in OSM and all three types of routers will build the route). Please make sure the tag is correct

Peter0 commented 1 year ago

Ok. Due to a similar mapping at node https://www.openstreetmap.org/node/10738740754 (that obviously works) I thought that it is ok. Albeit, at that node, there is no "backwards" key. My suggestion, according to "be conservative in what you send, be liberal in what you accept" is to permit it even on nodes. But I see the point that there is no direction, at least not until one take the direction of the underlying way into account.

Peter0 commented 1 year ago

Just recently, I added a way containing the restriction: https://www.openstreetmap.org/way/1165414799 Nevertheless, the router directs me through the blocked road.

scaidermern commented 1 year ago

Can confirm, doesn't work for me either (newest map + live updates, OsmAnd 4.4.7). Maybe vehicle:backward:conditional isn't supported by OsmAnd?

Peter0 commented 1 year ago

Added a oneway tag. Let's see what happens.

xmd5a2 commented 1 year ago

Tag is present on OsmAnd routing data: Road 74586547197 osmid 1165414799 cycleway:both='lane' cycleway:both:lane='advisory' highway='residential' lanes='2' lit='yes' maxspeed='50' oneway:bicycle:conditional='no @ (2023 Apr 11-2023 May 31)' oneway:conditional='yes @ (2023 Apr 11-2023 May 31)' sidewalk:both:surface='paving_stones' smoothness='intermediate' surface='asphalt' vehicle:backward:conditional='no @ (2023 Apr 11-2023 May 31)' osmand_ele_start='59' osmand_ele_end='58' osmand_highway_integrity_brouting='0' sidewalk='yes' name="Endenicher Straße" name:etymology:wikidata="Q153759" pointtypes [[1. vehicle:backward:conditional='no @ (2023 Apr 11-2023 May 31)' 50.73403 / 7.0877237 ]] lat/lon : 50.73403 / 7.0877237 , 50.73401 / 7.087657 ,

xmd5a2 commented 1 year ago

Now routing is correct is all directions (towards west and towards east). Closing.