[Script] WME Validator v2020.11.1 (PLACES BETA)

Version 1.0 released, please see the changelog above.

Important note for Firefox users: at the moment I'm unable to update the script at userscripts.org, so please use GreasyFork or my Google Drive instead.

I use the following custom condition to mark dead-ends without U-turn:
template ${deadEnd}:${Uturn}:${direction}
RegExp 1:0:3
It usually works properly, but fails to mark segments which have U-turn on the second end.

There are new ${deadEndA/B} variables in 1.0.0, so please try smth like:
Template: A${deadEndA}:${UturnA}:B${deadEndB}:${UturnB}
RegExp: /A1:0|B1:0/

I'd like to report a small issue with a false positive for abbreviations in France

I've sent your request to french CM for an approval, so will be fixed once I get a response.

It may also be that I'm doing something wrong?

Unconfirmed segment for Validator is a segment with no country assigned. There is a limit 300 reported segments per check, so if there are more than 300 unconfirmed segments in the area, Validator will report just 300 of them.

But this is only my guess. Guys, please include permalinks in your reports/requests.

Thanks!

My PC is not picking up anything at this zoom level

It's zoom lvl 3. WME does not load some segment types at zoom levels 0-3, so you need to use scan in the Validator.

The segment 189055302 you mentioned in your first post is outside the area you posted the permalink to. I zoomed out to lvl 0, run the scan and got the segment 189055302 in my report. So it looks fine to me...

Click Settings->Reset Defaults or select "search" tab and then clear the "Updated by" field. Your report does not include segments updated by you:

[ img ]

Thanks for your answers guys. Here is my variant

To highlight more than 100m long unnamed drivable streets:
Template: ${drivable}:${street}:${length}
RegExp: /1::...+/

Added to the list of examples: forum link

How does it define "drivable"? Is that just everything from Freeway to Street and Ramp, or does it also include conditionally drivable roads like Private, PLot, and Dirt?

Oh, your're right. We ought to exclude parking lot roads. I'll fix it later...

1> Walking trails and other non-drivable road types that have a elevation of something other than -5 be flagged.

You can use a custom check in Validator for that:
template: ${typeRank}:${elevation}
regexp: /^5:(?!-5)/

But in fact at the moment Validator does the opposite. In some countries it highlights walking trails with elevation -5 (check #105).

2> Now that the US is moving to a Functional Classification system,

I did not hear about US Functional Classification, so I can't comment this, sorry.

3> Another check [...] Just mark them all places(points) instead of places(areas).

At the moment Validator does not support landmarks/places layer. There are some plans, but no promises, sorry

Why is it that every time I open the editor it gives me that terms and condition notice?

Validator saves options into the local storage, so there might be two reasons:
1) your browser does not allow to set local data
2) your browser automatically clears local data once you quit the browser

For Chrome browser click menu->Settings->Advanced->Content Settings and make appropriate changes.

Ok i've found an example
[ img ]

In this particular case Validator missed a note reported by Toolbox. When I looked into the code, both Toolbox and Colour Highlight did not detect tile load properly and they both used a timer to periodically re-highlight segments.

So I had to implement a trick in Validator: once it detects the tile is loaded and ready, Validator dispatches an event to WMECH to force it to re-highlight the segments. It does not send anything to Toolbox though and I don't remember the reason. Probably the trick didn't work with Toolbox or smth


Generally speaking, those misses are plausible in Validator, esp. for the very long segments crossing the map view. So few month ago I send a message to Ohad asking a permission to use a low-level WME calls. It would allow Validator to scan the map few times faster and detect issues on the very long segments.

Now the validation functionality being implemented on the WME servers, I guess there is no reason to put much efforts here...

Lately I cannot use the Validator on the beta editor (Israeli server).

Confirmed, I'll try to fix it.

Is it possible to add a custom template field for {editorID} or {CreatedBy} {EditedBy} ?

In Validator you can simply click search tab and then put a username(s) into "Updated by" field. The 'Updated by" field is available for country managers only.

Given that Street would only be used at the end of the street name, but Saint would be used after the directional (if any) and before the name, could Validator look for St in this context?

There is a forum thread with lots of useful custom checks for US: WME Validator localization for US