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!BfIobp0WApKJtGdthwWvDt8IzNluZSwOaixW7PnmvJk

However I still found one spot where the fairway is still not visible:

https://mega.nz/#!IM1FjK6R!Q0pDo43Qu8alan4Qrk4QCGsQtTyoQg7eWQx5cLs_EU8

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.

Von: Ticker Berkin
Gesendet: Mittwoch, 16. November 2016 17:05
An: mkgmap-dev@lists.mkgmap.org.uk
Betreff: Re: [mkgmap-dev] Spurious points & Basecamp blank tiles

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@lists.mkgmap.org.uk

http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev