[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.4 (BETA) / 30.03.2014

Postby berestovskyy » Mon Apr 07, 2014 9:17 am

No worries, Validator is a read-only tool. At the moment it's dozens of files/~15K lines of source code project roots in WMET, so I never paid attention to those messages. And frankly, I have no idea how did you get into that part of legacy code :lol:

But sure, it will be fixed in the next release.
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: [Script] WME Validator 0.9.4 (BETA) / 30.03.2014

Postby berestovskyy » Fri Apr 04, 2014 4:18 pm

lg1992 wrote:Are there plans to enable checking for invalid elevation? If not, can I enable this checking just for me? If not, what's the correct rule to define custom condition for that?

Sorry, I couldn't reproduce the issue in my environment, so there is no plans to re-enable it unless someone ask me to. But sure you can use custom check to find null elevations.

Click Settings->custom and in "Custom template" field put:
Code: Select all
${elevation}

In the "Custom RegExp" field put:
Code: Select all
null
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: [Script] WME Validator 0.9.4 (BETA) / 30.03.2014

Postby berestovskyy » Wed Apr 02, 2014 5:55 am

sketch wrote:check out Street View on the service road at Aurora and Orion here — to prohibit drivers from cutting through the neighborhood when exiting the Interstate.

Wow, very nice and rare example. I just wondering how can we detect such a situation... A turn from a Ramp/Highway to the regular street or lower? Any ideas?

Although the map is perfectly correct, there are few possibilities to suppress the warning in Validator at the moment:
1. Add a 24/7 time based turn restriction from highway to the street.

2. Make an exiting piece of the screet one way.

3. Make the screet private.

I know it's ugly but a tempory solution. So, shall I exclude inward connectivities warnings for the turns from highways/ramps to streets/parking lots/dirts?
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: [Script] WME Validator 0.9.4 (BETA) / 30.03.2014

Postby berestovskyy » Tue Apr 01, 2014 8:35 pm

Please welcome one more language:

Localization and translation package* for Germany by BellHouse:
For Chrome browser: Chrome Web Store
For Firefox/Greasemonkey/Tampermonkey: userscripts.org
* Note: you also need the main package installed.

The package will be useful for any German-speaking editor, since it translates user interface, problem descriptions and solutions (once you switch WME into German), while applies the rules of the country you are using it in.

Many thanks to BellHouse for the great job!

If you would like to translate Validator into your language, please have a look at this forum post
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: right turn should be allowed

Postby berestovskyy » Tue Apr 01, 2014 6:18 am

sketch wrote:Wait, I have a problem with the "no right turn" check. Wouldn't it call for erroneous enabling of turns like the right turn from this segment?


Ok, how about that:
2. No right* turn (for any drivable road)
* for the right-hand traffic
Report/highlight the segment if at the node:
a) there is an up to 85° right turn
a1) and either this segment OR that right turn segment is longer than 300m (~1000 ft)
b) and that right turn segment is also drivable and non-private
c) and that right turn segment is not marked as closed
d) and the connectivity between those two segments is possible (road directions), but not enabled

Would that new a1) condition be sufficient to detect connectors and other possible exceptions?

BellHouse wrote:I don't get the idea behind 2.

The idea is that in right-hand traffic countries the right non-acute turns are mostly enabled except some rare situations. So we can assume that disabled right turn is an error.
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: [Script] WME Validator 0.9.4 (BETA) / 30.03.2014

Postby berestovskyy » Mon Mar 31, 2014 8:05 pm

Hi!
Got few new ideas, so I request for comments.

1. No road continuation (for Primary Streets and up)
Report/highlight the segment if at the node:
a) this segment's road type is the highest among the segments at the node
b) and there is another segment with the same road type and street name
c) and that another segment is not marked as closed
d) and the connectivity between those two segments is possible (road directions), but not enabled


2. No right* turn (for any drivable road)
* for the right-hand traffic
Report/highlight the segment if at the node:
a) there is a 90±5° right turn
b) and that right turn segment is also drivable
c) and that right turn segment is not marked as closed
d) and the connectivity between those two segments is possible (road directions), but not enabled


3. Geometry points are too close (for any drivable road)
Report/highlight the segment if:
a) the segment is a dead-end
b) and it has more than 2 geometry points
c) and the dead-end geometry point is very close (2 m?) to another point of the same segment
Here is an example posted on this forum some time ago: permalink

Any comments/suggestions?
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: [Script] WME Validator 0.9.4 (BETA) / 30.03.2014

Postby berestovskyy » Sun Mar 30, 2014 3:31 pm

30.03.2014 v0.9.4:
- Complete French translation of UI and checks.
Many thanks to arbaot and ClementH44!
- New variables for custom checks:
${altCity[index or delimeter]}
${altStreet[index or delimeter]}
- Fixed bug with highlighting at the screen edges
- CHECKS REVIEW:
I'm reviewing all the checks, removing unused, merging similar checks, adding params to some checks, splitting nodes A/B etc. So in this release:
Added 5 new checks #150-#154 for lock levels
Removed lock-related checks #65, #66, #67, #70, #71, #72, #76, #96, #97, and #122
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: [Script] WME Validator 0.9.3 (BETA) / 25.03.2014

Postby berestovskyy » Fri Mar 28, 2014 7:47 am

ditchi56 wrote:I wonder whether Validator could automatically fix some of the problems it detects when the user has asked it to run a scan? Is this feasible?

It was done few month ago. Validator is a stripped down read-only version of WME Mass Edit Tools (WMET). You can find the archival WMET thread over here: forum link

At the moment I have no plans to reincarnate WMET.
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: [Script] WME Validator 0.9.3 (BETA) / 25.03.2014

Postby berestovskyy » Wed Mar 26, 2014 2:10 pm

Hi!
BellHouse wrote:Is there a way to highlight segments which carry an alternate street name?

Sorry, alt. names are not available in the template at the moment. Since there might be few alt. street/city names, I'm not sure how to represent them in one string.

Any ideas?
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

Re: [Script] WME Validator 0.9.3 (BETA) / 25.03.2014

Postby berestovskyy » Tue Mar 25, 2014 9:34 am

25.03.2014 v0.9.3:
- Complete Spanish translation of UI and checks.
Languages: Español, Español América Latina and Galego
Many thanks to robindlc and fernandoanguita!

- CHECKS REVIEW:
I'm reviewing all the checks, removing unused, merging similar checks, adding params to some checks, splitting nodes A/B etc. So in this release:
Removed: #9, #11, #12, #75, #106 (duplicate/unused)
Added params to:
#52 'More than ${n} letters long street name'
#112 'More than ${n} letters long Ramp name'

- Check parameters are listed now in
'Settings->About->Available checks'
- Disabled nulls in #116 'Out of range elevations'

- Added Andorra as an alias for Spain
berestovskyy
 
Posts: 840
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 246 times
Been thanked: 690 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: abusimbel16, Google [Bot], RichardPyne