<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 16/09/2014 19:55, Paul Norman wrote:<br>
</div>
<blockquote cite="mid:c52ba2c6-831c-4bfe-9116-1f30170c10b1@me.com"
type="cite">
<div>On Sep 16, 2014, at 06:33 AM, "Dave F."
<a class="moz-txt-link-rfc2396E" href="mailto:davefox@madasafish.com"><davefox@madasafish.com></a> wrote:<br>
<br>
</div>
<div>
<blockquote type="cite">
<div class="msg-quote">
<div class="_stretch"><span style="white-space:pre-wrap;"
data-mce-style="white-space: pre-wrap;">On 16/09/2014
13:41, Matthijs Melissen wrote:<br>
> In general, we render smaller landuse on top
of larger landuse.<br>
<br>
I find it surprising something as arbitrary as size is
used as the <br>
defining factor. Comparing actual tags would surely make
more sense.</span></div>
</div>
</blockquote>
<br>
</div>
<div>As a recent bug (<a moz-do-not-send="true"
href="https://github.com/gravitystorm/openstreetmap-carto/issues/950">https://github.com/gravitystorm/openstreetmap-carto/issues/950</a>)
has shown, it's important to have *some* well-defined ordering
in cases where the ordering could make a visual distinction,</div>
</blockquote>
<br>
I wouldn't describe size based ordering as 'well defined'.<br>
<br>
<blockquote cite="mid:c52ba2c6-831c-4bfe-9116-1f30170c10b1@me.com"
type="cite">
<div> or the rendered result is undefined and potentially not
deterministic. This can lead to subtle bugs with clipped labels.</div>
</blockquote>
<br>
Hard to tell from the small graphic, but this doesn't appear to be
an ordering problem.<br>
<br>
<blockquote cite="mid:c52ba2c6-831c-4bfe-9116-1f30170c10b1@me.com"
type="cite">
<div><br>
</div>
<div>The two criteria are OSM ID and area. The first is truly
arbitrary being a computer-assigned number, while the second is
well-founded and is the standard way to order within a layer. </div>
<div><br>
</div>
<div>What you're more interested in is why are parks and trees
both in the same landuse layer. It would certainly simplify the
SQL (<a moz-do-not-send="true"
href="https://github.com/gravitystorm/openstreetmap-carto/blob/master/project.yaml#L102">https://github.com/gravitystorm/openstreetmap-carto/blob/master/project.yaml#L102</a>)
to split it up into different tags, but the problem is there is
no universally acceptable ordering of tags. You've pointed at a
case where it'd be good to have trees on top of parks, but I can
point to cases where parks should be on top of trees.</div>
</blockquote>
<br>
Please do, I'd be interested to see them.<br>
<br>
Cheers<br>
Dave F.<br>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="http://www.avast.com/">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
This email is free from viruses and malware because <a href="http://www.avast.com/">avast! Antivirus</a> protection is active.
</p>
</td>
</tr>
</table>
<br />
</body>
</html>