[mkgmap-dev] Memory limits for mkgmap and splitter

Tue Aug 4 18:06:05 BST 2009

> Crap, this means I'll have to split North America into two sections
> using Osmosis. At ground level this means broken routing between the
> sections and that some cities/villages will be divided into two...

I think you may have misunderstood me here. You can run the splitter against 
as big an osm file as you like, and the areas.list file that it generates 
should still be correct. The problem doesn't happen until the second stage 
of the split.

So to be perfectly clear, I think if you do the following you should be OK:

1) run the splitter against all of North America (or whatever). Once the 
areas.list file has been generated, hit Ctrl+C to kill the splitter.
2) create two (or more) files by hand, areas1.list and areas2.list, each 
with less than 256 areas in them. Together these contain all the areas from 
areas.list.
3) run the splitter again, giving it areas1.list as input. This should create 
osm files for just the areas in that areas1.list file.
4) run the splitter again, this time with areas2.list as a parameter. This 
should create the remaining osm files.

I haven't tried this myself and it's possible you'll run into some hurdles 
along the way though off the top of my head I can't think of any. If you 
do hit a problem please let me know and I'll see if I can create a fix so 
you can manually work around the 255 area limitation using the above steps 
until I have something more robust in place.

Chris