[Script] WME Validator v2021.3.5 (+ PLACES BETA)

[bz2012]

https://www.waze.com/editor/?zoom=7&lat=29.76326&lon=-95.37197&mapUpdateRequest=3404412&env=usa&layers=1925&segments=47698044


Validator flags the segment with a 'turn too sharp' at the north end when that end has the restricted turn (yellow) 24/7, but passes it when the turn is forbidden (red).

I am not sure this behavior is bad, but it seemed a bit strange.

[bz2012]

....
Why set it as TBTR (24/7) when it should be just a red arrow?

In the hope that someone 'killing red arrows' would be less likely to 'enable all turns' there.
(yeah, I know I can just lock it, but 'stuff happens' sometimes. And I wanted to see how well the idea works. When I noticed the slightly strange validator action, I thought I'd report it.)

[bz2012]

constant 'too many issues reported' flag showing up when any segment selected.

[bz2012]

Clearing the report does not remove the message. It pops up ANYTIME I select any segment in the Houston texas area.

[bz2012]

The bug fix fixed it.

[bz2012]

So you will get the issues on the "old" locked segments, but never on recently updated segments.

Sorry, did not see that discussion. And no one seemed to discuss it actually
I don't think new updated and locked segments should not be touched. Higher level users also make errors, and don't always leave the best of it all.

I think the point was that IF the segment is locked above YOUR level (so you can't touch it anyway, without help) AND it has been updated recently, THEN it won't be flagged.

That way, you don't see a bunch of 'errors' that YOU can't fix.

In other words, higher level editors will still see the errors flagged.

[bz2012]

The problem is.. If I don't report the problem.. no one will

But the problem is that many of those problems are 'false positives' that lower level editors don't have the experience to ignore.

Validator can't distinguish them from valid errors.

Perhaps the option to hid them should be an 'on by default' option that can be turned off by 'skilled lower level editors' that are able to tell which need to be passed on for fixing.

[bz2012]

Is it possible to add a custom template field for {editorID} or {CreatedBy} {EditedBy} ?
so we could do something like
${EditedBy}
/(user1|user2|user3)$/i
to highlight segments edited by any of a list of editors?

[bz2012]

FIrst time I have tried using the TYPE ferry, I see a problem: It is flagged as 'non drivable connected to drivable'.

Although literally, a ferry route isn't 'drivable', the vehicle enters and leaves the segment at the ends, so the segment NEEDS to be connected to drivables at both ends and should be treated by Validator as drivable.

[bz2012]

It appears that a recent update of WME has broken Validator.
It is now flagging ALL segments as 'no inward connectivity', 'no outward connectivity'.

This is true, even with ALL other extensions disabled.

Discussion in the WME thread shows that the same problem was known to exist in the beta WME.