As ever Chris, I am extremely grateful for all your hard work on this. Let’s hope Waze will actually use these data to solve the problem this time.
Are we getting any feedback from Waze on solving these problems? It’s now over 3 weeks since the last post on this thread, and we’re still getting URs raised with routing problems.
About all I can tell the reporter, before closing the UR, is that the editing community is aware of the problem and working with Waze to find a solution, and to keep trying until they do get a route.
I’m not telling them that if they can’t, they’d be better moving to a different navigation tool, such as Google Maps, which at least gives them a route even if it puts them through heavy traffic on the way, but the longer this goes on, the more likely that is to happen.
Can the CMs please exert some pressure on support to escalate this issue. It’s only outcome, currently, is a loss in confidence in the product and a move to something else.
Hi,
We found an error in the routing and we now it fixed.
Please share with us your feedback, is the problem fix or you still getting errors.
If so, please post the route, time & date and user name.
Thanks,
Shira
Shira, that sounds like very good news. Can you share any details about the issue? Presumably it’s something to do with the sanity check in the algorithm? Do you know the exact time the changes went live? Will the change affect just London or could it affect routing elsewhere?
Sent from my GT-N7100 using Tapatalk
Just tried to route from SW18 3QQ to Romford with my user name. No route found.
Sent from my GT-N7100 using Tapatalk
SE25 4AE to SW18 3QQ - routed OK
SE25 4AE to Leatherhead - routed OK
SE25 4AE to Romford - routed OK
SE25 4AE - Barnet Rd, Elstree - no route found.
My user name.
HTH
Hi,
We are upgrading some of our network components which are responsible for the communication between the APP and the routing server. And that should fix the problem.
Please try to find a route also at the live map and if there is a problem, send us permalink of the route.
(the permalink could be found at : route options -Share routes) with user name and time.
Thanks,
Shira
Should the changes now be live? I still get SW18 3QQ to Romford as an error. And how do a permalink if the live map hasn’t found a route?
Just fired up the automated test code used to generate the previous sets of results, and using the same routing request as before (see Shira’s earlier post for details) I’m not getting any routes returned at the moment (6 requests made so far). I’ll leave the code running for a few hours to see when routes start to appear…
We are in the process of rolling the change. If you get an error, please send us the exact address with the house number.
Thanks,
Shira
Thanks, I’ll wait to see when Chris’s scripts start returning results before commenting further.
Based on the results logged so far, it appears things are still being rolled around within the server room…
I don’t know whether it’ll help Waze confirm their solution will work, but I’ll offer this up anyway.
A UR found this morning here shows it’s still not working for even a short distance within not-very-central London, with the user asking for a route from Walworth Rd, by East St, 3 miles to SE22 8PT (I think that’s East Dulwich Grove - I can’t believe that’s really 3 miles but Google Maps agrees :o ). No house numbers, sorry.
Still picking up URs with routing issues. Has this gone live or not yet?
Don’t know if it was an error in the route tester or with the routing server, but for around an hour or so from half 10 this morning I wasn’t getting any responses logged from the server. I killed the tester and then restarted it just before 1pm, and since then it’s been consistently getting results where both routes aren’t reaching the required endpoint which isn’t something I’ve seen occur for such an extended period of time. So it looks as if something is going on with the server, and fingers crossed it’s intentional rather than just another snafu.
Maybe extra shopping traffic?
I’ve just been referred to this thread as I’m having routing problems with virtually every cross-London destination that I’ve tried. My start point is Richmond-Upon-Thames. I’ve tried routes to Swanley, Orpington and Wilmington and they’ve all failed so far.
I’m also getting “Could not find route” errors when navigating from Canary Wharf E14 to Feltham TW14 and back. After trying for a few a minutes I sometimes manage to get a route. Could it be busy servers at rush hour?
Ian, sorry not to have responded to this until now. I don’t know how I missed your post. Are these routes failing all the time or just weekdays? If all the time then I expect it might be an issue with your starting position. I’ve seen a similar issue with a crescent looped back on itself that I thought was the general London issue until we tinkered with the segment. It now routes fine. If on the other hand, the routes fail in peak times then I would think it’s the general problem.
Waze have not been entirely forthcoming with why this might be happening. I understand that they have put in some more resources but I think there is a bigger issue with the sheer complexity of providing the quickest (or a good approximation) route in London at peak times. I hope that I am proved wrong.
Do your problems occur at peak or all the time?