Route updates while driving

by **AggieJM** » Mon Apr 09, 2012 8:44 pm

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.

by **AggieJM** » Thu Apr 12, 2012 2:57 pm

Does anyone have any idea on this one?

When you pass a turn, does Waze recalculate a new route to your destination from your current location? Or does it just try to get you back to the route it previously selected?

by **AlanOfTheBerg** » Thu Apr 12, 2012 3:12 pm

It should do a route from your current location. If it can't find a "new" route due to map problems or other restrictions we may or may not be able to see on the map, it may look like it is trying to get you back onto the same route, though.

by **CBenson** » Thu Apr 12, 2012 3:45 pm

AggieJM wrote:Does anyone have any idea on this one?

I don't.

AggieJM wrote:When you pass a turn, does Waze recalculate a new route to your destination from your current location? Or does it just try to get you back to the route it previously selected?

When I have waze and another GPS running and skip the recommended turn, waze responds pretty much like the other GPS. For a little while waze thinks the initial route is better, but then switches to a route that takes into account the deviation from the initial route. So it can eventually recalculate a new route to your destination.

by **AggieJM** » Thu Apr 12, 2012 3:45 pm

Thanks Alan. My main concern was that it was taking what should have been a 3.5 hour trip of 215 miles (from that point) and routing it down a path that was around 300 miles and almost 5 hours long.

I was testing this route using the Live Map and think I may have found what the issue is.

If you look at US Hwy 77 between Co Rd 412 and Co Rd 417 in this section of the map:

https://www.waze.com/editor/?zoom=3&lat ... FTTFTTTTFT

It appears there are two stacked roads. The actual road that is connected through named "US Hwy 77" and a Minor Highway called N Hwy 77. If you zoom out to the 500m level, the Minor Highway shows up. Whenever I try to delete the Minor Highway, I get the "While you were editing, the elements you're trying to save have been modified and/or deleted. Please refresh and try again." error message. Can someone remove this duplicated segment?

Also, while comparing the Live Map and the WME map, I noticed some discrepancies. First, the WME map shows that the highway is named "US Hwy 77". The Live Map shows the name to be "N Hwy 77", but if you click on a segment the bubble shows "US Hwy 77".

Second, if you look at this location of the map you can see Co Rd 410 that intersects with US Hwy 77.

https://www.waze.com/editor/?zoom=3&lat ... FTTFTTTTFT

If you zoom out that same location one level, you see a Minor Highway segment following the path of Co Rd 410 that wasn't visible earlier.

https://www.waze.com/editor/?zoom=2&lat ... FTTFTTTTFT

This segment is invalid, but can't be deleted due to the same error message.

As I've been searching, I'm finding a number of segments like this along US Hwy 77 where there are duplicated Minor Highway segments named "N Hwy 77" that can't be removed.

by **AlanOfTheBerg** » Thu Apr 12, 2012 4:40 pm

AggieJM wrote:It appears there are two stacked roads. The actual road that is connected through named "US Hwy 77" and a Minor Highway called N Hwy 77. If you zoom out to the 500m level, the Minor Highway shows up. Whenever I try to delete the Minor Highway, I get the "While you were editing, the elements you're trying to save have been modified and/or deleted. Please refresh and try again." error message. Can someone remove this duplicated segment?

You must submit this as a ticket from the Support page. This is what we have recently dubbed the "ghost road problem" where the editor and even livemap is now showing roads which were edited, renamed, deleted, merged with other segments in previous map update cycle edits. But now they are appearing back in the editor again and causing all sorts of problems. Basically, the map is getting corrupted ALL OVER. I have found dozens of segments myself just in panning and scanning around my area. This is quite a big issue.

by **gettingthere** » Thu Apr 12, 2012 8:39 pm

AlanOfTheBerg wrote:Basically, the map is getting corrupted ALL OVER. I have found dozens of segments myself just in panning and scanning around my area. This is quite a big issue.

Not good at all. I wonder what the excuse is this time. Maybe the fault of the 'newly improved' tile generation process that is 'quicker'?

by **AlanOfTheBerg** » Thu Apr 12, 2012 8:50 pm

gettingthere wrote:
AlanOfTheBerg wrote:Basically, the map is getting corrupted ALL OVER. I have found dozens of segments myself just in panning and scanning around my area. This is quite a big issue.

Not good at all. I wonder what the excuse is this time. Maybe the fault of the 'newly improved' tile generation process that is 'quicker'?

No clue, of course. But I can imagine how even that process could be responsible for resurrecting a segment which hasn't existed for over a year.

by **thefatveganchef** » Thu Apr 12, 2012 9:42 pm

When I drive to work and I use navigation, there is a portion where I go off the recomended route (US 77 in Lexington OK) to go to the post office, Waze will always try to make you back track to the point you deviated until you reach at least a minor highway. The post office is one segment away from a minor highway (State Hwy 39) but yet it will make me backtrack through town to the point of deviation. Once I am on the major highway Waze will recalculate and navigate me back onto US 77 where it meets up with SH-39.

I have taken this as normal behaviour for Waze based on other forum posts where Waze can't calculate every senario out there so it is using the data it already knows to get you back to the precalculated route.

by **AggieJM** » Sat Apr 14, 2012 5:20 am

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)