Weird unroutable road

[mvl]

I just came across a strange issue:

There's a shortcut road in my area that tomtom refuses to use in routing. It's as if the route doesn't exist, as the routing will go waaay out of the way to avoid it.

If I use mapshare and block all alternatives, it says "no route found", refusing to route down the road.

However, if I do "find alternative" and set a spot on the road as a "route via" waypoint, tomtom will happily route down it. And it will show this path as shorter and faster than its original calculation.

To see what I mean, prepare a route from 129 Christina St to 398 Needham St, in Newton, MA.

About 5 years ago this road was a dirt road, that may have something do to with it. But I tried the "never avoid unpaved roads" and tomtom still avoids it. And I tried the "ask me about unpaved roads" setting and tomtom didn't ask me.

Anyone know why this could be?

Tomtom720, Map North_America_2GB v830, app 8.350

 

[kubel]

I have a road near my house that was recently paved, and my TomTom ONE 3rd Edition thinks it's dirt. So it will route me through a long winding neighborhood just to avoid as much of the road as it possibly can. And it prompts me whether or not I want to avoid dirt roads, too. I select "No", and it still avoids the road. I think it's a glitch that affects many models.

 

[canderson]

I just came across a strange issue:

There's a shortcut road in my area that tomtom refuses to use in routing. It's as if the route doesn't exist, as the routing will go waaay out of the way to avoid it.

What kinds of turns are necessary in order to navigate that particular route? You may be seeing something similar to what I was mentioning the other day. I'm still trying to get back to that area to duplicate it, but haven't had a reason. I thought at the time it was an aversion to a particular left turn. It routed me a good mile out of my way for no reason that I could discern, and a U-Turn wasn't involved. It did, however, require a left turn on a busy road to start the process -- but a very "doable" and legal one. As far as I could tell, the maps indicated no divided road or anything else that should have impeded it.

As an aside: That's something that the TT is usually pretty good at detecting, but is not perfect = knowing where roads become divided by medians that will prevent a left turn. There are always instances where some really abnormal routing occurs due to this, but that wasn't the case in the instance mentioned above.

 

[mvl]

The scenario is a straight drive, 1 block with 1 left turn at the end.

If the destination is changed to 298 Needham street, it becomes a 1 block drive with one right turn, and exhibits the same issue. Feel free to try it on "plan route".

One thing I noticed is if I zoom waaay in, the road is narrower than all other roads in the area. Perhaps it is an issue with the unpaved road preference not working. But unlike kubel, the tomtom doesn't even ask me if I set the unpaved preference to "prompt me"

Can someone identify a definite unpaved road in the tomtom map, I'll see if I get the same behavoir on my device there?

 

[mikealder]

What does the device do if you use the other route planning options such as pedestrian or cycling? - Mike

 

[mvl]

Fastest and Shortest avoid the road. Bicycle and Walking take the road. Fastest and shortest (with a waypoint on the road) also take the road.

Why would a "fastest" with a waypoint on the road still take it?

Is there any way I can mapshare this road so that tomtom thinks cars can drive it?

 

[dhn]

What if you were to adjust the speed limit on the road to some high amount? Think TT would consider that in its routing, then?

 

[pianoCM]

It maybe or used to be either one-way (toward Bernard St) or blocked at (Bernard St intersection) or the Highland Ave/Needham St is a divided route and the destination happens to be on the other side.
Don't know why but it's definitely weird.
Google Maps does the same.

 

[mvl]

Usually, if there are turn restrictions, the tomtom will say "no route found". It will route to a blocked road if you put a waypoint there.

I tried blocking the road. Then unblocking it. Then raising it to 150mph. Still no success.

Any other ideas? This is a weird road class, I've never seen this type of issue before.

 

[pianoCM]

Well, there's something for those Tomtom's coding guru work on, fixing that little glitch or finding a new algorithm. In the meantime, your knowledge is far better, m8

 

[ChillyWilly]

Another Weird unroutable road

I also have a similar road on my way to work that I take everyday. Its only a small piece of road, it will only take it if I select Bicycle or walking.

Navigate from 10655 NW 58th St. Miami, FL to 6298 NW 107th Ave, Miami, FL and it will make you go around, Now navigate from 10655 NW 58th ST, Miami FL to 6098 NW 107th Ave, Miami Fl and it will route you correctly.


Here are some pics from Route Planer, does the same thing !!


How to report this?

Thanks,


TomTom XL340S with 830 map

 

[dhn]

It may be that the map data 'thinks' that the route it doesn't select is 1-way the wrong way (which walking and bicycling routing ignores).

So, you can use mapshare to define that road section as 2-way.

 

[ChillyWilly]

Yeah, Thats what i thought, but i tried all that stuf, I checked to make sure that both direction were enabled in diferent spots, just to make sure. I also chaged the speed limit and I also tried to set my tomtom to travel via unpaved roads just in case and i get the same results. Actually if I tell it to navigate via that section of road then it will use it.

Same as the error that the other user was having, prety much the same situation.


Thanks for your repplys

 

[dhn]

You can try to change the setting in Home to not use any mapshare corrections at all, then see whatt route gets planned.

But if you select 'fastest', I don't think you'll ever see the unpaved road selected.

 

[zengshengliu]

go to Map corrections -> Corect a map error -> Change turn restrictions -> and select the intersection of NW 107th Ave and NW 62th St and see if someone accidently change to turn restriction of that intersection to not allowing go straight on
This might be the problem

 

[ChillyWilly]

Hi,

Thans for tip, I tried but everything was ok. The weird thing is that the online route plnner does the same thing. Might be a programing issue.


Thanks,

 

[Tim25]

I went back to the original unroutable road reported by MVL. I looked at Christina St in Google maps. It caught my eye that the "unroutable" portion of Christina was drawn thinner than the starting point on Christina. I opened this street in openstreetmap.com...In edit mode, you could see that the starting point of Christina was listed with a width of 12.2. The unroutable portion is listed as 9.8....Could there be a threshold in the TT routing algorithm which avoids narrow roads?

If those numbers are incorrect, you might try sending an update to TT/TeleAtlas (and updating in OSM).

 

[Tim25]

I took a look at the routing problem in Miami reported by ChillyWilly...If I try the same route on my TT, I get a different round-about route than ChillyWilly, but still very out of the way. I looked further at the roads....He is trying to route to an address on NW 107th Ave north of NW 62nd St. North of 62nd St, it is interesting that their is the "real" 2 way road: NW 107th Ave, but there is also a parallel 2 way road which is also called NW 107th Ave on the map. If I look at this parallel road on Google Maps satellite view...it looks more like a dirt road than a real road.

I'll bet that having 2 different roads both named the same is causing confusion for the routing. If the parallel road is a real road, I would change the name on that road to see if that solves it. If the parallel road is not a real road, I would block it, change the name to "unnamed rd"....and report it for deletion.

For that matter, NW 62nd St looks more like a dirt path in Google Maps satellite view than a real road.

 

[mvl]

I was playing around and was able to isolate this "unroutable" road class.

If you disable IQroutes and do a route demo, this road class drives at 20mph. All other road classes drive at 31mph or faster.

So there is something in the logic that completely/incorrectly avoids this 20mph road class even if it is the fastest and shortest route. The only workaround is to set a "travel via" waypoint on the road.