I think even if you define the order, it won't really workout well. Also you would need to check if all devices have the same order. At least on the consumer GPS side, Garmin turned the draw order upside down in newer vs older generation gps devices (same holds true for old Mapsource 6.13 vs Basecamp >=v3).
Maybe there would be a need for proper overlay checking with blacklists which types may not be in the same area as others, and then mkgmap cutting out some polygons. Or mkgmap cutting out smaller polygons from larger ones, similar to how mapnik does it... I cannot imagine this to be easy though (because I cannot even come up with a clean concept on how this should be done). On 11.10.2012 12:28, RheinSkipper wrote: > As I already mentioned, TYP-files are NOT supported by devices from the > Garmin marine line-up (GPSMap 421, GPSMap 526, GPSMap 720 ...). All Garmin > nautical chartplotters simply ignore the information in the TYP-file. > > >> -----Ursprüngliche Nachricht----- >> Von: [email protected] [mailto:mkgmap-dev- >> [email protected]] Im Auftrag von Henning Scholland >> Gesendet: Donnerstag, 11. Oktober 2012 09:26 >> An: Development list for mkgmap >> Betreff: Re: [mkgmap-dev] Feature request: Layer control >> >> Hi, >> I think you have to change the DrawOrder in your TYP-file. This tells the >> Garmin-device in which order the polygons should be rendered. >> >> Henning >> >> _______________________________________________ >> mkgmap-dev mailing list >> [email protected] >> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
