[Tagging] Feature Proposal - Voting - Tagging for complex junctions or traffic signals that are named

[Lukas Sommer]

Oh, sorry, Pieren was faster… ;-)

Lukas Sommer

2014-09-30 12:34 GMT+00:00 Lukas Sommer <sommerluk at gmail.com>:

> > If there is a need to tag traffic signal names and junction names on the
> same node, then the logical solution is junction:name=* and
> traffic_signals:name=*. Or in different languages: junction:name:th=* and
> traffic_signals:name:kr=*.
>
> Different names for junction and traffic signal are probably not a
> real-world case.
>
> Lukas Sommer
>
> 2014-09-30 12:21 GMT+00:00 Janko Mihelić <janjko at gmail.com>:
>
>> 2014-09-29 23:45 GMT+02:00 Lukas Sommer <sommerluk at gmail.com>:
>>
>>> The case of Japan is different. In Japan, the name belongs to the
>>> _traffic signal_, and _not_ to the junction. We need to distinguish this,
>>> because they are usually differently rendered (traffic signal names usually
>>> with an icon and junction names usually without an icon).
>>>
>>> But what would we gain when we distinguish between th:junction_area and
>>> kr:junction_area - because here we have two values for the same feature.
>>>
>>
>> If there is a need to tag traffic signal names and junction names on the
>> same node, then the logical solution is junction:name=* and
>> traffic_signals:name=*. Or in different languages: junction:name:th=* and
>> traffic_signals:name:kr=*.
>>
>>
>>
>> _______________________________________________
>> Tagging mailing list
>> Tagging at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/tagging
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20140930/50e84df3/attachment.html>