Goofy Garmin? Routes like a drunk.

AAAARRRRRGH! I just removed 2014.4 from my system two weeks ago...hadn't needed it for six months....:mad:

But then, I NEVER trust ANY Garmin map to autoroute correctly anymore and always add vias, so I will probably not see this anomaly.

Garmin should have bought Streets & Trips and used it as a base from which to develop Basecamp.
They would far ahead.

How can you tell about this break (discontinuity)?

How can you tell about this break (discontinuity)?

Well, in this particular instance there is a visible 263 foot offset along the border between the southernmost end point of the US_Arizona State Route 85 vector and the northernmost start point of the Mexican MX road vector in both the Garmin CNNA NT 2014.4 and 2015.2 maps, so I jumped to a new user conclusion.

However, C14_Rider, in following up on other posts, and yours in particular, in this thread it appears that there are other "crooked road" routing issues requiring added waypoints as well. So now I need to find where I put the seldom used Nuvi 56 to see how it behaves across Yosemite's California SR120 with the same maps. It does not seem that Garmin has closed SR120 merely for winter snow, but at first glance in January it might seem so.

I was also tempted to think there was a break in the 2015.x versions. But the route down highway 85 works fine in Mapsource using the same maps. And selecting the Trucking profile in Basecamp also works.

...ken...

Well, in this particular instance there is a visible 263 foot offset along the border between the southernmost end point of the US_Arizona State Route 85 vector and the northernmost start point of the Mexican MX road vector in both the Garmin CNNA NT 2014.4 and 2015.2 maps, so I jumped to a new user conclusion.

Is this with City Navigator North America NT or with City Navigator North America NT Lower 49 States?

Is this with City Navigator North America NT or with City Navigator North America NT Lower 49 States?

I'm using the full North America version that includes Canada, Mexico, Alaska, etc.

...ken...

Well, in this particular instance there is a visible 263 foot offset along the border between the southernmost end point of the US_Arizona State Route 85 vector and the northernmost start point of the Mexican MX road vector in both the Garmin CNNA NT 2014.4 and 2015.2 maps...

39_steps -- I'm not trying to be difficult, I'm just trying to understand... On my display of either of those maps, the connection between Rt 85 and the Mexican connecting road which is Benemerito de las Americas, which goes on to connect with the MEX road system, appears exactly continuous even at the 80 ft zoom level, and with the shaping point mentioned previously, the route happily makes that transition across the border seamlessly. So how do you see this 263 ft offset?

39_steps -- I'm not trying to be difficult, I'm just trying to understand... On my display of either of those maps, the connection between Rt 85 and the Mexican connecting road which is Benemerito de las Americas, which goes on to connect with the MEX road system, appears exactly continuous even at the 80 ft zoom level, and with the shaping point mentioned previously, the route happily makes that transition across the border seamlessly. So how do you see this 263 ft offset?

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.

However, the Global Map does seem connected, if not road-routable, on either side of the border. So far I have not been able to generate a BC Global Map route that follows the roads. Direct routing only. It is possible that the map which I was permitted to download due to a purchase of a Nuvi 56 in 2014 is different from maps supplied to support other device models. I am not yet checked out on Trip Planning on the (Win7) computer with BaseCamp, as the Nuvi 56 device trip planner was much simpler to learn and met my expectations.

I