message "There is not enough room ..."

Hi all, up to now mkgmap prints There is not enough room in a single garmin map for all the input data The .osm file should be split into smaller pieces first. to stderr without using the normal log format like this: Schwerwiegend (BufferedImgFileWriter): 63240006.o5m: There is not enough room in a single garmin map for all the input data. The .osm file should be split into smaller pieces first. The latter version tells you what input file is causing trouble. I think that's much better, but maybe there is a reason for not doing this? Gerd

Hi Gerd, adding file name is a good idea. I sometimes get these messages and then I look for a missing file or img with size 0 to find what area needs further splitting. Would be nice to have a standard template for a message, which include file name and object ID whenever applicable. Another suggestion is to add a summary at the end of processing with a number of successes/failures in compilation. When I compile a big map, like for example Europe, I get multiple warnings which hide important errors. It happens to me, that I don't notice missing tiles until I browse a final map in Mapsource. -- Best regards, Andrzej
participants (2)
-
Andrzej Popowski
-
Gerd Petermann