Goofy Garmin? Routes like a drunk.

I don't really believe this is just a Base Camp issue, seems more likely to be also linked to a map issue. It'll be interesting to get some input from the Base camp developer once he's had a look. I've used BC for years and rarely seen an issue.

With Mapsource or Basecamp?

In Mapsource I get a straight line until I hit the "Recalculate" button in the route properties and then I get the route like the original poster reported getting in Basecamp. So CNNA 2009 appears to have routing data in Mexico but something that stops it from going south to cross the border on highway 85. The route follows MEX-2 back east along the border and then drops south at the point where highway 85 comes across the border. So whatever Mapsource doesn't like in CNNA 2009 is happening north of the border, just like happens with Basecamp and the 2015.x series.

I have not fiddled with the routing options/avoidances in Mapsource to see if I can force it back to the correct routing as it does for the 2014.x and 2015.x maps.

In Basecamp when I hit the "Recalculate" button the recalculate dialog comes up and it tries but then the progress bar turns red and it says "There was an error calculating this route." This happens with all relevant profiles with CNNA 2009 selected.

If I put a waypoint at Lukeville and end the route there, Basecamp works fine, as you say. [with CNNA 2009]

If I just insert Lukeville into the original route, Basecamp spends a long time recalculating and eventually comes up with a route that goes down to Lukeville, doubles back north to Why, then way east to Tucson, down through Nogales and back west to Puerto Penasco. [with CNNA 2009]

...ken...

With BaseCamp.

I tried adding a point in Lukeville to the original route. It routes to that point and then gives me a straight line to Puerto Penasco [with CNNA 2009]. It recalculates fast so I'm getting a little different results then you are but not correct. I get this same routing With no avoidances checked or with them all checked.

I don't really believe this is just a Base Camp issue, seems more likely to be also linked to a map issue. It'll be interesting to get some input from the Base camp developer once he's had a look. I've used BC for years and rarely seen an issue.

I don't think it's a BaseCamp error ether. If it was a BaseCamp error I wouldn't think it would work with some maps and not others.

Does anyone have a good suggestion for which trip planning software might actually work and be compatible with the Nuvi 2699LMT ??

Personally I would recommend not giving up on BC just based on this one anomaly. My hunch is it's based on the map data thinking the monument area is a national park, which it will often avoid since those roads often require fees and are also often closed overnight. I have created literally thousands of routes using BC and not run into anything like this. I'd be surprised if in the long run it didn't turn out to be satisfactory, even if not perfect. I am not a Garmin employee or apologist.

Personally I would recommend not giving up on BC just based on this one anomaly. My hunch is it's based on the map data thinking the monument area is a national park, which it will often avoid since those roads often require fees and are also often closed overnight. I have created literally thousands of routes using BC and not run into anything like this. I'd be surprised if in the long run it didn't turn out to be satisfactory, even if not perfect. I am not a Garmin employee or apologist.

That is a good hypothesis. And a good quirk to know if true.
When I have time tomorrow I will try something similar that routes through Mt. Rainer National Park and see if it produces similar results.
Thanks for the help and encouragement.

Personally I would recommend not giving up on BC just based on this one anomaly. I have created literally thousands of routes using BC and not run into anything like this. I'd be surprised if in the long run it didn't turn out to be satisfactory, even if not perfect. I am not a Garmin employee or apologist.

Agreed. I've also used BC for years and it's migrated into a very stable and useful planning tool. I use it for planning every trip I do, both driving and hiking, with a bit of geocaching thrown in occasionally. I haven't found anything better.

Agreed. I've also used BC for years and it's migrated into a very stable and useful planning tool. I use it for planning every trip I do, both driving and hiking, with a bit of geocaching thrown in occasionally. I haven't found anything better.

I also agree. I've used different planning tools over the years. BaseCamp is my tool of choice.

Good confirmation. And it's really map-dependent. I have two maps selectable in BC 4.4.6, CNNA NT 2014.4 and 2015.2. Using 2014.4, your original route does go the direct route the way you expected it to using any profile. Using 2015.2, I can't get it to go the short way no matter what profile, not even trucking, unless I add that via point that forces it the short way. Others using other maps have different results like driving no, trucking yes. So there is some map data or road classification or something that does change, sometimes not correctly.

If you know of such an error, it can be reported, most easily from BC Help/Report Map Error. But don't hold your breath, it takes forever for map errors to get changed. That's my biggest disappointment with Garmin maps vs Google maps, Google is way more up to date. But it's OK, I just use Google Earth to check sometimes where I have questions about a Garmin map "curiosity".

In the end, the Insert tool used to add shaping points to customize routes will become your friend and constant companion. No worries... :cool:

It's not just the map data. It's also in Basecamp's routing calculations. With the newer 2015.x maps that give BC heartburn, Mapsource gets it right. So clearly it's a combination of map data and routing algorithm.

...ken...