I see this behavior as well with quite a few tiles. I work around this by using: ulimit -t 300 java -jar .... for rendering. Then check if an image file is created afterwards. If none is found the tile is split in half and then rendered again. This usually resolves it. Nop wrote:
Hi!
Can anybody tell me the meaning of this error?
What's remarkable: It seems that error was triggered by an oversize OSM file. I had 200 files that processed fine, then the oversize one triggered the error. The message was output about 14 times and mkgmap apparently went into an endless loop, I had to kill it after several hours of CPU without any progress/output.
bye Nop
Am 13.12.2009 08:44, schrieb Nop:
Hi!
Running mkgmap r1404 on a large map, I have encountered the following error message that I have not seen before:
SCHWERWIEGEND (MapSplitter): Area too small to split at http://www.openstreetmap.org/?lat=46.36971&lon=13.83734&zoom=17 (reduce the density of points, length of lines, etc.)
Is this the same as the previous error "too many objects for map file" or something else?
bye Nop
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev