Hi Minko, Minko-2 wrote
1) According to Steve the alignment to 2048 units is not mandantory, the ony important point is that you don't have gaps. The value 2048 results from the default resolution 13 : 2 ^ (24-13) = 2048.
I see. In resolution 13 the overview map is generated, right? This emtpy polygon for this map is visible behind the OSM map and doesn't match the foreground tiles if they are not aligned to this 2048 units.
This explains I think in this kind of artefacts at the corners: https://dl.dropbox.com/u/64716698/OSM/mkgmap/corners.jpg
I meant the default resolution used in splitter, but I think you are right that 13 is used for the overview map. I am not aware that the value has an influence on mkgmap, but I maybe wrong. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/issues-with-tile-boundaries-tp5753275p5753472... Sent from the Mkgmap Development mailing list archive at Nabble.com.