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

Sun Mar 13 18:27:12 GMT 2016

Hi,

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