Hi I've only taken a quick look so far, but it seems that the command line option is applied too late and the built in default is used initially to convert the level to resolution. So level 0 is converted to resolution 24 and this is then (correctly) omitted from a resolution 23 level.
I did wonder why this has never been noticed before and I think this is probably because the default style uses resolution rather than level in the type definitions. It is probably only the conversion of level when reading the style that is affected and if this is the case then the fix may be relatively easy. I will look at it some more later. ..Steve On 18 May 2015 16:45:31 BST, Andrzej Popowski <po...@poczta.onet.pl> wrote: >Hi, > >I think problem is with initial conversion levels -> resolution. > >I thought, that levels in style are depreciated, but Steve's suggestion > >works, I get correct results when using proper levels inside "options" >file. > >If I delete levels form style, then command line values still aren't >used. Are they any default values in code? _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
