[Script] WME Validator 2020.04.12 (PLACES BETA)

Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Moderators: Unholy, bextein, Glodenox, JustinS83

Forum rules
Discussion for the unofficial, community-developed addons, extensions and scripts built for the Waze Map Editor.

DO NOT START a new thread unless it is about a new idea. Keep discussion of existing tools within the main thread for that tool.

The official index of these tools is the Community Plugins, Extensions and Tools wiki page.

Re: [Script] WME Validator 2019.04.11 (BETA)

Postby berestovskyy » Tue Jul 23, 2019 7:15 pm

You have to install either chrome or tamper monkey extension. Both will auto update.
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2019.08.13 (BETA)

Postby berestovskyy » Mon Aug 12, 2019 10:49 pm

v2019.08.13:
- jangliss: Add lock checks for railroad and private roads
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2019.04.11 (BETA)

Postby berestovskyy » Mon Aug 12, 2019 10:55 pm

sven1999 wrote:For Austria, Germany & Switzerland [DACH] there is the custom rule to not use the new narrow street.
https://www.waze.com/forum/viewtopic.php?f=197&t=256066
[...]
hope you can add a rule which checks for this roadtype.

Validator is an open source project: http://github.com/WMEValidator/

Try to implement the functionality. I will answer all your questions and help with any issues.
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2019.08.16 (BETA)

Postby berestovskyy » Fri Aug 16, 2019 7:36 pm

v2019.08.16:
- jangliss: Fix for layer refresh if layer did not trigger update
(This fixes compatibility with WME Toolbox)
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2019.08.16 (BETA)

Postby berestovskyy » Tue Aug 27, 2019 9:40 pm

jarkaz wrote:This is the correct abbreviation, "kpt. Wilhelma Kosińskiego" according to our hash table. Abbreviation tables in wazeopedia: https://wazeopedia.waze.com/wiki/Poland/Tabela_skr%C3%B3t%C3%B3w
Permalink to place: https://www.waze.com/pl/editor/?env=row&lon=20.24565&lat=52.22956&zoom=6&segments=254724307
Screenshot: http://prntscr.com/owpw4w
Please add to Validator


Hey Jarek,
Validator is an open source project, so just go ahead and fix the abbreviation table for Poland on the GitHub:
https://github.com/WMEValidator/i18n/bl ... PL.js#L442

Then create a pull request to merge your change.
If you have any questions -- do not hesitate to ask.
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2019.08.29 (BETA)

Postby berestovskyy » Wed Aug 28, 2019 10:10 pm

v2019.08.29:
- luc45z: update PL abbreviations
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2019.08.29 (BETA)

Postby berestovskyy » Tue Sep 17, 2019 7:17 am

Hi everyone,
As it was announced long time ago, a new great feature is coming to Validator: checks for places! The feature was done entirely by davidkachaos, it's merged into the master branch and ready to be released. Thanks again, David!

As it's a huge change and a lot of internal functionality was touched, I'll give you a heads-up how we're going to release this change.

1. The places checks will be DISABLED by default for now. Not just reports will be filtered out, but the whole functionality will be under a checkbox.

2. The feature will be released on GreasyFork for a start. Hopefully there will be no urgent updates, so we will be able to release it in two waves.

3. After some time (and probably few release fixes), the places checks will be released on Chrome Web Store as well. After a month or so, the feature will be enabled by default.

Please let me know ASAP if you see any issues with this plan.

Thanks in advance,
Andriy
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2019.09.24 (PLACES BETA)

Postby berestovskyy » Mon Sep 23, 2019 11:02 pm

The places checks are here!

Just to remind, the new release is available for now only for GreasyFork/TamperMonkey users. If no major issues, the Chrome WebStore will be updated shortly.

Please report any issues (with permalinks) or suggestions.
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2019.09.24 (PLACES BETA)

Postby berestovskyy » Sat Sep 28, 2019 6:31 am

So far so good, so just published the Validator with Places checks in the Chrome Web Store!

The Places checks are disabled by default, so you have to enable them explicitly (big red checkbox at the top) in order to try.

Thanks in advance for your feedback!

Validator Places Checks.png
(95.65 KiB) Downloaded 285 times
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

Re: [Script] WME Validator 2020.04.12 (PLACES BETA)

Postby berestovskyy » Tue Jul 21, 2020 6:27 am

lg1992 wrote:It was possible in past to define a filter to hide some problems. May we get this feature back?

We have a really nice F.A.Q.: forum link ;)

  1. How to exclude annoying reports?
    Some areas on the map generate lots of minor reports like "unconfirmed speed limit". There are few options to deal with those annoying reports:
    1. On the main Validator window, "Filter" tab (opens by default). At the very bottom click "Exclude notes". This will stop Validator from highlighting/reporting any notes.
    2. On the main Validator window click "Search" tab (looking glass icon). There is a "Reported as" field at the bottom. Here we can exclude any check we want by its name, id or severity. For example, to stop Validator from highlighting/reporting checks #212 and #213, we should put in the "Reported as" field the following:
      Code: Select all
      !212, !213, *

      This mean we do not want Validator to report check #212 (!212) and #213 (!213), but report all the rest (*)

      Also we can use check title here, for example if we put in the "Reported as" field the following:
      Code: Select all
      !*speed*, *

      Will prevent Validator from reporting any check with "speed" in the title.
berestovskyy
 
Posts: 897
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 821 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: ardan74, bummerdude69, FourLoop, G_W1Z, Google [Bot], Google Feedfetcher, jm6087, Mapman44, Twister-UK