
Hi Minko, reg. problems with different mkgmap versions: I think this should not happen, but I have no idea why it fails. Can you tell me two release versions that show this problem? Or can you post two img files (one good, one bad) created with different mkgmap versions but no other changes? Maybe I can find out what's different... Gerd
Date: Mon, 27 May 2013 11:43:38 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Strange forest polygon
Hi, The 0x4a/0x4b polygon shouldn't be a problem as long as the upper map is transparent. But there are more issues with combining two map layers on top of each other, I noticed that merging img layers that were made with a different versions of mkgmap also leads to rendering problems. Don't know why this happens but you will see that contour lines appear/disappear at certain zoomlevels if it is made with another version of mkgmap. Only if I make the contour lines every time again with the same version, it renders ok. For my Benelux map I always use an already prepared mp file with contour lines, but for newer maps I start to merge the contour data with the geofabrik data before splitting, the outcome is more consistent.
is there a way to recognize this situation in mkgmap and issue a warning? I guess there should be no type 0x4a or 0x4b polygon in the input files when creating the gmapsupp?
Gerd
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev