[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.7.3 (BETA) / 24.02.2014

Postby berestovskyy » Fri Feb 28, 2014 7:29 am

magfro wrote:Why does WME Validator default to Spanish and not English and how do I change that?

Switch WME language to English for now, the bug will be fixed in the next release.
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby berestovskyy » Fri Feb 28, 2014 6:09 pm

28.02.2014 v0.7.4:
- UPD 'Too sharp turn at node A/B':
revCon turns are excluded
- UPD for US 'Lowercase street name (with exceptions)'
now the check ignores [ENSW] at the beginning
- Fixed 'Zoom out to start WME Validator' message
- Fixed Spanish in Swedish language
- UPD howto for 'The segment is overlapping'
- Disabled for AU 'More than 55 letters Ramp name'

bobthedog007 wrote:There was a discussion here about segments with the same endpoints causing problems.

It's still in this thread: forum post

ditchi56 wrote:Can you extend it to pick up cases like these, where the road loops round and ends on itself

I'll try to implement it, but no promises.
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.3 (BETA) / 24.02.2014

Postby berestovskyy » Fri Feb 28, 2014 9:54 pm

Timbones wrote:In my testing, the hasHNs attribute is only set to true immediately after editing the house numbers.

Hmm... As I wrote I tested the feature few days ago and it worked fine :? I just tried to reload WME with/without the segment selected and in both cases hasHNs was correctly set to true.

At the moment I see in WME just one line of code with hasHNs and it's just a simple return operator.
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby berestovskyy » Sat Mar 01, 2014 8:39 am

Laurentwb wrote:I am wondering if would be possible to get a version that would highlight primary streets that are not locked at level 2.

Sure, will be implemented in the next release for Benelux.
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby berestovskyy » Sun Mar 02, 2014 9:00 am

LeighGr wrote:Here's a segment breaking a couple of validation rules, but is not highlighted by WMEV

Validator does report 'Dead-end U-turn' and 'Soft turns on drivable road' on that segment, but please read below.

At the moment, Validator reports up to 300 segments per issue to save memory. So if you pan around the map for some time and there are more than 300 segments with 'Soft turns' for instance, Validator will stop highlighting soft turns, but will continue to highlight other issues.

When you reach the limit, the clear report button becomes red. If you click the button and start the report over, Validator will highlight soft turns and other issues again.

I'm aware that in some cities you can reach the limit almost instantly (there are too many soft turns or unknown directions), but I have no solution at the moment, sorry :(
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby berestovskyy » Mon Mar 03, 2014 10:43 am

LeighGr wrote:I had disabled Validator

I'll add a note in the segment's properties if Validator is disabled or the limit has reached.

GizmoGuy411 wrote:#47 The drivable non-private segment has no single inward turn enabled at node B.

This segment is two-way segment, that has no connectivity at node B. The segment after node B is one-way away from node B. The only inward access to the segment is via private business road.

A permalink would help. But in theory Validator reports #47 only if inward connectivity is possible at node B (i.e. there is at least one connected segment, it is drivable and its direction is two-way or one-way directed to the reporting segment)
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby berestovskyy » Mon Mar 03, 2014 9:11 pm

The problem is at node B (Freeway). I guess you have to make this Dearborn Ave a one-way road (direction to freeway).

But you are right, there might be some cases like this one. I guess we have to analyze a turn's angle as well...
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby berestovskyy » Tue Mar 04, 2014 1:44 pm

ditchi56 wrote:Would it be possible to have a function in Validator settings to control the maximum number of items reported?

Could you please give me a permalink to an area where your browser is out of memory? I'll have a look how many segments/issues are there...
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby berestovskyy » Tue Mar 04, 2014 9:23 pm

ditchi56 wrote:it said "WME Validator has checked 11653 segments and reported 12 errors (1‰), 277 warnings (24‰) and 261 notes"

It means there are just 12+277+261 issues :? Even if I lower the limit to a 100 of segments per check, I guess it will change nothing for such a low amount of the issues.

Maybe the problem is not related to Validator itself? You might opened too many WME windows or something?
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

Re: [Script] WME Validator 0.7.4 (BETA) / 28.02.2014

Postby berestovskyy » Thu Mar 06, 2014 8:52 am

ditchi56 wrote:I believe the problem (apart from a machine running low on storage) is the size of the "data" web page generated for the report.

I just measured the size of "data" document for the area you send me (12+277+261 issues). It is less than 100KB (Save page as->HTML Only).

I tried few versions back to generate the report in a bit different way, but this "data" method was the most reliable and worked both in Chrome and Firefox. I guess I have to try again...

ituajr wrote:Is it possible to produce a warning for a gas station landmark that is too small?

Sure it is possible and it is planned, but at the moment Validator does not analyze the landmark layer :( As you might know, Waze introduces significant changes in the landmarks, so IMO we better wait until it's all settled down...
berestovskyy
 
Posts: 1680
Joined: Fri Jul 15, 2011 1:50 pm
Has thanked: 259 times
Been thanked: 714 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: Babay_sar, dspille, MapOMatic