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

Mon May 3 10:17:19 BST 2021

Is the branch already worthy for tryout? I guess this is a bigger projekt.
Well sorry.... It would be great if the different DP level filters for
mkgmap by resolution could be somehow make it into trunk. I think that
should be pretty easy for you (notation can be the same as for the
min-size-polygon).

On Mon, 3 May 2021 at 13:59, Felix Hartmann <extremecarver at gmail.com> wrote:

> I think actually for any level >0 we do not need to keep specific points.
> The only important thing for level 1 and greater is that the roads have no
> holes. The lower the resolution the less important it is if they are
> starting ending at the correct point. Of course intersections need to share
> a common point, but it does not matter if that one is shifted a bit or not.
> Where roads are consisting of several parts - if they are merged then of
> course start-end points do not matter either.
>
> Visually the zig zag is not too nice - but without using lower detail
> usually not too apparent. It's more the performance that suffers from all
> those not needed points. And yes for level 0 if a routing point is moved,
> then it needs to be moved for all lines that use it. I do also think moving
> by a tiny bit is not too important. But yes moving more than 7-8m at level
> 0 will be annoying I feel.  That's why only maps made for cars start at
> resolution 23, while topographic maps start at 24 because resolution 23 may
> not be exact enough even though with lock on road you will not notice it at
> all. having a line 7-8m to one side - and having the GPS wandering off to
> the opposite side would not be optimal. Anyting below 5m should however not
> matter. maybe anything below 10m actually doesn't matter? Clearly if a road
> is off by 20m or more at level 0 that will matter.
>
> On Mon, 3 May 2021 at 13:40, Gerd Petermann <
> gpetermann_muenchen at hotmail.com> wrote:
>
>> Hi Felix,
>>
>> I started a new branch low-res-opt. I think the handling of the
>> "preserved" status of points needs more work. Current code preserves too
>> many points which are not important. Filters try to keep preseved points
>> and that means more points and more zig-zagging.
>> I think
>> - we MUST preserve routing nodes and end nodes of roads, at least for
>> level 0
>> - should preserve points which are shared by different lines or shapes so
>> that connections are not removed
>>
>> Work in progress...
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von
>> Felix Hartmann <extremecarver at gmail.com>
>> Gesendet: Montag, 3. Mai 2021 07:27
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> Actually I think I did some mistake concerning the patch - or the patch
>> is not working together with the simplify v4 patch. I think I made a
>> mistake and my changes were just based on having one version with wrong
>> angle fixer 0.05 vs 0.5 and that does create some tiny changes on
>> autorouting. Mind though I did never use preserve-element-order. I'm just
>> trying again and if again no change I will remove simplify v4 patch.
>>
>> On Mon, 3 May 2021 at 12:38, Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com>>
>> wrote:
>> Hi Felix,
>>
>> if you see random results with routing please check if you use
>> --preserve-element-order. For tests like this I really recommend it.
>> OTOH it would be very interesting to find out that the order of data has
>> an influence on routing in a way that a better or worse route is
>> calculated. So far I never found a hint for that.
>>
>> Gerd
>>
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag von Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com>>
>> Gesendet: Sonntag, 2. Mai 2021 19:15
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> Hi Felix,
>>
>> the more-merge.patch  should have no effect on routing. In my tests NET
>> and NOD data was identical. Did you really compare it with an unpatched
>> version? If there are differences in routing my understanding of the data
>> structures is wrong.
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag von Felix Hartmann <
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>
>> Gesendet: Sonntag, 2. Mai 2021 17:50
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> yes I tried it out now without additional DP changes. Routing was
>> identical in 18 out of 20 routes. Twice a tiny difference, hard to say if
>> worse or better. Pretty similar. As for if the visual quality was improved,
>> The jaggedness is a bit better - but still quite a lot of unneeded zig
>> zags. Higher DP values of course improve it.
>>
>> On Sun, 2 May 2021 at 21:16, Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>> wrote:
>> Hi Felix,
>>
>> please try first just my patch, not any further modifications from your
>> side.
>> You can use  unpatched DouglasPeuckerFilter from trunk.
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>> im Auftrag von Felix Hartmann <
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>
>> Gesendet: Sonntag, 2. Mai 2021 15:09
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> Going to test out the patch a bit more right now. Only problem for me is
>> - I cannot set custom dp filter anymore.. But I guess you will implement
>> that anyhow soon?
>>
>> compile:
>>     [javac] Compiling 1 source file to
>> C:\garmin\mkgmap_trunk\build\classes
>>     [javac]
>> C:\garmin\mkgmap_trunk\src\uk\me\parabola\mkgmap\filters\DouglasPeuckerFilter.java:64:
>> error: cannot find symbol
>>     [javac]                     this.maxErrorDistance = filterDistance *
>> 1.3 * (1<< config.getShift()); }
>>     [javac]
>>            ^
>>     [javac]   symbol:   variable config
>>     [javac]   location: class DouglasPeuckerFilter
>>     [javac]
>> C:\garmin\mkgmap_trunk\src\uk\me\parabola\mkgmap\filters\DouglasPeuckerFilter.java:66:
>> error: cannot find symbol
>>     [javac]                     this.maxErrorDistance = filterDistance *
>> 2 * (1<< config.getShift()); }
>>     [javac]
>> ............
>>
>> I will try out at least 20 routes back to back on longer distances to see
>> if something changes to the worse or better with the patch.
>>
>> On Sun, 2 May 2021 at 17:54, Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com>>>>
>> wrote:
>> Hi Felix,
>>
>> attached patch allows to merge roads at levels > 0. This reduced file
>> file and zig-zagging. I didn't see routing problems but didn't test this
>> much.
>>
>> The patch contains also experimtal code for DouglasPeuckerFilter which is
>> not yet enabled. It reduces a bit more but is not yet tested.
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>> im Auftrag von Felix Hartmann
>> <extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>>
>> Gesendet: Samstag, 1. Mai 2021 18:06
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> 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 bit different. It was more or less identical however. So
>> not sure if this makes sense or not. It can save maybe 0.5% of filesize.
>>
>> On Sat, 1 May 2021 at 14:02, Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>>> wrote:
>> Hi Felix,
>>
>> the WrongAngleFixer takes care about filtering at resolution 24. It calls
>> the DouglasPeucker filter with maxErrorDistance = 0.05.
>> See https://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4172
>>
>> Maybe try to play with the value 0.05.
>> WrongAngleFixer tries to produce a result that is closer to the OSM data
>> than simple rounding to Garmin raster and removes points which
>> don't improve the rendered image if they are not needed for routing.
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>>> im Auftrag von Felix
>> Hartmann <extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at g
>>  mail.com<mailto:extremecarver at gmail.com>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>>>
>> Gesendet: Freitag, 30. April 2021 16:42
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> Are you sure it would be needing that much more memory? If there is a big
>> penalty this simplification could only be done for lower resolutions, which
>> contain much less data. Even if its only 13-20 that would be a huge
>> improvement. 21 could need some love too but not as important, while 22 is
>> usually still quite performant on GPS devices. 13-16 or 17 is usually
>> basemap only anyhow. Maybe we could create static basemaps in the same way
>> that we have the sea and boundary files? Yes if a new highway is built at
>> some point it should show up in the overview map - but as this one is
>> really only for orientation, I really feel it's okay to be updated only
>> twice per year or so.
>>
>> Garmins maps in this aspect are clearly superior.
>>
>> On Fri, 30 Apr 2021 at 21:50, Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><m
>>  ailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>>>> wrote:
>> Hi all,
>>
>> attached is my proposed change based on the simplify3.patch by Andrzej
>> and the idea to use that only for contour lines.
>>
>> I see no simple way to implement major improvements for the rendering of
>> lower resolutions. Basically we need the WrongAngleFixer to work with a
>> given resolution.
>> So, something like a loop over each level  (starting with the highest)
>> +  collect the elements that should be rendered at this level
>> + use method like WrongAngleFixer for the corresponding resolution so
>> that distortions caused by rounding are reduced
>> + add code to detect parallel lines which should be deduplicated
>> + store the objects, each only valid for this one level
>>
>> Finally do the sub division splitting, the merging of lines and shapes in
>> each sub div and the binary encoding of the map.
>> If possible, the merging and the Douglas-Peucker-Filter (or whatever)
>> should be done before splitting into sub divs. I assume Garmins program is
>> doing it that way because the data structures suggest that they fist
>> calculate all the elements of all levels before it starts the splitting
>> into sub divs.
>>
>> I guess this would produce nicer looking maps at lower resolutions. It
>> would also require more heap memory (100% would be my guess) and more
>> compilation time unless we find clever tricks to avoid that.
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mail
>>  to:mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>>>> im Auftrag von Felix
>> Hartmann <extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at g<mailto:extremecarver at g>
>>  mail.com<http://mail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>>>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>>>>>>
>> Gesendet: Donnerstag, 29. April 2021 14:39
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> here is what I mean - zig zagging like crazy if you look at it with
>> lowest detail which is really helpful to see this problem. Those highways
>> should be just straight. Oh yes - because the highways are two separate
>> lanes they never have holes. Those holes with the patch are best visible on
>> highway primary and secondary. Actually for highways maybe mkgmap could
>> even include an algo to fix the double highway and just put it once into
>> the map if it overlaps. So step a) remove zig zagging. Step two - remove
>> any double highway if within 3-4 garmin units away from each other as long
>> as we do not create a hole by this (at intersections). Every style has
>> minimum width for highways of at least 3-4 units, if not 6-7, so drawing
>> two highways on top of each other is waste of resources.  Actually this
>> applies to all roads but will be mainly important for highways as they are
>> nearly always entered into OSM with both directions as a separate line.
>>
>> On Thu, 29 Apr 2021 at 20:30, Felix Hartmann <extremecarver at gmail.com
>> <mailto:extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>>>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com>><mailto:extremecarver at gmail.com<mailto:
>> extremecarver at gmail.com><mai
>>  lto:extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mai
>>  lto:extremecarver at gmail.com<mailto:lto%3Aextremecarver at gmail.com
>> ><mailto:extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>>>>>
>> wrote:
>> Yes - I also support Gerd that it doesn't work well for polygons.
>> Now for lines it's another story.
>> a) I love that lines are a bit straighter and looking better vs
>> increasing douglas peucker.
>> b) Sadly though there are bits and pieces of roads missing. If that is
>> fixed I would be all supportive to use this for all lines. But not before
>> those missing bits reappear.
>> How to check for it - just use lowest detail level in Basecamp.
>>
>> Oh yeah and mkgmap without that patch also has a zig zagging problem.
>> Maybe we would need a separate algorithm to check for zig zagging and make
>> sure this does not happen. I really think we could need an algorithm that
>> just checks for zig zagging from resolution 22 and lower and base it on the
>> principle that 90% of all those zig zags are unwanted therefore just
>> straighten lines if there is a zig zag.
>> So nothing to do with this patch - but a general really needed
>> improvement for mkgmap. (mkgmap is lacking a bit vs Garmin owns map at
>> lower resolutions. At resolution 24 mkgmap produces fantastic maps, but
>> garmins own maps are definitely better at lower resolutions regarding
>> problems like zig zagging or reducing detail). Avoiding those zig zags
>> would make the maps pan and load much faster on devices. I use a high DP
>> value of 5.4 because zoomed out further I feel this is needed. But the zig
>> zagging occurs anyhow, or because of it?
>>
>> I really feel some little tweaks here could be a huge improvement for
>> practical use on devices. We do not need exactness when zoomed out far -
>> but we need the map to look nice. If a line is 1 or 2 points away from
>> reality doesn't matter from resolution 17-21 and matters not too much for
>> resolution 22. Only 23 and 24 should be more or less exact. (maybe for
>> driving on highways with a car this is different - but is anyone actually
>> using mkgmap created maps for this? I think nearly everyone uses google
>> maps or smartphone. Garmin maps are mainly for outdoors or city maybe. But
>> not for automobile use. Some people but not many motorcycle maybe. So the
>> main importance for lower resolution is nice visual display and fast, not
>> if a road misses some tiny turn or is 100m left or right. And with a car we
>> have lock on road exactly for that. So visually it will be on the road
>> anyhow even if the road is moved 1 or 2 garmin units to one side.
>>
>> On Wed, 28 Apr 2021 at 22:59, Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><m
>>  ailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>><m
>>  ailto:gpetermann_muenchen at hotmail.com<mailto:
>> ailto%3Agpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com>>>>>>>
>> wrote:
>> Hi all,
>>
>> my observations at resolution 22:
>> I think the patch re-introduces rendering problems at T-shaped crossings,
>> sometimes they look like t-shapes at lower resolutions.
>> Sample: https://www.openstreetmap.org/node/260418111
>>
>> It seems to filter more small polygons, even with  --min-size-polygon=0.
>> I think it tends to make polygons smaller, not sure why.
>>
>> It sometimes reduces wrong zig-zagging, but only for ways with many
>> points. In cities, where roads are often split into many small parts it
>> sometimes makes things worse.
>>
>> It probably helps for the special case contour lines and therefore I
>> suggest to limit it to them.
>>
>> Maybe the code to find the best place for a rounded coord should also
>> consider to remove the point if that would give the best result.
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mail
>>  to:mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mail
>>  to:mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> to%3Amkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgma
>>  p-dev-bounces at lists.mkgmap.org.uk>>>>>>> im Auftrag von Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpeterm<mailto:gpeterm><mailto:
>> gpeterm<mailto:gpeterm>>
>>  ann_muenchen at hotmail.com<mailto:ann_muenchen at hotmail.com><mailto:
>> ann_muenchen at hotmail.com<mailto:ann_muenchen at hotmail.com>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>>>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail
>>  .com><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>>>>>
>> Gesendet: Mittwoch, 28. April 2021 15:21
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> Hi Felix,
>>
>> I expect (more) small missing parts of complex shapes like forests or
>> waterway areas (those without mkgmap:skipSizeFilter=true) and more obvious
>> differences between shapes and lines, e.g. if a style renders outlines of
>> buildings.
>>
>> The maps are very different at res 22, so it is hard to say if there are
>> more  improvements then worsenings.
>>
>> I've experimented with different orders of filters in the past. It's
>> difficult to test because the changes heavily depend on the Styte AND the
>> mapped objects AND the mappers preferences. For example, if landuse areas
>> are glued to highways or not, if landuse areas are glued to other landuse
>> areas or if there nodes are just very close.
>>
>> Gerd
>>
>> ________________________________________
>> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mail
>>  to:mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mail
>>  to:mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> to%3Amkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk>><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk><mailto:
>> mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgma
>>  p-dev-bounces at lists.mkgmap.org.uk>>>>>>> im Auftrag von Felix Hartmann <
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>><mailto:
>> extremecarver at g<mailto:extremecarver at g><mailto:extremecarver at g<mailto:
>> extremecarver at g>>
>>  mail.com<http://mail.com><http://mail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.
>>  com><mailto:extremecarver at gmail.com<mailto:extremecarver at gmail.com
>> >><mailto:extremecarver at gmail.com<mailto:extremecarver at gmail.com><mailto:
>> extremecarver at gmail.com<mailto:extremecarver at gmail.com>>>>>>>
>> Gesendet: Mittwoch, 28. April 2021 14:58
>> An: Development list for mkgmap
>> Betreff: Re: [mkgmap-dev] mkgmap-dev Digest, Vol 153, Issue 40 Resolution
>> 23 raster problems
>>
>> Oh I thought it was mainly meant for contourlines. Did not know you
>> intend it to be used in general. I am not really sure how and where to
>> check for quality.
>>
>> On Wed, 28 Apr 2021 at 20:13, Gerd Petermann <
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><m
>>  ailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>><m
>>  ailto:gpetermann_muenchen at hotmail.com<mailto:
>> ailto%3Agpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>>>>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>><mailto:gpetermann_muenchen at hot
>>  mail.com<mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>>>><m
>>  ailto:gpetermann_muenchen at hotmail.com<mailto:
>> ailto%3Agpetermann_muenchen at hotmail.com><mailto:
>> ailto%3Agpetermann_muenchen at hotmail.com<mailto:
>> ailto%253Agpetermann_muenchen at hotmail.com>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com>>>><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> ><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com>><mailto:gpetermann_muenchen at hotmail.com
>> <mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >>><mailto:gpeterm
>>  ann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com><mailto:
>> gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com
>> >><mailto:gpetermann_muenchen at hotmail.com<mailto:
>> gpetermann_muenchen at hotmail.com
>
>
>
> --
> Felix Hartman - Openmtbmap.org & VeloMap.org
>
>

-- 
Felix Hartman - Openmtbmap.org & VeloMap.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20210503/2acbe443/attachment-0001.html>