Oops, I meant should I remove mergeShapesFirst() completely? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Gerd Petermann <gpetermann_muenchen@hotmail.com> Gesendet: Montag, 24. Mai 2021 16:07 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Problems with sea in overview map Hi Ticker, you mean I should mergeShapesFirst() completely? Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 24. Mai 2021 15:57 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Problems with sea in overview map Hi Gerd Not sure about this. It is a very drastic change and might break a lot of the element>subdiv code (esp --order-by). Many element well be too big and have to be split again. It ends up as a merge attempt at all lines/shapes in the tile, so it might as well be resolution independent! Ticker On Mon, 2021-05-24 at 13:33 +0000, Gerd Petermann wrote:
Hi Ticker,
I think I found my mistake. The code to re-calc the preserved points was executed for each sub division instead of once per level.
The attached patch might already solve this.
Gerd
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev