[Script] WME Validator 1.1.16 / 29.01.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.

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 0.6.3 (BETA) / 12.02.2014

Postby SuperDave1426 » Wed Feb 19, 2014 6:31 pm

A feature request of my own. :-)

Is there any chance that a check can be added to highlight a road with a blank elevation? I've been running into two situations:

1) As I'm editing, I'm discovering blank elevations that I'm having to set as ground and then save, when then shows "ground" the next time I select those roads. This then results in my checking a lot of extra roads nearby that I'm not otherwise planning to edit to see if they've got the blank elevation as well. If the Validator highlighted empty elevations, then I'd be able to simply look around and know which ones need to be fixed.

2) I'll edit a road that already has a elevation of ground, but after I've made my edit(s) (none of which involve elevation), when I select the road again it will now be blank instead of "ground." This does not happen all the time - only for some roads. As a result, I'm wasting a lot of time editing a road and then having to select it again after saving to make sure the elevation is still right. If it is, then I move on and if not, then I change it back to ground and resave. If the Validator highlighted empty elevations, then I could eliminate the need to click on something I just finished editing simply to ensure that it's still set to "ground" and will only have to do it if it lights up after I save. (I sometimes have dead-end U-Turns that were green where the save at hard restricted didn't "stick" for some reason and reverted back to green after the save - since the highlighter lights up those roads, know I need to go back and do it again without having to waste time reselecting every dead-end I edit just to be sure the restriction is in place.)

So, any chance this check can be added? Maybe make it a selectable option so that those who don't care won't be pestered by them? :-)
ImageImageImageImage
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Places Guidelines Nevada Wiki
SuperDave1426
Country Manager
Country Manager
 
Posts: 780
Joined: Wed Oct 16, 2013 5:27 pm
Location: Nevada, USA
Has thanked: 73 times
Been thanked: 219 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby irowiki » Wed Feb 19, 2014 6:53 pm

Just wanted to say thanks for this, really helps a newbie get going!
irowiki
 
Posts: 250
Joined: Tue Feb 11, 2014 3:05 pm
Has thanked: 68 times
Been thanked: 39 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby BellHouse » Wed Feb 19, 2014 8:02 pm

SuperDave1426 wrote:Is there any chance that a check can be added to highlight a road with a blank elevation?

Blank elevations do not exist in the database, they are just sometimes displayed in WME by a long standing bug that's masked by the Junction Node Fixer Script (JNF). It happens after saves and the features are reloaded before the changes have fully propagated. Causing the features to reload (reload page, permalink, pan/zoom far enough, WME Toolbox key) clears it.
Image
Global Champ / DACH Champ / CM Germany / Self-Management-Team Germany
BellHouse
Waze Global Champs
Waze Global Champs
 
Posts: 2952
Joined: Sun May 12, 2013 5:57 pm
Location: Cologne / Germany
Has thanked: 618 times
Been thanked: 1717 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby berestovskyy » Wed Feb 19, 2014 8:16 pm

I couldn't find any blank elevation around, but I found few segments with out of range elevation (i.e. level 20) and WME displays it as a blank. Here is an example: permalink

'Two-way ramp' will be disabled for US.
berestovskyy
 
Posts: 924
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 248 times
Been thanked: 690 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby SuperDave1426 » Wed Feb 19, 2014 8:35 pm

BellHouse wrote:
SuperDave1426 wrote:Is there any chance that a check can be added to highlight a road with a blank elevation?

Blank elevations do not exist in the database, they are just sometimes displayed in WME by a long standing bug that's masked by the Junction Node Fixer Script (JNF). It happens after saves and the features are reloaded before the changes have fully propagated. Causing the features to reload (reload page, permalink, pan/zoom far enough, WME Toolbox key) clears it.

Ok, thanks for the info. Question: How does that account for times when I've gone into an area, and even before editing anything I've got empty elevation segments showing? I've tried zooming, moving around, etc., and it still shows empty instead of "ground."

By "masked by the JNF," do you mean that when I've selected a segment that was showing ground but then ended up as empty, that the JNF was masking the out-of-range elevation and thus it was showing as "ground" even though it wasn't actually that way in the database? And that for an apparently short time after I saved an edit it was showing as empty again until the JNF catches up to it? I'm just trying to make sure I understand what you're describing above.

If that's the case, then maybe the validator could be looking for things that are out of range and either give you a one-button fix or highlight them so that they can be looked into? The JNF may be making it so that out-of-range looks like "ground" in the editor (if I'm understanding you correctly), but that doesn't change the fact that the value is wrong in the database under those conditions....
ImageImageImageImage
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Places Guidelines Nevada Wiki
SuperDave1426
Country Manager
Country Manager
 
Posts: 780
Joined: Wed Oct 16, 2013 5:27 pm
Location: Nevada, USA
Has thanked: 73 times
Been thanked: 219 times

Re: [Script] WME Validator 0.6.3 (BETA) / 12.02.2014

Postby SuperDave1426 » Wed Feb 19, 2014 8:38 pm

berestovskyy wrote:I couldn't find any blank elevation around, but I found few segments with out of range elevation (i.e. level 20) and WME displays it as a blank. Here is an example: permalink


Based on my understanding of what BellHouse said in his post, that's probably what I've been running into.

That being the case, is there a way that you can have the Validator check for things like that or, better yet, give us a way to quickly fix them when we encounter them? :-)
ImageImageImageImage
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Places Guidelines Nevada Wiki
SuperDave1426
Country Manager
Country Manager
 
Posts: 780
Joined: Wed Oct 16, 2013 5:27 pm
Location: Nevada, USA
Has thanked: 73 times
Been thanked: 219 times

Re: [Script] WME Validator 0.7.0 (BETA) / 19.02.2014

Postby berestovskyy » Wed Feb 19, 2014 10:39 pm

19.02.2014 v0.7.0:
- complete Spanish translation thanks to robindlc and
fernandoanguita
- WME language switcher now also switch language of
problem and howtos (but not links)
- 'Updated by' search option for country managers

- NEW for ALL: 'Out of range elevation'
- NEW for ALL: 'Non-drivable connected to drivable'
- NEW for IT: 'Ramp name starts with an A' (untested)
- NEW for ALL: 'More than 55 letters Ramp'
- UPD #51 for PL 'Incorrectly abbreviated street name'
added: bł., kard., marsz., rtm.
- UPD #101 'Closed road': default marker is '(Closed)'
- UPD #40 'Soft turns on drivable road': check for
both nodes exist
- UPD 'Incorrect lock level' checks for traffic locks
- UPD 'No connection at node A/B': exclude non-editable
segments filter option
- UPD for IL 'Less than 2 letters long street name'
- DISABLED for US 'Two-way Ramp segment'
- What's the problem and howtos are replaced with icons
- fixed WME Color Highlights wiki URLs
- added input placeholders
- now Validator reports max 300 segments per check
berestovskyy
 
Posts: 924
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 248 times
Been thanked: 690 times

Re: [Script] WME Validator 0.7.0 (BETA) / 19.02.2014

Postby SuperDave1426 » Wed Feb 19, 2014 10:49 pm

berestovskyy wrote:19.02.2014 v0.7.0:
- DISABLED for US 'Two-way Ramp segment'

Can you make this an option that can be turned on/off, so that those of us who live in areas where two-way ramp segments simply don't happen won't miss one that gets created by mistake? :-)
ImageImageImageImage
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Places Guidelines Nevada Wiki
SuperDave1426
Country Manager
Country Manager
 
Posts: 780
Joined: Wed Oct 16, 2013 5:27 pm
Location: Nevada, USA
Has thanked: 73 times
Been thanked: 219 times

Re: [Script] WME Validator 0.7.1 (BETA) / 20.02.2014

Postby berestovskyy » Wed Feb 19, 2014 11:35 pm

SuperDave1426 wrote:Can you make this an option that can be turned on/off

You can "turn off" any check you want using 'Reported as' field in the "Search" tab.

For instance, to disable #40 'Soft turns' highlighting/reporting you may put the following:
Code: Select all
!40,*

Hover your mouse over the field for more examples.

Unfortunately, there is no way to force "turn on" a check once it has been disabled for your country :(

IMO Two-way Ramp is not a error and at the moment the check is enabled just for one country.


20.02.2014 v0.7.1:
- HOTFIX: fixed few highlight issues
berestovskyy
 
Posts: 924
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 248 times
Been thanked: 690 times

Re: [Script] WME Validator 0.7.1 (BETA) / 20.02.2014

Postby SuperDave1426 » Thu Feb 20, 2014 1:14 am

berestovskyy wrote:
SuperDave1426 wrote:Can you make this an option that can be turned on/off

You can "turn off" any check you want using 'Reported as' field in the "Search" tab.

For instance, to disable #40 'Soft turns' highlighting/reporting you may put the following:
Code: Select all
!40,*

Hover your mouse over the field for more examples.

Unfortunately, there is no way to force "turn on" a check once it has been disabled for your country :(

Then how about re-enabling it and letting the people who don't want the check to use the above trick to turn it off? ;) That way, everyone gets what they need from it.

IMO Two-way Ramp is not a error and at the moment the check is enabled just for one country.

I'm sure that will be a great comfort to the first person who gets routed the wrong way onto a freeway because an editor didn't see that it was allowing traffic in both directions.... 8-) (Yes, I'm being somewhat facetious here.)
ImageImageImageImage
Country Manager: USA (mostly oriented around NV & CA)
Editor Guide Best Editing Practices Editor Quick-start
Places Guidelines Nevada Wiki
SuperDave1426
Country Manager
Country Manager
 
Posts: 780
Joined: Wed Oct 16, 2013 5:27 pm
Location: Nevada, USA
Has thanked: 73 times
Been thanked: 219 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: DengKao