<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 20/10/23 10:32, Paul Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMPM96odmBiFYzvmvs6p85aX_wJBDghkdwaRTmcFfzqjFcxHOg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Oct 18, 2023 at
2:31 AM Warin <<a href="mailto:61sundowner@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">61sundowner@gmail.com</a>>
wrote:<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>
<p><br>
</p>
<div>On 17/10/23 23:22, Paul Johnson wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Oct 17,
2023 at 4:51 AM Warin <<a
href="mailto:61sundowner@gmail.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">61sundowner@gmail.com</a>>
wrote:<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>
<p><br>
</p>
<div>On 17/10/23 04:17, Paul Johnson wrote:<br>
</div>
<blockquote type="cite">
<div dir="auto">Presently, it's common for
route relations to have names that violate
"name is only the name" and "name is not
ref" and "name is not description" rules for
name=* tags. <br>
</div>
</blockquote>
<p><br>
</p>
<p>I don't find it common in 'my area' of
mapping. One or two examples would demonstrate
the situation? <br>
</p>
<p><br>
</p>
<p>In any case:<br>
</p>
<p>The name tag is used on may things for
example; buildings, parks, schools, highways
... </p>
<p>The use of the name tag as 'name only'
applies where ever the name tag is used. This
is similar for other tags such as elevation,
width, colour etc. No matter what feature they
are used on the tags carry the same
characteristics and restrictions. It is not
necessary to repeat these characteristics and
restrictions for every main feature. <br>
</p>
</div>
</blockquote>
<div>Routes have names, too! For example, here's
the relation for OK 51, named for the name of the
route. <a
href="https://www.openstreetmap.org/relation/3108562" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.openstreetmap.org/relation/3108562</a></div>
<div><br>
</div>
<div>Meanwhile, I 40 in Arkansas has a good example
of a name that is actually a ref and a
description, not a name. <a
href="https://www.openstreetmap.org/relation/6843700" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.openstreetmap.org/relation/6843700</a></div>
<div><br>
</div>
<div> Finally, OK 19 is an example of a properly
described no-name route. <a
href="https://www.openstreetmap.org/relation/7479405" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.openstreetmap.org/relation/7479405</a></div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>Ok. I still don't see a necessity of repeating the name
tag information inside the relation tag... Will you also
repeat the ref tag information, the description tag
information? How about the surface tag, maxspeed tag etc
etc.. <br>
</p>
</div>
</blockquote>
<div>The name of the route has nothing to do with the name of
the member ways. <br>
</div>
</div>
</div>
<br>
</blockquote>
<p><br>
</p>
<p>Confusing is probably the issue here? <br>
</p>
<p>I am taking of 'the name tag' possibly I should have said the
'OSM key name' .. <a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Key:name">https://wiki.openstreetmap.org/wiki/Key:name</a></p>
<p>Not taking of any individual feature with a 'name tag'. <br>
</p>
<p><br>
</p>
</body>
</html>