<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">A culvert goes under the road and only
carries the waterway. So it does not 'exist' for the road. As such
the culvert would be tagged on the waterway and not on the
roadway. The length of the culvert ... well it is at least as wide
as the road, if you cannot see it in imagery simply make it a bit
wider than the roads width. In Australia many streams are
intermittent - meaning the at water is not frequently there ..
that makes seeing these culverts difficult - I simply use the road
widths if I cannot see them. <br>
<br>
A ford is where a waterway crosses a road, so needs to be on both
waterway and roadway. So this tag should take place on both
waterway and roadway where they share a node (or a way). These too
can nbe hard to see in Australia, if I cannot make out what it is
(ford or culvert) I don't tag it .. that leaves an error, but it
is not something I can identify so I leave it. <br>
<br>
A reason whey tagging tunnel=culvert on a nod that has n=both road
and waterway is that the renders then have to decide it the tunnel
is on the road or the waterway .. or possibly there are 2 tunnels
... one on the road the other on the waterway ... too complex for
the renders... the mappers have to decide. <br>
<br>
<br>
On 01-Mar-18 08:31 AM, Vao Matua wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABvwQawQYj+prrcFGLdkwpYOyqwar+qS=hFdUszG0mK7GP8g1g@mail.gmail.com">
<div dir="ltr">Can someone help me understand two different types
of stream and road crossings?
<div><br>
</div>
<div>A <a href="https://wiki.openstreetmap.org/wiki/Key:ford"
moz-do-not-send="true">ford </a>can be a node or a way
(180,749 nodes & 63,842 ways)</div>
<div><br>
</div>
<div>However, a <a
href="https://wiki.openstreetmap.org/wiki/Tag:tunnel=culvert"
moz-do-not-send="true">culvert </a>can only be a way
(691,972 ways)</div>
<div><br>
</div>
<div>In many circumstances from imagery I can see a stream
crossing under a road without a bridge or ford and therefore I
assume that it is a culvert, but typically cannot see the ends
to split the watercourse. Why does a culvert have to be a way
rather than a way OR a node?</div>
<div><br>
</div>
<div>What I would like to do is simply merge a node of the road
and a node of the stream and give it the tag tunnel=culvert
(when I do this JOSM complains)</div>
<div><br>
</div>
<div>In the case where a culvert carries a watercourse over a
road then it would make sense to create a way and layer=1</div>
<div><br>
</div>
<div>Any insights for this apparent inconsistency?</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>