
On 11 Mar 2009, at 6:46 , Clinton Gladstone wrote:
On Wed, Mar 11, 2009 at 12:56 PM, Toby Speight <T.M.Speight.90@cantab.net> wrote:
In general, it might not help anyway. Consider a route that goes due north/south, close to the tile boundary. If it weaves slightly east/west and back a few times, it will cross tiles quite a lot - even more so if all the tiles are aligned.
A naive question: could some of the inter-tile routing problems be caused by the lack of an overview map?
Could it be that Garmin falls back to the larger routes defined in the overview map for longer distances, thus avoiding the intervening tiles completely?
This is pure speculation; I have no evidence to support this. But could this make sense?
good point. on the Etrex it seems sometimes it falls back to basemap routing for some parts. other times I get a out of memory message. it's just a random effect. Even Mapsource gives up on very long routes but can route all of it in shorter segments.
Cheers. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev