[Script] WME Validator v2020.11.1 (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 2018.09.13 (BETA)

Postby berestovskyy » Fri Sep 14, 2018 8:29 am

atrophicshiner wrote:How can I disable this in Validator :!:

Sorry for the inconvenience. There are few options:

  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 (including speed limits)
  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.

This "Reported as" field works the other way around. Say, if we want to concentrate just on a checks #212 and #213, ignoring all other reports, we just put there:
Code: Select all
212, 213


Or if we wish to concentrate on errors only:
Code: Select all
error


Will add this to the FAQ

Hope that helps.
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.09.13 (BETA)

Postby berestovskyy » Fri Sep 14, 2018 11:34 am

Hi guys,
We need someone to look through the Validator's Complete List of Checks and check each link to wiki/forum if it's still available/relevant.

There are 124 checks, each might have two links: one with explanations what's going on and another with the solution. We can also have those two links per-country, i.e. two default links, two for UK, two for DE, etc.

It would be nice to get a report like this:

#101 -- solution: https://wiki.waze.com/wiki/Real_time_closures
#191 -- city rename form: https://www.waze.com/forum/viewtopic.ph ... 14#p450378
etc.

We can also just remove outdated links or add a new one if there is already a wiki page for that case.

Anyone? Please?
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.09.15 (BETA)

Postby berestovskyy » Sat Sep 15, 2018 9:25 pm

v2018.09.15:
- berestovskyy: add custom check variables: speedLimit,
speedLimitAB, speedLimitBA and checkSpeedLimit
- berestovskyy: ignore speed limits issues on streets and ramps.
Please use custom checks instead (see below).

Also commit redirecting links to Wazeopedia is reverted. Seems most of the links work now, but might point to an outdated page on wiki though. Still need someone to look though all the links...


Here is how to highlight Streets without speed limits using a custom check:
On main Validator view click Settings (gear icon)->custom
Template: ${type}:${speedLimit}
RegExp: /^1:0$/

There are lots of other custom check examples in this forum post.
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.09.15 (BETA)

Postby berestovskyy » Tue Sep 18, 2018 8:28 pm

Nazride wrote:BETA: No public connection for public segment (slow) (# 202)
https://www.waze.com/fr/editor/?zoom=5& ... =303803801


Validator does not report anything for me. Could anyone please confirm?

GabiruX_ wrote:In Brazil, your script are giving alert to narrows streets giving the #131 error. It's a problem about highway. Narrow street are not error, don't need to show this error.


Could you please add a permalink?
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.09.15 (BETA)

Postby berestovskyy » Tue Sep 18, 2018 11:02 pm

GabiruX_ wrote:Yes, sure. Here's the link.

[ img ]


It seems you are using the localization pack for Brazil by mikenit. Unfortunately it is an external script, I cannot fix it :(

Please contact the author or your country manager regarding this issue. For now please disable check 131 as described in Validator's FAQ:

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. To stop Validator from highlighting/reporting check 131, we should put in the "Reported as" field the following:
Code: Select all
!131, *
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.09.15 (BETA)

Postby berestovskyy » Wed Sep 19, 2018 4:26 pm

Hey,
I just send PMs to (hopefully) all the people who took part in Validator localization asking them to:

1. Publish their localizations and translations under GPLv3 in the Validator's repo:
https://github.com/WMEValidator/i18n

2. Join the Validator development team to continue their great job to support just their localization or to take as big part in Validator as they want.

Thank you so much guys for your great job! If I missed someone, please don't by angry at me :) Just let me know if you are ok with the GPLv3.

Thanks for your prompt answers,
Andriy
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.09.15 (BETA)

Postby berestovskyy » Sun Sep 23, 2018 9:30 am

lg1992 wrote:The errors 107 and 108 (No connection - The node A/B of the drivable segment is within 5m from another drivable segment but not connected by a junction) are reported sometimes when two segments are connected with a 3rd short segment (example). Please tune the corresponding rules.


Looks like a minor WME bug to me: WME does not report nodes outside the visible area connected to a roundabout as "partial".

Not sure if we will be able to fix that, but there are two possible workarounds:

  1. Move nodes connected to the roundabout a bit further away (i.e. > 5 m).
  2. Reduce the length Validator detects as an error. But there are still will be cases where two nodes connected to a roundabout quite close.

The right solution is to fix the WME bug. Not sure how we report WME bugs nowadays...
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.09.15 (BETA)

Postby berestovskyy » Tue Sep 25, 2018 8:51 pm

Nazride wrote:error on : Noeud A: inutil (mode lent) (#36)
or here

https://www.waze.com/fr/editor/?zoom=7& ... =343409108

Same issues as with lg1992 report: WME sometimes does not report nodes as "partial". We will try to workaround it in the code.
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.10.04 (BETA)

Postby berestovskyy » Sat Oct 06, 2018 3:03 pm

atrophicshiner wrote:Seeing highlight of a current restriction as expired, restriction is for today only, maybe a calendar thing.

Thanks, will be fixed in the next release.
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

Re: [Script] WME Validator 2018.10.16 (BETA)

Postby berestovskyy » Tue Oct 16, 2018 10:18 pm

Hi,
Thanks to David, we are adding several new checks for Venues:

  1. No city name on Venue/The Venue has no city name set/Set the city name
  2. Automatically updated Venue/The Venue was updated by Waze/Verify and update Venue details if needed
  3. No type on Parking Lot/The primary Parking Lot type is not set/Set primary lot type to Public, Restricted or Private
  4. No cost on Parking Lot/The Parking Lot cost is not set/Set cost to Free, Low, Moderate or Expensive
  5. No payment types on Parking Lot/The Parking Lot payment types are not set/Set the payment types
  6. No elevation on Parking Lot/The Parking Lot elevation is not set/Set the elevation
  7. No entry/exit points on Venue/The Venue entry/exit points are not set/Set the entry/exit points
  8. No Parking Lot entry/exit points/The Parking Lot entry/exit points are not set/Set the entry/exit points
  9. No city name on Park/The Park has no city name set/Set the city name or change category to Forest / Grove
  10. No brand on Gas Station/The Gas Station brand is not in its name/Add or update brand in the Gas Station name
  11. No lock on Gas Station/The Gas Station should be locked at least to Lvl ${n}/Lock the Gas Station
    Param: {number} minimum lock level (default is 3)

Please let us know if the checks should be adjusted/disabled for your country prior to the release.

Also, we will be grateful for related links to Wazeopedia in English and/or in other languages, so Validator will show the users this link.
berestovskyy
 
Posts: 901
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 327 times
Been thanked: 822 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: JimboBaggins1966, jm6087, Mapman44, Mythdraug, n4dog, RichardPyne