[mkgmap-dev] Problem with bounds_*.zip

Wed Apr 10 08:06:03 BST 2013

Hi Wanmil,

I like your first option:
1. Merge the options of the style file at the very beginning of mkgmap
 so that all mkgmap sources can uses the same set of options.

A lot of options are related to the style files. When I distribute my styles,
people (like Lambertus who 'produces' my Openfietsmap Worldwide)
don't have to change their mkgmap args file. The less options in this
args file the better.

WanMil wrote:
> Yes, there seem to be two places where mkgmap parameters/options are
> handled.
> 1. The config file or mkgmap parameters. They are loaded directly when
> mkgmap starts.
> 2. The options files in the style system. These options are loaded and
> used only by the style itself.
> 
> So you have two places where you can define the name-tag-list
> parameter
> and both places seem to have their own distinct area in mkgmap where
> the
> parameter is used.
> 
> This is very irritating for the user. I guess this option system
> evolved
> due to historical reasons.
> 
> I see two options to make this point more clear:
> 1. Merge the options of the style file at the very beginning of mkgmap
> so that all mkgmap sources can uses the same set of options.
> 2. Completely remove the options handling in the style system and use
> mkgmap parameters/config file only.
> 
> Any objections to 1. or 2.? Maybe there are reasons to have these two
> distinct option handlings?