[mkgmap-dev] Suggestion - Make Douglas Peucker Algorithm more Configurable

Fri Jan 8 20:23:52 GMT 2010

That patch works pretty nice. I upped the value to 40 and that gave nice 
results when zoomed far out.
Here is the settings that I would find optimal
resolution 24 == 4 (I think 4 is anyhow the minimum because if less than 
4 pixels than it ain't an area)
resolution 23 == 6 ( resolution 23 is not used by all GPS devices if 
resolution 24 and 22 are present)
resolution 22 == 6
resolution 21 == 20
resolution 20 == 40
resolution 19 == 80
resolution >18 == 120

The only problem of course appears when large areas are splitted up into 
tiny polygons, but I think this is not really solvable without the very 
difficult work of merging.

On 08.01.2010 20:16, Johann Gail wrote:
> Just created a patch for it.
>
> Thilo Hannemann schrieb:
>> The problem with the roads is that the SizeFilter is called for lines 
>> as well as for polygons. But the call to the filter is in two 
>> different places in mkgmap/build/MapBuilder.java. So if you make the 
>> MIN_SIZE a parameter and use different values for lines and polygons 
>> you won't have any holes in the roads at all and can set MIN_SIZE to 
>> a bigger value for the polygons.
>>
>> Regards
>> Thilo
>>
>> Am 08.01.2010 um 15:52 schrieb Felix Hartmann:
>>
>>
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20100108/971bbac0/attachment.html 