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?
  • What is considered a 'correct' route varies from person to person. It also varies depending on the routing and avoidance settings you have set, and the map you're using. Without knowing what you have set it's difficult to comment on what you believe is a 'goofy' route in Basecamp.

    I can't quite see what activity profile you have selected, that sets routing and avoidance choices, but it doesn't look like the normal driving one, so that would be the first potential problem.
  • Looks like you have RV activity profile selected. Try changing the profile to Driving, and also check your avoidances: Edit/Options/Activity Profile/Routing
  • Former Member
    0 Former Member over 10 years ago
    Profile matters very little. Basecamp seems to simply fail to find the correct route.
    For exercise, I unchecked all "avoidances", set profile to "driving" and "shortest route".
    Basecamp gets even worse when using the "driving" profile.

    If I add a waypoint for "Lukeville" on the American side of the border, Basecamp will then proceed with correct routing.
    But simply telling Basecamp to go from point A to point B is a fail.
    Here is a screenshot of how the route search is set up:


    And this is a screenshot of what the route planner should have produced:
    (I had to add waypoint town in order to achieve the correct route with Basecamp.)


    Original point A to point B search:


    Can anyone try this trip plan on their Basecamp and see if it works the same?
  • Which map are you using?

    I did a test using City Navigator North America and attached the screen shot.
  • I only have an OSM map and that routes fine. Looking at it though I wonder if AZ85 has a seasonal closure on it? Could that be the issue?

    Edit: Just seen Dave's post, seems like it's an issue with the OPs map/settings somewhere. Wonder if it's just the basemap selected?
  • Tested using Mapsource v6.16.3 and Basecamp 4.3.5. Both using City Navigator North America 2015.2. The Mapsource test used the [EDIT] "Car/Motorcycle" profile with the "Auto-routing" route style.[/EDIT] In Basecamp I used the Driving profile and set the avoidances to match those in the Mapsource profile.

    See the attached screenshots: Mapsource gets it right on the first try with no adjustments.


    Basecamp is just bizarre using the same mapset and the same settings.


    ...ken...
  • So if it works for Dave something must be different between his setup and yours. Basecamp version maybe, since 4.3.5 is an older one?
  • I only have an OSM map and that routes fine. Looking at it though I wonder if AZ85 has a seasonal closure on it? Could that be the issue?

    I just checked the Basecamp settings I used in the Driving profile and I had intentionally unchecked the "Date and Time Closures" avoidance in case there might be a border crossing issue. Interestingly, I have it checked in Mapsource (forgot to uncheck it) and it still worked fine.

    ...ken...
  • I played around with settings after seeing SUSSAMB's question about seasonal closure and tried the basemap. Basemap gave a straight line. Date and Time Closures didn't change the route so I started checking other options and found that State Highway avoidance will route like the OP shows.
  • In my example above I have "State Highways" avoidance unchecked in Basecamp so that's not it.

    ...ken...