logo separator

[mkgmap-dev] [PATCH] Reduce the resolution of natural=coastline

From Felix Hartmann extremecarver at googlemail.com on Thu Mar 4 20:49:05 GMT 2010


On 04.03.2010 20:03, Johann Gail wrote:
>
>
> Felix Hartmann schrieb:
>> It would be better to have more aggressive dp-filter instead. As I 
>> wrote a while back, the increase of the dp filter in low resolutions 
>> has to be much higher. Currently a level of 10 is very good, but too 
>> strong for resolutions 23-21 and a bit too strong for 20.
>>
>>
> For the setting of dp filter:
> Would it be a reasonable solution to take the settings from the 
> options file of the style folder?
>
> I.e. in the style file should be a line like dpfilter = 0:12 1:20 2:50 
> 3:100
> similar to the resoltuion settings. With this it would be possible to 
> set the filter for each resolution.
>
> Or would it be a better aproach to set this line at the commandline as 
> a parameter?
>
> Regards,
> Johann
I think it would be best like the resolution file. But it needs to be 
seperated by polygons and lines (there's already a patch 
"reducepolygonpointdensitypatch" to have different behaviour on roads vs 
polygons. It would just be needed to have additional settings for each 
resolution).
Maybe it could be included into the resolution file in the style. (and 
if not given then put in some defaults. A little bit more ramp up should 
be default however). My ideal settings would be more or less (multiplied 
by the resolution bits, meaning the same correction as right now if I 
set e.g. 5.4, it shall correspond to that 5.4 as it is used currently, 
and not multiplied by the resolution bits)) - as for the resolutions I'm 
currently using:
Resolution:linesdp/polygonsdp
0=24 -- currently not possible without breaking routing.  A reduction of 
roads with very very dense points would be great however. No clue to 
which agressiveness dp filter would have to be setup.
1=22:2/2
2=21:4/6
3=20:6/9
4=19:8/13
5=18:9/15
6=16:10/20 (-- Ideally this would be inside the overview map)
7=14:15/30 (-- Ideally this would be inside the overview map)




More information about the mkgmap-dev mailing list