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

[crazycaveman]

To tell, disable all scripts/extensions and it will be easy to tell . For the most part, though, all scripts make their own tab and keep most things in there (with the sole exception of Validator, which the author has yet to change).

[crazycaveman]

That check is part of the US localization the PesachZ has been maintaining. It should be pretty simple to modify the check to exclude periods that immediately follow and precede a number.

As for the checks, yes, it just is for things that could potentially be wrong; everything that is marked should be checked for correctness and fixed only if it is actually wrong.

[crazycaveman]

Can't the report already be saved as an HTML file? I remember doing that before, at least you could just use the browsers save page functionality to do so

[crazycaveman]

This has always been a problem with Validator. It runs a scan on every segment rendered on the screen and refreshes when the map is moved... it's how it works.
It is doing more in-depth scanning than Highlighter.

My wish list for Validator would be the following:

1 - Move it to its own tab so it is not reliant upon WME

As mentioned before, right as you posted this, Validator got updated to 1.1.18, which now puts it in its own tab! So, looks like your (and mine, and everyone elses) wish was granted

2 - Provide a quick "on/off" toggle button that kills the continual scanning, but leaves the "Run report" option on the tab and enabled... Pressing the "play" button auto-activates the script and runs a scan logging to a report as it does now.

For me it works like this. As you can see in the screenshot, the highlighting is disabled, but the run and show scan buttons are still enabled (ran a scan fine without highlighting enabled).

validator_disabled_runscan.png

(19.46 KiB) Downloaded 1453 times

3 - The ability to export the report (with HTML links) to an external HTML file to allow a detailed scan to be run and saved for later in the event we get called away, browser crash, etc...

As I mentioned before, you can already save a report by using the browser save page function. Additionally, there is a "Save this report" button at the beginning and end of the report that will save it as an HTML file. Do you not have that button?

Validator_save_report.png

(13.77 KiB) Downloaded 1455 times

[crazycaveman]

The buttons "Show report" and "Send" don't work in the WME beta.

I can confirm this. Also, the scan, pause, and stop buttons do not work. Attempting to initiate a scan causes validator to disable all layers and zoom in as if it will start scanning, but it stays in that one spot and never moves. Attempting to pause or stop scan doesn't do anything (the buttons don't even change to allow you to continue scanning)

[crazycaveman]

If you look at the top left (just below the yellow bar), you'll see that the Validator text is greyed out, indicating that it is turned off/not highlighting on the map. When the text is black, Validator is turned on and highlighting as you pan

[crazycaveman]

How to disable this pop-up each time I open waze map editor?

WME Validator v1.1.20:
- Fixed #23 Unconfirmed road

04.06.2016 v1.1.19:
- Fixed WME Beta
- Fixed icons in segment properties
- The work is still in progress...

What browser are you using? Have you restricted the default browser settings at all (i.e. prevented web pages from being able to store data)?

[crazycaveman]

So I did some further testing, and it seems if you use the following in the "header" section it kicks in for both languages, the problem is that it doesn't really match the languages later on.

With ".lng" set to both "EN" and "EN-US" it picks up both languages. That said, if you use the "en" (or "en-us") in the title, problem, or solution text, it doesn't pick it up in either platform. For example:

Either way, I think I got it working so I just need to do some tweaking, and such.

Based on just playing around with it for a little bit, this is how it seems to work. Whatever you set as the language(s) with ".lng" is what Validator looks for in "*.title", "*.problem", "*.solution", etc. so you don't need to put "*.title.en-us" (nor should you); basically, you already told validator what languages will be localized using the ".lng" property. You can look at the default Validator localizations to get a feel for how they do things (the ES.js is a good one). Hope that helps

[crazycaveman]

Hi,

Is it possible (or can it be made possible) to make a report of all the roads that have been changed since a certain date or in the last number of days?
Currently a similar functionality is available in the color highlighter script, but this only changes the color of the segments, which requires extensive zooming and panning around. I'd rather have the availability of a nice report.

Thanks in advance!

Erwin

Yes, that is already built in. If you go to the search options (click the magnifying glass in Validator's settings to switch to that tab), you can enter the date. If you want to find all segments that have been updated since a certain time, you'll need to set up a custom check, as well. Click the Gear button and enter the same text in both the template and RegExp fields (something like a and a would do it).

[CreekOfJohn]

Validator has become an part of our everyday wme use, and to work without it is like working with one eye closed.....

I agree with your statement above 100%, which is why Waze should invest into building validation into WME. This essential editor function should not be left to unpaid volunteers.