<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=DE link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-GB>Yes, mkgmap:drawLevel is our Christmas wish this year!<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>Von: </b><a href="mailto:alexandre.loss@gmail.com">Alexandre Loss</a><br><b>Gesendet: </b>Sonntag, 13. November 2016 12:49<br><b>An: </b><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">Development list for mkgmap</a><br><b>Betreff: </b>Re: [mkgmap-dev] Commit r3702: sortAreas_v5.patch:Addoption--order-by-decreasing-area</p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Hi Ticker,</p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I think that create mkgmap:drawLevel is a great idea! </p></div><div><p class=MsoNormal>This will give developers more autonomy to decide the order of the polygons on their maps.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Alexandre</p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>2016-11-13 9:40 GMT-02:00 Ticker Berkin <<a href="mailto:rwb-mkgmap@jagit.co.uk" target="_blank">rwb-mkgmap@jagit.co.uk</a>>:</p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal>I should have thought harder before replying last night. I imagine<br>these river-bank polygons are a mixture of sizes, sometimes divided up<br>at arbitary lines, hence they might be bigger or smaller that the<br>fairway and this explains result you get.<br><br>It's related to the way I handled sea where I give all sea polygons the<br>same, large, areaSize, overwriting the actual size of the arbitrary<br>polygons that make up the sea - this forces them to be output first and<br>other features drawn on top.<br><br>Keeping with the --order-by, in this case it would be better to force<br>fairway to be consider small, hence overwriting the river. At the<br>moment there is no way of doing this, but I was thinking about adding<br>something like mkgmap:drawLevel to be used like:<br><br>natural=sea<br> {add mkgmap:skipSizeFilter=true; set mkgmap:drawLevel=9}<br> [0x32 resolution 10]<br>seamark:type=fairway<br> {name 'fairway'; set mkgmap:drawLevel=0}<br> [0x10307 level 2]<br><br>where drawLevel takes a range of values from 0, being smaller than any<br>natural area to, say, 10 which is much larger than any natural area.<br>This would override the area value calculated from the polygon. Hence<br>allowing control of the output ordering.<br><br>In answer to some points earlier in the thread:<br><br>--order-by should work correctly on large area that cover multiple sub<br>-divisions and even on composite maps provided the splitter has<br>preserved the full polygons in all maps that it has been split into -<br>which I think it does.<br><br>I did intend the areaSize to be the size of each outer-polygon, without<br>subtracting the size of any inner polygons.<br><br>Ticker<br><br>On Sun, 2016-11-13 at 10:21 +0100, Felix Hartmann wrote:<br>> I still think the best solution would be cutting out smaller polygons<br>> from larger - however we would need to define two categories in the<br>> polygons style-file:<br>> 1. polygons that are used transparently in .typ (and will be given<br>> high draworder anyhow) - these can be skipped. Also usually very<br>> small polygons that you give high draworder (e.g. buildings) don't<br>> need to be cut out. It's easier if they simply appear on top.<br>> 2. Other polygons which usually cover large areas - here overlapping<br>> smaller polygons should be cut out.<br>><br>> Looking at area size of polygons of all polygons that fall under 2.<br>> will be needed of course. But because of 1. we will save time as any<br>> polygon that is flagged as belonging to 1. category can be skipped.<br>> Main problems are anyhow forest, water, island and similar where<br>> people are too lazy to use multipolygons.<br>><br>> Even though wrong tagging - looking at the layer tag if present to<br>> decide which polygon should be cut out should still be done.<br>><br>><br>> On 13 November 2016 at 09:47, <<a href="mailto:rheinskipper1000@gmx.de">rheinskipper1000@gmx.de</a>> wrote:<br>> > Yes, I would appreciate a draw order command for the style language<br>> > very much.<br>> ><br>> ><br>> ><br>> > Von: Gerd Petermann<br>> > Gesendet: Sonntag, 13. November 2016 08:22<br>> > An: <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>> > Betreff: Re: [mkgmap-dev] Commit r3702: sortAreas_v5.patch:<br>> > Addoption--order-by-decreasing-area<br>> ><br>> > Hi,<br>> ><br>> > I am not sure regarding the sizes of the area. At least one of the<br>> > riverbank<br>> > polygons is a<br>> > multipolygon with two outer rings. The size calculation treats each<br>> > outer<br>> > ring separately, without<br>> > subtracting the area of inner rings.<br>> > @Ticker: Is that intended?<br>> ><br>> > Besides that I think that the examples show that one needs both a<br>> > draw order<br>> > for types and size ordering to get reasonable results.<br>> ><br>> > Gerd<br>> ><br>> ><br>> > rheinskipper1000 wrote<br>> > > I eagerly awaited the order-by-decreasing-area option.<br>> > ><br>> > > Results are a bit different than I expected at the moment:<br>> > ><br>> > > My style contains:<br>> > ><br>> > > waterway=riverbank [0x10302 resolution 20]<br>> > > seamark:type=fairway {name 'fairway'} [0x10307 level 2]<br>> > ><br>> > > Unfortunately the smaller (white) fairway polygons are still<br>> > partly<br>> > > covered by (blue) riverbank polygons:<br>> > > <a href="https://mega.nz/#!NN8UWDCK!LeR_h1cJeBVDGMxFeUf48l_qARfVdKXTMzRoHj" target="_blank">https://mega.nz/#!NN8UWDCK!LeR_h1cJeBVDGMxFeUf48l_qARfVdKXTMzRoHj</a><br>> > y_rEw<br>> > > <a href="https://mega.nz/#!0B9AgZQJ!AZcQ9zHktIQ0D9Uq_nb_gRGG0eDGxCQaT0XuQJ" target="_blank">https://mega.nz/#!0B9AgZQJ!AZcQ9zHktIQ0D9Uq_nb_gRGG0eDGxCQaT0XuQJ</a><br>> > aebWc<br>> > ><br>> > ><br>> > ><br>> > > Von: svn commit<br>> > > Gesendet: Freitag, 11. November 2016 17:11<br>> > > An:<br>> ><br>> > > mkgmap-svn@.org<br>> ><br>> > > ;<br>> ><br>> > > mkgmap-dev@.org<br>> ><br>> > > Betreff: [mkgmap-dev] Commit r3702: sortAreas_v5.patch: Add<br>> > > option--order-by-decreasing-area<br>> > ><br>> > > Version mkgmap-r3702 was committed by gerd on Fri, 11 Nov 2016<br>> > ><br>> > > sortAreas_v5.patch: Add option --order-by-decreasing-area<br>> > ><br>> > > Patch by Ticker Berkin, slightly modifed<br>> > ><br>> > ><br>> > > <a href="http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3" target="_blank">http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3</a><br>> > 702<br>> > > _______________________________________________<br>> > > mkgmap-dev mailing list<br>> ><br>> > > mkgmap-dev@.org<br>> ><br>> > > <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>> > ><br>> > ><br>> > > _______________________________________________<br>> > > mkgmap-dev mailing list<br>> ><br>> > > mkgmap-dev@.org<br>> ><br>> > > <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>> ><br>> ><br>> ><br>> ><br>> ><br>> > --<br>> > View this message in context: <a href="http://gis.19327.n8.nabble.com/Commit" target="_blank">http://gis.19327.n8.nabble.com/Commit</a><br>> > -r3702-sortAreas-v5-patch-Add-option-order-by-decreasing-area<br>> > -tp5885761p5885809.html<br>> > Sent from the Mkgmap Development mailing list archive at<br>> > Nabble.com.<br>> > _______________________________________________<br>> > mkgmap-dev mailing list<br>> > <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>> > <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>> ><br>> ><br>> > _______________________________________________<br>> > mkgmap-dev mailing list<br>> > <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>> > <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>><br>><br>> _______________________________________________<br>> mkgmap-dev mailing list<br>> <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>> <a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>_______________________________________________<br>mkgmap-dev mailing list<br><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></p></blockquote></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>