Hint regarding creation of bnd files with mkgmap
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? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Hint-regarding-creation-of-bnd-files-with-mkg... Sent from the Mkgmap Development mailing list archive at Nabble.com.
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. WanMil
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Hint-regarding-creation-of-bnd-files-with-mkg... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi WanMil,
Date: Wed, 1 Feb 2012 18:18:46 +0100 From: wmgcnfg@web.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Hint regarding creation of bnd files with mkgmap
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?)
I was testing my new routines (BoundaryPreparer with QuadTree) with all european bnd files. That crashed at some point. While debugging the code with a smaller input in --createboundsfile I got errors for the previously produced wrong bnd files. The new BoundaryPreparer is really a difficult to code. I had to sort out where my algorithm was wrong and where the OSM data contains errors. It's hard to say when results are only 99.9% identical to the trunk, but I am still optimistic.
One should never create the .bnd files in a directory where bnd files already exist.
Okay, I've learned that the hard way ;-) Ciao, Gerd
WanMil
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Hint-regarding-creation-of-bnd-files-with-mkg... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Gerd Petermann -
GerdP
-
WanMil