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

Postby sketch » Tue Apr 15, 2014 5:21 pm

Discussion on the US localized Validator checks has been moved to the United States forum.

WME Validator localization for US
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: [Script] WME Validator 0.9.8 (BETA) / 15.04.2014

Postby sketch » Thu Apr 24, 2014 5:16 am

MGODLEW wrote:I'd like to make a request for Validator. In Pennsylvania we have a lot of roads that have not had their primary names updated since the base map. For the example here the roads primary name is currently "T493" however the actual primary name is in the alternative "Hanny Beaver Rd" Is there a way you can color roads that are a letter & number? I'm no programmer or script writer but my guess is the script would be something like <If street name = character (T)(integer)(integer)(integer) then color = Lime Green> I this possible to add? If not an always on feature then something that can be turned off and on.

Is it always T followed by 3 digits and that's it?

If so, set this in your custom check:
custom template:
Code: Select all
${street}
custom regexp:
Code: Select all
/^T[0-9]{3}$/
That will report every instance where the road name is "T###" exactly, nothing before or after, not even a space. (It seems to be working for this example.)

If you remove only the "$" it will report everything that starts with "T###" regardless of what follows, if you remove only the "^" it will report everything that ends with "T###" regardless of what comes before, and if you remove both ^ and $ it will report everything that has T### in it at all.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: [Script] WME Validator 0.9.9 (BETA) / 27.04.2014

Postby sketch » Sun May 11, 2014 6:46 pm

I like to use http://www.downforeveryoneorjustme.com/ for that purpose.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: [Script] WME Validator 0.9.9 (BETA) / 27.04.2014

Postby sketch » Mon May 19, 2014 3:44 am

Right, I'm not even sure it should be offered. Might encourage editors to change a category erroneously. For example, a cigar shop – doesn't really fit anywhere besides the general "Shopping and services".
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: [Script] WME Validator 1.0.0 / 26.05.2014

Postby sketch » Sun Jun 01, 2014 1:54 am

Sorry if I'm just remembering wrong, but is the scan supposed to pick up on custom checks and put them in the report?
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: [Script] WME Validator 1.0.0 / 26.05.2014

Postby sketch » Mon Jun 02, 2014 9:40 pm

ispyisail wrote:Any chance you could expand the your example for PLR exclusion?

template: ${type}:${street}:${length}
expression: /^[1234678]::([0-9]{3,5}|[5-9][0-9]$)/

That will highlight for Street, Primary Street, Freeway, Ramp, Major Highway, Minor Highway, and Dirt Road. I think.
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: That BEEPING Beeping!

Postby sketch » Tue Jun 03, 2014 6:25 pm

An alternative to ${type} is ${typeRank}, which uses the following codes:

${typeRank}
15 freeway
14 major highway
13 minor highway
12 ramp
11 primary street
10 street
9 service road
8 dirt road
7 parking lot road
6 private road
5 walking trail
4 pedestrian bdwk
3 stairway
2 railroad
1 runway

Kinda makes it easier if you wanna do, say, all public drivable roads (1[0-5]). Also a little easier to remember.

bummerdude69 wrote:Two questions
1) what does the various beeps mean? Seems to have a purpose, but haven't figured it out.
2) How do you turn that NOISE OFF?!? ;)

1) One beep per "screen", with a higher-pitched beep at the end.
2) Gear, wrench, uncheck "Enable sounds".
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: [Script] WME Validator 1.0.0 / 26.05.2014

Postby sketch » Tue Jun 03, 2014 7:12 pm

How does it define "drivable"? Is that just everything from Freeway to Street and Ramp, or does it also include conditionally drivable roads like Private, PLot, and Dirt?
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: That BEEPING Beeping!

Postby sketch » Tue Jun 03, 2014 7:29 pm

bummerdude69 wrote:1) I'd guess the longer between pages (beeps), the more segments to check?

Yep, at least I believe so. When I scan an area that has both urban/suburban roads and large lakes/swamps, I get lots of really quick beeps and a number of well-spaced ones, with some in between (probably along the edges between built areas and swamps/lakes).
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

Re: New thoughts

Postby sketch » Fri Jun 06, 2014 3:38 pm

krikketdoug wrote:1> Walking trails and other non-drivable road types that have a elevation of something other than -5 be flagged. By running the script near my home, I found a few examples of this, so I have a feeling it's not that uncommon of an error.

I'm not sure how much of the rules support this, exactly. Railroads are to be set at -5, certainly, as are Walking Trails (if mapped at all), I believe, but a Pedestrian Boardwalk shouldn't always, necessarily. I think a lot of these rules are in flux.

2> Now that the US is moving to a Functional Classification system, I've found an odd segment here and there that don't match the new FC system. Each side of the segment has a different road type but the same street name. Usually it's a short segment between a parking lot and a cross street, but I'm wondering how many more are out there. From what I understand, the changing of the road type can cause routing problems. So I propose we check against that as well.

This could be good -- given 3 segments with the same name, if the segment in the middle has a different type than the segments on the ends, flag it. I imagine this would be a 'slow' check, but that's fine.

3> Another check that would probably have to be handled on the country level now that Landmarks has transisitioned to Places is a check on the new Places markers versus what the rules say they should be. For example, for a while a religious site was permitted while a simple church was not. On the other hand many editors concluded that any site that had hundreds of worshippers visiting it every day or was over a hundred years old (Hey! I'm in America! Here that is a long time!) or... You get the idea. In each country there should be (eventually) a list of approved typed of markers in the Wiki that could be used to compare what is used. [edited to remove additional unnecessary examples]

Much simpler under the new rules, if I understand everything correctly. Just mark them all places(points) instead of places(areas). [edited to remove a reference to the unnecessary examples]

Krikket

I don't mind the idea, but I think Places is still too young to start incorporating things into Validator about it -- especially in the rest of the world.

kentsmith9 wrote:Validator and Toolbox both believe this segment should be straightened, but in my opinion is pulls the road a little too far off the actual road since it curves. It seems like it might be a little too aggressive in what they are both considering is a straight enough line.

The Validator-Toolbox highlights are pulled straight from Toolbox -- in other words, Validator is just reporting what Toolbox reports in its reports -- so only Toolbox's selection criteria will affect this (but I agree that Toolbox is too aggressive in this function).
ALL US EDITORS READ: New USA road type guidance
assistant regional coordinator • south central region • usa
waze global champ • beta leader • tier one • new orleans
2017 chevrolet ss sedan 6mt • slipstream blue metallic
[ img ] [ img ]
sketch
Waze Global Champs
Waze Global Champs
 
Posts: 6535
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2205 times
Been thanked: 2669 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: Google Feedfetcher, Mapman44