<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">I agree. Sometimes the name tag
containes just something like "Red Route" or "Rundweg" and there
is nothing available that could be added as "ref", "from", "to" or
"via".<br>
<br>
"personalized adaptable template" sounds quite complicated to me.
Why not propose to add something to this new iD functionality so
that it shows the value of another tag when there is no "name",
"ref", "from", "to" or "via" tag present? Perhaps "name:informal"
or something else. Then every case could be handled without
"abusing" the name tag.<br>
<br>
On 01.07.2021 09:37, Peter Elderson wrote:<br>
</div>
<blockquote
cite="mid:CAKf=P+vfEbWSyzeAmtccZoDZ5GMUkRB9v-=VaPdSo-XQoqx4GA@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">Looks good!
<div>I think for recreational routes (for hiking, cycling,
horse riding, skiing, paddling, motorboat, skating), it is
also an improvement, but these are much more varied in
labeling than PT and road routes. Especially when
considering heavily sectioned routes; hierarchically ordered
routes; two-directional routes where the two directions are
in one route relation; node network routes using numbered,
coded and named nodes as start/end points which are
reflected in the labeling of the routes; and combinations of
these types. </div>
<div>Even when not considering 'pretty print'-wishes, it would
be very hard to design a single labeling format that
contains all the elements that mappers have stacked into
(combinations of) the name, ref, note, network, description
and other tags of the recreational route relations. </div>
<div><br>
</div>
<div>So, well done and it is an improvement, but, while it
does apply to all routes, I would not say it solves the
labeling problem for all routes, especially
considering current tagging practices.</div>
<div><br>
</div>
<div>At the moment, I think only a personalized adaptable
template, allowing free placement of text, punctuation and
data elements in one display string, would solve the route
labeling issue for all routes.</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Peter Elderson</div>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</body>
</html>