[Script] WME Validator 1.1.20 / 03.11.2016

by **SiewMeng98** » Sat Dec 06, 2014 4:43 am

In Malaysia most of us is facing the same problem - shows an unneeded node but when we click on the segment it returns to normal.

by **sketch** » Sun Oct 19, 2014 4:31 pm

Ok great! So for me it will show all highlights, even if edited yesterday. Just wanted to make sure nothing changed. I like that lower level users can see older locked errors so they can submit an unlock or update request.

by **MauricioCGB** » Thu Dec 01, 2016 3:41 pm

ldriveskier wrote:I am VERY happy that Validator is working again. Thank you!!! However, I get a pop-up every time I open a page in WME or hard refresh WME. I don't know if it is something that changed in Validator or an incorrect setting on my end, but it is annoying. Can someone help to get rid of this please?

Thank you!

+1

Enviado do meu iPhone usando Tapatalk

by **berestovskyy** » Tue Jan 07, 2014 1:15 pm

What is WME Validator?
This script validates a map area in Waze Map Editor, highlights issues and generates a very detailed report with wiki references and solutions (see demo report in this forum post)
F.A.Q.: forum link
Complete list of validations: forum link
How to translate and set up Validator for your country: forum link

Why WME Validator?

Validator reports issues for your country and provides links to the country wiki. See how to adjust Validator for your country: forum link
Validator highlights issues not features. For example, it highlights not just any locked segment, but only if the lock is an issue.
There are many country-specific checks on every segment and counting! See complete list of validations: forum link

Download links:
> For Chrome browser please download the script at Chrome Web Store
> For Firefox browser please download the script at GreasyFork.org
Note: for Firefox browser you also need Greasemonkey or Tampermonkey installed.

Main package includes English and the following translations:
French by arbaot and ClementH44
Hebrew by gad_m
Polish by Zniwek
Spanish by robindlc and fernandoanguita
+ localization for 19+ countries

Other languages and localizations to download and install (optionally)*:
* Note: you also need the main package installed (see links above).

Czech (Čeština) by petrjanik, Kebb01, Zirland:
For Greasemonkey/Tampermonkey: GreasyFork.org
Forum thread: forum link
German (Deutsch) by BellHouse:
For Chrome browser: Chrome Web Store
For Firefox/Greasemonkey/Tampermonkey: GreasyFork.org
Portuguese (Português - Brasil) by mikenit:
For Greasemonkey/Tampermonkey: GreasyFork.org
Forum thread: forum link
Russian (Русский) by Manzareck:
For Greasemonkey/Tampermonkey: GreasyFork.org
Forum thread: forum link
Slovak (Slovenčina) by ChoseS:
For Greasemonkey/Tampermonkey: GreasyFork.org
Forum thread: forum link

Screenshots:

Annotated Screenshots 0.5.1c.png: (116.75 KiB) Downloaded 72241 times

Changelog: please follow this forum link

Known issues:

Some checks are temporarily disabled

Please note, Validator does not work over certain territories. It's not a bug.
WME Validator is based on WMET script: link

by **MGODLEW** » Wed Oct 01, 2014 8:26 pm

Olestas wrote:If there is chance.. it should not be highlighted. What if someone enables nonexistent turn?

Most roads in the US are locked to Rank 3 or Higher, I would hope at this rank, they would know to check why a turn might be restricted

by **fvwazing** » Thu Mar 27, 2014 12:08 pm

In chrome you can have setups synced across multiple machines - by using the same google-id.

by **WazingArch** » Tue Feb 25, 2014 10:44 pm

berestovskyy wrote:

But still we have plenty of options for 'Non-drivable connected to drivable' check:
1. We can exclude dead-ends up to 300 m long.
2. Or we can enable check #115 just for some countries by request.
3. Or we can report just railroads connected to drivable roads.

Enable "report/highlight railroads connected to drivable roads" for any country.

by **fvwazing** » Sat Feb 22, 2014 9:17 pm

berestovskyy wrote:
But still we have plenty of options for 'Non-drivable connected to drivable' check:
1. We can exclude dead-ends up to 300 m long.
2. Or we can enable check #115 just for some countries by request.
3. Or we can report just railroads connected to drivable roads.

I would go for #1; but the summum would be a recursive dead-end-check ;-)

Railroads are ALWAYS to be reported if connected to something drivable. As there are a number of countries that have substituted railroads by walking trail (with a distinctive name like "spoorlijn" or "railroad") those should be treated equivalent to RR.

by **davielde** » Sun Feb 09, 2014 10:09 pm

I currently get an indicator that a median u-turn segment is too short when it is actually a one way cross street that intersects with a split road. No direct left turn is enabled from the split road onto the cross street, so it's not technically a u-turn segment. Would it be possible to disable this when the street name of the "u-turn" segment is different from the intersecting road (and not "no street" or "u-turn" as well), when there are more than three segments intersecting at a junction, or some better solution? On tapatalk, so no permalink right now unfortunately.

by **AlanOfTheBerg** » Tue Jan 21, 2014 2:30 pm

gizmouf wrote:[b]Street name starting without upper case

There was a US discussion in the last couple of months about whether there are proper places to not have first letter upper case on real streets. I don't remember the thread or the outcome at this time, but this needs examination. Ramps starting with "to" should definitely be an exception for this check, at least in the US.