<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 22, 2017, at 4:51 PM, yo paseopor <<a href="mailto:yopaseopor@gmail.com" class="">yopaseopor@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Anyone else with an opinion ? Two of us might be the very beginning of a<br class="">
consensus but we need a little more before even putting a proposal<br class="">
page up on the wiki...<br class=""></blockquote><div class=""><br class=""></div><div class="">I think to include direction inside the tag with a subkey :forward :backward following the scheme for lanes and so one are the best option instead of using a specific key as direction because we save one key, and we follow a well-known scheme.</div><div class="">Other thing is the side of the road the traffic sign is , as it changes the form and the style of it (motorway panel vs. little traffic sign on the right side of a road)</div><div class=""><br class=""></div></div></div></div></div></blockquote><br class=""></div><div>“stop:forward=yes” & “stop:backward=yes” seem like they are putting a value in the key as the stuff to the right of the equals may never be anything other than “yes”. On the “lanes:forward” and “lanes:backward” keys at least the values carry variable values.</div><div><br class=""></div><div>There is already a “traffic_signals:direction=forward | backward” usage. “stop:direction= forward | backward” and “give_way=forward | backward” would fit that schema too.</div><div><br class=""></div><div></div><blockquote type="cite" class=""><div><div class="">On Mar 22, 2017, at 4:57 PM, Martin Koppenhoefer <<a href="mailto:dieterdreist@gmail.com" class="">dieterdreist@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">generally it is unsafe to rely on a "direction" like forward or backward as tag on a node. Nodes do not have directions, and there is no relation from a node to a single way, the relation is from a way to a node and many ways can reference the same node, that's not an error. Will it become forbidden to split ways on nodes with stop sign or traffic signal tags, because it breaks the information tagged on those nodes?<br class=""></div></div></div></div></div></blockquote><br class=""><div class="">Good point. Although one might suggest that it is a theoretical situation as the definition of the stop tag [1] indicates that if on the node connecting multiple then it is a all way stop. And if not on an intersection node then it should be placed at the stop line. [2] I don’t think we are likely to have a stop line in the middle of an intersection. :)</div><div class=""><br class=""></div><div class="">[1] <a href="https://wiki.openstreetmap.org/wiki/Tag:highway%3Dstop#All-way_stop" class="">https://wiki.openstreetmap.org/wiki/Tag:highway%3Dstop#All-way_stop</a></div><div class="">[2] <a href="https://wiki.openstreetmap.org/wiki/Tag:highway%3Dstop#Tagging_minor_road_stops" class="">https://wiki.openstreetmap.org/wiki/Tag:highway%3Dstop#Tagging_minor_road_stops</a></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>