<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 14/03/19 02:37, s8evq wrote:<br>
</div>
<blockquote type="cite"
cite="mid:E1h45wV-0002ck-25@rmmprod06.runbox">
<blockquote type="cite">
<pre wrap="">If you want to indicate the preferred direction of a walking route that is
basically loop-shaped, a concept that is different from the legally binding
oneway, then some kind of clockwise / anticlockwise tagging should be used.
</pre>
</blockquote>
<pre wrap="">
Yes Volcker, this is what I'm after. It's about loop-shaped walking/hiking/cycling routes, that should only by done in one direction, because of way-marking and signposts. (Most of the bicycle routes in this overpass query fall in that category <a class="moz-txt-link-freetext" href="https://overpass-turbo.eu/s/GWB">https://overpass-turbo.eu/s/GWB</a>, quite a lot!)
I'm not talking about individual ways that are oneway restricted for pedestrians.
How to properly indicate the preferred direction of this kind of relation?
method (1) With proper forward / backward roles on the members of the relation? (as stated in the route=bicycle wiki page <a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Tag:route%3Dbicycle">https://wiki.openstreetmap.org/wiki/Tag:route%3Dbicycle</a> and mentioned by Volcker Schmidt and Kevin Kenny)
method (2) By using the tag oneway=yes, (as stated on the route=hiking and route=foot wiki page <a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Tag:route%3Dhiking">https://wiki.openstreetmap.org/wiki/Tag:route%3Dhiking</a> <a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Tag:route%3Dfoot">https://wiki.openstreetmap.org/wiki/Tag:route%3Dfoot</a> but it causing a lot of confusion here)
I have not seen anybody on this mailing list defend the usage of method (2). Can I ask the question: why it is in the wiki?</pre>
</blockquote>
<pre><a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Tag:route%3Dhiking">https://wiki.openstreetmap.org/wiki/Tag:route%3Dhiking</a> says
</pre>
<pre>"to indicate that the route is to be walked in only one direction, according to the signposts on the ground" </pre>
<pre>
So ONLY in one direction. </pre>
<pre wrap=""><a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Tag:route%3Dfoot">https://wiki.openstreetmap.org/wiki/Tag:route%3Dfoot</a> </pre>
<pre>
"to indicate that the route is to be walked in only one direction, according to the signposts on the ground"</pre>
<pre>So ONLY in one direction.
The signposts on the ground should state something about 'one way only".
If the signpost don't say anything about one way only but are aligned it a particular direction then oneway=recommended is a better value to use.
</pre>
<pre>The <span data-field="name" data-db-type="text" class="has-data">Larapinta Trail relation 3066363 is such a trial - the signs are oriented best for an east to west walk. But you can walk it in any direction.
</span></pre>
<h3 class="ui-bar"><span data-field="id" data-db-type="osm-url"
class="has-data"></span></h3>
<pre>Where the confusion arises is the "recommendation of direction" rather than the direction being compulsory. </pre>
<pre>
</pre>
</body>
</html>