[mkgmap-dev] more refined mkgmap:skipSizeFilter=true handling

Wed May 15 07:13:43 BST 2013

Hi,

I'll implement a parm like 
min-size-polygon="0:12, 1:12, 3:12, 4:12, 5:10, 6:8, 7:8, 8:4, 9:2, 10:1"

@WanMil:
I also like the idea that SeaGenerator should try to generate larger
polygons.
I assume it should be sufficient to merge the land-only and sea-only
rectangles.
This will not create too complex shapes which would then cause run time
problems in
the split process. 

Gerd

Felix Hartmann-2 wrote
> for me not (I only need it for sea anyhow). but the current 
> implementation is to have the mkgmap:skipSizeFilter=true to be added to 
> the style-file. min-size-polygon="0:12, 1:12, 3:12, 4:12, 5:10, 6:8, 
> 7:8, 8:4, 9:2, 10:1" or similar was my original request for this...
> 
> On 14.05.2013 17:47, Henning Scholland wrote:
>> But this should be handled in options. Like:
>>
>> min-size-polygon="0:12, 1:12, 3:12, 4:12, 5:10, 6:8, 7:8, 8:4, 9:2, 10:1"
>>
>> Or is it necessary to handle it different for different polygon types?
>>
>> Henning
>>
>> Am 14.05.2013 23:25, schrieb Felix Hartmann:
>>> b) A more optimal solution would be the following:
>>> mkgmap:changeSizeFilter="level:filter_strenght" so e.g. "0:12, 1:12,
>>> 3:12, 4:12, 5:10, 6:8, 7:8, 8:4, 9:2, 10:1"
>>> A filter working this way, would have great impact on the overview.img
>>> size, as well as normal map.img size - without leading to strong visual
>>> impact. (up to 50% saving on the overview.img size)
>>
> 
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

--
View this message in context: http://gis.19327.n5.nabble.com/more-refined-mkgmap-skipSizeFilter-true-handling-tp5761046p5761060.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.