Waze forum

berestovskyy wrote:Hi!
Sorry, I missed the expiration date

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...

crazycaveman wrote:

ispyisail wrote:Hi all

I'm looking for a custom search that will find all "Street" and "Primary Street" that have more than one "alternate name"

as always

Thanks

Try this:

Code: Select all

Template: ${typeRank}:${altStreet[1]}
Regexp: /1[01]:.+/

crazycaveman wrote:Here's an updated type list (not typerank):
${type}

Code: Select all

1:  Street
2:  Primary Street
3:  Freeway
4:  Ramp
5:  Walking Trail
6:  Major Highway
7:  Minor Highway
8:  Dirt Road / 4X4 Trail
9:
10: Pedestrian Boardwalk
11:
12:
13:
14: Ferry
15:
16: Stairway
17: Private Road
18: Stairway
19: Runway/Taxiway
20: Parking Lot Road
21: Service Road (deprecated)

taco909 wrote:Not sure if this was mentioned before.
Validator triggers an error on "Incorrect abbreviation" when the street name terminates with a period.

With the new handling of cardinals, we need to have Validator ignore this iff the last character pair is " N.", " S.", " E.", or " W."

Example: "W Avenue N." comes out properly on TTS as "West Avenue N"
This is valid, but Validator triggers on the "N."

LeighGr wrote:I'm busy creating a WMEV localization pack for South Africa, but am bashing my head against a wall with some weird errors. The following code works fine for mH segments named R100 to R512, and then again from R516 onwards, but R513, R514 and R515 all get flagged as incorrect. WHY?????

Code: Select all

// Custom Check - Minor Highway Name Format
  "137.enabled": true,
  "137.params": {
    "titleEN": "Incorrect name format on Minor Highway",
    "problemEN": "All Minor Highways name format should be (R###) numbered > 100 ",
    "solutionEN": "Change name to ... (R###)",
    "template": "${typeRank}:${street}:${direction}",
    "regexp": "/(13):(?!R[0-9]{3} [NESW]:(1|2) ?|(R[0-9]{3}:(3))$)/"
  },
  "137.solutionLink": "W:South_Africa#Road_Network", 

"regexp": "/^13:(?!(R[1-9]\\d{2}( [NESW]:[12] ?|:3))$)/"

vince1612 wrote:Quick question : I keep getting this in the Validator report after I scan a certain area.

Might be incorrect city name (only available in the report) (#24)
The segment might have incorrect city name: wiki
Consider suggested city name and use this form to rename the city: forum

Gy — city name is too short
Allée du Chambet, Gy
65434649
...

But that village's name is really just "Gy"
I would use the filter in the city name with !Gy to ignore it, but then it would just not show any potential errors on these segments as they would be ignored (if I understand this right).

How can I make it ignore the "city name is too short" error only, from the report, while still scanning these segments for anything else that could be wrong with them ?

I hope the answer is not too obvious

!24,*

AlanOfTheBerg wrote:Sheesh, I can't even get Validator to load at all. The only line in the console on load is "WME Validator v1.1.8: login AlanOfTheBerg". Win7/Chrome 46.0.2490.71 m. Ideas?

AlanOfTheBerg wrote:

PesachZ wrote:

AlanOfTheBerg wrote:Sheesh, I can't even get Validator to load at all. The only line in the console on load is "WME Validator v1.1.8: login AlanOfTheBerg". Win7/Chrome 46.0.2490.71 m. Ideas?

Are you in WME Beta? Validator is broken in the latest beta.

Nope, I wish it was that simple. I knew that it wasn't working in beta.