[mkgmap-dev] mkgmap creates bad mapset, when input files aren't sorted

Sun Mar 13 21:07:38 GMT 2016

Hi,
 
I'm trying to bypass some weird filtering by my email provider, so please forgive me if this report comes duplicated.
Following command produce good mapset for Mapsource:
> mkgmap --code-page=1252 --route --index --bounds=bounds
29624847.osm.pbf 29624849.osm.pbf 29624850.osm.pbf
This command creates bad mapset:
> mkgmap --code-page=1252 --route --index --bounds=bounds
29624849.osm.pbf 29624847.osm.pbf 29624850.osm.pbf
The only difference is changed order of input pbf files. Bad mapset crashes Mapsource, when trying to send map to GPS. Mapsource gives information about error in MDR_TRIM_ADDR.CXX, which suggest mapset index.
I have compared output files for both compilation. Index *_mdr.img is very different. Additionally first and second img are different, while third is the same (except compilation time). I think that output img should be the same, regardless of compilation sequence.
-- 
Best regards,
Andrzej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20160313/20e6f8a9/attachment.html>