[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.6.3 (BETA) / 12.02.2014

Postby GizmoGuy411 » Wed Feb 19, 2014 3:22 pm

The issue I had previously was while using the latest version of Chrome.

I scanned the same area again with the sound muted and it did NOT crash. I then unmuted the sound, and ran the scan and it still did NOT crash.

The only other difference, I can think of is that I shut down the background programs for Skype, and for Screenhero (desktop sharing).

If I get brave I'll try to narrow it down further at a later time.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Sat Feb 22, 2014 5:19 pm

Opinions please:
https://www.waze.com/editor/?zoom=8&lat ... s=16841710

Would anyone edit this any differently? Note that street DOES have house numbers, and is NOT drive-able.

Of course Validator reports this with "No Inward" and "No Outward" connectivity. How else could Validator handle this?

2014-02-22_12h37_49-2.jpg
2014-02-22_12h37_49-2.jpg (35.35 KiB) Viewed 1093 times
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Sat Feb 22, 2014 5:47 pm

CBenson wrote:
GizmoGuy411 wrote:Would anyone edit this any differently?

I guess I'd be inclined to map it as a walking trail. It seems (though it remains essentially unstated) that this is why waze will route to the end of a walking trail when the address is associated with the trail.


I changed it to a Walking Trail. I have been under the assumption that ONLY Street could House Numbers.

Thanks.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Mon Feb 24, 2014 2:11 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.


Just a caution here. In the process of implementing this, be sure to still allow the use of capital letters within a word. As just one example, I have a local street named and signed "ProMedia Parkway" with no space between the two word parts with capital letters.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Mon Mar 03, 2014 8:57 am

Not sure if this is even important enough to consider, as it is not likely to happen often.

#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. This happened due to the abandonment of a railroad crossing for the road. The road is still city property.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

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

Postby GizmoGuy411 » Mon Mar 03, 2014 8:18 pm

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


Woops. Sorry! (posted edited too)
https://www.waze.com/editor/?zoom=6&lat ... 50&env=usa

I forgot it because I didn't have that handy WP+ to use any longer! :) It had nothing to do with being up at 4am.
ImageImageImageImage

Global Champ
U.S. CM
U.S. Great Lakes RC: IL, IN, MI, OH, WI
AM: NW OH, NE IN, SE MI
Wiki Profile
Verizon: Galaxy S6 Edge w/ Android 5.0.2 & iPad "3" w/ iOS 8.2.0
GizmoGuy411
Global Champ Mentor
Global Champ Mentor
 
Posts: 1327
Joined: Wed Oct 13, 2010 3:14 am
Location: NW Ohio, SE Michigan, NW Indiana tri-state area
Has thanked: 428 times
Been thanked: 276 times

Re: [Script] WME Validator 0.5.0 (BETA) / 20.01.2014

Postby gizmouf » Tue Jan 21, 2014 11:08 am

Great job with that script of yours :)

I didn't read the whole 14 pages but I did read the "Complete List of Checks for v0.5.0" and didn't find a couple of stuff I had in mind, so here it is:

Street name starting without upper case
What is the problem?

[EN]The street name starts with a lower case letter.
[FR]Le nom de la rue commence par une miniscule.
How to fix?
[EN]Set the first letter in upper case.
[FR]Passer la première lettre en majuscule.
Wiki instructions: link
Severity: warning
Countries: FR, GF, NC, RE

Another one (maybe too specific?):

'Eglise' should be written 'Église'
What is the problem?

[EN]Wrong spelling => wrong speech in navigation.
[FR]Mauvais orthographe qui provoque une mauvaise prononciation.
How to fix?
[EN]Correct the spelling (É = alt-144).
[FR]Corriger l'orthographe (É = alt-144).
Wiki instructions: link
Severity: warning
Countries: FR, GF, NC, RE

The same could be done to a lot of other words but 'Église' (Church) exists in every city at least once.
Image
gizmouf
Waze Local Champs
Waze Local Champs
 
Posts: 4771
Joined: Sat Jul 13, 2013 2:28 pm
Location: Nantes, France
Has thanked: 50 times
Been thanked: 676 times

Re: [Script] WME Validator 0.5.0 (BETA) / 20.01.2014

Postby gizmouf » Tue Jan 21, 2014 3:29 pm

Entrance ramps here in France just start with the name of the road they are leading to, without the "to".
And I can't think of any example where a segment could/should start with a lower case.
Image
gizmouf
Waze Local Champs
Waze Local Champs
 
Posts: 4771
Joined: Sat Jul 13, 2013 2:28 pm
Location: Nantes, France
Has thanked: 50 times
Been thanked: 676 times

Re: [Script] WME Validator 0.5.8 (BETA) / 31.01.2014

Postby gizmouf » Mon Feb 03, 2014 8:30 am

berestovskyy wrote:31.01.2014 v0.5.8:
- NEW 'Construction zone (only available in the report)'
Default marker: 'CONST ZN'
Marker for Poland: 'REMONT'


For FR, GF, NC, RE, the equivalent is "*TRAVAUX*".
Image
gizmouf
Waze Local Champs
Waze Local Champs
 
Posts: 4771
Joined: Sat Jul 13, 2013 2:28 pm
Location: Nantes, France
Has thanked: 50 times
Been thanked: 676 times

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

Postby gizmouf » Mon Feb 10, 2014 11:28 am

Here is another idea to be discussed (or not :) ): checking average speed on a segment (don't know if you can get it like the Color Highlights script do) and highlight those with excessive speed regarding the road.

I have URs that appears with weird detours being proposed and the explanation seems to be one or several segments with illogical speeds registered. The cause of this is segments that have been re-used and modified, sometimes generating a false average speed.

Like 150 km/h on a ramp (with the Freeway attached to it being limited to 90), and Waze tells the driver to exit the Freeway just to re-enter on it the next ramp (without any trafic jam or whatever on the Freeway).

Since you won't be able to know what the correct speed should be for each segment, you could do a general check and mark all the segments with, for example, a speed over 150 km/h. Or 130 km/h but excluding Freeways. Or whatever seems logical in your country regarding a type of road.

The type of warning is to be determined (orange or red since it affects the routing).
Image
gizmouf
Waze Local Champs
Waze Local Champs
 
Posts: 4771
Joined: Sat Jul 13, 2013 2:28 pm
Location: Nantes, France
Has thanked: 50 times
Been thanked: 676 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: tonestertm