waze.com

25.06.2014 v1.0.1:
- Disabled for IL #52 'Too long street name'
- Disabled for IL #41, #42 'Reverse connectivity'
- Fixed for IL WME Beta

Added to the F.A.Q.:

Search for a specific username
Validator does support a search for a specific username. Click "search" tab and put a desired username(s) into the "Updated by" field.

For privacy reasons the feature is available for country managers only. Regular users and area managers have "Include only your edits" option instead.

The "Updated by" feature was implemented months ago and we agreed that it's for country managers only.

But I still get questions and requests to implement the feature or variables for custom checks, so I decided to add it to the F.A.Q.

Sorry for the misunderstanding.

04.07.2014 v1.0.2:
- Complete Hebrew translation thanks to gad_m
- Minor UI changes for right-to-left languages (please report any issues)
- Changed keyboard shortcut to 'Alt+V'

+ Two new external translations:
Note: you need to install them along with the main Validator package using Tampermonkey

• Czech (Čeština) by petrjanik, Kebb01, Zirland:
  For Greasemonkey/Tampermonkey: GreasyFork.org
  Forum thread: forum link
  
  
• Slovak (Slovenčina) by ChoseS:
  For Greasemonkey/Tampermonkey: GreasyFork.org
  Forum thread: forum link

Super-mega-cool! Thanks guys!

Few answers:

SuperDave1426 wrote:is there any chance that Validator can be updated to no longer highlight roads with "Unconfirmed turn at node {A|B}" when node {A|B} is a dead end?

Thanks, will be fixed.

qwaletee wrote:Does the keystroke automatically update? Mine had stayed at Shift-W (interfering with Waze's new Shift-W for closing SV) until I manually changed it.

Validator does not save keyboard shortcuts, so I guess it's another script saved that.

bummerdude69 wrote:Is it possiable to identify the geometric nodes (not the end points, but the ones in the middle) that are at 180 degrees?

Thanks, added to my todo list.

mikenit wrote:I will like to see the type of road connected to the A junction?
Is there an variable that expands the type of conected segment?

There is no such a variable and it would be slow to implement and tricky to match. It's better to implement such checks inside the Validator using Javascript, not just regular expressions.

Taco909 wrote:Is there a way to add non-approved speed and RL cameras (or even all cameras) to the custom search feature?

Sorry, at the moment Validator analyze just road segments.

Olestas wrote:It is possible to search just for segments updated by User?

You can use a custom check to highlight all segments and then search for a specific username, i.e.
Template: 1
RegExp: /1/

houstonmg wrote:Some notice about the reported behavior in the beta editor?

Confirmed. Lot's of work to rewrite Validator and then to review and retest all the affected checks...

Taco909 wrote:The report seems to catch things, but I'll be at a wider view and might see a blue highlight, zooming in it changes to yellow, or something goes away completely.

Seems to work fine on non-beta world. A permalink would help to confirm.

KB_Steveo wrote:I noticed some freeway segments that had an Automatic (1) lock that Validator did not pick up. They were not highlighted nor did they show up in a validator report.

A permalink?

Hi!
Sorry, I missed the expiration date

sketch wrote:could you remove the dead-end U turn check, and make it such that the "unconfirmed turn" checks etc. don't look at dead-end nodes?

Done.

Taco909 wrote:It will appear and disappear at various zoom levels and change as the map is panned, and in some cases display blue on a wide view, then change to yellow or even red when zoomed in.

All your links look fine to me. Validator does not run slow checks on low zoom levels AND it re-checks segments once WME loads in more data (i.e. when you pan or zoom in).

I suggest to use zoom level 4+ to make sure everything is loaded and all checks are available.

alexschrod wrote:Being a software developer,

So could you help me to adapt Validator to WME beta then? I would really appreciate any help here...

alexschrod wrote:In the next update, if the author wants this kind of behavior in place, they should add another check first that sends a request to see if there is an actual update ready

Validator does not send or receive any data from the internet for security reasons.

wlodek76 wrote:Could you explain us why do you lock this script ? What is purpose of doing this ?

The script has an expiration date since the v0.3. The first few versions expired just in 7 days to force users to update the script...

It also forces me to update the script and publish a new version. And it really motivates me lately...

In turn, I'd like to ask you to help me to finish Polish translation. Here are the detailed instruction: forum link

iainhouse wrote:Could we please have the highlighting of dead-end u-turns turned back on for the UK, please?

I guess you can still use a custom check for that (i.e. match deadEndA&UturnA or deadEndB&UturnB).

Let me know if you still would like to get those checks back for UK.

wlodek76 wrote:Many of us could feel a little frustrated with this "lock"

This "lock" was introduced in v0.3 on demand of Waze Champs.

iainhouse wrote:Yes please.

Ok.

SuperDave1426 wrote:when the "expiration" date has passed and there actually isn't a new version online yet

Validator does not send or receive any data from the internet for security reasons.

sketch wrote:only 5 custom checks may be added in a localization pack? Is it possible to increase this number?

Sure, but if you're checking street names, please use #16x checks instead.

ispyisail wrote:New Zealand wants the same as the UK

Ok.

MdSyah wrote:Would you please put back the highlight of dead end u turn check back for Malaysia like those of the UK.

So, maybe it's easier to turn it back on for all countries but US then?


New advanced example in Custom Checks Examples:
New! To highlight segments if primary street name and one of the alt. names are the same
Template: #${street}#${altStreet[#]}#
RegExp: /(#.+)(?=#).*\1#/

Guys,
The update (v1.0.4) has been published. You need to force your browser to update the extension.

Also you can click Search tab and put the following into the "Reported as" field:

Code: Select all

!44, !45, !50, *

i.e. to disable checks 44, 45, 50 and report any other issues.

Have a nice weekend for those of you who still has