Please try Settings->Reset defaults or just make sure your search tab has no options activated.
Now, as landmarks have been changed with places that have categories and sub-categories, I occasionally meet a place with a general category only. It would be nice to have the Validator to mark such places.
Bug fix request:
For error 114 āThe non-drivable segment makes a junction with a drivable at node Aā the Wiki link needs to change from:
https://wiki.waze.com/wiki/Road_Types_(USA)#Non-drivable
to
https://wiki.waze.com/wiki/Road_Types_(USA)#Non-drivable_roads
Many thanks for this invaluable script.
If done, Iād like this to be optional. The sub-categories are hardly comprehensive. Many of the places around me only have a general category as none of the sub-categories are appropriate.
Agreed. I donāt really see a need for it at all. Even if they were more comprehensive, we donāt have any rules currently discouraging use of the upper level categories.
Right, Iām not even sure it should be offered. Might encourage editors to change a category erroneously. For example, a cigar shop ā doesnāt really fit anywhere besides the general āShopping and servicesā.
You can try ${segmentsA/B} and ${outA/B} variables, for example:
Template: ${segmentsA}:${outA}
RegExp: /3:[^3]/
This will match a segment connected to 3 other segments at node A, but having not 3 outward turns enabled.
But itās not that simple. You have to take into account segmentās direction etc etc. So I suggest you use instead Shift+Z WME shortcut which shows you disabled turns.
How should I search for segments shorter then 17m?
Try to match length 0-9 OR 1 following 0-6:
Template: ${length}
RegExp: /^([0-9]|1[0-6])$/
I simply love this toolā¦ Very helpful and helped me solve a lot of map problems 
Thanks
Since userscript.org (even :8080) doesnāt seen to work anymore, is there another way I can install it ?
Could add to https://greasyfork.org/ or https://openuserjs.org/
Thx
Why this again? I thought it was allowed for validator to check locked segments, so lower levels can alert higher levels about errors.
ĖĖ Maybe this could be made an option?
My bad, could not find it, thx
Hi!
As we discussed earlier, Validator skips any segment updated after 2014-05-01 and locked for you.
You can still check locked segments updated prior that date, so it does not skip base maps, old edits etc.
Sorry, did not see that discussion. And no one seemed to discuss it actually 
I donāt think new updated and locked segments should not be touched. Higher level users also make errors, and donāt always leave the best of it all.
I think the point was that IF the segment is locked above YOUR level (so you canāt touch it anyway, without help) AND it has been updated recently, THEN it wonāt be flagged.
That way, you donāt see a bunch of āerrorsā that YOU canāt fix.
In other words, higher level editors will still see the errors flagged.
The problem isā¦ If I donāt report the problemā¦ no one will
But the problem is that many of those problems are āfalse positivesā that lower level editors donāt have the experience to ignore.
Validator canāt distinguish them from valid errors.
Perhaps the option to hid them should be an āon by defaultā option that can be turned off by āskilled lower level editorsā that are able to tell which need to be passed on for fixing.