Make sense, though I don't like leaving the red flag if there is a legitimate way to clear it, if only to prevent a new editor working from a Validator script from opening the restriction (which would then show the blue alert, so he then deletes the node)PesachZ wrote:The red flag would be expected, the blue unneeded flag I'm asking to be fixed so it considers turn restrictions and allowed U-turns
Lock level didn't do it for me here
That's why I brought up the one-way segment. It avoids both alerts (if the u-turn is set) at the small cost of the time penalty for the one extra junction (and this situation is likely going to be on a small street that we probably don't want to encourage detour route-through anyway).
I've been using the one-way segment to make private driveways on gated communities exit-only. It avoids routing non-residents into the closed gate, once inside, the gates typically open automatically to allow exit, and residents with an opener or code will know they can use the gate and can ignore Waze directing them to the guard shack.
Simply having a turn restriction on a single node should cause any editor to do a double-take. First look (in your case) shows a high ranking editor name, but that could be assumed to be from FC. A more experienced editor would move in closer on SV and notice the lack of UR to confirm... the one-way segment would provide a flag to a less experienced editor that says "This is not a mistake, I did this for a reason"
It would be very helpful if WME were to include a comment field on junction and segment ID database entries. If that were done, then Validator could include the comment in the report page on any alert.
Re: [Script] WME Validator 1.1.1 / 30.08.2014