Hi Ticker, sorry, I didn't keep that specific case. If you cannot reproduce I'll try to find it again. Both the triangle and the rest was visited in clockwise order and the start/end was somewhere else on the rest. I think the cut did not go through the triangle but I'm not sure.
Gerd ________________________________________ Von: mkgmap-dev <[email protected]> im Auftrag von Ticker Berkin <[email protected]> Gesendet: Montag, 31. Mai 2021 11:18 An: [email protected]; [email protected] Betreff: Re: [mkgmap-dev] [mkgmap-svn] Commit r4749: remove/disable code to merge shapes to the max for now: Hi Gerd Do you have an example of this triangle / concave shape? Are you sure there isn't a rotation through the connection point, resulting in something like a figure-of-8. Ticker On Mon, 2021-05-31 at 07:41 +0100, svn commit wrote: > Version mkgmap-r4749 was committed by gerd on Mon, 31 May 2021 > BRANCH: low-res-opt > remove/disable code to merge shapes to the max for now: > - hole detection was too simple, sometimes removed outer parts of > shapes > - ShapeSplitter doesn't handle some degenarated shapes well where > parts are connected in a single point, like a triangle connected to a > concave shape. > > Will try again with a different approach once ShapeSplitter is able > to handle these cases. > > http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4749 > _______________________________________________ > mkgmap-svn mailing list > To unsubscribe send an mail to [email protected] > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-svn _______________________________________________ mkgmap-dev mailing list [email protected] https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list [email protected] https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
