<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">
<pre>I have ordered a few bus, train, cycling and walking routes. </pre>
<pre>In principle:</pre>
<pre>Both bus and train routes need to be ordered in version 2 of public transport (both stop positions and ways need to be ordered from start to finish). </pre>
<pre>Cycling and walking routes should be ordered for correct interpretation by data users.</pre>
<br>
<br>
<br>
<br>
<br>
On 04/05/18 04:13, James wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CANk4qi9jiybQUcka0r+1gPZbt91MtTvoSH1916DoucOLj1xfww@mail.gmail.com">
<div dir="auto">bus route relations can get very complexe if they
are not ordered. I order them to make sure I haven't missed
anything</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Thu, May 3, 2018, 11:28 AM Yves, <<a
href="mailto:yvecai@gmail.com" moz-do-not-send="true">yvecai@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Un-ordered route members make it very hard to detect a
broken route.<br>
Best practice :<br>
1. If you edit a route, order it at best and check if you
haven't broken it.<br>
2. If you find an unordered route, order it, check if broken
and try to repair it.<br>
<br>
Use for instance <a href="http://ra.osmsurround.org/."
target="_blank" rel="noreferrer" moz-do-not-send="true">http://ra.osmsurround.org/.</a><br>
Yves <br>
<br>
<div class="gmail_quote">Le 3 mai 2018 17:05:32 GMT+02:00,
Michael Andersen <<a href="mailto:osm@hjart.dk"
target="_blank" rel="noreferrer" moz-do-not-send="true">osm@hjart.dk</a>>
a écrit :
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<pre class="m_3731764961769211554k9mail">I regularly edit a number of cycle routes (primarily the danish national
cycleroutes) and do my best to sort/order the members (it's helpfull when
looking for gaps and other peculiarities in JOSM), but have found that it's
often near impossible to make them perfectly sorted.
Consider for example <a href="https://www.openstreetmap.org/relation/20828." target="_blank" rel="noreferrer" moz-do-not-send="true">https://www.openstreetmap.org/relation/20828.</a> Where's the
end points here?
Also note that inexperienced mappers doing minor edits somewhere along a route
cannot be expected to reorder it.
On torsdag den 3. maj 2018 07.38.04 CEST Tod Fitch wrote:
<blockquote class="gmail_quote" style="margin:0pt 0pt 1ex 0.8ex;border-left:1px solid #729fcf;padding-left:1ex"> While I’ve mapped a number of trails most of them are not part of a
designated larger route so I am not 100% sure, but I think hiking routes
are much like highway routes: The ways in the relation should be ordered.
Not sure why you’d need a node in there, especially without an explicit
role. If the route ways are ordered it is obvious where the end points are.
Cheers!
<blockquote class="gmail_quote" style="margin:0pt 0pt 1ex 0.8ex;border-left:1px solid #ad7fa8;padding-left:1ex"> On May 3, 2018, at 5:06 AM, David Marchal <<a href="mailto:Penegal@live.fr" target="_blank" rel="noreferrer" moz-do-not-send="true">Penegal@live.fr</a>> wrote:
Hello, there.
I recently worked a bit on hiking routes, and noticed that some routes
have unordered members. That's particularly noticeable on
<a href="http://waymarkedtrails.org" target="_blank" rel="noreferrer" moz-do-not-send="true">waymarkedtrails.org</a> <<a href="http://waymarkedtrails.org/" target="_blank" rel="noreferrer" moz-do-not-send="true">http://waymarkedtrails.org/</a>>, as it makes the
elevation graph rubbish and useless. I read the relation:route wiki page,
but there is only advice regarding stops order, and not way members
order. Shouldn't there be a note on this page regarding the importance of
sorting the ways to have a more useful relation than only spaghettis?
By the way, I saw some hiking relations having a node without explicit
role, seemingly as a start point; is it a generally accepted, used
feature, or only an idiosyncrasy?
Awaiting your answers,
Regards.
<hr></blockquote></blockquote></pre>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>