[Script] WME Validator 1.1.20 / 03.11.2016

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

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 0.9.6 (BETA) / 08.04.2014

Postby SuperDave1426 » Tue Apr 08, 2014 3:20 pm

pjlasl wrote:I noticed that street names that begin with numbers (i.e. 8th Steet) are being flagged with the following message: #170 The street name starts with a lowercase word.

Yup, this morning I found a whole bunch of stuff suddenly highlighed by the validator complaining about lowercase street names, and they were all streets such as "W 2nd St" and so on. Needs to be fixed. :-)

I would also exclude the word "to" from the lower case filter selection as shown here

I thought that "to" already was exempted previously, since that's used as part of an onramp name and it's almost always been lowercase. Definitely agree that if the Validator has started flagging those, that's something else that needs to be fixed.

Edit: Yup, I can confirm that it's flagging "to" as longercase name on ramps. It seems to happen to ramp segments that aren't directly connected to a freeway. Here is an example. It needs to not flag "to" on a ramp name, regardless of what it's connected to.

berestovskyy wrote:PS. I hope I'll get #170 fixed soon, sorry :(

Ok, I guess you know about and are working on all that stuff then. :-)
SuperDave1426
Country Manager
Country Manager
 
Posts: 869
Joined: Wed Oct 16, 2013 5:27 pm
Location: Nevada, USA
Has thanked: 80 times
Been thanked: 250 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby berestovskyy » Tue Apr 08, 2014 3:17 pm

Ok, guys I got that you need to see issues on locked segments.

Any ideas regarding
we need to agree on how do we mark those false positives on the map, so other editors do not try to fix them just because Validator says so.

or I didn't get your proposal with highlighting :? I wish we had a comment field...

But how about this: do not highlight/report a segment:
1) if the segment was locked above editor's level
2) and it was modified after 2014-05-01

So you will get the issues on the "old" locked segments, but never on recently updated segments.

PS. I hope I'll get #170 fixed soon, sorry :(
berestovskyy
 
Posts: 844
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 711 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby kentsmith9 » Tue Apr 08, 2014 2:48 pm

berestovskyy wrote:Kent, it's always available under Settings->About->Available checks. If you click it over the US, Validator will show enabled/disabled checks for US. And I just added a red link to the OP ;)

- New for US #106 'No state name selected'

Great and Greater! :D
kentsmith9
Waze Global Champs
Waze Global Champs
 
Posts: 5522
Joined: Mon Apr 23, 2012 3:33 pm
Location: SF/SJ Bay Area of Northern California
Has thanked: 1466 times
Been thanked: 1670 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby pumrum » Tue Apr 08, 2014 2:26 pm

sketch wrote:Perhaps for locked segments the Validator highlight could be displayed differently. Maybe a few dark or black stripes along the segment? Alternating lighter-darker colors?


I can see value in this. Something similar to what WMECH does -- segments locked to your rank or lower are accented in color, segments locked above your rank are accented in black. For validator, maybe the "halo" could be outlined in either bright pink or black depending on the above? If you really want to get crazy, you could vary the shade of pink based on the lock level - higher the lock the brighter the pink? just some ideas...

but in the end I definitely want to see validator show me issues with locked segments, even if they're above my rank. :)
pumrum
 
Posts: 669
Joined: Mon Dec 09, 2013 3:02 am
Has thanked: 92 times
Been thanked: 299 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby sketch » Tue Apr 08, 2014 1:43 pm

Perhaps for locked segments the Validator highlight could be displayed differently. Maybe a few dark or black stripes along the segment? Alternating lighter-darker colors?
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6007
Joined: Sat Aug 08, 2009 6:13 pm
Location: New Orleans, LA
Has thanked: 1479 times
Been thanked: 2024 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby pjlasl » Tue Apr 08, 2014 1:07 pm

I noticed that street names that begin with numbers (i.e. 8th Steet) are being flagged with the following message: #170 The street name starts with a lowercase word.

I would also exclude the word "to" from the lower case filter selection as shown here
pjlasl
Area Manager
Area Manager
 
Posts: 378
Joined: Tue Nov 13, 2012 2:41 pm
Location: Weatherford, TX
Has thanked: 31 times
Been thanked: 110 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby j4m35ch3w » Tue Apr 08, 2014 1:07 pm

Hi berestovskyy,

I'm getting a lot of false positives in the US for rule "#170 'Lowercase street name' (merged #93, #94)" since v0.9.5.

Permalink: https://www.waze.com/editor/?zoom=5&lat ... 89&env=usa

The false positives come in the form of "25th St" or "A St" and the likes. I appreciate you looking into it.

Another false positive type in the form of "W U pass St" here: https://www.waze.com/editor/?zoom=7&lat ... ts=7067915

Thanks,
James
Last edited by j4m35ch3w on Tue Apr 08, 2014 1:36 pm, edited 2 times in total.
j4m35ch3w
 
Posts: 13
Joined: Sun Aug 04, 2013 2:11 pm
Location: Singapore
Has thanked: 3 times
Been thanked: 2 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby pumrum » Tue Apr 08, 2014 12:33 pm

olestas wrote:Hiding problems in locked segments is bad. I report those to corresponding level editors in my area. You could add option that hides them by default after installation of script.. but it should be possible to change it.


Agreed. I find that the top level editors are busy fixing major infrastructure issues... It's up to us lower level editors to scour the maps looking for everything they don't have time to search for. I frequently find issues with rank 5/6 segments as the validator gets better updates. I post them to the unlock forum, and the CMs fix it when they have time. Good system.

The rank lock system is an invaluable tool to prevent damage to the critical infrastructure, and ignoring locked segments makes the incorrect assumption that the last editor was perfect in their changes :)
pumrum
 
Posts: 669
Joined: Mon Dec 09, 2013 3:02 am
Has thanked: 92 times
Been thanked: 299 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby irowiki » Tue Apr 08, 2014 12:30 pm

olestas wrote:Hiding problems in locked segments is bad. I report those to corresponding level editors in my area. You could add option that hides them by default after installation of script.. but it should be possible to change it.


That's how it was, by default. Maybe move the "exclude non editable" into the settings (where the sound setting is)
irowiki
 
Posts: 250
Joined: Tue Feb 11, 2014 3:05 pm
Has thanked: 68 times
Been thanked: 40 times

Re: [Script] WME Validator 0.9.6 (BETA) / 08.04.2014

Postby JohnDoe75 » Tue Apr 08, 2014 11:31 am

olestas wrote:Hiding problems in locked segments is bad. I report those to corresponding level editors in my area. You could add option that hides them by default after installation of script.. but it should be possible to change it.


I totally agree and do the same.
JohnDoe75
Local Champ Mentor
Local Champ Mentor
 
Posts: 3134
Joined: Sun Dec 25, 2011 10:06 am
Location: Paris, France
Has thanked: 130 times
Been thanked: 517 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: Baidu [Spider], bz2012, dfortney, dspille