<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<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>okay, can you give an example where areas are causing problems?</p>
<p>For example the id of a mp-relation?</p>
<p>I ask because I assume that the problem is in the data.</p>
<p><br>
</p>
<p>Besides that the img format isn't that simple, it has different sub areas</p>
<p>for one resolution, each can contain many polygons which don't have to</p>
<p>fit into the sub area, in fact it is quite likely that a polygon in one sub area</p>
<p>overlaps polygons in other sub areas. I assume that the order in which these</p>
<p>sub areas are rendered depends on the direction you are moving.<br>
</p>
<p><br>
</p>
<p>Gerd<br>
</p>
<p><br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><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 22:00:12<br>
<b>An:</b> mkgmap-dev@lists.mkgmap.org.uk<br>
<b>Betreff:</b> Re: [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 Gerd<br>
<br>
I don't understand how multi-polygon processing works, but was<br>
presuming that, if my idea works, sorting on the size of each<br>
individual polygon is the correct thing to do.<br>
<br>
Partial overlap of polygons is generally not a problem I'm trying to<br>
solve here, and it is unlikely that, say, if there is a field next to a<br>
wood with a lake spanning the two, the mapping data would have 2 land<br>
areas fully abutted with the lake overlapping both; I'd expect there to<br>
be 3 distinct, non-overlapping, areas.<br>
<br>
Ticker<br>
<br>
On Sat, 2016-07-23 at 19:23 +0000, Gerd Petermann wrote:<br>
> Hi Ticker,<br>
> <br>
> mkgmap analyses multipolygon relations and cuts inner parts, so<br>
> correct mp-relations<br>
> should not be a problem. I've seen overlapping polygons, e.g. when<br>
> you chose to render<br>
> place=island and also the land polygons created by the sea generator.<br>
> You suggest to write the larger polygon first, but in those cases<br>
> this would not help.<br>
> I think this solution would also not help when polygons partially<br>
> overlap.<br>
> <br>
> Gerd<br>
> Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag<br>
> von Ticker Berkin <rwb-mkgmap@jagit.co.uk><br>
> Gesendet: Samstag, 23. Juli 2016 20:42:02<br>
> An: mkgmap-dev@lists.mkgmap.org.uk<br>
> Betreff: Re: [mkgmap-dev] Option to output polygons in size order<br>
> <br>
> Hi<br>
> <br>
> I'm sure that the order in the map has some effect on the Legend; as<br>
> I<br>
> zoom in or scroll across areas with greenery they appear briefly and<br>
> are then cleared, by the island polygon that covers everything, as it<br>
> starts drawing the ways...<br>
> <br>
> Generally, the openStreetMap data order is OK, but I have found<br>
> examples where there are lakes, within the same meadow, that occur<br>
> both<br>
> before and after it. Not sure if this is related to multi-polygons,<br>
> but<br>
> if sorting was performed on the individual polygons there wouldn't be<br>
> any problem.<br>
> <br>
> Also it looks like splitter is delaying the British Isles (and other<br>
> large) polygons because they occurs on multiple tiles.<br>
> <br>
> Typ _drawOrder cannot solve the problem when there are nested<br>
> polygons<br>
> with more that one instance of the same type, whereas drawing outer<br>
> ones first solves it completely.<br>
> <br>
> I have seen mention somewhere that areas with the same _draworder are<br>
> rendered in file order<br>
> <br>
> Ticker<br>
> <br>
> On Sat, 2016-07-23 at 17:17 +0000, Gary Bamford wrote:<br>
> > Hi Ticker/Gerd<br>
> > <br>
> > The draw order does work for the Legend ( it is the device I have<br>
> ).<br>
> > I also came across problems with multiple polygons, the problem can<br>
> > be one of several things, not all multi polygons are correct on<br>
> > openstreetmap, I cam across one today "fairhaven lake" golf<br>
> course,<br>
> > was hiding, due to draw order, but the problem was, it is contained<br>
> > within a polygon for a residential area, so I had to change the<br>
> data<br>
> > on openstreetmap, to make it an inner polygon. when i download the<br>
> > new OSM data I expect it to work correctly.<br>
> > <br>
> > if the polygons are set correctly on openstreetmap, then draw order<br>
> > will will as you expect. <br>
> > <br>
> > Gary<br>
> > <br>
> > From: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> on behalf<br>
> > of Gerd Petermann <GPetermann_muenchen@hotmail.com><br>
> > Sent: 23 July 2016 17:05<br>
> > To: Development list for mkgmap<br>
> > Subject: Re: [mkgmap-dev] Option to output polygons in size order<br>
> > <br>
> > Hi Ticker,<br>
> > <br>
> > are you sure that the order matters? I've never heard that theory<br>
> > and I would be surprised when that is true.<br>
> > The normal way to handle the draw order is to use a typ file, not<br>
> > sure<br>
> > if this works on your device, but it seems to work well for others.<br>
> > <br>
> > Gerd<br>
> > Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag<br>
> > von Ticker Berkin <rwb-mkgmap@jagit.co.uk><br>
> > Gesendet: Samstag, 23. Juli 2016 18:45:59<br>
> > An: mkgmap development<br>
> > Betreff: [mkgmap-dev] Option to output polygons in size order<br>
> > <br>
> > 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<br>
> > Isles"<br>
> > is rendered near the end, on top of everything else. I guess that<br>
> the<br>
> > Etrex has all area types as the same draworder and renders them in<br>
> > 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<br>
> 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<br>
> polygons<br>
> > in size order, largest to smallest. Could this be done easily?<br>
> either<br>
> > in splitter then --preserve-element-order, or in mkgmap, possibly<br>
> > 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 href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
> > mkgmap-dev Info Page <a href="http://www.mkgmap.org.uk">www.mkgmap.org.uk</a><br>
> > This is a general development list for mkgmap. To see the<br>
> collection<br>
> > of prior postings to the list, visit the mkgmap-dev Archives.<br>
> > <br>
> > _______________________________________________<br>
> > mkgmap-dev mailing list<br>
> > mkgmap-dev@lists.mkgmap.org.uk<br>
> > <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
> _______________________________________________<br>
> mkgmap-dev mailing list<br>
> mkgmap-dev@lists.mkgmap.org.uk<br>
> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
> _______________________________________________<br>
> mkgmap-dev mailing list<br>
> mkgmap-dev@lists.mkgmap.org.uk<br>
> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
mkgmap-dev@lists.mkgmap.org.uk<br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</div>
</span></font>
</body>
</html>