I sent the attached mail a couple of weeks ago. Reducing --max-nodes seems to make a difference; I tested another route this morning in Basecamp after creating it in Mapsource and it worked fine (both latest versions); and I have tested on my Dakota 20. My guess is Garmin software uses fixed length buffers, so if there is too much information in the tiles it sorts it on size order and disposes of the smaller bits of information. I'm not saying it's perfect; but it helped me. If someone who is experiencing routing across tile boundary problems tries with a --max-nodes=750000 and confirms this fixes the problem then we could have a work around. Regards, Geoff. -----Original Message----- From: Johannes Formann Sent: Wednesday, July 03, 2013 11:12 PM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Stronger Intertile Routing Problems with Basecamp4.2.1? Felix Hartmann <extremecarver@gmail.com> wrote:
Well, I like some other people have noted that Basecamp 4.2.1 doesn't autoroute very well. I tried through many examples, and what I found out was that intertile routing seems to be the major problem. As soon as the route leaves one tile more than two times - to go back into it, seems to crash the routing - if it is the preferred way. Anyone else finds another solution?
I found also some strange behaviour with Basecamp 4.2.1 on OS X. http://picpaste.de/Bildschirmfoto_2013-07-04_um_00.00.37-hag375X7.png Dont know if the problem is a tile border, but the routing has some serious bugs. Regards Johannes _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev