Stewart Andreason <[email protected]> writes: > I am positive GPS was locked on, over 20 sats in view, this device is the > most accurate one I've seen, it doesn't lose lock or wander like a couple > others I've tried, and the other app recording data points has good gps > data.
hmm, well that's probably not it. > I acknowledge there is a possibility it made the second announcement > because of a second tag, because there is one barrier for each one-way > path. Perhaps I should delete one of the 2 tags, and move it to the > building between the roads? No, the barrier tag belongs on a node in the way; passing near a barrier is not passing the barrier. The point is not that there is a building, but that when using the road one has to stop. My main point is that it is not ok to change osm tagging to make osmand happy. One has to understand established tagging consensus and follow that, and then if osmand is doing things wrong file a bug with osmand. There are many other consumers of OSM data. Have you tried reading the osmand source code to understand what it is doing? It could be that it alerts ahead of time and then at the time of crossing the node. But it doesn't do that for stop signs, I think. -- 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.
signature.asc
Description: PGP signature
