
Hi Klaus, I think I fixed the problem for your configuration, but as you already saw it revealed new issues. The current status is this: - splitter can calculate tiles based also on the number of nodes in the precomp-sea tiles. For your case, that results in a few more tiles for norway some of them are only filled with data from the generate-sea option. These tiles may cause crashes on some devices (I did never try that) - the multipolygon handling in mkgmap has two major problems: 1) it is removing a lot of the small polygons created by the generate-sea method, this leads to the white stripes that you see in low resolution 2) it is saving large polygons with far too many details for low resolution, this leads to the message "There is not enough room in a single garmin map for all the input data..." I have a work around for the 2nd issue, but the first one requires a major redesign of the program. Gerd
Date: Thu, 3 Jan 2013 07:56:53 -0800 From: easyclasspage@googlemail.com To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Norway not buildable with the no-trim option
Hi Gerd,
does it makes sense to build a norway map with the "new" splitter ? Currently I don't think so - right ?
Regards Klaus
-- View this message in context: http://gis.19327.n5.nabble.com/Norway-not-buildable-with-the-no-trim-option-... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev