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

I have found, that it's possible to put House Numbers on a junction.. Can you include that in the check (at least for Denmark), as an error?

Here is an example this

Sorry, the permalink looks fine to me

As written on https://wiki.waze.com/wiki/Benelux_Freeway, "E42 - A15" is a valid name for this freeway.

Thanks, will be fixed in the next release.

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

Hey,
Do we use ferries yet? This wiki page says: "Do not use the Ferry Road type for any purpose": https://wiki.waze.com/wiki/Ferries

I've deleted it and it comes back.
I've reset to defaults and it clears but comes back.

Make sure you have closed all other WME windows and tabs. Seems like the settings come back from another WME instance...

I believe I've found a scenario of overlapping segments which is not caught by validator:
The segments do not share both endpoints,

You are right, Validator detects overlapping segments connected at the same node only.

It was already requested few times to detect any segment overlapping any other segment. Unfortunately, it would be extremely slow

29.08.2014 v1.1.0:
- Compatibility with beta WME
Note: some checks are still disabled
- Updated for BE #160 'Incorrect Freeway name'
- Disabled for IL #91 'Two-way Ramp segment'
- Removed 1 sec startup delay introduced in v0.6.2

Guys,
Please turn off the 'Two way by default' option in advanced settings. I'll fix it ASAP.

Edit: fixed in v1.1.1

30.08.2014 v1.1.1:
- Fixed 'Two-way segments by default' option

Any reason the Custom Templates are locked to having only two

If you have few useful custom checks, please share them with other users! To do so, please post them here or create your own localization package.

You can customize, enable, disable and add custom checks with the localization pack. Optionally, you can translate user interface and check descriptions, but it's not mandatory.


Regarding the color selection. If a segment has a blue note and a red error it will be highlighted in red, because in Validator errors are more important than notes. In a turn, custom checks are more important than errors. So I'm not sure if a color selection will make any sense having this predefined color "hierarchy" in Validator.

But if you're looking for a way to highlight specific issues on the map, you have 2 options:
1. Click "Search" tab and put the issue(s) you're looking for into the "Reported as" field. For example, you can put there *lock* to highlight just issues with the lock levels.

2. Or you can scan an area and then click "Show report" button. Every permalink you open in the specific part of the report will have exactly the same issue.

Unable to get my custom localization script to work.

Very good start! Few notes:

1. You have to put checks inside the country block, i.e.:

Code:

window.WME_Validator_Canada = {
  // checks should be here
}

2. You don't need to add a template to checks #171 and #174, since they are designed to match street names. We use templates in custom checks only (#130-#139). Please refer this forum post for the check params (or in Validator click Settings (gear)->About->Available checks.)

3. To use a backslash inside a string you need to escape it, i.e. to match an alphanumeric character use "\\w" and to match a dot use "\\."

Here is your script with the above changes:

Code:

// ==UserScript==
// @name                WME Validator Localization for Canada
// @version             1.1.1
// @description         This script localizes WME Validator for Canada. You also need main package (WME Validator) installed.
// @match               https://editor-beta.waze.com/*editor/*
// @match               https://www.waze.com/*editor/*
// @grant               none
// @run-at              document-start
// ==/UserScript==
//

window.WME_Validator_Canada = {
  ".country": "Canada",
  ".codeISO": "CA",
  ".author": "manoeuvre",
  ".updated": "2014-09-03",
     
  "171.enabled": true,
  "171.params": {
    "regexp": "/ (Aly|Avenue|Bnd|Boulevard|By-pass|Centre|Center|Circle|Cl|Court|Cr|Ct|Crescent|Cul-de-sac|Drive|Extension|Fld|Gardens|Gln|Grn|Grounds|Grv|Harbour|Harbr|Heights|Highway|Hl|Holw|Landing|Landng|Ln|Mnr|Mdw|Mountain|Orchard|Park|Parkway|Passage|Pass|Ptwy|Place|Pt|Prt|Pvt|Promenade|Rg|Rdge|Road|Square|Subdiv|Street|Terrace|Ter|Trl|Tr|Thick|Tline|Turnabt|Village|Villge|North|East|South|West)$/i",
  },

  "174.enabled": true,
  "174.params": {
    "titleEN": "St. not St",
    "problemEN": "St. not St",
    "solutionEN": "Use St. instead of St",
    "regexp": "/^St \\w\\w/",
  },
}


Why do you need two backslashes?

You don't if you put your regexp into an edit field, i.e. when you use Validator interface for the custom checks you should use just \w, \d and \.

But you do need to double each backslash when you put the regexp into a JavaScript string, i.e.

Code:

"regexp": "/this is a JS string, so we use \\w and \\. here/",

In JS, Java, C, C++ and many other programming languages we use a backslash as an escape character. Have a look at the Using special characters in strings at MDN.