It is easy. It occurs because OSMAnd incorrectly considers for barrier=bollard node and cars the default access=yes, instead of obviously correct access=no
So as there is no other explicit node access hint, OSMAnd considers that bollard as free to go. It should be fixed in the internal routing.xml, or you can overwrite trhe file temporarily as workaround in the routing.xml <https://raw.githubusercontent.com/osmandapp/OsmAnd-resources/master/routing/routing.xml> downloaded from the OSMAnd GitHub site, placed in OSMAnd data folder. After reviewing the routing.xml file, I have realized bollards as obstacle are addressed in way context only, not in node context. And at the map the bollard is the node. So it is ignored, regarding the access. Note that the crossing OSM ways are not "aware each other", if they do not share the node, like if they were at different levels. Seen often on water ways. Dne 02/01/2017 v 22:12 'P Wat' via Osmand napsal(a): > Thank you CP for supporting my belief that this is an instance of > OsmAnd false routing. > Can anyone who understands OsmAnd algorithms clarify why this occurs? > Can someone explain what can be done about it? > Thanks > Paul W > -- Poutnik ( The Wanderer ) My Brouter profiles https://github.com/poutnikl/Brouter-profiles/wiki -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
