<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Thank you Michael! Saves me from doing
it.. it is on my list of 'things that should be done' .. quite a
long list. <br>
<br>
On 06/12/19 21:15, Michael Behrens wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGkbqG1fqky-n25jPkAbdGiN5XLdm2KpFOcMuqZavy86Kpx2Qg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr"><a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/hiking_trail_relation_roles"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/hiking_trail_relation_roles</a>
<div><br>
</div>
<div><br>
</div>
<div><span style="font-family:sans-serif;font-size:14px">There
is no unique way to tag roles in hiking route relations
although they carry a high potential for the rendering of
hiking trails. This proposal was requsted by Sarah Hoffmann
on the FOSSGIS conference. A only officially marked trails
should be added to the relations!</span></div>
<div><span style="font-family:sans-serif;font-size:14px"><br>
</span></div>
<div>
<table class="gmail-wikitable"
style="font-size:13.3px;background:rgb(249,249,249);margin:1em
0px;border:1px solid
rgb(170,170,170);border-collapse:collapse;font-family:sans-serif">
<tbody>
<tr>
<th style="border:1px solid
rgb(170,170,170);padding:4px;background-color:rgb(233,233,233);text-align:center">Role
name</th>
<th style="border:1px solid
rgb(170,170,170);padding:4px;background-color:rgb(233,233,233);text-align:center">Explaination</th>
</tr>
<tr>
<td style="border:1px solid
rgb(170,170,170);padding:4px"><i>None</i> or <code
style="font-family:monospace,monospace;color:rgb(0,0,0);background-color:rgb(248,249,250);border:1px
solid rgb(234,236,240);border-radius:2px;padding:1px
4px">main</code></td>
<td style="border:1px solid
rgb(170,170,170);padding:4px">The main "normal"
roletype for the main section of the hiking trails.</td>
</tr>
<tr>
<td style="border:1px solid
rgb(170,170,170);padding:4px"><code
style="font-family:monospace,monospace;color:rgb(0,0,0);background-color:rgb(248,249,250);border:1px
solid rgb(234,236,240);border-radius:2px;padding:1px
4px">forward</code></td>
<td style="border:1px solid
rgb(170,170,170);padding:4px">Section of the hiking
trail that can only be hiked into the direction of the
way.</td>
</tr>
<tr>
<td style="border:1px solid
rgb(170,170,170);padding:4px"><code
style="font-family:monospace,monospace;color:rgb(0,0,0);background-color:rgb(248,249,250);border:1px
solid rgb(234,236,240);border-radius:2px;padding:1px
4px">backward</code></td>
<td style="border:1px solid
rgb(170,170,170);padding:4px">Section of the hiking
trail that can only be hiked against the direction of
the way.</td>
</tr>
<tr>
<td style="border:1px solid
rgb(170,170,170);padding:4px"><code
style="font-family:monospace,monospace;color:rgb(0,0,0);background-color:rgb(248,249,250);border:1px
solid rgb(234,236,240);border-radius:2px;padding:1px
4px">alternative</code> or <code
style="font-family:monospace,monospace;color:rgb(0,0,0);background-color:rgb(248,249,250);border:1px
solid rgb(234,236,240);border-radius:2px;padding:1px
4px">alternate</code></td>
<td style="border:1px solid
rgb(170,170,170);padding:4px">Tags the members of an
alternative path to <i>main</i> path.</td>
</tr>
<tr>
<td style="border:1px solid
rgb(170,170,170);padding:4px"><code
style="font-family:monospace,monospace;color:rgb(0,0,0);background-color:rgb(248,249,250);border:1px
solid rgb(234,236,240);border-radius:2px;padding:1px
4px">excursion</code></td>
<td style="border:1px solid
rgb(170,170,170);padding:4px">Can be used on parts of
the trail that leads to a viewpoint, peak or other.
The path has to be hiked back again or else it will be
a <i>alternative</i>.</td>
</tr>
<tr>
<td style="border:1px solid
rgb(170,170,170);padding:4px"><code
style="font-family:monospace,monospace;color:rgb(0,0,0);background-color:rgb(248,249,250);border:1px
solid rgb(234,236,240);border-radius:2px;padding:1px
4px">approach</code></td>
<td style="border:1px solid
rgb(170,170,170);padding:4px">A path that is leading
from a town, train station / bus station or parking to
main hiking trail or the other way around.</td>
</tr>
<tr>
<td style="border:1px solid
rgb(170,170,170);padding:4px"><code
style="font-family:monospace,monospace;color:rgb(0,0,0);background-color:rgb(248,249,250);border:1px
solid rgb(234,236,240);border-radius:2px;padding:1px
4px">shortcut</code></td>
<td style="border:1px solid
rgb(170,170,170);padding:4px">A trail that shortens
the main trail.<br>
</td>
</tr>
</tbody>
</table>
<br>
</div>
</div>
</blockquote>
<br>
A 'shortcut' is an alternative .. I see no need for a separate role,
just use 'alternate'? <br>
<br>
Roles on member ways or on member relations?<br>
The example given has a super relation with a number of member
relations, these have no role in the super relation.<br>
An alternative is the super relation with each member relation
having roles. A poor example would be relation 176684 that has one
member relation with part of the name 'alternative routes'. <br>
<br>
What is 'best'? In this case best for the mapper (as is usual OSM
practice). Any thoughts? <br>
<br>
<br>
</body>
</html>