I have just seen a UR where a user was quite clearly directed through a private road (Bus only). I can’t get waze to replicate the route so the restriction is working as it should be.
So I was wondering if a user goes the wrong way, or starts a route and waze is facing a particular way it will always route through this particular section, now I know there is no instruction on the client (yet???) but in order to prevent this would it be worth adding an enabled uturn shortly in front of it so that if needed waze can backout of what is effectively a dead end for cars?
There’s no point in enabling u-turns at a node. Iain wrote the following in response to a query of mine on the “To dual and add u-turns, or not” thread:
I think the only solution to getting a routing that a car could follow in this situation is to actually add a junction with a u-turn segment that would allow Waze to show the user they’ve got to about face. That would be terribly inelegant and inaccurate and probably cause a lot of other problem reports about it not being there.
I wonder whether the better solution is to use a restriction rather than a private road - taking out the dualling and making it two way with buses only permitted westbound, with a buses-only turn permission to enter the segment. I have no idea whether that will force Waze to route another way if it’s convinced the user is west of Rowdell Rd and facing west. Try it and see - at least you can tell the user you’ve made some changes that might resolve the problem he found.
I’m still not convinced that’s the issue that the user had, I can only guess the user either made a wrong turn, or there was an even higher penalty somewhere else that made it go that way.
Either way, I know there is no instruction, hence why I thought I would suggest it to see what the consensus was, working on the assumption that eventually there would be an instruction…
I think the restriction may also have the same problem, it’s will all be down to whatever has the highest penalty. Even we did manage to find a penalty high enough, it would either give a proceed to highlighted route, or make up its own uturn somewhere which will have the same effective problem.
I thought I read somewhere that if only one direction is busses only then forget about restrictions and private roads etc just create a normal one way road (in the opposite direction).
Yes this is all true (dont look at me I never set it up), but I am also thinking of the bigger picture, imagine this was busses only both ways and was set to private, would hit the same issue.
I originally set this one up, so I guess I’d better contribute! :lol:
Obviously we didn’t have restrictions back then, hence the half-private/half-street split carriageway. If I was doing it now, or minded to re-do it, I would use restrictions. I wouldn’t make it just one-way because there might be MPs generated by bus passengers - there might even have been some that prompted me here. I definitely wouldn’t leave the westbound bus segment there but disconnect it - that would be pointless.
I can’t explain why the user was routed through this private segment. This might be one that’s worth reporting to Waze via nanoRep. If you do, drop a “note” UR there to ask other editors to leave it alone.
As for adding a u-turn, whether as an enabled u-turn arrow or by some form of junction, this just won’t help drivers in this situation. If it’s a proper u-turn, they’ll get no instruction at all and they will follow the purple line until it ends at the bus section. Even if they see in advance that the purple line simply ends, they’re likely to still follow it to the end - what else are they going to do? So, despite the enabled u-turn, drivers will still end up driving up to the bus section and realising they have to turn round.
Putting in some sort of constructed u-turn junction is also just going to confuse them. If it’s small enough to “fit” in the available space it will be invisible on the map. The driver will still face a purple line that peters out - except in this case Waze will be telling them to take 1 or more “invisible” turns at the end of it. If the junction is big enough to see clearly on the client, you’re going to get URs along the line of “WTF is that on the map?! Doesn’t match reality”.
yeah I know what it looks like, what my thinking was though, what is the lesser of two evils?
Being routed through somewhere you can’t go, or confusing instructions. I agree we certainly have some options here, so I can change the junction in this case, which would hopefully prevent this issue.
I’m sure there are other places though where the idea may help, for example the road I drove up earlier, had a one way section in the middle of it, and as soon as I drove up, waze had no idea what to do and refused to route.
Also I was under the impression they were going to add a turnaround instruction at some point - yeah I know, waze soon and all that…