Goofy Garmin? Routes like a drunk.

oops sorry ... but it was your call lol

I think though the automatic update has been removed, I had to manually update to 4.4.6

Hmmn ... so why does Dave's work correctly yet yours and the OPs doesn't :confused:

I have no idea. Dave didn't say what profile, what avoidances or what map he used to get it right. I can't find any profile that works except the Trucking profile, no matter what I do to the avoidances in the other profiles. And I don't even have to tweak the Trucking profile. It just works.

...ken...

Looks like it might be something in the map data. The Driving profile gets it right with CNNA 2014.3 but gets it wrong in 2015.1 and 2015.2. So it looks like Garmin has introduced something in the CNNA 2015.x series that messes with Basecamp's ability to route properly. I don't have 2014.4 to test with so I can't verify exactly when it starts.

Interestingly, it can't even calculate a route with CNNA 2009 no matter which profile is selected.

EDIT: testing with Basecamp 4.4.6.

...ken...

Just out of curiousity I went back and checked with Mapsource. It gets it right with the Car/Motorcycle profile unmodified in CNNA 2014.3, 2015.1 and 2015.2. So whatever change is messing with Basecamp between CNNA 2014.x and 2015.x seems to have no effect on Mapsource.

However....

Mapsource is also able to calculate a route using CNNA 2009, which Basecamp can't do. But Mapsource gets it wrong with CNNA 2009. It does the same thing Basecamp is doing with the 2015.x maps; it shoves the route way west over to highway 95 and MEX-2.

Wierd. But there might be something useful to be learned.

...ken...

I notice that the expected route goes through the Goldwater Air Force Range and the Organ Pipe Cactus National Monument, whereas the BC route bypasses those. I know the routing algorithms use data other than pure speed/time. I wonder if it tries to avoid military bases (authorized personnel only) or national parks (fee to enter)? I'm not saying that either of these features are restricted or require admission, I don't know. But maybe the default routing is to avoid those? That said, this is a case where the route it takes is twice as far/long as the short way, so I'm surprised it doesn't override the default. Also, earlier maps may not have classified one or the other of those features, so it may be a change in map data, not the BC routing algorithm.

To the OP, this is a good lesson that you can't totally depend on BC or any other GPS to work 100%. I always plan routes in BC and if a route doesn't look reasonable or what I expect, I duplicate it and modify it to compare alternatives, then decide what I like best and use that. It doesn't really create problems for pre-planned routes, but it does create surprises when you're on the road and are just using your device to create a new route.

I have no idea. Dave didn't say what profile, what avoidances or what map he used to get it right. I can't find any profile that works except the Trucking profile, no matter what I do to the avoidances in the other profiles. And I don't even have to tweak the Trucking profile. It just works.

...ken...

Driving using City Navigator North America NT 2013.3. I tried the Trucking profile after seeing your post and I get the same route as Driving as long as State Highway is not checked. If I check It I get a longer route but it's different than the one I get checking it in Driving. I can check everything under Feature Type Avoidances with no change. Under Road Type the only options that change the route Interstates small change around Phoenix, Major Highways will send the route farther east and State Highways sends it way west like the OP shows. If I check Major and State Highways it will go north and loop to the east.

As SUSSAMB said I think you are OK on the auto updates. I had to agree to let it update to 4.4.6.

Driving using City Navigator North America NT 2013.3. ....

So that makes it look even more likely that something was introduced into City Navigator NA around the start of the 2015.x map series.

As SUSSAMB said I think you are OK on the auto updates. I had to agree to let it update to 4.4.6.

That's good to know. Thanks.

...ken...

However....

Mapsource is also able to calculate a route using CNNA 2009, which Basecamp can't do. But Mapsource gets it wrong with CNNA 2009. It does the same thing Basecamp is doing with the 2015.x maps; it shoves the route way west over to highway 95 and MEX-2.

Wierd. But there might be something useful to be learned.

...ken...

Interesting! I tried CNNA 2009 and get a straight line like its not a routeable map. I tried unchecking all avoidances with no change. However if I create a route that ends before the border it routes OK.

Interesting! I tried CNNA 2009 and get a straight line like its not a routeable map. I tried unchecking all avoidances with no change. However if I create a route that ends before the border it routes OK.

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...

I'm using Basecamp 4.6.6
I have not tried the "Trucking" profile yet - but that would make sense because the highway 85 route is an international trucking crossing.
It is also a major route for snowbirds and Arizonan's seeking warmer weather during the winter.

Thank you all for troubleshooting this inegma.
I was hoping to move on from Streets & Trips onto more current mapping software and thought that Garmin/Basecamp would be a solution.

Microsoft quit making/updating Streets & Trips and left it crippled - S&T fails to produce a standard GPX file!
Does anyone have a good suggestion for which trip planning software might actually work and be compatible with the Nuvi 2699LMT ??