[Script] WME Validator v2025.02.26 (+ PLACES BETA)

[taco909]

@PesachZ

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)

[doctorkb]

I’m having trouble thinking of a case where you’d want a red arrow on a two-segment node… Unless one of the segments is one-way.

[PesachZ]

@PesachZ

Node A on this segment is being flagged as not needed, even though it is there to show a legitimate turn restriction. The map is actually accurate as is, but the node is being flagged by validator.

This is a 2-way road segment with a barrier in the middle only allowing eastbound through traffic, however it is still a 2 way road on either side of the barrier. Westbound traffic is restricted through this junction.

@doctorkb

I’m having trouble thinking of a case where you’d want a red arrow on a two-segment node… Unless one of the segments is one-way.

Take a look at the link which started this discussion, the satellite and street view images both confirm that it is a two way street on both sides of the barricade.

Unless you feel there should be a 5 meter segment at the do not enter sign? But that becomes an unnecessary hack, and an added node just to make validator happy. (Maybe not just to appease validator, as it could also allow the client to display the blockade)

Sent using Tapatalk for Android 4.4.2

[jemay]

@Taco909

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.

Note: Having the one way and when the resident ignore Waze and travels on the one-way (the wrong way) it will generate a MP. So a different solution is needed. - Lets talk about this issue in another thread… or PM… Thanks

[doctorkb]

@PesachZ

Take a look at the link which started this discussion, the satellite and street view images both confirm that it is a two way street on both sides of the barricade.

Unless you feel there should be a 5 meter segment at the do not enter sign? But that becomes an unnecessary hack, and an added node just to make validator happy. (Maybe not just to appease validator, as it could also allow the client to display the blockade)

I don’t think I’d call that a hack. It’s unfortunate that we can’t have segments shorter than 5m without fouling up the routing engine, but I’d say that is the truth.

You have a span that appears to be about 3m that is one-way traffic only. I realize this could be marked as a red arrow (and since you show this, I can see that being correct), or it could be a one-way segment. The one-way segment may cause errors, as jemay mentions, but that’s no different from a map error for disobeying a turn restriction.

[jemay]

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?

[PesachZ]

Just to recap, I mentioned this here to bring up a validator concern, not to determine the best editing practice for this scenario. After speaking to jemay we concluded both methods are equally accurate, and have about equal benefits. So as jemay said validator should handle both.

The validator concern is when nodes are flagged as unneeded. Validator consider

• lock level
• red turn restrictions
• and allowed U-turns
  when deciding if a node is extra.

Sent using Tapatalk for Android 4.4.2

[taco909]

@jemay

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&lon=-117.88964&lat=33.65514&layers=1861&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

[t0cableguy]

today’s update has broken the highlighting function of validator. Not sure if anything else is broken. Thanks for your script and the help it provides I hope you can figure out a fix asap!

[Nomenclator1677]

Validator doesn’t work right now!

[berestovskyy]

01.10.2014 v1.1.2:

• Disabled for IL #28 ‘Street name on two-way Ramp’
• Updated Polish abbreviations
• Fixed custom checks #135-139
• Updated Spanish translations thanks to robindlc
• Enabled for NL #150-154 ‘Lock levels’
• Updated segment properties UI

[manoeuvre]

edit: nvm, I just upgraded… working now :oops:

[taco909]

@manoeuvre

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

[SpeedDzel]

had the same error popping up.

forced the “Update extensions now” button on my chrome://extensions/

[Nomenclator1677]

But right now, validator is useless as the display is on the upper left corner of the window.

Can’t use it!

[berestovskyy]

@Nomenclator1677

But right now, validator is useless as the display is on the upper left corner of the window.

Sorry, I’ve tried World and NA servers, beta and prod WME, but I can’t reproduce the issue.

Could you please include a screenshot?

[Nomenclator1677]

Here you are. But only when you select the button and push it up, then it appears.

You have only this window placed on top of.

You can’t close it! you can reduce or enhance it and then it is completely unreadable! :mrgreen:

And you can’t access to road names!

[berestovskyy]

Sorry, I’m not sure if it is a screenshot of Validator :?

[sketch]

@Nomenclator1677

Here you go. But only when you select the button and push it up, then it appears.

You have only this window placed on top of.

You can’t close it! you can reduce or enhance it and then it is completely unreadable! :mrgreen:

And you can’t access to road names!

That is a Toolbox window, not a Validator window.

[Nomenclator1677]

No, toolbox is desactivated as you could see it in the photo attached in which toolbox is now activated!