[Tagging] noexit=yes on ways ?

fly lowflight66 at googlemail.com
Tue Apr 8 10:57:44 UTC 2014


On 08.04.2014 12:10, Pieren wrote:
> On Sun, Apr 6, 2014 at 3:48 AM, fly <lowflight66 at googlemail.com> wrote:

>> noexit=yes has nothing in common with the traffic_sign as:
>>
>> 1. it only is about motorized traffic where noexit=yes is about every
>> travel mode.
>> 2. it is used at the beginning of a cul-de-sac and an information for
>> driver of motorized vehicles where noexit=yes is always tagged on the
>> end node of a way without any connection and is a hint for mappers and
>> QA tools.
>>
>> Please, do not mix it up.
> 
> Please, return to earth. Tagging traffic signs is just a funny
> activity in fully mapped areas. How do you specify a speed limit in
> OSM ? with a "traffic_sign" tag on a node or primarily with the
> "maxspeed" on the way ? I could repeat the same question for many
> other features.

Do not know if you speak german, but one person did tell us that she/he
is mapping the traffic_signs as addition one the ways on talk-de at osm [1].

> I'm still waiting some clear explanation about the difference of a
> "noexit" and a "cul-de-sac".

You find quite some differences, if you read the mails carefully.

The major points in my view are:
* We do not need to tag cul-de-sac as defined by the traffic_sign. This
information is available through geometry and/or access tags.
* The traffic_sign is always about motorized vehicles but we map for all
traffic modes. noexit=yes is wrong as soon as there is any connected
highway.

One way to manifest the difference is to only tag it on nodes and not on
ways.

> Once you understand there is no
> difference, you understand why 40% of the noexit tags are on ways ....
> When you have this huge gap between the wiki definition limiting the
> tag on the last node and the real contributors behaviour, you should
> ask if the wiki makes sense but not blaim the contributors.

No one did blame anyone. I only tried to find the reasons for this
misunderstanding and one was definitely the wiki page which is still not
perfect but did get some updates the last days. Some other pages where
updated, too.

> Note that for QA tools, the tag on the last node or on the way itself
> are both technically easy to support.

Sure, but overall it makes it more difficult and how should this work
with splitting ways ? Could you please point me to one editor which
properly works with splitting a way tagged with noexit=yes or don't you
think that it is wrong that after the split both parts are tagged with it ?

We could simply deprecate noexit=* and replace it with note=noexit but I
am not sure if this solves our problem and tools need to support strings
and multivalues as noexit might not be the only word of the note=* tag.


fly

[1] https://lists.openstreetmap.org/pipermail/talk-de/2014-April/107967.html



More information about the Tagging mailing list