logo separator

[mkgmap-dev] Hint regarding creation of bnd files with mkgmap

From WanMil wmgcnfg at web.de on Wed Feb 1 17:18:46 GMT 2012

Hi Gerd,

> Hi,
> if you plan to use the --createboundsfile parameter to create your own
> precompiled boundary data,
> I suggest to use it with an empty target directory (default is bounds).
> Reason:
> mkgmap will create new *.bnd files for the data given in the input file, but
> it will "rework" all (!) *.bnd files that are found in the target directory.
> This rework process is very time consuming and it will fail if your target
> directory contains corrupted bnd files that are not overwritten in the first
> step.
> I don't know if this was intended?

Corrupt .bnd files are corrupt, so I don't mind when that causes mkgmap 
to fail. (Bye the way: how did they get corrupt?)
One should never create the .bnd files in a directory where bnd files 
already exist.


> Gerd
> --
> View this message in context: http://gis.19327.n5.nabble.com/Hint-regarding-creation-of-bnd-files-with-mkgmap-tp5432439p5432439.html
> Sent from the Mkgmap Development mailing list archive at Nabble.com.
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

More information about the mkgmap-dev mailing list