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

[berestovskyy]

15.04.2014 v0.9.8:
- Fixed #24 filtering in 'Reported as' field
- Fixed #173 'No space after abbreviation' for '11.'
- Fixed segment length for newly created segments
- Custom check severities are now warnings by default.
(sorry, I'm a bit busy these days, so a "real" fix will come in one of the next releases)

- Improved RegExp debug log
- Added a link to custom checks examples on the forum
- Fixed default regexps for #160-163

- CHECKS REVIEW:

Code: Select all

  Added new checks with params to validate city names:
    #190 'Lowercase city name' (merged #92)
    #191 'Incorrectly abbreviated city name'
    #192 'Unneeded spaces in city name' (merged #31)
    #193 'No space before/after abbreviation' (merged #33)

[berestovskyy]

There used to be an option to filter based on username - I see it's been removed (or perhaps hidden for non CMs)

Filter by username is available only for Country Managers and only in that countries. Due to privacy concerns, there are no plans to change this nor implement any editor identification for custom checks.

is it possible in the future to filter based on the object's Area Manager?

I'll have a look, but I'm not sure if it's even possible to implement.

Try to use "City name" filter in the search tab instead. You can list few city names in there, i.e:

Code: Select all

City, Another City, Town, etc

[berestovskyy]

So I fail to see how this type of filtering would be a privacy concern issue.

Maybe I used the wrong term, but I would not like to see editors to lynch other editors using Validator.

[berestovskyy]

I can't seem to find any info on the ${roundabout} template -- i've tried true, false, 1, 0, yes, no, roundabout... what can I regex on to highlight roundabouts?

The following works fine with me (highlights roundabout segments):
Template: ${roundabout}
RegExp: D/1/

You don't have to "guess". Just add D at the very beginning of RegExp (just like above), then open JS console (Ctrl+Shift+J) and check the debug log. Here is an example:

Code: Select all

WME Validator v0.9.8 debug log for segment 248090636, check #128:
1. Expand template: ${roundabout} -> 0
2. Match RegExp: /1/ -> null
=> skip the segment
WME Validator v0.9.8 debug log for segment 248091485, check #128:
1. Expand template: ${roundabout} -> 1
2. Match RegExp: /1/ -> ["1"]
=> REPORT the segment as #128 'User-defined custom check (green)'

So you can easily figure out that ${roundabout} expands to 0 or 1.

[berestovskyy]

Is there some way to correct this behavior?

Unfortunately, once a node goes off-screen in WME, there is just a partial information available about the node.

I'll try to fix the issue, but excluding 'Unneeded node A/B' checks for segments with off-screen nodes seems to be the only way...

[berestovskyy]

None of the nodes are "off screen".

Sorry, I just tried to split/merge same endpoints segments on different zoom levels, but the only way I can reproduce the issue is when both of the nodes are off-screen.

[berestovskyy]

Is there a regexp phrase I can concoct that will highlight segments that are one way and don't connect to a road at the "to" end of their one-way-ed-ness?

It must be already highlighted as #44/#45 'No inward/outward connectivity'

Just in case you still need the custom check to highlight one-way dead-ends:
Template: ${deadEnd}:${direction}
RegExp: /1:[12]/

[berestovskyy]

Excuse me... what about this?

I clicked "Thanks" to inform you that I've read your message. No questions. The bug will be fixed

[berestovskyy]

27.04.2014 v0.9.9:
- Fixed #190 for Cyrillic letters
- Fixed false positive in #171 for FR: 'Rue du Mal Assis'
- Fixed #36 and #37 'Unneeded node' for partial nodes
- Improvements in Settings->About->Available checks
- Temporarily disabled #79 'Too short U-turn connector'
(the check will be updated in one of the next releases)

[berestovskyy]

Am I missing something with regards to negated regex's?

The report is cleared automatically once you change either a template or a regexp field. I guess you changed your custom check after the scan has been completed. This is my best guess. A permalink would help.