I also suggest to use --preserve-element-order to make results predictable. If that option changes the routing we have a good hint that something has to be in a specific order. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <GPetermann_muenchen@hotmail.com> Gesendet: Freitag, 6. Januar 2017 19:56:02 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours Hi Carlos, that is interesting. I added the option --nsis (as last option) for my tests and with your command I got only the overview map named 55190000.img. With --mapname=55190001 I got an additional file with the real map named 55190001.img Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Carlos Dávila <cdavilam@orangecorreo.es> Gesendet: Freitag, 6. Januar 2017 19:32:52 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Estrange detours El 06/01/17 a las 09:06, Gerd Petermann escribió:
just want to mention that the command in your first post has an error in the options: --overview-mapname=55190000 --mapname=55190000 this cannot work, the values must be different.
It seems mkgmap automatically increases mapname 1 unit. This is what I get after running that command: 55190000.img 55190000_mdr.img 55190000.mdx 55190000.tdb 55190001.img If I use --overview-mapname=55190000 --mapname=55190001 I get 55190000.img 55190000_mdr.img 55190000.mdx 55190000.tdb 55190002.img _______________________________________________ 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