[mkgmap-dev] mkgmap:drawLevel and --order-by-decreasing-area

Thu Nov 17 15:55:28 GMT 2016

Can you drop some sample input that shows this behaviour along with
your command-line/options and style somewhere, and I'll try and work
out what is happening.

Ticker

On Thu, 2016-11-17 at 15:04 +0100, rheinskipper1000 at gmx.de wrote:
> After some more testing I can confirm that even three different draw
> levels also work as expected. This example shows fairway on top of
> intertidal zone which is on top of sea polygon:
> https://drive.google.com/file/d/0Bz9KchYfWW3reHRrSGR6c0Jmc0U/view?usp
> =sharing
>  
> But I got some errors regarding ShapeMergeFilter which I think were
> introduced with the new option:
> https://drive.google.com/file/d/0Bz9KchYfWW3rbUhkMVF2R3p4REU/view?usp
> =sharing
>  
>  
>  
> Von: rheinskipper1000 at gmx.de
> Gesendet: Mittwoch, 16. November 2016 22:08
> An: mkgmap-dev at lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] mkgmap:drawLevel and --order-by-decreasing
> -area
>  
> Meanwhile I repaired the “Bad Godesberg” fairway polygon (in osm
> data) and now can confirm that draw order works perfectly for fairway
> on river polygons.
>  
> After that I tested intertidal zones on top of sea polygons.
> Everything works perfect. It is amazing:
> https://mega.nz/#!oJ1WmLKT!AbxYucPbfP79F1Rv_5B5btUK3KkkWktBnqtyfTZIBV
> 8
>  
> I tried to achieve this for about 5 years, but had no chance. And now
> it works. Many thanks to Ticker for making this possible.
>  
> And sorry for mixing up threads. It´s because I´m so excited about
> the new feature!
>  
>  
>  
> Von: rheinskipper1000 at gmx.de
> Gesendet: Mittwoch, 16. November 2016 18:45
> An: mkgmap-dev at lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] mkgmap:drawLevel and --order-by-decreasing
> -area
>  
> My first test look really promising. All the draw order problems for
> fairway on river Rhine in the Mainz/Wiesbaden area are gone. It looks
> very beautiful now:
>  
> https://mega.nz/#!dFE1QIKK!BfIobp0WApKJtGdthwWvDt8IzNluZSwOaixW7PnmvJ
> k
>  
>  
> However I still found one spot where the fairway is still not
> visible:
>  
> https://mega.nz/#!IM1FjK6R!Q0pDo43Qu8alan4Qrk4QCGsQtTyoQg7eWQx5cLs_EU
> 8
>  
> But this should not be a mkgmap issue because same problem also
> exists in openseamap online map. I will investigate further and keep
> you informed.
>  
> Thank you so much for this great improvement. It is a huge step for
> the openseamap project because it is pre-condition for rendering
> crowdsourced water depth as different shades of blue. There are 7
> different predefined extended types for water depth which all have
> same built in draw order. Now chances are good that they can be
> controlled.
>  
>  
>  
> And sorry for mixing LEVEL and RESOLUTION. I used LEVEL but my style
> is based on default style which uses RESOLUTION.
>  
>  
> Ups, thread was still wrong.
>  
>  
> Von: Ticker Berkin
> Gesendet: Mittwoch, 16. November 2016 17:05
> An: mkgmap-dev at lists.mkgmap.org.uk
> Betreff: Re: [mkgmap-dev] Spurious points & Basecamp blank tiles
>  
> Hi
>  
> Not quite, you should have something like:
>  
> seamark:type=fairway {name 'fairway'; set mkgmap:drawLevel=60 }
> [0x10306 level 2]
> waterway=riverbank { set mkgmap:drawLevel=02 } [0x10302 resolution
> 18]
>  
> but you only need one of the mkgmap:drawLevel for the fairway to be
> written after/overwrite the riverbank. Which you use depends on what
> you want the behaviour to be with other polygons sharing the same
> area.
>  
> Also, slightly confusing to have level and resolution in the same
> style.
>  
> And the wrong thread.
>  
> Regards
> Ticker
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>  
>  
>  
>  
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev