<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 06/12/19 21:23, Andy Townsend wrote:<br>
</div>
<blockquote type="cite"
cite="mid:c1119c6b-3e86-6770-e4a5-404f36c90ff4@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class="moz-cite-prefix">On 06/12/2019 10: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"><br>
<div><span style="font-family:sans-serif;font-size:14px">There
is no unique way to tag roles in hiking route relations <br>
</span><br>
</div>
</div>
</blockquote>
<p>I'd suggest making it clear that that table is currently for
way members only - it doesn't mention node members (start, end,
marker, etc.). This may be deliberate, or you just haven't
expanded it yet, but I'd definitely mention node members.</p>
</blockquote>
<br>
<br>
<br>
For nodes .. think the roles of ways should be done first, but some
thoughts for later proposal/s.<br>
<br>
Are they necessary? <br>
<br>
Start and finish points will be at the end of the main route ways ..
should be obvious? No? <br>
<br>
Markers .. humm I need some time to think on it. <br>
<br>
Well for 'start'/'beginning'/'finish' .. err many routes can be
'started' at either end. So why not use 'end' as that does not
identify it as either start of finish?<br>
<br>
Then should 'end' be only used for the main route, or can it be used
on 'approaches' and 'excursions' too?
</body>
</html>