Sorry, I may have missed part of this endless discussion.
But how do I tag a dead-end sign on a road
(e.g. http://commons.wikimedia.org/wiki/File:Zeichen_357.svg).
These signs exist in various forms in various countries, and they are
placed at the beginning of the road or stretch of roads which don
> Am 31/mag/2014 um 10:06 schrieb Volker Schmidt :
>
> But how do I tag a dead-end sign on a road
> (e.g. http://commons.wikimedia.org/wiki/File:Zeichen_357.svg).
you'd tag it best on a node with traffic_sign=* (e.g. dead_end)
cheers,
Martin___
Tag
This is not so obvious, because it has to be directional (for the router).
If you start your route in such a dead-end street you never get out, if
it's not directional.
The noexit=yes on the way to me seems much simpler and intuitive.
(I used the tag initially in this way, when I started with OSM.
What does the router have to do with the traffic sign? What information
does it get from it that can not be easier got from the topology?
André
On Sat, May 31, 2014 at 12:46 PM, Volker Schmidt wrote:
> This is not so obvious, because it has to be directional (for the router).
> If you start yo
Am 5/31/14 12:46 , schrieb Volker Schmidt:
This is not so obvious, because it has to be directional (for the router).
If you start your route in such a dead-end street you never get out, if
it's not directional.
The noexit=yes on the way to me seems much simpler and intuitive.
(I used the tag ini
Any decent router will totally ignore a noexit=yes tag as it determines the
topology from the actual ways and how they are connected.
The noexit=yes tag serves only one purpose and has two different "data
consumers": the next human mapper that comes along and automated QA tools. It
allows those
"The noexit=yes tag serves only one purpose and has two different "data
consumers": the next human mapper that comes along and automated QA tools.
It allows those two data consumers to know that a way that ends close to
another way but is not connected to it is not a mistake. For that purpose
it sh
