<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi Ticker/Gerd</p>
<p><br>
</p>
<p>The draw order does work for the Legend ( it is the device I have ). I also came across problems with multiple polygons, the problem can be one of several things, not all multi polygons are correct on openstreetmap, I cam across one today "fairhaven lake"
golf course, was hiding, due to draw order, but the problem was, it is contained within a polygon for a residential area, so I had to change the data on openstreetmap, to make it an inner polygon. when i download the new OSM data I expect it to work correctly.<br>
</p>
<p><br>
</p>
<p>if the polygons are set correctly on openstreetmap, then draw order will will as you expect.
<br>
</p>
<p><br>
</p>
Gary<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> on behalf of Gerd Petermann <GPetermann_muenchen@hotmail.com><br>
<b>Sent:</b> 23 July 2016 17:05<br>
<b>To:</b> Development list for mkgmap<br>
<b>Subject:</b> Re: [mkgmap-dev] Option to output polygons in size order</font>
<div> </div>
</div>
<div>
<meta content="text/html; charset=UTF-8">
<div dir="ltr">
<div id="x_divtagdefaultwrapper" style="font-size:12pt; color:#000000; background-color:#FFFFFF; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Ticker,</p>
<p><br>
</p>
<p>are you sure that the order matters? I've never heard that theory</p>
<p>and I would be surprised when that is true.<br>
</p>
<p>The normal way to handle the draw order is to use a typ file, not sure</p>
<p>if this works on your device, but it seems to work well for others.<br>
</p>
<p><br>
</p>
<p>Gerd<br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>Von:</b> mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk><br>
<b>Gesendet:</b> Samstag, 23. Juli 2016 18:45:59<br>
<b>An:</b> mkgmap development<br>
<b>Betreff:</b> [mkgmap-dev] Option to output polygons in size order</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt">
<div class="PlainText">Hi<br>
<br>
I'm using splitter-r437/mkgmap-r3676 to make a map for Etrex Legend<br>
from british-isles-latest.osm.pbf from geofabric.de.<br>
<br>
Using "default" style and not using a TYP file, no land features<br>
(woods,marsh,green) show because an island polygon for "British Isles"<br>
is rendered near the end, on top of everything else. I guess that the<br>
Etrex has all area types as the same draworder and renders them in file<br>
order.<br>
<br>
I presume I could use TYP / _DrawOrder to change this behaviour<br>
slightly but I keep finding examples of woods in islands in lakes in<br>
marsh in islands etc etc, so _DrawOrder can't solve the problem.<br>
<br>
What would make everything show correctly would be to output polygons<br>
in size order, largest to smallest. Could this be done easily? either<br>
in splitter then --preserve-element-order, or in mkgmap, possibly after<br>
style processing because there will be a lot fewer polygons at this<br>
point.<br>
<br>
Regards<br>
Ticker Berkin<br>
<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<br>
<a id="LPlnk888383" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a>
<div style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;" id="LPBorder_GT_14692938765930.5806581191338313">
<table style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" id="LPContainer_14692938765690.5495131066433981" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td colspan="2" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" id="TextCell_14692938765840.22673419834893926">
<div id="LPRemovePreviewContainer_14692938765850.4646691056635712"></div>
<div style="top: 0px; color: rgb(0, 75, 139); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height: 21px;" id="LPTitle_14692938765850.7902811714222151">
<a target="_blank" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" style="text-decoration: none;" id="LPUrlAnchor_14692938765870.29898008524749975">mkgmap-dev Info Page</a></div>
<div style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 14px;" id="LPMetadata_14692938765890.4655241751296505">
www.mkgmap.org.uk</div>
<div style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;" id="LPDescription_14692938765910.37148586319918475">
This is a general development list for mkgmap. To see the collection of prior postings to the list, visit the mkgmap-dev Archives.</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
</div>
</span></font></div>
</div>
</div>
</body>
</html>