Routing problems with the Nuvi 2460

 

I have a Nuvi 2460 and having problems with routing.

Here's an example. I select a route from Petaluma Calif. (starting from US101 and Washington St) to the Bodega Bay RV resort just north of Bodega Bay. In this case once the route gets into the small town of Bodega Bay instead of staying on US 1 it veers off on a side street and then reconnects with US 1 before the RV resort. The problem is that the street it picks would be a real problem if not impossible when pulling an RV.

I have a similar problem when routing the reverse, only it picks a different local street that would be extremely difficult to follow.

The old MapSource did not do this and neither did my Nuvi 765T.

When Basecamp came out as the replacement for MapSource I had the exact same routing problems. To fix the problems I had to create a bunch of favorites and force the route to go where I know it's safe and stays on major roads.

I have had similar problems with the 2460 in other routings such as from Reno NV to Chula Vista RV Resort in Chula Vista CA. It's as if the routing engine picks the shortest distance at the expense of staying on main highways and I can't fix it.

The just released version of Basecamp seems to have fixed the problem but the new software version for the 2460 did not.

In these two examples I pretty much know where I have to go but it scares the heck out of me when planning a trip I'm not familiar with.

Am I just not versed enough in the 2460 or are others having similar problems?
Thanks for your help.

traffic

Disable the traffic and see if the problem goes away.

--
Garmin 38 - Magellan Gold - Garmin Yellow eTrex - Nuvi 260 - Nuvi 2460LMT - Google Nexus 7 - Toyota Entune NAV

Maybe overkill--and not what you want to hear, but...

This may be overkill and unless you're in the market for a replacement GPS, you don't want to hear this, but one option that may work when in a large RV or pulling a 5th wheel or mobile home is to buy a trucker's nuvi like the 465LMT or dēzl 560LMT.

It offers:

nüvi 465LMT provides specialized routing to support truck-related restrictions in the U.S. and Canada (customizable by height, weight, length, width and hazardous materials).

and one would think this would avoid your side street issue.

Thanks Traffic...I did

Thanks Traffic...I did disable traffic and no joy.

recreate

regor33 wrote:

Thanks Traffic...I did disable traffic and no joy.

I'll try to recreate the route with my 2460 and do a simulation and will get back with what my results are.

Ok I did the Reno to Chula Vista Resort and it has me going on main HWY no side streets at all around 565 miles
395 toward San Bernandino
left to I-215
to I-15 S
then city streets to the resort

Check your avoidances

--
Garmin 38 - Magellan Gold - Garmin Yellow eTrex - Nuvi 260 - Nuvi 2460LMT - Google Nexus 7 - Toyota Entune NAV

You're right!

flaco wrote:
regor33 wrote:

Thanks Traffic...I did disable traffic and no joy.

Ok I did the Reno to Chula Vista Resort and it has me going on main HWY no side streets at all around 565 miles
395 toward San Bernandino
left to I-215
to I-15 S
then city streets to the resort

Check your avoidances

Mea Culpa your are correct it does route correctly from Reno to Chula Vista RV. I either have a false memory on problems with that route or they fixed it. I will assume I had a false memory.

My problem with the 2460 avoiding a small but critical section of US 1 on the Bodega Bay route persists so maybe its just a quirk in that area. As I said the older version of Basemap had the same issue but the new one doesn't.

I can live with that... I was convincing myself the problem was endemic on the 2460. It appears I'm wrong.

Thanks Flaco for taking the time to help me out.

CraigW ... I learned about

CraigW ... I learned about these units after I bought the 2460. In fact I noticed a fellow in the spot next to me in the Bodega Bay RV had a garmin. I asked him if he had the same routing problem into Bodega Bay and he said no. I asked what unit he had and he began to tell me about his unit being for large trucks.

I appreciate the suggestion and if I continue to have problems I will look into a truck unit. A 33 foot 5th wheel and a long bed crew cab Ford is too big for local streets to save a few feet in the route.

As it turns out I am probably wrong and this problem is limited to a short section of US 1 in Bodega Bay and not an overall flaw in the routing engine.

avoidance

regor33 wrote:

My problem with the 2460 avoiding a small but critical section of US 1 on the Bodega Bay route persists so maybe its just a quirk in that area. As I said the older version of Basemap had the same issue but the new one doesn't.

I can live with that... I was convincing myself the problem was endemic on the 2460. It appears I'm wrong.

Assuming the problem persist in Bodega Bay you can make the 2460 avoid a street, a road, a Hwy or a general area by creating a custom avoidance or just ignoring the 2460 and continue on US 1 and if you have the myTrends™ enabled the 2460 will learn your preferred route to Bodega Bay.

We all know most of the units in the market are designed with automobile use in mind and drivers with big rigs need to be extra careful with the directions the GPSr is displaying when you are not familiar with the area of travel.

What GPSr manufacturers needs for those units to be “big rig” friendly is to add an avoidance for city streets just like the have for Tolls and Hwys, the unit then will avoid placing you on city streets unless it is absolutely necessary.

--
Garmin 38 - Magellan Gold - Garmin Yellow eTrex - Nuvi 260 - Nuvi 2460LMT - Google Nexus 7 - Toyota Entune NAV