Hi Nop, this is a known mkgmap problem and there have been several questions about that within the last month. You might read: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q1/009960.html The only possible solution is to split the polygon so that it contains less points (either by selecting the splitter split points or by changing the osm data). But that's a try and error solution. WanMil
Hi!
I have been trying to build a map of portugal for a while, but it never quite works out. There is no exception, but mkgmap shows a large number of messags like this:
Area too small to split at http://www.openstreetmap.org/?mlat=38.59838&mlon=-7.34522&zoom=17 (reduce the density of points, length of lines, etc.)
When this happens, the data is dropped, so the map looks rather like patchwork. :-)
The reason seems to be a large and highly detailed lake in the area, a multipolygon with 1600+ points. As splitting the map takes only the total number of points into account, the lake should not be a problem, but internally it appears that due to the extensive size of the polygon too much detail always ends up in the same MapArea until the MapSplitter gives up and drops the data.
From what I've seen, this should be a general problem unless the input data is somehow deliberately cut right through the large polygon - but I can't figure out how to calculate the proper place to cut it or how to force a cut there.
Can you build a map for the area -8.0, 37.8, -6.7, 38.9 without any "Area too small to split" appearing?
bye Nop
-- View this message in context: http://gis.638310.n2.nabble.com/Mkgmap-dropping-data-Area-too-small-to-split... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev