<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Just as Bryan does, I can see supporting special casing transit
relations (as we already have to do the same for turn
restrictions). I am -very- reluctant to support one-off tag
semantics that require special code to handle them.</p>
<p>Note with respect to the parallel discussion on tagging
systematics, this kind of thing is multiple orders of magnitude
worse than inconsistencies in tag naming and so on (which at least
from an editor pov can typically handled by configuration in a
preset).</p>
<p>Simon</p>
<br>
<div class="moz-cite-prefix">Am 11.06.2018 um 06:42 schrieb Bryan
Housel:<br>
</div>
<blockquote type="cite"
cite="mid:04EF9861-1301-43F2-A5E8-417C14C88D63@gmail.com">I’ve had
a few recent conversations about this proposal:
<div class=""> <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/transit"
class="" moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/transit</a></div>
<div class=""><br class="">
</div>
<div class="">Unfortunately I can’t support it.</div>
<div class=""><br class="">
</div>
<div class="">Not only is the name bad (it should be named
`transition:lanes` but whatever), the bigger problem is that, as
proposed, the tag can be placed on either a way or a relation.</div>
<div class=""><br class="">
</div>
<div class="">The problem with tagging these on ways is that<i
class=""> if you split the way, the tag breaks</i>. </div>
<div class=""><br class="">
</div>
<div class="">No other tag works this way (except maybe for
address interpolation lines, but presumably anybody splitting
one of those would know that they need to adjust the numbers on
the endpoints). </div>
<div class=""><br class="">
</div>
<div class="">I’m not going to add a special rule in iD to warn
people if they are splitting a way with a lane transition tag.
I don’t want to speak for the JOSM devs, but I doubt they would
implement something like this either.</div>
<div class=""><br class="">
</div>
<div class="">The only way I’ll be able to support lane
transitions would be as a relation that has similar semantics to
turn restrictions.. from/via/to. Keep it simple (no multi via
ways please). This is already an understood way of tagging
things that connect 2 ways. (could you imagine if we tagged
turn restrictions as maybe-a-relation or maybe-a-way-tag ??
nope!)</div>
<div class=""><br class="">
</div>
<div class="">I notice that `transit:lanes` has already been
tagged on around 4000 or so ways, so I thought it would be worth
pointing out that the proposal is Dead on Arrival in it’s
current state. We should rework it before people tag too many
more of these and end up disappointed.</div>
<div class=""><br class="">
</div>
<div class="">thanks, Bryan</div>
<div class=""><br class="">
</div>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
</body>
</html>