<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2014-12-01 15:11, Frank Vdm wrote :<br>
</div>
<blockquote
cite="mid:CAEbe9CMZ+BNJt7ezCBL4BgHhDPV7nzKeFA=Ynx1=PrBG0zAhgw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>André,<br>
<br>
</div>
Is it the validator ore myself (possible i do not see a
small item that give the error)<br>
</div>
The hiking closed circle route I put it in. Pole with
markers with one direction.<br>
</div>
Name Kortewagenpad.<br>
</div>
The relation looks good<br>
<div>
<div>
<div>
<div>
<div><a moz-do-not-send="true"
href="http://ra.osmsurround.org/analyzeRelation?relationId=4225213">http://ra.osmsurround.org/analyzeRelation?relationId=4225213</a><br>
</div>
<div>But de josm validator doe not recognize
forward/backward<br>
<br>
</div>
<div>Place Lauweplaats Lauwe if you want to look youself<br>
<a moz-do-not-send="true"
href="https://www.openstreetmap.org/#map=17/50.7945/3.18653">https://www.openstreetmap.org/#map=17/50.7945/3.18653</a><br>
</div>
<div><br>
-- <br>
<div class="gmail_signature">Met vriendelijke groeten,<br>
<br>
Frank (Jakka)<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
Hi Jakka,<br>
<br>
The best way to show a relation is by adding <a
href="https://www.openstreetmap.org/relation/4225213#map=17/50.79450/3.18653">/relation/4225213</a>
to your URL like this:<br>
<a
href="https://www.openstreetmap.org/relation/4225213#map=17/50.79450/3.18653">https://www.openstreetmap.org/relation/4225213#map=17/50.79450/3.18653</a><br>
forward/backward are not mandatory, hiking routes are usually mapped
without any and JOSM doesn't support them.<br>
BTW, JOSM doesn't support (yells at) start/end either, which mappers
love to indicate a node where to start (parking ...).<br>
<a
href="http://www.waymarkedtrails.org/en/?zoom=12&lat=50.5403&lon=5.63978">Look
here, over this region for examples</a>.<br>
generally, forward/backward are only necessary when and where one
direction does not follow the same route as the opposite.<br>
In that case, the best idea for clarity is/would be to make 2
opposite routes, best bundled in a top relation like for bus routes,
but I don't know how well this is supported.<br>
Web editors users say they have problems with that, but it's not a
valid reason to stop mapping<br>
As fuzzily as ever, <a
href="http://wiki.openstreetmap.org/wiki/Walking_Routes#Tags_of_the_relation"><span
class="tocnumber">3</span> <span class="toctext">Tags of the
relation</span></a> and <a
href="http://wiki.openstreetmap.org/wiki/Hiking#Tags_of_the_relation"><span
class="tocnumber">2.1</span> <span class="toctext">Tags of the
relation</span></a> do not say a single word about the elements
and their roles.<br>
Usually, hiking routes are designed to be walked in a single
direction (the signs are not well visible in the other) and that can
be stressed with oneway=yes.<br>
<br>
Cheers
<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
</body>
</html>