It is the 2013.10 map that gives wacky routing

I've noticed for years that sometimes the routing is just not logical. This is my 2nd GPS and I don't make an important trip with a mapquest or AAA TripTik as a backup.

I replied to your previous post that I was having the same issues on the SI expressway with my Nuvi 765T, and I came to the same 2013.10 problem map conclusion. Did you fix your problem? If so, how (reinstall old map, hard reset, etc.). But I was also wondering if new installs of Nuvi Firmware could have contributed to the wacky routing? I don't know if firmware has any role in the routing algorithms, but I thought I'd throw the idea out there for comments.

Since I posted last, I sent a note to garmin Cartography about this issue and their reponse is pasted below:

Good afternoon,

I have an idea or two from my part in the investigation—from looking at the different map versions and some different buried attribution between the versions. My thoughts may or may not hold water in the end, but all appropriate parties are looking into it deeply now thanks to your mentioning it.

Best regards,
Loy

Garmin Cartography Administration
1200 E 151st Street
Olathe, KS 66062

I am having a similar problem to all the others on my nuvi 3590. It will route me past the street of the place I want to be going, then backtracks me on another to my destination turning onto the street I just passed. As others I have everything un-checked. Strange!

Back when I first got my 765, I had a situation where the root of the problem was a divided highway. When routing it would take me past my destination on my left to the end of the devided highway where it would have me make a u-turn and return on the other lanes of the divided highway to my destination now on my right.

Spoke with Navteq and they agreed that there was a major intersection on this divided highway where I could have turned to the left directly into my destination.

My thought was that it was the divided highway designation that was driving the error.

3590LMT and it isn't acting strang. Works like it is suppost to. Went to Louisiana and back with no problem.

I guess that may have been the problem. If I would have turned onto the street that the store was on (a right turn) I would have to cross the divided street into the parking lot (left)via one of the pull out left turn lanes. Instead it brought me all the way around the block and entering it without crossing traffic. Still it was kind of a strange way to get there.

Divided Highway. Sometimes when the McDonalds is on the far left-hand side of the intersection, my 1490 routes me to the next intersection for a u turn. Of course I know that I can turn and enter the McDonalds from the side street.

I sometimes drive the same route and get different directions.

BTW. Did not know there was an update. Maybe a good thing

Here's the latest excerpt from my communication with Garmin regarding being routed off the Staten Island Expressway onto local routes for no reason (I re-posted this in other related thread):

We have the data which will be 2013.30 hosted now, and it has the attribution change I talked about before which changed routing behavior.
I just gave its early, rough self a test next to 2013.20 to be sure. What will make up 2013.30 does behave differently/better.
What makes up 2013.20 is the same there as 2013.10.
Even if I had caught my error, it couldn’t have been changed in time to get into 2013.20. By then, all of it was already in the hands of the paperwork gods.
Too many mapping windows & programs & versions open at once…
Best regards,
Loy
Garmin Cartography Administration
1200 E 151st Street
Olathe, KS 66062

No doubt you still think the 1200 baud modem is the best too. It was all great at the time but now who would want to go back?

Cheers

I had a very similar issue with my 2595 when I first got it in February of this year. It came with map version 2012.30 and I immediately installed 2012.40.

On one of the very first trips I used it I was travelling along RT3 south in Lowell, MA and was approaching I495. My next leg was 495S. The unit tried to route me to 495N, then RT3 north and then to the 495S exit. The normal RT3 south to 495S exit has been there for at least 40 years. Everything was turned off including traffic. Other folks simulated or reported the same thing. It did the same thing every time I made this trip. I used my old 255W one trip and it routed me the correct way with no problems. I reported the issue to both Garmin and Navteq who advised they were unable to duplicate it. (in other words: OE)

The issue went away when I installed map version 2013.10 on the 2595.

After I did 2013.10 on my 1450LMT it started calculating distances incorrectly. Bel Air, MD to Ashtabula, OH calculated to 286 mi. Instead of the app. 393 miles that it is.

Thanks for the info. of all the posts here. I have not updated my maps yet for this cycle. Maybe I should wait.

Here have a Zumo experiencing these issues?

I had been having the exact same problem with mine as well. Ugh, I am glad to know that Garmin is trying to fix this issue.

My Nuvi has had me make 4 rights to get on the same road I was on to get to a destination. Very strange.

Problem solved.
I loaded 2013.30 last week. My Nuvi 765T now took me on a straight run on the Staten Island Expressway, from the Goethals bridge to the Verrazano bridge, without suggesting any local road detours at all.

Just updated 2013.3 2 days ago on 1350, notice the screen go blank for less than second during navigation.

If this happens a lot or becomes a problem for you, try a hard reset:

http://www.poi-factory.com/node/26136

Many folks do a hard reset after each firmware or map upgrade although I'm not among them. I'll do a reset only if I see freezeups or other issues.

I hadn't updated my gps in a while so today I decided to update to the new map, which I did. then I went to garmin dashboard and it said that I should update the usb drivers, which I did. Now my gps will not turn on. please help me.

Since USB drivers are installed to the computer, there should be no effect on the GPS. More than likely, it was something that occurred during the map update, or as already suggested in another thread, a need to fully charge the GPS battery, that is causing your problem now.

Did the map update appear to go OK; i.e., download, prep, transfer to GPS over a period of possibly a couple hours? Did your computer go to sleep during the process? Did you "safely disconnect" the GPS or "eject" it at the end of the map and extra software update?

Just to be sure, does you GPS not turn on when it's disconnected from the computer? If there's a SD card installed, try removing the card when it's off, then see if the GPS will start up. (Disregard the SD card suggestion if your map update was installed to the SD card.) Is the problem with your 765T, 650 or something else?

Does nothing happen when you try to power up the nuvi or does it freeze at some early point?

Your return route my have one way streets or places your turn is restricted,.

I recently entered an address in Grasonville, Maryland and the GPS wanted me to travel to Pennsylvania - very weird.

As mentioned in another post. I did the latest map upgrade, and 8 hours later went across country....
Chicago to Mountains of N.C.

We live on Norther Suburbs of Chicago, and as we routed through Chicago, I also got the same "Get off at every stop" Issue...

It was the first route of the new Map Firmware.

I stopped the route... Selected it again, and after calculating the route a 2nd time... No further issues... Throughout the trip, and we used the Garmin multiple times each day to get from location to location, and then back to Chicagoland...

That one 'burp' was the only issue of the entire trip, and the new Maps worked correctly every time but this one time... Which was the first route after the Map upgrade....

I have also noticed crazy routing with the new update. I am not happy about it.

CraigW,
Thank you. I called Garmen customer service and they had me plug it into my car mount. It came on immediately. Don't know what happened but I am relieved that it is now working. I love my 765t and would hate to have to get a new gps.