<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>>I don't think the concept of layers in the style has any advantage over<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> TYP _draworder.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Again:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>All marine devices ( <a href="https://buy.garmin.com/en-US/US/cOnTheWater-c519-p1.html">https://buy.garmin.com/en-US/US/cOnTheWater-c519-p1.html</a> ) do NOT read anything from your TYP file. TYP _draworder is simply ignored. Please give us a method of controlling draworder that works on all modern Garmin devices.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>TYP _draworder only works on handhelds and automotive units!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>On Fri, 2016-10-28 at 16:47 +0200, rheinskipper1000@gmx.de wrote:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> My suggestion would be to have something like a layer command for the<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> style language.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> Example:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> seamark:type=fairway [0x10702 resolution 20 layer 3]<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> So polygons could be drawn sorted by layer for controlling draw-order<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> on devices not supporting TYP.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> Remember: All these recent devices need maps without TYP:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> https://buy.garmin.com/en-US/US/cOnTheWater-c519-p1.html<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> Currently it is even very problematic to draw just simple buildings<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> on those devices. Not to mention water depth areas or intertidal<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> zones.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> Jürgen<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> Von: Ticker Berkin<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> Gesendet: Freitag, 28. Oktober 2016 16:31<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> An: mkgmap-dev@lists.mkgmap.org.uk<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> Betreff: Re: [mkgmap-dev] patch to write polygons in decreasing order<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> I maintain that there isn't a universal _draworder that will render a<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> map from OpenStreetMap data on the Garmin device in a similar way to<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> how it is shown by www.openStreetMap.org - there are so many examples<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> of nested areas of pasture, woods, grass, playgrounds, etc in any<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> order<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> of overlaying.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> You could say that these should be expressed as inner/outer multi<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> -polygon relationships, but this is rarely done; it would be a lot of<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> effort and the resultant system would be very unwieldy. It would<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> have<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> to be taken to its logical conclusion where, for any area, there is<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> only one (non-transparent) representation. This is because, even for<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> multi-polygon relationships, OpenStreetMap has the concept of the<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> background behind the outer polygon that shows in the inner holes.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> This<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> background seems to considered as such simply by being bigger than<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> than<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> the area in question.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> If the display represention is reduced to a single layer, then<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> _draworder becomes irrelevant!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> On Sun, 2016-10-23 at 09:02 -0700, nwillink wrote:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > OK<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> ><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > Point taken.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> ><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > There is a mystery about some if not most TOPO TYP files containing<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > draworders which are not linked to polygon .<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> ><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > Either they are left overs, which is very unusual, or they imply<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > another<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > purpose as yet undefined - the word container was used to describe<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > such<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > draworders but its unclear what they are grouping.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> ><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> ><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> ><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > --<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > View this message in context: <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> http://gis.19327.n8.nabble.com/patch-to<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > -write-polygons-in-decreasing-order-tp5884038p5884816.html<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > Sent from the Mkgmap Development mailing list archive at<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> Nabble.com.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > _______________________________________________<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > mkgmap-dev mailing list<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > mkgmap-dev@lists.mkgmap.org.uk<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> _______________________________________________<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> mkgmap-dev mailing list<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> mkgmap-dev@lists.mkgmap.org.uk<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> _______________________________________________<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> mkgmap-dev mailing list<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> mkgmap-dev@lists.mkgmap.org.uk<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>_______________________________________________<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>mkgmap-dev mailing list<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>mkgmap-dev@lists.mkgmap.org.uk<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB>http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p></div></body></html>