<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
I think this inconsistency is bad for OSM.<br>
<br>
Many ways don't have names, even if they have routes along them.
They are just footpaths, & tracks etc.<br>
<br>
This instance on giving them a name tag is fake. It'll mean sections
with one route will have their name tag rendered, but where
additions routes join there will be no rendering. <br>
<br>
If multiple routes are of equal standing, but you insist on adding a
name tag to the way, how do you decide which takes precedent? <br>
<br>
This thread reinforces my belief there's a lack of understand of
route relations' purpose.<br>
<br>
DaveF<br>
<br>
<div class="moz-cite-prefix">On 30/12/2022 19:15, Yves wrote:<br>
</div>
<blockquote type="cite"
cite="mid:31E4558B-2F88-4E8A-9D00-BF89BE5955DE@mailbox.org">
Remove the name of the way, put a name on each relations. Except
if it makes sense to keep the name also on the way for whatever
reason you see fit. <br>
<br>
<div class="gmail_quote">Le 30 décembre 2022 18:06:12 GMT+01:00,
Dave F via Tagging <a class="moz-txt-link-rfc2396E" href="mailto:tagging@openstreetmap.org"><tagging@openstreetmap.org></a> a écrit :
<blockquote class="gmail_quote"> What do you do if there are two
routes?<br>
<br>
DaveF<br>
<br>
<div class="moz-cite-prefix">On 30/12/2022 02:19, brad wrote:<br>
</div>
<blockquote type="cite"
cite="mid:72a3bad5-a35c-b772-884f-508809ee6f22@fastmail.com">
+1<br>
If the only name is the route name I think it makes good
sense to put it on the local way too, that's the name of the
trail.<br>
<br>
Brad<br>
<br>
<div class="moz-cite-prefix">On 12/29/22 08:59, Zeke Farwell
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAH-nfWOOTLOA_u3=w5nfjA-oYss1sXMmtDLRBzVvsQpdYjmf2g@mail.gmail.com">
<div dir="ltr">
<div>I've heard the assertion that a way has no name but
the route that passes over it does many times. While
this is true in some cases, in others it is not.
Where the primary purpose of the way is not for the
route, this does make sense. For example mentioned by
Jmapb where the Appalachian trail follows an unnamed
driveway or sidewalk. In these cases, the primary
purpose is a driveway or sidewalk for local use, and
the Appalachian Trail just happens to follow it as
well. Here putting the name Appalachian Trail on the
way makes no sense. However, there are also dedicated
sections of trail built first and foremost to be a
part of the Appalachian Trail and that have no other
name. Omitting the name Appalachian Trail in a case
like that makes no sense to me. That section of trail
is indeed called the Appalachian Trail. The whole
route is also called the Appalachian Trail and that's
ok. <br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Dec 29, 2022
at 10:38 AM Jmapb <<a href="mailto:jmapb@gmx.com"
class="moz-txt-link-freetext" moz-do-not-send="true">jmapb@gmx.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">
<div>
<div>On 12/29/2022 10:13 AM, Zeke Farwell wrote:<br>
</div>
<blockquote type="cite">
<div class="gmail_quote">
<div>Yes, the way name tag should be the most
local trail name. However, sometimes there is
no local trail name and the long distance
route name is the only name. In this case
putting the long distance route name on the
ways also makes sense.</div>
</div>
</blockquote>
<p>I've been doing some mapping on the Appalachian
Trail lately and this appears to be the common
practice, although the AT is dominant enough that
constituent trails sometimes lose their local
names over time.</p>
<p>Some mappers will take it a little too far and
tag sections of sidewalk and driveway that the AT
follows with name=Appalachian Trail (or even
name=Appalachian National Scenic Trail... IMO this
is an official_name, and probably only belongs on
the route superrelation.)</p>
<p>It's common to see ref=AT as well, which is fine
on trails (even locally named ones) and perhaps ok
on the sidewalks, but adding it to a vehicular
road seems iffy.</p>
<p>Jason<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org"
target="_blank" class="moz-txt-link-freetext"
moz-do-not-send="true">Tagging@openstreetmap.org</a><br>
<a
href="https://lists.openstreetmap.org/listinfo/tagging"
rel="noreferrer" target="_blank"
class="moz-txt-link-freetext" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:Tagging@openstreetmap.org" moz-do-not-send="true">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:Tagging@openstreetmap.org" moz-do-not-send="true">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>