[mkgmap-dev] special case where splitting fails without a log message
From Ticker Berkin rwb-mkgmap at jagit.co.uk on Tue May 25 11:51:25 BST 2021
Hi Gerd OK - I've reproduced this. Is split-failed.osm self-intersecting? I'm not sure how to tell from Josm, but it looks like it isn't. I get the messages from shapeSplitter because it thinks it is and then the result is not good - as expected. I'll investigate more. Ticker On Tue, 2021-05-25 at 10:04 +0000, Gerd Petermann wrote: > Hi Ticker, > > while looking at the problems with sea I found this case where > ShapeSplitter removes a small part of an island from a self > -intersecting polygon in res 24. > Compiled with mkgmap from trunk, default style and no options. > > Look at 67.6742611, 14.6783525 > > Found this with some check code that compares the area of the > original polygon with that of sum of the parts. > > Gerd > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev at lists.mkgmap.org.uk > https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
- Previous message: [mkgmap-dev] special case where splitting fails without a log message
- Next message: [mkgmap-dev] special case where splitting fails without a log message
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list