Hi Minko, that' s good news :-) When you reach the limit again you may have to remove some details from the overview map, e.g. use level 19/20 instead of 18 or remove the "background" type 0x10100. I only see one potential improvement in the program: Many bytes are used to store sea / coastline polygons. If we ever manage to find a better algo to simplify them for the low Garmin resolutions we may be able to store better info with fewer bytes. The current combination of filters tends to produce self-intersecting ugly looking triangles which often contain spikes, which means they have redundant bytes. @Mike Baggaley: I think your pointInPolygon-v0.patch showed a completely new approach to simplify polygons using the Java Graphics2D.fillPolygon() method. Maybe this could be used as a new filter for shapes in MapBuilder. It seems to do exactly what we want. Gerd Date: Thu, 14 May 2015 11:17:20 +0200 From: ligfietser@online.nl To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] EU map too big? Hi Gerd, Probably something went wrong the first time. I now managed to produce a full map with all the tiles and mkgmap-r3595. Thanks again for the quick fixes! _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev