[mkgmap-dev] Overflowed directory errorFrom Carlos Dávila cdavilam at jemila.jazztel.es on Fri Aug 21 19:07:16 BST 2009
Carlos Dávila escribió: > charlie at cferrero.net escribió: > >> Quoting Carlos Dávila <cdavilam at jemila.jazztel.es>: >> >> >> >>> Hello all >>> While compiling a map from 6 tiles obtained with splitter (manually >>> adjusted areas.list) I get the following error: >>> GRAVE (BlockManager): overflowed directory with max block 65534, >>> current=65535 >>> 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. >>> I guess I must split some of the tiles but, how to know which one? Does >>> it depend on the size (in MB) of the resulting maps? >>> Regards >>> Carlos >>> >>> >> I also create manual areas.list files. My experience is that even if >> I set max-nodes smaller in splitter, it can still create tiles that >> are too big for mkgmap. My rule of thumb is that no tile created by >> splitter should be bigger than ~20MB (compressed, obviously). This >> makes it easy to spot tiles that are too big and I've not (yet) had >> mgkmap fail when applying this rule. >> > Thanks for the figure. I'm currently splitting the same input osm with a > new areas.list. I'll take your size into account before processing tiles > with mkgmap (previously I had one of 28 MB, thus the overflow). Just for information, with a compressed input file of 25 MB I had no problem.
- Previous message: [mkgmap-dev] Overflowed directory error
- Next message: [mkgmap-dev] Regression causing Heap space exhaustion?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list