logo separator

[mkgmap-dev] Option handling with polish input (*.mp)?

From Gerd Petermann gpetermann_muenchen at hotmail.com on Wed Feb 13 10:31:05 GMT 2019

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.


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Vadim <bombur at mail.ru>
Gesendet: Dienstag, 12. Februar 2019 16:40
An: mkgmap-dev at 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]

Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk

More information about the mkgmap-dev mailing list