[mkgmap-dev] tile takes very long time to generate

Wed Mar 31 11:34:40 BST 2021

Hi Gerd

I think this might be the reason why you backed out the Polish
inner/outer definition changes:

http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2019q1/029478.html

Maybe there needs to be an option to say how multiple DATA{sameLevel}
should be handled:
a/ first outer, following inners.
b/ outers clockwise, inners anti-clockwise;
   presume each outer is followed by its inners.
c/ try to work out from geometry.

Ticker

On Wed, 2021-03-31 at 09:39 +0000, Gerd Petermann wrote:
> Hi Ticker,
> 
> reg. polish input: There was code based on the documentation and I
> removed it again. Don't remember why, see changes for r4269 and r4272
> and
> http://gis.19327.n8.nabble.com/Artifacts-in-final-map-MP-gt-IMG-conve
> rsion-tc5932812.html
> 
> The current code is really too complex. A lot of the code exists for
> reporting purposes only. Another big portion is for the handling of
> incomplete data.
> There are probably hundreds of possible error cases with MPs. One of
> my goals is to find out which ones are tolerated by the current code
> and why they are tolerated.
> 
> If nobody offers an approach regarding unit tests we may try to
> simply write a 2nd implementation for MultipolygonRelation and use an
> option to switch between them.
> 
> Gerd