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

2021-03-17 Thread Ticker Berkin
ocessing? > > 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 floodblocker

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

2021-03-17 Thread Gerd Petermann
mailto:rwb-mkg...@jagit.co.uk] Sent: 17 March 2021 09:28 To: mkgmap development Subject: [mkgmap-dev] Removal of floodblocker generate-sea option 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

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

2021-03-17 Thread Mike Baggaley
1 09:28 To: mkgmap development Subject: [mkgmap-dev] Removal of floodblocker generate-sea option 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.

[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