Re: [mkgmap-dev] found multiple points with equal coord.....

2021-05-01 Thread Gerd Petermann
Hi Thomas, yes, it is a hint for wrong OSM data, but may also just be caused by the lower precision used in mkgmap. When I see that message I use JOSM, load the file for which the messages was created and check the given area. Typically there are two barrier=* or highway=* nodes at the same pl

Re: [mkgmap-dev] found multiple points with equal coord.....

2021-05-01 Thread Gerd Petermann
Hi Thomas, please try also if current version (r4680) shows the same message. Gerd Von: mkgmap-dev im Auftrag von Thomas Morgenstern Gesendet: Samstag, 1. Mai 2021 08:56 An: Development list for mkgmap Betreff: [mkgmap-dev] found multiple points with e

Re: [mkgmap-dev] Request - set --reduce-point-density= for each resolution

2021-05-01 Thread Gerd Petermann
Hi Felix, reg. low resolutions: I think there is also an error in mkgmap which filters e.g. large parts (almost all) of motorways at resolution 14. Gerd Von: mkgmap-dev im Auftrag von Felix Hartmann Gesendet: Freitag, 30. April 2021 16:55 An: Developm

Re: [mkgmap-dev] Request - set --reduce-point-density= for each resolution

2021-05-01 Thread Gerd Petermann
Hi all, sorry for the noise. Got confused by the special case with mkgmap:fast_road=yes in the default style. Gerd Von: Gerd Petermann Gesendet: Samstag, 1. Mai 2021 10:46 An: Development list for mkgmap Betreff: AW: [mkgmap-dev] Request - set --reduce-

Re: [mkgmap-dev] Request - set --reduce-point-density= for each resolution

2021-05-01 Thread Felix Hartmann
haha, no worries. I could have only said, I never noticed that problem. The main problem is the zig-zagging at lower resolution. On Sat, 1 May 2021 at 16:54, Gerd Petermann wrote: > Hi all, > > sorry for the noise. Got confused by the special case with > mkgmap:fast_road=yes in the default style

Re: [mkgmap-dev] Request - set --reduce-point-density= for each resolution

2021-05-01 Thread Gerd Petermann
Hi Felix, I think one reason for the zig-zagging is that we don't merge roads at lower resolutions and maybe DouglasPeucker should ignore "preseved" points at level 1 and higher. Gerd Von: mkgmap-dev im Auftrag von Felix Hartmann Gesendet: Samstag, 1

Re: [mkgmap-dev] Request - set --reduce-point-density= for each resolution

2021-05-01 Thread Felix Hartmann
That could well be - it does seem a bit strange that pretty straight roads become so zig zagged - surely also taking up more space in the map itself. On Sat, 1 May 2021 at 17:23, Gerd Petermann wrote: > Hi Felix, > > I think one reason for the zig-zagging is that we don't merge roads at > lower

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

2021-05-01 Thread Felix Hartmann
well I increased it to 0.5, and could not see any place which was actually different. I noticed in some places the labels were at different positions, so it indeed changed something. Also file size decreased a little bit. I tried about 15 routes with autorouting, and one actually routed a little bi

[mkgmap-dev] Commit r4689: merge the check-precomp-sea branch to do some basic plausibilty tests on precompiled sea data.

2021-05-01 Thread svn commit
Version mkgmap-r4689 was committed by gerd on Sun, 02 May 2021 merge the check-precomp-sea branch to do some basic plausibilty tests on precompiled sea data. The new file sea-check.txt contains characters s (sea), m(mixed), and l(land). Each character represents one entry in the index file that