Option handling with polish input (*.mp)?

Hi, with OSM data we provide options like family id, mapname etc. as program arguments. In *.mp files many of these options can be specified in the so called "IMG ID" section. In the past the polish reader in mkgmap didn't evaluate most of these parameters, there was no intention to replace the functionality of cGPSmapper. Now I learned about tools that create *.mp files as output and that mkgmap might be the better choice to process those files. So far so good. Problem: What is expected when the mkgmap options conflict with those in the *.mp file? My current understanding is this: 1) *.mp overwrites mkgmap builtin defaults 2) mkgmap options overwrite *.mp information Would that work? Gerd

It is a good idea to take the settings from the MP file. All those who will convert the MP file for the first time with Mkgmap will expect exactly this behavior. I remember, I was very surprised when I first converted the MP file and got an IMG file with a name different from the ID identifier from the [IMG ID] section... -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

Hi all, this looks like a bigger change. The current code in mkgmap mixes the meaning of map name and the map id. In some places the map name is retrieved from the file name if that name matches the typical 8 digit pattern. If not, weird results are produced, e.g. when I process the two files 00008001.mp and AmericanLake.mp (in that order) I'll get 00008001.img and 00008002.img When I reverse the order I get 63240001.img and 00008001.img When you compile the file AmericanLake.mp with cGPSmapper it produces AmericanLake.img. I have no idea if mkgmap should do that as well and what side effects we'll get if it does. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Vadim <bombur@mail.ru> Gesendet: Dienstag, 12. Februar 2019 16:40 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Option handling with polish input (*.mp)? It is a good idea to take the settings from the MP file. All those who will convert the MP file for the first time with Mkgmap will expect exactly this behavior. I remember, I was very surprised when I first converted the MP file and got an IMG file with a name different from the ID identifier from the [IMG ID] section... -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Gerd Petermann
-
Gerd Petermann
-
Vadim