If Waze is going to have a properly defined u-turn functionality, I have no problem with it. But I'll make a few points about that:
First of all, we need to be told
. This is the first I've heard that this behaviour might be deliberate. Of course, it might have been discussed in the champs forum, or I might have just had my head up my ass (happens frequently
) and I missed it.
Secondly, the arrows for these u-turns must be visible & controllable in the editor. And yes, once this happens, there won't be any need for the script to highlight them. I'm sure it only does so now because selfcons are a hidden junction property that has a direct (and problematical) effect on client routing.
Thirdly, Waze needs to stop automatically creating these u-turns. There are areas where I have removed all the selfcons I could find and they are gradually re-appearing again. This can only be because people are actually doing u-turns (or 3-point turns, or going just around a corner and reversing out again), because there's no way for us editors to create them. I presume Waze then creates a soft-allowed u-turn. However, just because one driver managed to do it does not mean it will be a safe or sensible manouevre. I know of junctions where u-turns aren't prohibited and are quite easy at 1am, yet would be suicidal at 8am.
Lastly, the client needs to handle u-turns with an instruction like "at the next junction, make a u-turn" and a visual navigation instruction, rather than silence and a purple route that apparently comes to a dead end.
Given the numbers of them that I encounter and their random locations, I would suggest that, should this functionality go live, it would have to be preceded by a system-wide removal of the existing ones. Then we as editors can put in the ones that really should be there.
None of this is "complaint", BTW. It's just important points which I think might need some discussion. For that matter, there should probably be some discussion on whether u-turn functionality is a good idea or not. And it all may have been discussed already, in which case I apologise.