<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-04-21 22:20, Martin
Koppenhoefer wrote :<br>
</div>
<blockquote
cite="mid:CABPTjTAA0B6=wWO=dZ=sTwYK=PaSczu-UerS1RkAgxGpb4SAdw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-04-21 20:48 GMT+02:00 Richard Z.
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ricoz.osm@gmail.com" target="_blank">ricoz.osm@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class="">> Without any additional tags like
"tunnel=*" or "covered=*", a<br>
> "layer=-1" river shouldn't be rendered differently
than a "layer=1" or<br>
> even in the absence of any "layer" tag. This is a
bug in OsmAnd. You<br>
<br>
</div>
except for the the very frequent case when the river with
a layer=-1<br>
goes through a landuse=* area with a layer=0.</blockquote>
</div>
<br>
<br>
</div>
<div class="gmail_extra">+1, as soon as there is any other
object on a different layer, be it landuse, a place area or
something else, with the lower layer tag you are excluding the
river from this feature and putting it below.<br>
</div>
</div>
</blockquote>
-2<br>
<br>
First because generally a landuse (think of residential) is not a
physical object but a boundary. Just like highlighting a
municipality area by coloring it does not hide what is inside it,
coloring a landuse must not either.<br>
<br>
Second, because, even if physical like the often debated case of a
forest, where there is a road there is no forest, no plants, it is
interrupted, it does not hide anything and there is no question of
levels where something does not exist. The same applies for river
beds, railway lines and buildings. In the eyes of a renderer, they
are exclusive with a forest and other "something else".<br>
<br>
A different case is a railway line in a tunnel, which is effectively
under ground. In that case, the line must be dotted (in hope that
the source of the data used the same idea and you know where it is.
Never tag source=GPS in a tunnel ;-))<br>
Don't laugh: <a
href="https://taginfo.openstreetmap.org/tags/source=GPS#combinations">https://taginfo.openstreetmap.org/tags/source=GPS#combinations</a>
and combine with "tunnel" ;-)<br>
<br>
The Osmand's (or its renderer's) bug looks much like this.<br>
To say it more precisely than "it looks bad", It uses dotted lines
for -1, -2 and probably below. There is no reason why.<br>
It should be corrected and not be worked around by changing all
levels all over OSM (and discovering that doing so raises another
bug in Osmxor).<br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<br>
</body>
</html>