waze.com

PesachZ wrote:Validator flags are just that, flags of a potential error. The reason validator doesn't actually did anything is because they want human editor eyes to actually confirm that something needs to be fixed first. Looking at the segment, seeing the restriction and the rank lock, should tell any editor to confirm on satellite or street view before changing it, or send the previous editor a pm. An editor who doesn't know to do that on a locked segment, usually doesn't deserve that rank. On a side note we could also leave a [NOTE] UR describing the details, but I felt it wasn't necessary here with the clear GSV images.

I don't disagree with that at all.
If it is locked above L1, then we shouldn't encounter an editor blindly clearing it (and it would not show on the L1's Validator report)

jemay wrote:Both are correct... I don't remember reading anything that one way is better over the other, so Validator should be able to handle both.

The resolve this question which is better should be taken to a new thread.

5m One way vs Red Arrow Restriction?
Note: Q? Which has a higher penalty that Waze puts on wrong way on one-way vs through a Red Arrow?

Red arrow restriction, Validator (used to) flag that as "No inward connectivity of driveable road"
With the one-way segment it didn't if the U-turn was set as permitted.

I would imagine that Waze would put a higher penalty on the one-way, but I saw a UR today down in Irvine where it apparently routed against a one-way:
https://www.waze.com/editor/?env=usa&lo ... 861&zoom=5

Should have routed right, then right on Monte Vista to Santa Ana to University and back to Irvine.
Unless this was a case where TTS said "left" but the map directions pointed right

manoeuvre wrote:[ img ]

Got the same on initial loading. It updated itself after a few minutes.

mikenit wrote:When I update and save any segment, the custom ${elevation} /[^0]/ alarm, until I click in segment again, or refresh all. Tested in green custom.

I was getting that on the previous WME from time to time as well.

bart99gt wrote:Referencing this thread: https://www.waze.com/forum/viewtopic.php?f=8&t=112938

Is there any way Validator could check for a segment that is in the opposite direction of the ones surrounding it, perhaps limited to minor highways and above? Bugs like the one in the thread above have very significant routing implications and given the lack of user feedback, tracking these down is tedious and difficult to say the least.

That is a great idea, I wouldn't even want to see it limited to mH and above. It not that common for one-way roads to converge or separate outside of parking lots... but even then, this is something that should be looked at. It's not like the map would be covered with highlights.

Perhaps an option to ignore roads below "xxxxxx" so PLRs and private roads can be ignored manually.

bart99gt wrote:My thought was that in an area that hasn't seen the light of an editor it may return a ton of errors on ordinary surface streets where the street directions are all out of whack. Since mH and above would be the most critical to routing, I thought that may be a good start, or at least as you mention, offer some kind of toggle to allow all street types to be considered if you wanted.

True, but we need to have those issues on the local roads brought to our attention as well.
Any editor working with MH would likely be L3+ and would have the understanding that the MH/mH/Primary need attention first.

Enhancement request:

Separate the highlights and listings in the report for "one way" and "toll"

We have a BUNCH of split roads, so we have a lot of legitimate one-way, but we have very, very few legitimate "toll" roads and none that are editable by L4 and below.
I am frequently catching the "toll" flag set incorrectly, but Validator is not helpful in locating them.

Also, I seem to have lost the "No inward/outward connectivity of a driveable road"
I'm assuming this has to do with the WME changes that changed the attachment the turn restrictions to the junction vs segment (same thing that killed RevCon detections).
I'm hoping that this will be restored soon.

ispyisail wrote:It appears that validator no longer finds disabled turn restrictions?

If this is true, is this a known issue?

The most Validator ever did was "No Inward/Outward Connectivity of a driveable road" but it only takes one permitted turn into and out of each 2-way junction (or one permitted turn either into or out of each 1-way junction) to quash that alert.
This, like the check for Revcons, was "broken" during the WME update a couple of months ago (the one that broke nearly every feature of Toolbox) because it changed how the turn restrictions were attached to the segment vs junction.

I don't think Validator itself ever alerted on turn restrictions in general.
The screencap in your message is the result of using Shift-Z and is a part of WME and has always worked.

Edit: On the N/A server... I can't say with any certainty on the ROTW server.

Gotcha.

Ya, I mentioned it a couple of days ago. I haven't seen it discussed before.