More XT Routing Weirdness

[Mzokk]

Mainly because I use garmin navigation devices to navigate pre-defined routes I wasn't aware (Until today) that if you go to Where To>search a destination and select it you get a fork in the road logo on the XT and a "Routes" menu option on the Garmin 390/340. When these options are selected the unit offers two alternate routes. For testing I selected a destination of Westport Co. Mayo from my house. The 390/340 offer a fastest time route of 193 miles and 4.21 Hrs and an alternate of 192 miles and 4.30 Hrs the shorter route missing Enniskillen. So fair enough. The XT offered a route of 196 Miles (OK) But talking you through Enniskillen which is often a traffic Jam interestingly MyRoute app offered almost the same route. The XT's second route was hilarious at 289 miles via Dublin and heading west well south of the final destination and taking an hour longer. Whoever sorted the routing algorithms for the XT was/is clearly bonkers.

Google maps offered two shorter routes taking the same time, one at 186 miles and the Alternative (that I'd normally take via Maguires Bridge and Carrick-on -Shannon) at 183 miles. I really like Google's point to point navigation.

 

[John Armstrong]

The 396, XT and XT2 all have the faster roads vs fastest route problematic algorithm. Basecamp doesn't which is why I feel a need to add via / way / shaping points so that these devices don't amend the route in a manner I didn't intend to. I have to remind myself when I use the "Go to" option on the device to be wary of the faster roads problem.
The older 590 and 595 manage to avoid this, just a pity their screens are so dull in daylight.