mkgmap (with routing) telling me about "Directory overflow"
Hi, I wanted to try out the routing version of mkgmap (r806, osm2mp from svn). I tried the baden wuerttemberg file for testing (from download.geofabrik.de). At first I got some message that sounded like not enough memory, so I added some -Xmx parameter. Then I got: hanno@libertalia ~/osm/routing $ java -Xmx1500M -jar mkgmap.jar --route bawue.mp SCHWERWIEGEND (BlockManager): overflowed directory with max block 65534, current=65535 Directory overflow. This is a bug in mkgmap Maybe this file is just too big? -- Hanno Böck Blog: http://www.hboeck.de/ GPG: 3DBD3B20 Jabber/Mail: hanno@hboeck.de http://www.jukss.de/ Jugemdumweltkongress, 27.12.-4.1.
On Dec 12, 2008, at 15:12, Hanno Böck wrote:
I wanted to try out the routing version of mkgmap (r806, osm2mp from svn). I tried the baden wuerttemberg file for testing (from download.geofabrik.de).
At first I got some message that sounded like not enough memory, so I added some -Xmx parameter. Then I got:
hanno@libertalia ~/osm/routing $ java -Xmx1500M -jar mkgmap.jar -- route bawue.mp SCHWERWIEGEND (BlockManager): overflowed directory with max block 65534, current=65535 Directory overflow. This is a bug in mkgmap
Maybe this file is just too big?
Probably. Maybe passing --block-size=1024 (instead of the default 512) will help? Cheers Robert
Hi
hanno@libertalia ~/osm/routing $ java -Xmx1500M -jar mkgmap.jar --route bawue.mp SCHWERWIEGEND (BlockManager): overflowed directory with max block 65534, current=65535 Directory overflow. This is a bug in mkgmap
Well the short answer is that the file is too big. But when I wrote that message I believed that you would never see it because you would always see the 'too big' error first. So the message is probably wrong and shouldn't say that it is a bug in mkgmap. ..Steve
participants (3)
-
Hanno Böck -
Robert Vollmert -
Steve Ratcliffe