Hi, The second use should not be encouraged IMHO as it is redundant with the direction of the way. Reguarding the third use, you can use either traffic_signals:direction or direction but the first form will explicitly apply to the traffic_signals while the second may apply to different tags of the node. Imagine a node which is tagged as a traffic light (or a stop) and a crossing or a camera. To which one the direction apply if you don't specify it? If the second form is used, then it applies to all tags which may be associated to a direction. This is how I understand and use it. From my understanding stops, give ways and traffic lights can be mapped the same way but editors (JOSM, iD) have implemented presets for those features at different point in time without feeling the need for consistency. I know that iD is currently doing the job of having a consistent behavior for those three features and that they might prefer (traffic_signals|stop|give_way):direction instead of direction (to be confirmed). They are also working to display the direction on the node on the map. LeTopographeFou
The “direction” tag [1] has different uses that seem disjoint to me.
Oddly, that third use seems only for stop and yield signs but not for traffic signals where a “traffic_signals:direction=forward | backward” tag is to be used. However that seems to be the most used form [2]. Apparently some have figured that if we have “traffic_signals:direction” there should be “stop:direction” [3] and “give_way:direction” [4] tags. And other things where a direction like tag might be used, like roof aspect have their own tags (“roof:direction=*”) [5] which follow the syntax and semantics of the first definition of the “direction=*” tag. It seems to me that the first and the third definitions should be split into separate tags with the second definition deprecated. From a data consumer point of view, there may not be a conflict as map rendering is likely to only use the bearing definition while routing would use the forward/backward definition. Though I suppose that a really detailed map may wish to show the actual angle of a stop or yield sign as they are not necessarily exactly aligned with the traveled way. From a mapper’s point of view having totally different meanings for a tag based on context seems confusing. Since the “forward” and “backward” values are most used, it may be reasonable to keep the third definition of that tag even though it is inconsistent with “traffic_signals:direction”. Should we come up with a new tag to replace the angle/aspect meaning of the “direction=*” tag? If so, what tag name would make sense.
Thoughts? | ||
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
