[mkgmap-dev] Option handling with polish input (*.mp)?From Gerd Petermann GPetermann_muenchen at hotmail.com on Tue Feb 12 14:53:59 GMT 2019
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
- Previous message: [mkgmap-dev] Commit r4275: improve reader for polish (*.mp) format:
- Next message: [mkgmap-dev] Option handling with polish input (*.mp)?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list