There is a closure here which Waze routed through as can be seen on the gps trace with the UR.
Any idea why?
I’m assuming this is for the UR 10122748 (on Kensington Road with GPS route turning onto Alexandra Gate/West Carriage Drive). If it is, then i noticed that there is no road closure, just a restriction from 00:00 to 05:00 (so midnight to 5am) for all vehicles, and All Day for “Some vehicles” (which an addon specifies at “commercial vehicles”). I’m unable to see full restriction info due to being outside my editing area and above my editing level.
Based on everything I can see, GPS routing is correctly reflected. Maybe changing the restrictions or disabling turns would be the solution?
Oh bother, I think I may have attached the wrong UR and it definitely had a closure. Here is the correct location. (Have also corrected the original post).
The principal of my question is still valid though!
What’s possibly happened here is that the app updated navigation during the journey and was unable to connect to the routing server, so used the offline routing capability which, unfortunately, doesn’t take account of closures or, I seem to recall, turn prohibitions.
Offline routing seems to happen regularly in London which, given the level of 3G/4G coverage you’d expect to find, is surprising. It may just be that the number of users in London makes these issues more common than expected. In the back of beyond in the more remote parts of the country where there’s no mobile coverage, yes, but not in the concrete jungle, yet it happens.
The problem is, IME, more often than not the ongoing difficulties the app has in maintaining connectivity to the Waze servers specifically, even when the phone has perfectly decent connectivity to the internet at large. Whilst this has been a recurring theme since I started using Waze (and I wouldn’t be surprised if the old-timers saw similar problems even in the earlier days), it seems to have been particularly bad in the London/SE area over the last couple of weeks.
It does surprise me a little that, given how much emphasis the app devteam generally seems to put on the assumption that mobile connectivity will be present at all times, they’ve included offline routing capabilities at all. It’s also a bit annoying that, when the app is doing offline routing, it doesn’t make it clear to the user that this is what’s happening, and that the routes it returns may therefore be complete bollix…