Route updates while driving

[Bigbear3764]

Have you looked at all segments and connections? A wrong one way, red arrow, incorrect cities, states, countries in the middle will re-route. Also try zooming in on live map to see if there is something obvious. I have seen problem on live map, gone to edit it, and it looked normal. I had to wait for map update to go thru, someone already fixed it.


Sent from my iPhone using Tapatalk

[AggieJM]

Does the ghost road issue actually cause the segment to be unroutable? After looking at this a little longer, and finding ghost segments in other areas of 77 that didn't have routing issues, I was wondering if this was actually the problem that screwed up my routing results. Can someone check out this area of the map and see if they see any issues that would prevent routing from south to north on 77?

https://www.waze.com/editor/?zoom=3&lat=30.52322&lon=-96.98792&layers=BFTFTTTFTTTTFTTFTTTTFT

When I tested on LiveMap, if my origin was north of 77/Co Rd 412, it would route me north to get to Dallas. If my origin was south of 77/Co Rd 417, it would route me south on 77 which is incorrect.

Just wanted to make sure the ghost issue wasn't hiding another issue.


---
Sent from my iPhone using Tapatalk (blame my phone for any typos)

[AggieJM]

I was using Waze last night on my drive back to Dallas.

When I started Waze, I was on US Hwy 77 just south of FM1624 as shown here on the map:

https://www.waze.com/cartouche_old/?zoo ... FFFFFFTTTT

The fastest route back to Dallas is to take US Hwy 77 north to Waco, then pick up I-35 north into Dallas. The route that Waze generated had me go north on US Hwy 77, then turn onto State HIghway 21. I ignored the turn onto State Hwy 21 and continued north, so Waze recalculated my route. The new route that it came up with had me continue north on US Hwy 77 for just under 10 miles to Private Road 7018, where it basically had me turn around and backtrack to State HIghway 21. I'm not sure why it selected this private road to turn around on since I passed through the town of Lexington where I could have turned around, plus any number of other state and county roads off of 77 that would have allowed me to turn back. Since my intention was to continue north, I ignored this turn as well so Waze recalculated the route again. The new route had me continue north for approximately 17 miles to US Hwy 79 at Rockdale. At this intersection, the route wanted me to take the exit to Hwy 79, then turn back onto the other ramp to go south on 77 all the way back to State Highway 21. At this point, the route being given was a little over an hour longer than the normal time needed to reach my destination.

I stopped navigation from the menu, then selected my destination again to generate a new route. When the new route was generated, it matched up with my desired route that takes the correct amount of time. So the question is, when you miss a turn and Waze recalculates the route, does it work out a new route to the destination from your current location? Or does it just try to get you back the route it originally generated? I originally assumed there was a map issue that was preventing my desired route from being found which it was it wanted to use Highway 21, but when it suggested backtracking almost 30 miles and passing numerous other roads, I wasn't so sure. And since it found the correct road when I restarted navigation, it doesn't appear to be a map data issue.

[CBenson]

Is there a problem with how the editable areas are calculated?

Yes, there is.

[AggieJM]

I followed 77 south from Rockdale all the way down to Giddings. I found one segment on 77 where there was a restricted turn for the straight through segment on 77. I made that update, so I'll have to see if that fixes the routing the next time I go through there.

I also noticed something else while going down that section of road. If I look at the recent drives list, I can see my full path along 77. But if I turn on the 'editable areas' overlay on the map, my editing area stops just south of Rockdale. I was still able to edit 77 itself, but I could fix any of the side roads or their turn restrictions on/off of 77.

Is there a problem with how the editable areas are calculated? My most recent trip through there was at the beginning of November, so I figured I should be able to edit the 4 miles section around my path.

[AlanOfTheBerg]

I'm not seeing the "ghost road" issue on the edit map like I was originally, but I am still seeing some incorrect items on the Live Map at various zoom levels.

Don't trust the look of the livemap. It is updated in terms of structure (click on a blank spot where a road should be, for example, and it will be there.) Go to Rockdale on the edit map and follow 77 looking for disconnected segments, incorrectly restricted turns, and just general correctness.

[AggieJM]

Just wanted to bump this one back up to the top.

I'm still seeing the exact same issue using routing on the Live Map and route generation from that area north to Dallas through the app is still incorrect on many points of US Hwy 77. On my last trip, I was almost to Rockdale on 77 before the route finally settled into the correct one.

The routes that the app is trying to use are up to an hour and a half longer in most cases and there was no traffic that would cause it to try and reroute. In some cases, it would search a new route after I ignored a directed turn. In other cases, it would automatically reroute when it determined a "better" route.

I'm not seeing the "ghost road" issue on the edit map like I was originally, but I am still seeing some incorrect items on the Live Map at various zoom levels.

[CBenson]

The problem is that there is only one junction between those two origins where something could be wrong, and it's not. I can even shift my origin to just a few feet south of Co Rd 417 and it will still route to the north. So I'm getting two totally different results when I route from two different positions on the exact same road segment. I'm not sure what else to check on that segment that would cause this difference.

Exactly, it makes no sense to me. The only thing I can think of is that possibly when waze went from the 200 mile limit to the 1000 mile, they added a restriction for minor highways like they have for streets and primary streets. And this little distance decreasse the total length of minor highway at the beginning of the route to the acceptable limit. The problem with this theory is that my understanding is that waze has stated that there is no difference between highway designations for routing. Thus, I don't know what could cause this.

[AggieJM]

The problem is that there is only one junction between those two origins where something could be wrong, and it's not. I can even shift my origin to just a few feet south of Co Rd 417 and it will still route to the north. So I'm getting two totally different results when I route from two different positions on the exact same road segment. I'm not sure what else to check on that segment that would cause this difference.

[ img ]

[AggieJM]

If I route from here:
[ img ]

I get this routing:
[ img ]

If I move just slightly up the road to this point:
[ img ]

I get this routing:
[ img ]

It's barely a mile difference between the starting points on the same highway, but my routes are over an hour different.