<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Two issues here.</span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">First, the tag is not “transit:lanes” the tag is “transit” and it can be used with the generalized “:lanes” suffix.<span class="Apple-converted-space"> </span><o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-family: Calibri, sans-serif; font-size: 11pt;" class="">There are general rules for the :lanes suffix which can be added to pretty much any tag you would have on a highway were the value could be different for different lanes. See</span> <a href="https://wiki.openstreetmap.org/wiki/Lanes" class="" style="font-family: Calibri, sans-serif; font-size: 11pt; color: purple;">https://wiki.openstreetmap.org/wiki/Lanes</a></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-family: Calibri, sans-serif; font-size: 11pt;" class="">It’s the same with e.g. “turn:lanes” (a “turn” key with the “:lanes” suffix) or “access:lanes” (a “access” key with the “:lanes” suffix).</span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""></span></div></div></blockquote><div><br class=""></div><div>.. none of this matters because the tag can’t go on a way anyhow.</div><div><br class=""></div><div><br class=""></div><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Second, the “transition” tag is already in use:<span class="Apple-converted-space"> </span><a href="https://taginfo.openstreetmap.org/keys/transition" style="color: purple; text-decoration: underline;" class="">https://taginfo.openstreetmap.org/keys/transition</a></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">Now, as far as I can tell, these are pretty much all transition=yes tags on power=tower or power=pole nodes. These seem to be left-overs from a previous tagging scheme, which has been replaced by the use of the location:transition=yes tag (and at 342 vs 13388 uses that seems to have been well accepted by now).</span><span style="font-family: Calibri, sans-serif; font-size: 11pt;" class=""> </span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">So I guess it might be possible to coordinated with people that are involved in power mapping to have these remaining ones retagged to free up the transition key.</span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">The type=transition value is currently unused, so in that regard the change would be fine.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""></span></div></div></blockquote><div><br class=""></div><div>Ok, so add a new type of relation and call it `type=lane_transition`</div><div><a href="https://wiki.openstreetmap.org/wiki/Types_of_relation" class="">https://wiki.openstreetmap.org/wiki/Types_of_relation</a></div><div><br class=""></div><div><br class=""></div><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 12pt;" class="">I agree that this tag when used on ways is problematic from an editor perspective.</span> </div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">Though by following pretty simple rules, the editor could prevent the transit(ion):lanes tag on a way from breaking:<o:p class=""></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""></div></div></blockquote><div><br class=""></div><div>Maybe seems simple to you, but I’m not going to do it, and the JOSM and Vespucci folks have also already said no too. </div><div><br class=""></div><div><br class=""></div><blockquote type="cite" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">Transit relations have no via, and they don’t need a via. The from and to way should always touch at exactly one node. Otherwise they are invalid. So you can always determine the “implicit” via node from that.</div></div></blockquote><br class=""></div><div><br class=""></div><div>I’ve already written plenty of code to deal with turn restrictions. There are lots of rules for splitting and joining things to other things depending on where the via node is. </div><div><br class=""></div><div>If you are curious, here is a recent commit where I tried to improve iD’s handling of this.</div><div><a href="https://github.com/openstreetmap/iD/commit/87841fc4035c7de9e0f58ca50f05f65723ad5226" class="">https://github.com/openstreetmap/iD/commit/87841fc4035c7de9e0f58ca50f05f65723ad5226</a></div><div><br class=""></div><div>In other words if this new relation works like a turn restriction, it’s already mostly supported… Otherwise expect basic editing (like splits, joins, connections) to break it.</div><div><br class=""></div><div>Thanks, Bryan</div><div><br class=""></div><div><br class=""></div></body></html>