logo separator

[mkgmap-dev] [PATCH v5] - fix clipping when node falls on tile boundary

From Mark Burton markb at ordern.com on Tue Jul 21 10:04:25 BST 2009

v5 - Tweaked the test that catches zero-length segments - otherwise the
same as before.

Maning - I can't see why your example is failing, if you still have the
data, please try with this version although I don't really think it
will behave any differently. Also, does it just fail to route and give
a straight line or does mapsource barf and give you the error box?

Valentijn - This works well enough with your example - however, I did
notice that mapsource fails to find a route that starts in one tile,
goes into the second and then back to the first tile. See attached
piccy. That shows a successful route. But if you move the destination
point (102) to below the map join (visible as line across way not far
below the destination point), mapsource gives up and draws a
straight line. But there's nothing wrong with that way (Zuiddijk)
because you can happily route across the boundary in both directions.
Adding an intermediate point to the route in the upper tile, solves the
problem. It's not implausible that this is a limitation of the Garmin
routing algorithm.

Unless we find any new problems, I intend to commit this stuff in the
next day or so.

Cheers,

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mb-clip-at-node-fix-v5.patch
Type: text/x-patch
Size: 7413 bytes
Desc: not available
Url : http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20090721/e16901d4/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tunnel-route-2.png
Type: image/png
Size: 123001 bytes
Desc: not available
Url : http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20090721/e16901d4/attachment.png 


More information about the mkgmap-dev mailing list