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
mkgmap-dev@lists.mkgmap.org.uk
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: mkgmap-dev-boun...@lists.mkgmap.org.uk
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
Hi
I have attached a proper fix that deals with all the cases.
I just committed this fix, an email was not sent because I forgot to
restore the post-commit hook which sends it. Should be OK from now on.
..Steve
___
mkgmap-dev mailing list
Cutting out holes will be the best solution off course. In case of the
riverbank and fairway multipolygons, fairway has also to be considered as
the inner multipolygon of the riverbank. But for the buildings it will be
more complicated as there are more tags involved.
I really hope you can find a
On 11/10/2012 11:45, Felix Hartmann wrote:
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
