[Script] WME Validator 1.1.8 / 07.05.2015

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.

Moderator: Unholy

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 1.1.2 / 01.10.2014

Postby berestovskyy » Wed Oct 01, 2014 6:57 am

Nomenclator1677 wrote:But right now, validator is useless as the display is on the upper left corner of the window.

Sorry, I've tried World and NA servers, beta and prod WME, but I can't reproduce the issue.

Could you please include a screenshot?
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.2 / 01.10.2014

Postby berestovskyy » Wed Oct 01, 2014 7:20 am

Sorry, I'm not sure if it is a screenshot of Validator :?
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.3 / 07.10.2014

Postby berestovskyy » Tue Oct 07, 2014 10:10 pm

07.10.2014 v1.1.3:
- Updated Polish translations thanks to Zniwek
- Enabled for ES #130-133 'Custom lock levels'
- Updated #114 and #115 'Non-drivable connected to drivable': excluded Railroads
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.3 / 07.10.2014

Postby berestovskyy » Mon Oct 13, 2014 4:56 pm

Gerrit1965 wrote:Update & additional information: I am using Firefox Version 32.0.3 and I restarted the browser, but the problem persists:
Please report WME Validator CODE BLUE: -30472

Code blue is the integrity check.

If you copy-paste the Validator, try to save it to a file and then load or drag and drop into the Tampermonkey. And vice versa.
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.3 / 07.10.2014

Postby berestovskyy » Fri Oct 17, 2014 8:43 pm

voludu2 wrote:I am seeing inconsistencies with custom template/regexp highlighting, This makes it somewhat less useful than it could be for identifying "state smudging"

Unfortunately, WME was not created with Validator in mind, so there are few limitations. If you combine them together it will look like a bug sometimes, but from your description it it sound like a strange but normal behaviour:

1. WME does not load all of the geometry at zoom levels 0-3. So you see the image of the streets, but there are no geometry, so those streets are not selectable and Validator can't check/highlight them.

2. Sometimes there are exceptions to the rule #1. For instance, if you zoom in to lvl 4 and then zoom out to lvl 3, the geometry may be still there, so Validator highlight some of the streets, but not the others.

3. Out of screen segments are not loaded, but sometimes they are still there when we pan around. Some Validator checks need all of the segments to be loaded.


Plus there are few Validator limitations:
1. Checks marked with "slow" does not run on zoom level 0-3.

2. There is a limit of reported segments per check (300). The 'Clear' button becomes red and there is a message in the segment's properties for that. So you can't report/highlight more that 300 blue custom check segments, you need to click the 'Clear' button time to time :(

3. There is a total number of segments limit (20K). Same, you'll see the red 'Clear' button and the message.

4. The therm "editable segment" in Validator has a bit stricter meaning: the segment properties should be editable and both of the nodes.

I hope that answers your questions.

EDIT: There is also few "bypasses" in Validator I forgot to mention:
1. Validator skips all checks for non-editable segments, which were updated after the 2014-05-01. There is a message in the segment's properties for that. We mark "exceptions" this way.

2. Validator skips all checks (but overlapping segments) for unconfirmed roads.

3. Validator skips all checks (but overlapping segments) for construction zones.
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.3 / 07.10.2014

Postby berestovskyy » Sun Oct 19, 2014 7:43 am

Hi,
voludu2 wrote:is a custom check like ${state} !/Pennsylvania/ a slow search?

No, custom checks are not marked as slow, so they run whenever all other conditions are met.

voludu2 wrote:should a segment which is locked above my level and which matches the custom check be highlighted?

There is also few "bypasses" in Validator I forgot to mention:
1. Validator skips all checks for non-editable segments, which were updated after the 2014-05-01. There is a message in the segment's properties for that. We mark "exceptions" this way.

2. Validator skips all checks (but overlapping segments) for unconfirmed roads.

3. Validator skips all checks (but overlapping segments) for construction zones.


bart99gt wrote:Is there any way Validator could check for a segment that is in the opposite direction of the ones surrounding it, perhaps limited to minor highways and above?

If I understand that correctly, two one-way segments connected at a node and running in opposite directions should trigger "no inward/outward connectivity". Unfortunately, those checks are not working at the moment :(
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.3 / 07.10.2014

Postby berestovskyy » Sun Oct 19, 2014 4:28 pm

sketch wrote:By "locked", do you mean any lock at all, or just locks past a certain level?

Good point. Sure, Validator skips all the checks if user level is less than segment lock level.
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.5 / 06.01.2015

Postby berestovskyy » Tue Jan 06, 2015 12:22 am

06.01.2015 v1.1.5:
- Temporary disabled #36, 37 (Unneded node A/B)
- Fixed the crash on a new segment save
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.4 / 07.11.2014

Postby berestovskyy » Tue Jan 06, 2015 12:33 am

SuperMedic wrote:Is there a way to provide an access function that returns an array or object of all of the segments that have been found?

Well, internally there is such an array. Unfortunately due to the compilation process, the fields might change their names from version to version :(

I plan to release an open source version o Validator, so it would be possible to access such an array there.
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

Re: [Script] WME Validator 1.1.8 / 07.05.2015

Postby berestovskyy » Thu May 07, 2015 7:32 pm

The update has been published.
Sorry for the inconvenience :(
berestovskyy
Waze Global Champs
Waze Global Champs
 
Posts: 919
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 235 times
Been thanked: 644 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: No registered users