Recently I took a trip from Phoenix to Las Vegas and used Waze to navigate. The best way to go is to take U.S. 93 north from Wickenburg. When I plugged my destination in at the start, Waze did not identify this route, instead trying to send me north on 1-17, which adds about an hour to the trip. I ignored it and headed for Wickenburg, but when I got partway there Waze did not re-route to U.S. 93, and said it couldn’t find the destination. The kicker about the route is that on the way back from Vegas it calculated the route via U.S. 93!
On this trip and another one up in Northern Arizona I had another problem. In some locations, it continually (say every 60 seconds or so) said “recalculating route” even though it had a route on the screen and I had not deviated from this. Sometimes it would quit doing this after a time; other times the route and road would disappear, and some time later it would recalculate again and the road would come back. This was very annoying.
Anyone have an idea what the problems here are? At this point Waze is looking like a not very reliable app for road trips outside of cities…
For the Vegas trip, it sounds like there’s a turn restriction somewhere that’s set to “off.” If there is, it’ll take a little while to find it. For the other trip, I’m not 100% sure what’s going on there.
On my routine trips in West Virginia, there are many stretches of of Interstate 64 where I have a similar problem, Steve… I get a constant “chime” and “Proceed to Highlighted Route” message – even though my blue car arrow is right on top of the purple route. Other times, the Interstate disappears altogether! I’ve “paved” many miles of interstate highway, but when I go back to the map editor to fix it and post it, the roads are all there already. In my case, I think it might be related to slow 1x data connections in the rural areas of the state. In other cases, it might be that the actual road is offset by a few too many feet from the “waze” road – I’ve tried slightly re-aligning the road geometry, and I think that may be helping, but the problem was inconsistent to begin with.
It IS frustrating to have the constant chime and “proceed to highlighted route” issue, and especially frustrating to have a major highway disappear altogether. I’ll keep experimenting…
How recently did y’all see this? There was an ever increasing problem of this happening, and a patch was supposedly installed a week or two ago that was supposed to eliminate this problem.
Note that if you have poor cellular or GPS reception, this is going to happen occasionally, but it was happening way too much, which prompted the need for the patch.
This doesn’t surprise me, I’ve gone over that route a couple times heading south from Vegas in the Editor fixing problems to where 93 will route. But it looks like I or someone needs to work back up the otherway as well. Particularly as I didn’t have the JNF or highlighter scripts when I worked the route previously.
My guess is there is a problem at one of the stretches where the road has been built into two separate lanes from the original single lane hwy. For that matter the last time I went down it it was because someone had started splitting the road and then left the job undone making it unrouteable. Maybe that has happened again for the NB routing.
I’ll try to remember to take a look, once I finish my current project (lot’s o little towns in eastern central Utah)
I think I found the problem. There was a road segment on top of another road segment. I’m still going through US-93 in the north direction, but I think that was it. I had seen 3 URs before that segment, but haven’t seen any since that segment. I also found 3 nodes turned to the OFF position, so I think it’s fixed. When the next update happens, see if it’s fixed. I also combined a bunch of little segments into longer segments and I only did US-93 going north. I didn’t worry about the southbound lanes when it was split, as I didn’t see any URs going that way. I think this work will fix the problem.
As of right now, I only did up to I-40. Lunch is on its way, so I may not get back to it for awhile.
You’re right, it was a lot to look at and go through. I cleaned a lot of it up, deleting the ghost roads and the roads that really don’t need to be there. There is a little town that I ran across that needs to be cleaned up, but I was more concerned on fixing the major problem at hand.