[Script] WME Validator v2020.11.1 (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.6.1 (BETA) / 05.02.2014

Postby sketch » Wed Feb 05, 2014 10:21 pm

^ (here, in response to Alan/Timbones)

Consider someone going to one of the buildings near the gate, after the gate is closed. If Waze doesn't ignore restricted roads entirely, having the restriction on the whole segment would make Waze indifferent to which direction it came into the segment, and would be just as likely to send you through the closed gate as it would be to send you through the complex (the "possible" way). If Waze does ignore restricted roads entirely, it'll send you to R806 instead of North Rd (inside the complex), which is unhelpful because those buildings are inside the fence.
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: [Script] WME Validator 0.6.2 (BETA) / 07.02.2014

Postby sketch » Sat Feb 08, 2014 3:23 am

dbraughlr wrote:I think it should not report any unless one of the junction angles is 0. I see the error when the junction angles are 90 degrees or more.

I think you misunderstand the need for the error. It's not just to show hidden segments, it's because of known navigation errors when segments share end-nodes.
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

Re: parallel paths to the same endpoints

Postby sketch » Mon Feb 10, 2014 2:12 am

dbraughlr wrote:Let's consider first a one-way terminal loop.

What is the known navigation error in this situation?
How do you correct it?

I'm not sure what the problem would be on a one-way terminal loop, if any, but knowing which way to go from a dead-end isn't really a problem.

Where I have seen numerous problem reports from segments which share endpoints is with simple parking lots and drive-thrus and simple freeway parking areas. I experienced the first personally in that same location. There have been a few threads on it; I don't have time to dig any of them up right now.
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

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

Postby sketch » Thu Feb 20, 2014 7:40 pm

Is it possible to make a report that includes every street segment with a particular name? For instance, we name U turn segments "U turn" in the New Orleans area, but many have been named "U-Turn" and "U Turn". Trying to standardize all of them is a heck of a task, but being able to search "U-Turn" in Validator would make a big difference.

Toolbox helps to some extent, but having to comb at Zoom 4 to load street type segments takes much, much longer than a Zoom 0 or 1 scan.
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

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

Postby sketch » Thu Feb 20, 2014 10:54 pm

Toolbox does not "scan" at all; it can only see what I can edit at a given zoom. The scan feature is Validator's great strength over other plugins, and it would be uniquely suited to this particular task. Not to mention it'd be a trivial addition to Validator, whereas adding a scanner to Toolbox would be a big change.


Sent from my iPhone using Tapatalk 2
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

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

Postby sketch » Fri Feb 21, 2014 5:13 pm

Regarding "(Closed)" / "(Construction Zone)" / "CONST ZN":

The "CONST ZN" suffix was a relic from a time before text-to-speech. It's pronounced "Const Zee Enn", which makes no sense. Adding the parentheses adds a pause, and now it says what it means, and it's easier to read, too. Also, when applied to closed roads, "CONST ZN" isn't really descriptive. I wouldn't expect the standard to change again unless Waze gives us a construction zone flag with a little digging man icon. One change to the Wiki in 3-4 years isn't too bad ;)

As such, the Validator should show results for anything containing "Construction Zone", "Closed", or "CONST ZN". The first two as a reminder, and the last so it can be changed.

berestovskyy wrote:
sketch wrote:Is it possible to make a report that includes every street segment with a particular name? For instance, we name U turn segments "U turn" in the New Orleans area, but many have been named "U-Turn" and "U Turn". Trying to standardize all of them is a heck of a task, but being able to search "U-Turn" in Validator would make a big difference.

You mean a check which reports all of those errors (i.e. "U-Turn", "U Turn" and so on)?

That would be nice for my purposes, but I don't know if "U turn" is used at all outside my state, or even metropolitan area. So I don't know if it'd be an appropriate addition to the entire script for the US. What I was thinking was that I could put in a name (whether "U-Turn" or "* North *" or whatever else), run the report, and get all the streets matching that name 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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

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

Postby sketch » Fri Feb 21, 2014 5:29 pm

SuperDave1426 wrote:
As such, the Validator should show results for anything containing "Construction Zone", "Closed", or "CONST ZN". The first two as a reminder, and the last so it can be changed.

You're talking about flagging the first two without parentheses, correct?

Right, in case someone marked one without them, it could be changed. I doubt there are any "Construction Zone Blvd"s out there. "Closed" without parentheses would also be useful for showing things like ramps which are closed for construction and marked with specific messages (e.g., "CLOSED until July 2014").
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

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

Postby sketch » Sat Feb 22, 2014 9:08 pm

berestovskyy wrote:
sketch wrote:Regarding "(Closed)" / "(Construction Zone)" / "CONST ZN":

According to wiki:
When a road is under long-term construction, but is not closed, add "(Construction Zone)"

So I'm not sure if Validator should suppress issues at the "not closed" road :?

A report for obsolete CONST ZN markers will be added.

Oh, of course, I wouldn't wanna suppress other issues there. I think having "Construction Zone" as a note, though, could alert editors to construction projects which may have been completed.

berestovskyy wrote:
sketch wrote:What I was thinking was that I could put in a name (whether "U-Turn" or "* North *" or whatever else), run the report, and get all the streets matching that name in the report.

At the moment all the filters run afterwards the scan. Validator scans and collects all of the issues. Then you click "Show report" and Validator applies the filters and shows the report.

This street match option you suggested would be applied during the scan and once it changed you would need to rescan the area. So this option does not fit well with the existing filter options :(

Understood, thanks anyway! :D
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

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

Postby sketch » Mon Feb 24, 2014 6:49 pm

berestovskyy wrote:
dbraughlr wrote:When a USA street name starts with a compass indicator [ENSW], the next word should start with a capital letter.

We can go further and check if every word in the street name starts with a capital letter. But at the moment #94 is checking just the beginning of the street name.

No thank you. It took me about ten seconds to think of a valid example that would violate this. Similar examples, I'm sure, exist in many places.
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

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

Postby sketch » Wed Feb 26, 2014 5:41 pm

qwaletee wrote:You may be misreading this. It seems aimed at the "E main st" situation. A better wording of the rule logic would be "If street name begins with EWNS followed by a space followed by a lowercase letter." Yes, it is just a special case of checking first letter capitalization in general. I don't know how prevalent the problem is that we should spend CPU cycles on it.

Yes, that's what @dbraughlr asked for, which is fine. It's not, however, what @berestovskyy proposed in the alternative. I was replying to the latter.
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: 6545
Joined: Sat Aug 08, 2009 6:13 pm
Location: Nouvelle-Orléans, Louisiane, États-Unis
Has thanked: 2213 times
Been thanked: 2689 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: ehepner1977, Google Feedfetcher, jm6087, Mythdraug