Re: [mkgmap-dev] Removal of floodblocker generate-sea option

2021-03-17 Thread Ticker Berkin
Hi Gerd Without floodblocker, I don't think there is a need for mkgmap/reader/osm/SeaPolygonRelation which extends MultiPolygonRelation Ticker On Wed, 2021-03-17 at 14:37 +, Gerd Petermann wrote: > Hi Ticker, > > I don't see yet how floodblocker is related to MP processing? > > Gerd > >

Re: [mkgmap-dev] Removal of floodblocker generate-sea option

2021-03-17 Thread Gerd Petermann
Hi Ticker, I don't see yet how floodblocker is related to MP processing? Gerd Von: mkgmap-dev im Auftrag von Mike Baggaley Gesendet: Mittwoch, 17. März 2021 15:18 An: 'Ticker Berkin'; 'mkgmap development' Betreff: Re: [mkgmap-dev] Removal of floodblock

Re: [mkgmap-dev] Removal of floodblocker generate-sea option

2021-03-17 Thread Mike Baggaley
I don't use precomp-sea, but I don't use floodblocker either, so the suggestion is fine by me. It may however be worth displaying a warning if a tile appears to be flooded. Cheers, Mike -Original Message- From: Ticker Berkin [mailto:rwb-mkg...@jagit.co.uk] Sent: 17 March 2021 09:28 To:

[mkgmap-dev] Removal of floodblocker generate-sea option

2021-03-17 Thread Ticker Berkin
Hi all I think it is time that that the floodblocker logic is removed. I doubt if anyone uses it. The recommended way to have sea is to use --precomp-sea and floodblocker is irrelevant to this. Using the coastline data from the normal OSM input, the common sea problems are in tiles that extend