[mkgmap-dev] mkgmap_locator choking if --index not given

Thu May 19 17:26:21 BST 2011

Mkgmap locator branch, chokes on compiling Albania...

With the following command it just never  finishes. It does create a 
0bit 64140000.img though.

c:\OpenMTBMap\maps>start /low /b /wait java -ea -jar -Xmx6500M 
c:\openmtbmap\mkgmap_locator.jar "--style-file=c:\openmtbmap\new4" 
--max-jobs=4 --generate-sea=extend-sea-sector
s,close-gaps=6000,floodblocker,fbgap=60,fbthres=200,fbratio=0.6 
--latin1  "--boundsdirectory=c:\openmtbmap\maps\bounds" 
--reduce-point-density=4 --nsis --transparent --adjust-
turn-headings --add-pois-to-areas --ignore-maxspeeds 
--x-reduce-point-density-polygon=8 --link-pois-to-ways 
--ignore-turn-restrictions --min-size-polygon=15 --remove-short-arc
s=4 --description=openmtbmap_al --merge-lines --location-autofill=1 
--route --country-abbr=al --country-name=albania  --mapname=64140000 
--family-id=6414 --product-id=1 --seri
es-name=openmtbmap_albania_19.05.2011 --family-name=mtbmap_al_19.05.2011 
--tdbfile --overview-mapname=mapset --keep-going 
--area-name="albania_19.05.2011_openmtbmap.org" -c c:
\openmtbmap\maps\template.albania

Well the above wouldn't be really problematic, however last night mkgmap 
locator branch finished my map of Europe, but choked on creating the 
mdr.img because there existet three 0bit .img files. I stopped it and 
created the index within 10minutes after having deleted the offending 
0bit files.

Now I thought I'll just create all maps without --index, then clean up 
broken 0bit .img files, and create the index. This is not possible 
however, as the locator branch chokes when not providing --index.

So there needs to be a change that mkgmap itself deletes the 0bit .img 
files, before creating the mdr.img and mdx files. (note I already used 
max-nodes 700.000, so Europe worked out at a whopping 1123 .img files, 
the biggest around 12MB - so I am sure (also seen nothing in log) that 
further reducing max-nodes won't solve mkgmap to create broken .img 
files -- on all three there was not a problem related to max-nodes. They 
simply did not compile.