What are the best practices for mapping an all-way stop intersection? I've seen where the stop is a single shared node for all the ways at the intersection and I've also seen a separate stop for each way usually at the point of the stop sign or crosswalk. I'm wondering primarily about stop signs but do the same rules apply for traffic signals?
asked 30 Aug '21, 00:54 mccarbc |
The stop page on the wiki is rather firm on the mapping of all way stops, although the degree to which mappers agree with the wiki is a little variable. There are supplementary traffic signs tags if you would like to map the sign separately in this instance (same again for stop lines). The various accepted traffic light tagging methods are described here. answered 30 Aug '21, 03:10 InsertUser 2
The section isn't really reasonable on duplicating
(30 Aug '21, 04:56)
Kovoschiz
Where does it recommend duplicate tagging? The all way stop section says don't remove the tag on the intersection and recommends
(30 Aug '21, 11:52)
InsertUser
2
The text is a bit ambigues. I also read it as Kovoschiz: "All-way stops should ALWAYS be shown using highway=stop at the intersection node. If you also want to add the individual stopping points, say for use by a safety app (so that the exact stopping points have been recorded) do NOT remove the intersection node highway=stop, which confirms that this junction is an all-way stop." -> It says not to remove the intersection node but to also add nodes at the stopping points. Here there is no mention of traffic sign so I would assume "If you want to show that the stop line highway=stop nodes are marked with traffic signs, use the traffic_sign=* tag to indicate a physical sign, painted line or an implied stop such as a driveway." -> and here the
(30 Aug '21, 13:03)
TZorn
I also find the stop page to be ambiguous (per Kovoschiz) on the point of keeping the intersecting node A follow-up question regarding how to mark the single intersecting node, I see that the stop page mentions the option of adding
(30 Aug '21, 16:34)
mccarbc
1
I hadn't seen the combination stop=all + direction=both before, so I just went to find some. The cases I found were all three- or four-way intersections. IMO, direction=both makes no semantic sense in this context. "Both" directions implies both forward and backward. When tagged on an intersecting node with three four possible directions, the tag doesn't provide anything useful. The only reason I can think of for using direction=both on a highway=stop is in the middle of a way where both forward and backward directions are required to stop (maybe for a footway crossing), though such a case would probably be better represented by two separate highway=stop each with the correct direction. I would consider it redundant.
(30 Aug '21, 17:23)
alester
|
If you want to map these crosswalks which have no set-back from the intersection and stop line, it's also more logical to represent the answered 30 Aug '21, 05:00 Kovoschiz |