I agree that adding for filter lanes like your example is too much…there must be many thousands of these standard junctions up and down the country.
Using “View Only” also causes problems in my opinion. Initially I though it would be a good addition to select View Only for the straight on lanes…in theory on WME it seems like a good idea. In practice though, when you use the app it becomes confusing, particularly when there is another junction instruction coming up. The visual instruction is completely at odds with what Kate is telling you to do. IMO, View Only should only be used on roads with large distances between junctions, e.g. motorways. Using it in cities isn’t good at all…I’ve gone back and removed it from junctions where I previously added it.
Which junction do you mean?
I think the junction with the A38 definitely benefits from LG, I would find it helpful to know that I can turn right from the middle lane.
LG at the Hamilton Rd junction is more debatable, but it doesn’t add anything unnecessary or cause confusion. I think its a good visual addition to a 4 lane junction when turning left or right.
Regarding the PLR and the UR here…you could say the same even if LG wasn’t enabled. Kate is still going to be telling you to turn right, its up to the user to listen to the distance and check the screen to make sure they are taking the correct turn.
Don’t get me wrong I think lane guidance is an excellent addition to Waze. It was the one feature that would make me turn to Google when navigating an unfamiliar area. I just think it should be used sparingly
Remember that the majority of Waze users have never read the Wazeopedia or know what the guidelines are for when to display LG. It could cause more confusion if it only pops up at a select few junctions but not others. How do we predict when a user already knows which lane to be in without LG? I think a lot of users would expect an all-or-nothing approach, either Waze shows lanes at a junction or it doesn’t (you could use the argument from Continue Straight TIO on crossroads, if a user sees a CS at one junction they expect to see them at all junctions)
View Only is only helpful if a running lane becomes turn only.
But you need to consider how it appears in the app as well. I’ve found that it seems like a good idea to add View Only in the editor, but the experience when using the app is often not good. I assume that most people use Waze in a similar way to me when navigating junctions…listen to Kate, and occasional glances at the screen for confirmation as to where and when I need to do something. Its confusing when, for example, Kate is saying “in 400m turn left at the roundabout”, then you glance at the screen and that is telling you to keep right in the right hand lane…because View Only has been added to the junction before the roundabout.
Not necessarily, there will be users who have it set on Sound Off/Alerts Only or, like my car, Waze defaults to bluetooth even though I’m listening to the radio so I get no voice directions until several screen taps to put it back onto speaker.
I do agree that it could be confusing if a turn voice alert happens while CS is showing but I still think we need consistancy, if a user expects to see LG for a lane drop then they should always see it when they encounter one. You could add a TIO or CS View & Hear which will delay the roundabout instruction until after the junction.
Agree. I have been setting to View and Hear when I think its necessary. But I’ve seen lots of examples of “View Only” being selected at normal junctions where there is no lane drop…and in cities where users will likely be getting lots of verbal instructions.
