[Script] WME Validator 1.1.8 / 07.05.2015

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.

Moderator: Unholy

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 qwaletee » Wed Apr 09, 2014 4:29 pm

> - Validator now skips locked segments, so the locks may be used to hide issues for low-level users.

I don't like this one. I'm an AM, and if there's an error in the setup of an interstate in my area, I want to know about it. I can choose to ignore it (lots of validator stuff depends on context or is non-urgent).

However, if I think it might affect routing, I will request an unlock/fix.

Lest I be called an ingrate, my thanks for the whole system. It has helped me immeasurably.
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

Re: traffic circles

Postby qwaletee » Thu May 15, 2014 3:11 pm

dbraughlr wrote:
CBenson wrote:To get the roundabout instruction to work correctly on this roundabout, I had to not have the segments connect at the same point.


I do not consider traffic circles (e.g., Washington Circle to be roundabouts. They are circular roads controlled by traffic lights. In a real roundabout, traffic does not stop and roads do not cross. However, I do somewhat see how instructions to enter and exit the circle could be useful.


The question of roundabout versus traffic circle has been discussed a number of times before. Since Waze doesn't have a separate traffic circle equivalent to roundabout, they are all roundabouts. This is also consistent with user expectations due to users not knowing (and not caring) about the difference between the two, and common experience across other GPS and mapping systems.
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

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

Postby qwaletee » Fri May 16, 2014 7:24 pm

Validator is no longer highlighting issues on the map for me. If I click a problem segment, it does give me the list of things wrong with it, but there's no color coding anymore.

I have tried disabling all other scripts. I have made sure that the highlight issues on the map option is enabled.

The script is obviously not dead, because it does display issues on the highlighted segment.

Windows 7, Chrome 34.0.1847.137 m (current version), Tampermonkey is loading Validator 0.9.9
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

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

Postby qwaletee » Mon May 19, 2014 2:23 am

CBenson wrote:
lg1992 wrote:Now, as landmarks have been changed with places that have categories and sub-categories, I occasionally meet a place with a general category only. It would be nice to have the Validator to mark such places.

If done, I'd like this to be optional. The sub-categories are hardly comprehensive. Many of the places around me only have a general category as none of the sub-categories are appropriate.


Agreed. I don't really see a need for it at all. Even if they were more comprehensive, we don't have any rules currently discouraging use of the upper level categories.
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

Re: [Script] WME Validator 1.0.0 / 26.05.2014

Postby qwaletee » Mon Jun 02, 2014 4:35 pm

ispyisail wrote:Hi all

I would like a custom check for for segments with "no name" and over "50 meters" long?

Is this possible?

and can anybody suggest how to do it?


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

Matches from 50-99999 (note: includes 50, not just 51, and will not find any that are 100km or more)

Also note that this is not specific to road type. You might want to exclude PLRs, for example.
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

Re: [Script] WME Validator 1.0.0 / 26.05.2014

Postby qwaletee » Tue Jun 03, 2014 2:40 am

Just FYI, here is the list of codes for each ${type}:

1 Street
2 Primary Street
3 FW
4 Ramp
5 Walking trail
6 MH
7 mH
8 Dirt
9 Unassigned?
10 Boardwalk
11-15 Unassigned?
16 Stairway
17 Private
18 Railroad
19 Runway
20 PLR
21 Service rd

Putting it at the end (the $ says there can't be anything after it, so 1-Street is not confused with 10-Boardwalk or 16-Stairway, etc.):

template: ${street}:${length}:${type}
expression: /^:[0-9]{3,}:[1-46-8]$/

This says street name is blank (nothing between start and first colon), length has at least 3 digits ([0-9] is any digit, {3,} means 3 or or of that), and [1-46-8] means any single digit except 0, 5, or 9, which most of the common types that you would expect to have a name, except that ramp may not have a name. Railroad should probably also be included, in which case:

expression for nameless >=100m of types expecting a name (which EXCLUDES ramps): /^:[0-9]{3,}:([1-36-8]|18)$/

Excuse the RegEx tutorial :)
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

Re: [Script] WME Validator 1.0.0 / 26.05.2014

Postby qwaletee » Mon Jun 09, 2014 11:55 pm

Waze development and Validator apparently have different definitions of road overlap and sharp angles. Recently Waze has started making available "reports" to RCs, so that we can go through the map and fix them so they don't cause routing issues. I have noticed that Waze uses a stricter definition than Validator, and it would probably be useful to have Validator use the same expectations.
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

Re: [Script] WME Validator 1.0.2 / 04.07.2014

Postby qwaletee » Tue Jul 08, 2014 1:00 pm

Don't forget that WME Toolbox incorporates much of JNF, including the Q functionality, so test this with Toolbx and JNF both off. It will probably work anyway BUT with the side effect of making all junction traversals illegal (all red arrows).

krikketdoug wrote:
SuperDave1426 wrote:It would appear that Waze has decided that U-Turns and dead-end U-Turns are not going to be editable any more. Personally, I think that's a bad idea at intersections, since how can you indicate where a U-Turn is actually legal to perform for the routing engine? But that's another topic.

Since that seems to now be the case, is there any chance that Validator can be updated to no longer highlight roads with "Unconfirmed turn at node {A|B}" when node {A|B} is a dead end?


I just tested this. You can still make it a hard no u-turn by clicking on the end node and typing "q". This works while running JNF and without JNF installed. (I just tested both cases.) So you just need a keyboard to edit them.

Krikket
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

Re: [Script] WME Validator 1.0.2 / 04.07.2014

Postby qwaletee » Tue Jul 08, 2014 1:04 pm

I went straight with "V" unmodified :)

Does the keystroke automatically update? Mine had stayed at Shift-W (interfering with Waze's new Shift-W for closing SV) until I manually changed it. I checked, and I did have 1.0.2.

berestovskyy wrote:04.07.2014 v1.0.2:
- Complete Hebrew translation thanks to gad_m
- Minor UI changes for right-to-left languages (please report any issues)
- Changed keyboard shortcut to 'Alt+V'

+ Two new external translations:
Note: you need to install them along with the main Validator package using Tampermonkey

Super-mega-cool! Thanks guys!
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

Re: [Script] WME Validator 1.0.2 / 04.07.2014

Postby qwaletee » Sun Aug 03, 2014 9:18 pm

The whole U-turn thing has become another source of frustration and confusion... well, I should say, and even greater source, it always was a source. The guidance is ambiguous, the way it works is unclear, the advice seems contradictory, and the implementation of the temporary fix counterintuitive and perhaps counterproductive.
NYC Metro | Mentor | USA Country Manager | Responding to Map Issues
qwaletee
Map Raider
Map Raider
 
Posts: 2168
Joined: Wed Feb 13, 2013 1:42 am
Location: NYC Metro
Has thanked: 165 times
Been thanked: 746 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: No registered users