Goofy Garmin? Routes like a drunk.

Former Member
Former Member
We gave our Garmin verbal instructions to go to a nearby restaurant as a test.
We knew the easiest, fastest most direct route - but the Garmin took us off the main thoroughfare through a bunch of side streets to get there.
Another test with Basecamp is just as scary.
We know that there is a very direct route from Phoenix to Puerto Penasco, Mexico.
So, as a test, I programed the start and end points and got a route that takes us hundreds of miles off course.
Attached is a screen shot of the goofy Garmin route and a dashed line illustrating the correct route.
What is wrong?
Should I return this new 2699LMT to Costco for a refund?
Or is there a fix for this nonsense?
  • Upon further review, the detailed 2014.4 and 2015.2 maps for BaseCamp, which include Canada, still show the large disconnect at the Mexico MX8/AZ SR85 border crossing.

    I see the following in both Basecamp 4.4.6 and Mapsource.

    I just took a look at CNNA 2009 and I can begin to see the disconnect at 1km zoom level. If I zoom to 20m and use the ruler tool the west-to-east disconnect right at the border measures 83m (~270ft).



    When I switch to CNNA 2014.3, 2015.1 and 2015.2 they all show the USA and Mexico segments joining perfectly at the border. No gap on any of them.

    I do notice one difference between the 2014.3 map and the 2015.x versions. In the 2014.3 version the Mexican segment extends north across the border and overlaps the USA segment in the USA. In the 2015 versions it's the USA segment that extends south across the border and overlaps the Mexico segment in Mexico. Interesting.




    As you observed, Global Map shows a contiguous segment across the border. But it crosses the border a good bit west of where the detail CNNA maps show the road. Or, more correctly, I guess, the Global Map shows the US-Mexico border a good bit north of where it's shown on the detail maps. If you look at the detail maps, the kink in the road occurs at the border. In the Global Map the border is shown well north of that kink.



    ...ken...
  • I see the following in both Basecamp 4.4.6 and Mapsource.

    I just took a look at CNNA 2009 and I can begin to see the disconnect at 1km zoom level. If I zoom to 20m and use the ruler tool the west-to-east disconnect right at the border measures 83m (~270ft).


    I was looking at CNNA 2009 my copy doesn't Have Mexico so it switches to the base map at the border and I see the ~270ft offset. I don't see it on any of my other maps that is why my earlier question of if it was the full NA version.

    The 2009 map is the only one I have with routing problems. All my other maps will route in BaseCamp. All my other maps look like your 2014-3 map with the Mexican segment extending north across the border.

    If someone has maps between your 2014-3 and 2015-2 it would be interesting to see if the routing problem started at the same time the US segment started going south of the border.
  • Upon further review, the detailed 2014.4 and 2015.2 maps for BaseCamp, which include Canada, still show the large disconnect at the Mexico MX8/AZ SR85 border crossing.

    Well, my display of the same maps shows no such disconnect, so I'm not sure what's going on there...
    So far I have not been able to generate a BC Global Map route that follows the roads. Direct routing only.

    Yep, the Global Map is not routable anywhere AFAIK.

    I do notice one difference between the 2014.3 map and the 2015.x versions. In the 2014.3 version the Mexican segment extends north across the border and overlaps the USA segment in the USA. In the 2015 versions it's the USA segment that extends south across the border and overlaps the Mexico segment in Mexico. Interesting.

    Interesting indeed. And every other US/Mexico border crossing showed this same change between 2014.4 and 2015.2 maps. But if you check the same thing at any US/Canada border crossing, the overlap direction stays the same between those two maps. Ah, the Garmin Mysteries just keep coming...
  • Former Member
    0 Former Member over 10 years ago
    Seems like I wasn't looking beyond the specific secondary US/Mex border crossing in my newby comments. A good night's sleep, a computer reboot, and deletion of user inserted shape points on certain routes clears up many of the issues and questions. The version of BaseCamp that I have provides international base routing for all of Central America that does not necessarily play well with the specific routing desires of US border crossing users.

    Clear as mud now. Thanks. When I find my Nuvi 56, it is not going anywhere near BaseCamp. I like the Nuvi 56 trip routing just like it came out of the box.
  • Former Member
    0 Former Member over 10 years ago
    With that avoidance, is this the result you expect?
  • Former Member
    0 Former Member over 10 years ago
    With that avoidance, is this the result you expect?

    Any map routing that helps avoid accidentally driving over a bridge into Juarez while following US traffic in El Paso is fine. Did that once a half century ago. BaseCamp 2015.2 routing seems to have "that" covered.
  • Former Member
    0 Former Member over 10 years ago
    I drive in that area a lot so I know where you're talking about. Well a lot is a strong term. Two - Three times a year on road trips.