Hello, I have a map where I get this exception: uk.me.parabola.imgfmt.MapFailedException: 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. How can I now which input file is too big? Thanks, N.
Which OSM-file have you used?! Have you splitted it before?! How many nodes have you chosen? Cheers, Martin Am 28.03.2011 um 03:37 schrieb Nakor:
Hello,
I have a map where I get this exception:
uk.me.parabola.imgfmt.MapFailedException: 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.
How can I now which input file is too big?
Thanks,
N. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi
How can I now which input file is too big?
You can usually work it out by looking for the last map tile that was created. If its zero size of very small then that is the tile. If its normal size then it is the next tile. But it would be nice if we could put the file name into the message somehow. ..Steve
That would be great. I work with a fixed template.args list but now and then tiles get too big to process. If mkgmap could create a list of those 0kb files maybe I could run a script to process the original osm.gz tiles again and run mkgmap another time for those files that havent been done. I know Lambertus uses some kind of script but its too complicated for me. If there are other alternative scripts around, pref. a dos batch script let me know. Steve wrote: But it would be nice if we could put the file name into the message somehow.
Various responses: I have used splitter and have a very conservative number of nodes: 200000 mkgmap does not stop when encountering the error but I have a 0k .img so I suppose this is the candidate. I'll try to spit just that one further. Thanks, N.
participants (4)
-
Martin -
Minko -
Nakor -
Steve Ratcliffe