help to solve this error..

[gianekaren]

It's not the first time that happen..
also other time it happen to me in different roads..
can anybody help me to understand an error like that??
https://www.waze.com/editor/?zoom=6&lon=-75.8517&lat=41.25132&layers=BFTFTTTFTTFTTTTTTTTTFT

thank you.

[WeeeZer14]

Looks like you have the right turn restrictions in place now. Not sure if you changed them or something else.

That ramp segment should be of type street instead (which may help since ramps are treated as preferred over streets).

It could be that taking a proper left has a real long delay from the traffic signal that the illegal movement through the right turn ramp looks better to Waze since it is quicker.

And finally and most likely it may be that the user has "prefer cookie munching" on in the client which basically ignores all the rules and tries to get the driver to do crazy things. (We've asked Waze to disable this option or at least ignore it on the routing server.) If that is the case, there is absolutely nothing we can do.

[gianekaren]

Looks like you have the right turn restrictions in place now. Not sure if you changed them or something else.

That ramp segment should be of type street instead (which may help since ramps are treated as preferred over streets).

It could be that taking a proper left has a real long delay from the traffic signal that the illegal movement through the right turn ramp looks better to Waze since it is quicker.

And finally and most likely it may be that the user has "prefer cookie munching" on in the client which basically ignores all the rules and tries to get the driver to do crazy things. (We've asked Waze to disable this option or at least ignore it on the routing server.) If that is the case, there is absolutely nothing we can do.

thank youuuuuu

[AlanOfTheBerg]

I may have mentioned this before, but I find that the "stay right" command is used when we as drivers actually would expect to hear a "turn right" even for the "pre-right-turn-cutoff-lanes" such as this one in your area. I have tried, and with pretty good success in many places, implemented a small work around which gives a turn instruction but still looks like a "cutoff lane." One such example is this one. Notice that on zoom-out, and in the client, the small kink to make a right-hand turn is barely visible.

Also, in the previous permalink you provided, there are incorrect turn restrictions enabled at both the beginning and end of all these segments. It looks like you overused the 'w' key. And if you're doing it there, then you are likely doing it in other places. 'W' should be used very lightly in situations involving 1-way segments especially. It does truly enable ALL TURNS, which is often what you do not want in these situations.

[gianekaren]

oookk.. got it..
i never used the w key.. i honestly didn't check at the time of the first edit the restriction... now corrected..
Thanks!!!

[AlanOfTheBerg]

oookk.. got it..
i never used the w key.. i honestly didn't check at the time of the first edit the restriction... now corrected..
Thanks!!!

You're welcome. Keep in mind the level of detail we must go to to ensure all turns are correctly restricted. It is often that we get map issue/wrong direction complaints from drivers when they are recommended to make a strange move at an intersection like this where turn restrictions are incorrect. The most common is that when there is a right-turn "cutoff" lane, that at the main intersection, the right turn should be disabled. Such is still the case for this segment, which is why I highlighted it previously for you. It still needs to be restricted.

[AlanOfTheBerg]

This segment still has two incorrectly allowed turns.

[AlanOfTheBerg]

https://www.waze.com/editor/?zoom=7&lon ... s=61944182 still has the right turn enabled which shouldn't be.