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: [email protected]Subject: Re: [mkgmap-dev] Stronger Intertile Routing Problems with Basecamp4.2.1?
Felix Hartmann <[email protected]> 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 tocrash 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 [email protected]http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
--- Begin Message ---Hi, This is not a bug report, but something I found interesting. I recently noticed a problem with polygon draw order in Mapsource; and on my Dakota 20. Sometimes a polygon was drawn correctly above another (according with the draw order specified in the TYP file), and at other times not. I don’t believe mkgmap actually processes the TYP file so I did not report it here. This morning I was playing with drawing dark lines around polygons to “fix” this, but found mkgmap created a 28000+ Kb file that was too large for Mapsource to show. When I reduced the –max-nodes option to produce smaller tiles I noticed it fixed some, but not all of the polygon draw order problems. So I reduced it further (from the original 1500000, to 750000) and found it fixed all the draw order problems I had noticed. >From previous posts and experience, I knew there was a problem routing across >tile boundaries (which is why I had been using 1500000 to reduce the number of >tiles produced, and thus the boundaries). So I found an area where 4 tiles met >close to each other, and tried auto-routing across the boundaries in >Mapsource. To my surprise reducing the max-nodes had now fixed this problem as >well, and I could route anyway I liked E->W, W->E, N->S, S->N across the four >boundaries. Auto-routing also worked fine on my device as well So if anyone is experiencing similar problems; I suggest trying to reduce the max-nodes and seeing if that helps. Geoff.<<wlEmoticon-smile[1].png>>
--- End Message ---
_______________________________________________ mkgmap-dev mailing list [email protected] http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
