[mkgmap-dev] AssertionError: Point marked as boundary node
From Bernd Weigelt weigelt.bernd at web.de on Sat Sep 1 08:30:34 BST 2018
Hi Gerd Thank you for this fast fix, will test it when it's on the download site ;-) My build script creates a new areas.list every month to prevent to much nodes or similiar errors, a new one was created this morning. With the new file, the build process run as expected. Bernd Am Samstag, 1. September 2018, 09:05:41 CEST schrieb Gerd Petermann: > Hi Bernd, > > okay, this was a special case introduced with r4223 [1]. The node 5609637907 > is very close to the tile boundary and is also part of a way that is an > admin_level=2 boundary. In this case mkgmap adds a node that is exactly on > the tile boundary and later detects that this node causes a zig-zagging. > The WrongAngleFixer replaces the artificial node with the original one and > that causes the Assertion Error. I hope I corrected this with r4237 [2] > > ciao, > Gerd > > [1] http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4223 > [2] http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4237 > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20180901/f19e6ba6/attachment.sig>
- Previous message: [mkgmap-dev] AssertionError: Point marked as boundary node
- Next message: [mkgmap-dev] Commit r4237: revert most changes from r4223 in WrongAngleFixer
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list