Insane routing

[khark]

On my new XL335 I try to plan a route to a gas station that is about 6.5 miles from my house and it plans a route that is 38.7 miles that tells me to go where there are not even any roads over a mountain range that is about 10,000 feet high.

It doesn't matter whether I tell it to use the shortest route, fastest route or to avoid unpaved roads. It also doesn't matter whether I enter it as a POI or street address. This could get someone who isn't familiar with the area in real trouble.

I planned the same route on my older XL and it does it right. It has V850.2784 map.

Before I posted this I disabled the I.Q Route planning on the XL335 and then it planned the correct route. This is definitely a serious flaw in the software, I wonder how may other erroneous routes it will give me to places I am not familiar with.:argue:

 

[canderson]

More 'unknown' streets? Am starting to wonder about your unit. Please do the following for us...

Pick a spot somewhere near, but not at your home (we don't need for people to know where you live) as the starting point, and then the gas station as the ending point. Make sure it still routes silly. If it does, please advise us of the starting point and the location of the gas station, unless you picked it as a POI - if so, tell us what it's called.

It sounds as though there's errors in the map data near your location - something seriously wrong with the IQ speed data for US89 perhaps? It's possible we can help to sort it out if we can replicate it.

 

[khark]

More 'unknown' streets? Am starting to wonder about your unit. Please do the following for us...

Pick a spot somewhere near, but not at your home (we don't need for people to know where you live) as the starting point, and then the gas station as the ending point. Make sure it still routes silly. If it does, please advise us of the starting point and the location of the gas station, unless you picked it as a POI - if so, tell us what it's called.

It sounds as though there's errors in the map data near your location - something seriously wrong with the IQ speed data for US89 perhaps? It's possible we can help to sort it out if we can replicate it.

I found that nearly all of the POIs near the town of Thayne, Wyoming are too far north by about one half mile or more. I have made and uploaded corrections a few minutes ago. I also find that the street addresses near my house are wrong by quite a lot.

When I want to plan a route from a point on the map, the streets don't show up until I change the zoom factor.

The menus on the XL335 are not nearly as user friendly as the are on my old XL.

 

[Andy_P]

So it was the POI being in the wrong place NOT the routing being wrong all along!
To me your first post read that the destination was right but the navigation instructions took you past it.

 

[khark]

So it was the POI being in the wrong place NOT the routing being wrong all along!
To me your first post read that the destination was right but the navigation instructions took you past it.

It was both that were wrong. It was taking me miles away from the POI where there was not even a road. Also the POIs were wrong by one quarter mile or more.

 

[Andy_P]

It was taking me miles away from the POI where there was not even a road.

If the POI is placed on a navigable road, then a "Navigate to..." it will always (by definition) take you to that precise spot.
But whether that spot is where the place you want actually *is*, is another matter!

If the POI was not placed on a road, it should take you to the nearest point on the map it can on a navigable road.

 

[khark]

I guess I am not precise enough in my description. The POI is about 7 miles southwesterly from the starting point on a road but the planned route went where there was not a road, eventually getting to a road about 15 or 20 miles northerly of my starting point over a mountain range that you couldn't get over even on a horse.

After it finally got to the correct road it then finally got to the POI. The POI was incorrectly located on the map but only one quarter mile or so from the correct location which still does not explain why it would route me 38.7 miles to a POI 6.5 miles away.

The beginning point is 454 Alta Dr. Star Valley Ranch, WY and the POI is Maverik Country Store in Thayne, WY.

 

[canderson]

What happens if you specify 160 N Main St, Thayne, WY as your destination? That's the address for the Maverik in Thayne. FWIW, here's how the planner on TomTom's own servers manage it - seems OK.

 

[khark]

What happens if you specify 160 N Main St, Thayne, WY as your destination? That's the address for the Maverik in Thayne. FWIW, here's how the planner on TomTom's own servers manage it - seems OK.

That is the wrong location. The store is south to the road that runs all the way to the east. It is on the northeast corner of the intersection of Hiway 89 (Main St.) and Dana St.

As I said before the POIs in this area all seem to be off by about this amount.

I have attached pictures of a route it gave me to Alpine Market in Alpine, WY.
Error 1 shows a weird routing it calculated. Error 2 is the almost correct route.
Error 3 shows how far off the location of Alpine Market is, the correct location is in the upper left where the little marker is at the southeasterly corner of the intersection but look where the routing shows I should go.

 

[drg560]

another insane route

If I put in Monteagle, TN and want to go to Athens, AL instead of going down HWY 64 all the way to I65 and into Athens it has me take a round-a-bout route that takes at least a hour longer. I just updated my map last night, 11/22/11. I have read other posts and lots of people are having problems with insane routes. I know that the route is wrong so it's not a problem but what if I didn't know any better. The cost of the update and the uncertainty of the devices routes don't equal out. How can I trust that I am getting the right directions? I have a TOMTOM ONE 3RD EDITION

 

[alfie67]

If I put in Monteagle, TN and want to go to Athens, AL instead of going down HWY 64 all the way to I65 and into Athens it has me take a round-a-bout route that takes at least a hour longer. . .

Did you have Fastest Route as your choice? I plugged in your route on mine, and it shows 1:56 and 106 miles, going via Hwy 64 and I65 . . . ?

 

[dhn]

If I put in Monteagle, TN and want to go to Athens, AL instead of going down HWY 64 all the way to I65 and into Athens it has me take a round-a-bout route that takes at least a hour longer. I just updated my map last night, 11/22/11. I have read other posts and lots of people are having problems with insane routes. I know that the route is wrong so it's not a problem but what if I didn't know any better. The cost of the update and the uncertainty of the devices routes don't equal out. How can I trust that I am getting the right directions? I have a TOMTOM ONE 3RD EDITION

I do not believe that model has IQ routing in its map data. That can make a **world** of difference in route selection .......... and apparently has in this case.

 

[Andy_P]

mvl's Hardware reference chart reckons the XL335 does have IQ routing.

Also I think that without IQ Rouring, a TomTom picks the more direct routes. Adding IQ means thatthe TomTom knows about the jams on the major routes and creates more devious ones to avoid them.

 

[drg560]

I had the fastest and the shortest picked and both were the same. I read on here somewhere to do a return to factory settings. I did and it now shows the more direct route.