Hi Ticker/Gerd
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. if the polygons are set correctly on openstreetmap, then draw order will will as you expect. Gary ________________________________ From: mkgmap-dev <[email protected]> on behalf of Gerd Petermann <[email protected]> Sent: 23 July 2016 17:05 To: Development list for mkgmap Subject: Re: [mkgmap-dev] Option to output polygons in size order Hi Ticker, are you sure that the order matters? I've never heard that theory and I would be surprised when that is true. The normal way to handle the draw order is to use a typ file, not sure if this works on your device, but it seems to work well for others. Gerd ________________________________ Von: mkgmap-dev <[email protected]> im Auftrag von Ticker Berkin <[email protected]> Gesendet: Samstag, 23. Juli 2016 18:45:59 An: mkgmap development Betreff: [mkgmap-dev] Option to output polygons in size order Hi I'm using splitter-r437/mkgmap-r3676 to make a map for Etrex Legend from british-isles-latest.osm.pbf from geofabric.de. Using "default" style and not using a TYP file, no land features (woods,marsh,green) show because an island polygon for "British Isles" is rendered near the end, on top of everything else. I guess that the Etrex has all area types as the same draworder and renders them in file order. I presume I could use TYP / _DrawOrder to change this behaviour slightly but I keep finding examples of woods in islands in lakes in marsh in islands etc etc, so _DrawOrder can't solve the problem. What would make everything show correctly would be to output polygons in size order, largest to smallest. Could this be done easily? either in splitter then --preserve-element-order, or in mkgmap, possibly after style processing because there will be a lot fewer polygons at this point. Regards Ticker Berkin _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev mkgmap-dev Info Page<http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev> www.mkgmap.org.uk This is a general development list for mkgmap. To see the collection of prior postings to the list, visit the mkgmap-dev Archives.
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
