[Script] WME Validator 2020.04.12 (PLACES BETA)

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, Glodenox, JustinS83

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.20 / 03.11.2016

Postby ldriveskier » Wed Apr 19, 2017 8:21 pm

Sorry, I don't understand the nuts and bolts of the required updates, but I know that XanderB updated the Validator Localization scripts for the states that I use it for when the new language was released to WME. I would suggest dropping him a PM if you'd like to compare notes (or to point him to your post here). Good luck!
[ img ][ img ][ img ][ img ][ img ][ img ]
USA LC/CM, MAR ARC, GLR LC (resident of Ohio), App Beta Leader
ldriveskier
Coordinators
Coordinators
 
Posts: 904
Joined: Fri Feb 19, 2016 9:05 pm
Location: Northeast Ohio, United States
Has thanked: 1793 times
Been thanked: 1051 times

Re: [Script] WME Validator 1.1.20 / 03.11.2016

Postby ldriveskier » Mon Jul 17, 2017 2:38 pm

I would recommend locking this thread and adding a "MOD NOTE" to the OP like was done for the Closest Segment script. This topic could be reopened if/when the original author returns.
[ img ][ img ][ img ][ img ][ img ][ img ]
USA LC/CM, MAR ARC, GLR LC (resident of Ohio), App Beta Leader
ldriveskier
Coordinators
Coordinators
 
Posts: 904
Joined: Fri Feb 19, 2016 9:05 pm
Location: Northeast Ohio, United States
Has thanked: 1793 times
Been thanked: 1051 times

Re: [Script] WME Validator 2019.09.24 (PLACES BETA)

Postby ldriveskier » Mon Mar 09, 2020 4:23 pm

RichardPyne wrote:Using version 2019.09.24 when trying to scan, it appears that the scan starts, then just stalls.


Try turning off other scripts, especially WME Color Highlights. IME, it seems to be a script conflict.
[ img ][ img ][ img ][ img ][ img ][ img ]
USA LC/CM, MAR ARC, GLR LC (resident of Ohio), App Beta Leader
ldriveskier
Coordinators
Coordinators
 
Posts: 904
Joined: Fri Feb 19, 2016 9:05 pm
Location: Northeast Ohio, United States
Has thanked: 1793 times
Been thanked: 1051 times

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

Postby LeighGr » Mon Feb 24, 2014 11:44 pm

berestovskyy wrote:24.02.2014 v0.7.3:
- NEW for All 'BETA: Overlapping segments at node A/B'
- NEW for All 'BETA: Too sharp turn at node A/B'
- check IDs moved to the end of the check title


Something isn't quite right. The only instruction I'm getting is "Zoom out to start WME Validator". I'm at zoom level 0, and can't go out anymore :)
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
LeighGr
Waze Local Champs
Waze Local Champs
 
Posts: 469
Joined: Mon May 28, 2012 5:50 pm
Location: Durbanville, Cape Town, South Africa
Has thanked: 268 times
Been thanked: 123 times

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

Postby LeighGr » Mon Feb 24, 2014 11:48 pm

LeighGr wrote:
berestovskyy wrote:24.02.2014 v0.7.3:
- NEW for All 'BETA: Overlapping segments at node A/B'
- NEW for All 'BETA: Too sharp turn at node A/B'
- check IDs moved to the end of the check title


Something isn't quite right. The only instruction I'm getting is "Zoom out to start WME Validator". I'm at zoom level 0, and can't go out anymore :)


:oops: Sorry, Brain dead. Validator was disabled. :oops: Though not the right error message, should be more like "Click the button below to enable"!

Repeatable by disabling WMEV, then pressing the "Clear the report and segment cache" button, and you're left with a "Zoom out to start WME Validator" message.
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
LeighGr
Waze Local Champs
Waze Local Champs
 
