<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
I'll start with the conclusion:<br>
The problem is in your software. Code needs to added to ignore any
relations members with link roles.<br>
<br>
<div class="moz-cite-prefix">On 13/01/2022 19:49, Zeke Farwell
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAH-nfWNrBfMo7YNHdrHKRhJbrynE5Gaq9C8vMf6rK8y4kWozDA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Thu, Jan 13, 2022 at 2:15 PM Dave F <<a
href="mailto:davefoxfac63@btinternet.com"
moz-do-not-send="true" class="moz-txt-link-freetext">davefoxfac63@btinternet.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div> I'm well aware of route relations, of all types, but
what have these to do with 'destination:ref*' tags on
/ways/?<br>
<br>
How does routing software, which "lacks support for the
'role' tag" of route relations "cause problems for any
editor, QA tool, or data consumer"? It makes no logical
sense. (quotes from Minh's original post)<br>
</div>
</blockquote>
<div><br>
</div>
<div>We're just trying to determine if there is a reasonable
use case for the link role in a road route relation. The
only reason destination:ref is part of the discussion is
because the only use case we've been able to think of for
the link role is already handled by destination:ref. <br>
</div>
</div>
</div>
</blockquote>
<br>
Already handled? How long has it been in existence? Before 'link'
roles?<br>
<br>
<blockquote type="cite"
cite="mid:CAH-nfWNrBfMo7YNHdrHKRhJbrynE5Gaq9C8vMf6rK8y4kWozDA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><a href="https://wiki.openstreetmap.org/wiki/Role:link"
moz-do-not-send="true"><br>
</a></div>
<div><a href="https://wiki.openstreetmap.org/wiki/Role:link"
moz-do-not-send="true">The wiki defines 'role=link'</a>
as:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Link roads
(highway=*_link) from and to the route. See <tt dir="ltr"
class="gmail-mw-content-ltr"
style="background:rgb(238,238,255) none repeat scroll 0%
0%;font-size:1em;line-height:1.6"><a
href="https://wiki.openstreetmap.org/wiki/Key:highway"
title="Key:highway" moz-do-not-send="true">highway</a>=<a
href="https://wiki.openstreetmap.org/wiki/Tag:highway%3Dmotorway_link"
title="Tag:highway=motorway link"
moz-do-not-send="true">motorway_link</a></tt>.
<br>
</blockquote>
<div><br>
</div>
<div>Mappers are following this documentation and including
on/off ramps in route relations with role=link. In most
cases, an on ramp leading to a numbered route is generally
not considered part of that route. To indicate which
route it leads to, they way gets tagged with
destination:ref.</div>
</div>
</div>
</div>
</blockquote>
<br>
You're using destination:ref to indicate what's written on a sign,
That's fine for adding niceties to routing software, but not for
defining directions of a route.relation. You've added
destination:ref to ways, suggesting it applies to all traffic using
that way: 'To Dayton' etc., but as I've said previously, *multiple*
route relations can be added to that way - <br>
<br>
Not all of them will have Dayton as their destination. <br>
A way that could have a link role in one route relation, indicating
access to a route relation, could be a middle section of another
route relation.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAH-nfWNrBfMo7YNHdrHKRhJbrynE5Gaq9C8vMf6rK8y4kWozDA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>
<div> So also including it in the route relation with the
link role doesn't seem to add any information. Given this
we're thinking it makes sense to remove this suggestion
from the wiki.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
It may not specifically to you in your specific case, but it doesn't
mean it irrelevant to others. If you literally ignore it, your
problem goes away.<br>
<br>
DaveF<br>
</body>
</html>