
Hi Andrzej, thanks for the test data, I was able to reproduce the problem now. It is at a different place in LineClipper. The problem is: Even if I fix that error, the restriction doesn't work. Don't know yet why, I guess Garmin is not able to connect the right boundary nodes when it finds two or more with the same coordinates. On the other hand, I see similar cases in original maps. I'll post version 3 soon. Gerd popej wrote
Hi Gerd,
If you like, please try to comment lines 83-85 in LineClipper:
These were lines 80-82 for me, I don't know why there is a difference. I have compiled sources 3189 with your patch v2.
Removing these lines hasn't helped.
Here are my files: http://files.mkgmap.org.uk/download/201/test.7z
The via node of restriction is really exactly on tile border. I think you would have to bend the border to get restriction working.
-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Patch-v2-route-restrictions-tp5803296p5803368... Sent from the Mkgmap Development mailing list archive at Nabble.com.