I’d appreciate one of the senior editors looking at this UR please, as it’s clear that Waze has routed a user straight through a 6m segment set to private road.
From looking at the user’s route to get there and the provided route, something went wrong for him to be going south-east down Commercial St in the first place, but Waze could have routed him right into Fleur De Lis St rather than using Folgate St, particularly as it shouldn’t be routing through a private road segment, aiui, unless the destination is on that segment, or can only be reached by going through it.
Two ideas to prevent a reoccurrence - change the private road segment to a permanent all-vehicle timed-restriction, or break the road there leaving a gap and living with the MPs that might result. But does anyone have any thoughts as to why the “rule” about going through private roads appears to have been broken?
If it re-calculated when he was already going west on Folgate St, then waze’s only* option was to go over the private road.
*because it has an aversion to turning around/u-turn
I can’t see any explanation - other than that private road is just a penalty. Perhaps that penalty was overcome by the length of alternative routes. It looks much like the driver turned left out of the A10 and Waze was trying to turn him around and send him back the other way.
As for fixing it - I definitely remove the private section and leave the road broken at that point.
I’ve not looked at the map, but what’s the real world restriction on those 6m? If it’s bus only, then I’d definitely delete it. It doesn’t sound like a legitimate section of road that is access only.
That is true, but something must have made the user turn into Folgate St to start with (who wasn’t worried about entering the CCZ - that would have made me pause and look for another way to turn round), and if Waze was recalculating, it could have suggested continuing one more turn on Commercial St, then right into Lamb St, right Wheeler St, right Folgate St, left Commercial St. There are other “turn round” options.
I look forward to the user responding and telling me how he ended up in Folgate St to start with.
It’s a barrier which can be raised.
Done!
Thanks, gents.
I don’t think there’s any need to get distracted about why the driver entered the CCZ - the Waze-suggested route fragment in the UR uses the restricted bypass segment rather than the toll segment, indicating the route had been generated outside of the CCZ operating periods.
So I’d guess that, having turned left instead of right onto Commercial Street, and having then not taken either the first alternate route via Fleur-de-Lis Street (this may not have been possible due to the roadworks in progress along this stretch of Commercial Street) or one of the around the block u-turn routes Waze would then have suggested to head back north, the driver has then seen what appears to be an obvious cut-through route along Folgate Street and turned down there having not spotted the dead end signs (or chosen to ignore them thinking that, like several such signs around London, they’ve been placed to discourage rat-running rather than indicating a genuine dead end).
As soon as Waze realised the driver was on Folgate Street heading west, the only routing option available was to then use the private segment.
Given that in this instance, the “private” segment is a locked gate which provides an actual physical barrier against non-authorised drivers, as opposed to a stretch of road which is merely signed as private without doing anything to stop anyone driving along it, I support the decision to remove it entirely and leave a hard break in the map at that location. Unlike a “signed-only” private road segment, the nature of this one (padlocked shut therefore requiring some effort on the part of an authorised driver to get through it) leads me to think the likeihood of there being many URs or MPs raised by removing it completely is going to be quite low.
Enabling the u-turns at any of the junction nodes along the eastern end of Folgate Street would probably also have prevented this route from being offered, and had the private section been one with no physical barrier, or one where the nature of the barrier (e.g. one opened via a swipe card or ANPR match) meant it was more likely to be used by Wazers, then this would have been my preferred means of resolving the problem.
U-turns are not yet supported or offered by Waze, nor are they deemed suitable for UK roads.
Enabling the u-turn at the junction node between the public and private segments is exactly the fix I’ve used and validated in a couple of places with this same type of routing problem, where disconnecting the private segment wasn’t an appropriate solution.
Thanks, all. I’ve prompted the reporter to respond and let us know where Waze was routing him before he turned into Folgate St.