logo separator

[mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution 23 raster problems

From Felix Hartmann extremecarver at gmail.com on Wed Apr 28 03:50:31 BST 2021

Thanks for that patch, the improvement is not as big as from the previous
patch - but there is some.
I analysed it a bit more - and I think there needs to be one more change -
actually in general and not only for contourlines.

We need different values for the douglas peucker algorithm depending on
resolution!

Right now we can only set one value, and that is multiplied for each
resolution?
Based on the current state I would like to have

resolution
24= 0.0 or maybe actually have it active at 24 as well trying a value of
0.3 or so. Where there any problems with autorouting or why is it not
possible to use it at resolution 24 as well?
23=1.3
22=2.6
21=3.9
20-11=5.4


Especially if we produce a map without resolution 24, then resolution 23
needs to have much lower DP value than the subsequent resolutions. Using
1.3 for resolution 23 makes the quality IMHO good enough to be used for an
contourlines only map for GPS devices and skipping resolution 24
altogether. For Desktop use resolution 24 may still make sense for
contourlines - but even then the difference is only in very steep areas.

Attached some screenshots at resolution 24, and at 23 with different DP
values and one of patch2.

On Tue, 27 Apr 2021 at 23:16, Andrzej Popowski <popej at poczta.onet.pl> wrote:

> Hi,
>
> some more experiments, see attached patch. I have tried to optimize
> rounding of coordinates for lowest distance to line. This is not good
> for polygons, because can creates gaps between adjacent polygons.
>
> --
> Best regards,
> Andrzej
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev



-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210428/4f6305b2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 23_patch2_5.4.PNG
Type: image/png
Size: 208608 bytes
Desc: not available
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210428/4f6305b2/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 24_correct.PNG
Type: image/png
Size: 316734 bytes
Desc: not available
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210428/4f6305b2/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 23_patch3._5.4.PNG
Type: image/png
Size: 197282 bytes
Desc: not available
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210428/4f6305b2/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 23_patch3_0.0.PNG
Type: image/png
Size: 305070 bytes
Desc: not available
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210428/4f6305b2/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 23_patch3_2.6.PNG
Type: image/png
Size: 134752 bytes
Desc: not available
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210428/4f6305b2/attachment-0009.png>


More information about the mkgmap-dev mailing list