<div dir="ltr"><div>Name tag of recreational routes usually contain lots of information to make them sortable and presentable for the end user. Theis information does not belong in a proper name tag, but I can see why people do it, because maintenance and presentation are unmanageable if there is no alternative.</div><div><br></div><div>I have started to use the from and to tags, at the same time removing this information from the name. I still ran into some difficulties with applications not supporting this, and not going to, because "the information is always in the name tag". Data users supporting from and to will keep on supporting the name tags with extra information, because they need to be backwards compatible. So now I tag from and to, but leave the name as it is. It's a bit of a chicken and egg problem.</div><div><br></div><div>In section relations of longer routes, I have removed the from and to information from section names after adding the from and to tags. This seems to work out fine. No comments received at all. I did leave the section numbers in the name tag, because applications usually sort the sections by name. I use section_ref=* in section relations for section numbers, but this is not supported nor approved, and it has the disadvantage that, if a section relation is used in multiple (super)routes, it probably has a different section number in each (super)route. Not a big problem, though. Tolerating section numbers in the name as an exception to the "name is only the name as it appears on the signs" rule. I support the rule, but until an alternative is present I don't think it is a big deal.</div><div><br></div><div>I have never encountered the idea that from and to indicate a mandatory direction, just a main direction, because operators usually indicate a main direction for maintenance and presentation purposes, while supporting both directions on the ground. For node network routes I do not use from and to tags though. These are bidirectional, no preference, unless explicitly stated otherwise, so from and to tags would suggest a main direction that doesn't exist at all. </div><div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Fr gr Peter Elderson</div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op zo 27 jun. 2021 om 11:36 schreef Warin <<a href="mailto:61sundowner@gmail.com">61sundowner@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>An alternative is to use the
description key. <br>
</div>
<div>Possibly do both, some renders may use
the description key. </div>
<div>Some may view the from/to as being a
mandatory direction that is not true for most hiking routes. <br>
</div>
<div><br>
</div>
<div>On 26/6/21 7:43 pm, Mateusz Konieczny
via Tagging wrote:<br>
</div>
<blockquote type="cite">
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Jun 25, 2021, 22:24 by <a href="mailto:ml@osm.datendelphin.net" target="_blank">ml@osm.datendelphin.net</a>:<br>
</div>
<blockquote style="border-left:1px solid rgb(147,163,184);padding-left:10px;margin-left:5px">
<div>But knowing the start and end of each segment (which was
used as the<br>
</div>
<div>name) helps maintaining the hiking network. So the change
will add the<br>
</div>
<div>from=* and to=* tags to the Swiss wiki page to map the
start and end<br>
</div>
<div>place. That way, the name tag does not get misused, and the
data is<br>
</div>
<div>still there for mappers to use for maintenance.<br>
</div>
</blockquote>
<div dir="auto">Seems good alternative to using fictional name as
form of <br>
</div>
<div dir="auto">mistagging for the renderer.<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Once such tags become clearly used it may make
sense to propose<br>
</div>
<div dir="auto">supporting them in JOSM, iD, Vespucci etc in
relation listings<br>
</div>
<div dir="auto">(if name tag is missing then show "{from} - {to}
hiking route" in<br>
</div>
<div dir="auto">the name field)<br>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Tagging mailing list
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<p><br>
</p>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>