Posts: 469
Joined: Mon May 28, 2012 5:50 pm
Location: Durbanville, Cape Town, South Africa
Has thanked: 268 times
Been thanked: 123 times

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

Postby LeighGr » Tue Feb 25, 2014 4:25 am

Here's an example of rule "#119 The segment is overlapping with the adjacent segment at node B." being triggered, but it's actually an unneeded geometry point that needs to be removed, so possibly a changed to the resolution wording:

Spread the segments at 2° or delete the duplicate segment or unneeded geometry point at node A/B.
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
LeighGr
Waze Local Champs
Waze Local Champs
 
Posts: 469
Joined: Mon May 28, 2012 5:50 pm
Location: Durbanville, Cape Town, South Africa
Has thanked: 268 times
Been thanked: 123 times

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

Postby LeighGr » Sun Mar 02, 2014 8:35 am

Hi berestovskyy

Here's a segment breaking a couple of validation rules, but is not highlighted by WMEV, though a modified WMECH to highlight bad street names in South Africa does pick it up.

The street name is a single period(.) and the dead end u-turn is enabled.

I couldn't figure out what the two black dots on the screen were, as they moved when I panned around. :)

Regards,

Leigh
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
LeighGr
Waze Local Champs
Waze Local Champs
 
Posts: 469
Joined: Mon May 28, 2012 5:50 pm
Location: Durbanville, Cape Town, South Africa
Has thanked: 268 times
Been thanked: 123 times

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

Postby LeighGr » Sun Mar 02, 2014 9:14 am

berestovskyy wrote: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 :(


Thanks, I'd forgotten that. I'd zoomed right out, ran the scan which took for 10 minutes - that only should have jogged my memory :oops: Next time I'll clear the report and rerun the scan at a higher zoom level.
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
LeighGr
Waze Local Champs
Waze Local Champs
 
Posts: 469
Joined: Mon May 28, 2012 5:50 pm
Location: Durbanville, Cape Town, South Africa
Has thanked: 268 times
Been thanked: 123 times

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

Postby LeighGr » Sun Mar 02, 2014 9:32 am

berestovskyy wrote:
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.


:oops: Now I feel like a right royal idiot. I had disabled Validator, then ran the scan, and hadn't turned Validator on again. Just enabled it and the whole map lit up. :oops:
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
LeighGr
Waze Local Champs
Waze Local Champs
 
Posts: 469
Joined: Mon May 28, 2012 5:50 pm
Location: Durbanville, Cape Town, South Africa
Has thanked: 268 times
Been thanked: 123 times

Re: [Script] WME Validator 1.1.8 / 07.05.2015

Postby LeighGr » Thu Oct 01, 2015 7:17 pm

I'm busy creating a WMEV localization pack for South Africa, but am bashing my head against a wall with some weird errors. The following code works fine for mH segments named R100 to R512, and then again from R516 onwards, but R513, R514 and R515 all get flagged as incorrect. WHY?????

Code: Select all
// Custom Check - Minor Highway Name Format
  "137.enabled": true,
  "137.params": {
    "titleEN": "Incorrect name format on Minor Highway",
    "problemEN": "All Minor Highways name format should be (R###) numbered > 100 ",
    "solutionEN": "Change name to ... (R###)",
    "template": "${typeRank}:${street}:${direction}",
    "regexp": "/(13):(?!R[0-9]{3} [NESW]:(1|2) ?|(R[0-9]{3}:(3))$)/"
  },
  "137.solutionLink": "W:South_Africa#Road_Network",
Leigh Greyling
Redmi 8, Android 10.0.0, Waze: Whatever the latest beta is!
LC: South Africa
CM: Southern Africa
LeighGr
Waze Local Champs
Waze Local Champs
 
Posts: 469
Joined: Mon May 28, 2012 5:50 pm
Location: Durbanville, Cape Town, South Africa
Has thanked: 268 times
Been thanked: 123 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: BenEnmen, jangliss, Mapman44, Mythdraug