[Script] WME Validator 1.1.7 / 06.03.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 1.0.2 / 04.07.2014

Postby CBenson » Sat Aug 02, 2014 11:11 am

Taco909 wrote:Unless we are in the UK, we are not supposed to do this anymore... we've been asked in multiple threads by various global champs and Waze staffers.
Validator needs to ignore the u-turn, and the "Q" function in JNF needs to be changed so it likewise ignores u-turns if they are at a dead-end.

I continue to disagree. The waze stance seems to be that they will* enable all the u-turns at which point they would like them to remain enabled to confirm that the short detour prevention mechanism does solve the problems with enabled u-turns at dead end. First, the whole point then will be to see if problems are due to the u-turn being either enabled or not. As they have taken the ability to see whether the U-turns are enabled away from us in the WME interface, I find it now somewhat critical that this indication remain in Validator so I can troubleshoot and report problems with enabled or disabled dead-end roads. The point is if waze is going have routing affected by a property that can be changed by editors, then we should be able to see that property.

* If "soon" means "we might get around to it someday" then "will" means what?
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1803 times

Re: [Script] WME Validator 1.0.2 / 04.07.2014

Postby CBenson » Sat Aug 02, 2014 11:46 am

More or less. Basically my position is that it absurd for routing to depend on some setting that we can inadvertently change (say by disconnecting a road that has become a dead end and leaving a rev con in place) where we have no way to see that property. What waze should do is not make routing decisions based on the condition of the reverse connectivity at dead-ends. In essence if all dead-end u-turns should be enabled, then they should remove the ability to have disabled u-turns in the model. If that's too much of a change at this point, they should completely ignore the property. Then we could ignore it too. But they don't. The idea that good routing or routing to a stop point on dead end roads is going to depend on having the dead-ends reverse connections enabled when they have removed the ability to easily enable them does seem absurd to me.

So yes, it would be better for Validator to highlight the disabled dead-end u-turns.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1803 times

Re: [Script] WME Validator 1.0.3 / 04.08.2014

Postby CBenson » Tue Aug 19, 2014 12:59 pm

ditchi56 wrote:- there's no reason to remove the link to Google maps since Google own Waze, they're not going to object to their own property being enhanced?
To the contrary there is no reason to believe that all of the Google map data suppliers entered into agreements that include using the data for waze.
ditchi56 wrote:- there's no reason to remove the link to OpenStreetMap since that prides itself on being copyright-free?
OpenStreetMaps is certainly not copyright free. See here and here.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1803 times

Re: [Script] WME Validator 1.0.4 / 24.08.2014

Postby CBenson » Thu Aug 28, 2014 3:38 pm

sketch wrote:
Taco909 wrote:Likewise, there may be some cases where it is desired to execute the turn instruction early, but to overlay the departing segment onto the feeder segment for a short distance.
As for the early instructions, IMO it's better as an editor to lay the departing segment just next to, but not directly coincident with, the continuing segment.


I agree in part.

My understanding is that if you overlap segments, no turn instruction is given. So overlaying a departing segments on the road it departs from to achieve an early instruction I think is futile. So I agree that such segments should not be directly coincident with the continuing segment.

I would go further however as In my personal opinion angles of less than about 20 degrees should be avoided whenever possible. My reasoning is that the road closure feature in the app is next to useless for intersections with small angles. But there is the question of whether we should be mapping to the make the road closure feature work or whether the road closure feature should be made to work with the map that conforms to reality.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1803 times

Re: [Script] WME Validator 1.0.4 / 24.08.2014

Postby CBenson » Thu Aug 28, 2014 5:11 pm

sketch wrote:I will not edit the map to enable a feature that doesn't really work anyway. That feature needs a lot of work, and it's not up to us to fix it.
Understood. I agree that the closure feature would remain deeply flawed even if we never used narrow angles on the map.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1803 times

Re: [Script] WME Validator 1.1.4 / 07.11.2014

Postby CBenson » Tue Nov 11, 2014 8:42 pm

They are highlighting for me here.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Turbo, Android 4.4.4, Waze 3.9.4.0
CBenson
Waze Global Champs
Waze Global Champs
 
Posts: 9032
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 748 times
Been thanked: 1803 times

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

Postby Challenger3802 » Mon May 12, 2014 4:18 pm

Great script, works fine and very useful!
Image Image Image
AM Gillingham (Kent) & Maidstone
Challenger3802
Area Manager
Area Manager
 
Posts: 267
Joined: Sun Mar 09, 2014 7:41 pm
Location: Gillingham, Kent
Has thanked: 112 times
Been thanked: 22 times

Re: [Script] WME Validator 1.0.3 / 04.08.2014

Postby coontex » Sun Aug 24, 2014 2:42 pm

Nearly impossible to see what needs to be corrected and what does not. Have to click on every segment.


Sent from my iPhone using Tapatalk
coontex
Map Raider
Map Raider
 
Posts: 652
Joined: Fri Jan 17, 2014 3:01 am
Location: Katy TX
Has thanked: 195 times
Been thanked: 119 times

Re: [Script] WME Validator 1.0.4 / 24.08.2014

Postby coontex » Sun Aug 24, 2014 4:43 pm

Thank you for the fast update.


Sent from my iPhone using Tapatalk
coontex
Map Raider
Map Raider
 
Posts: 652
Joined: Fri Jan 17, 2014 3:01 am
Location: Katy TX
Has thanked: 195 times
Been thanked: 119 times

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

Postby crazycaveman » Wed Apr 30, 2014 6:55 pm

I'm running into a strange issue with user-defined checks, but I'm not sure if it's due to the order the checks are run. For some reason, when Waze did the base map import, several roads in South Carolina have been assigned to the state of Georgia. I've cleaned up most of these, but there are a few stragglers, so I entered the regex /Georgia/ with the template ${state}, ran the report, and got 18 hits. I then thought, "what if there are others that should be set to South Carolina that currently aren't?" So I changed the regex to !/South Carolina/, ran the report, and got none (using the exact same view)! I ran the initial report (Georgia) with duplicates and non-editables excluded and ran the second report with non-editables excluded and with and without duplicates, but got similar results (as stated above). Is there a reason one regex works properly while the other one doesn't? Am I missing something with regards to negated regex's?
Nexus 5
CM: USA
Image Image
crazycaveman
Country Manager
Country Manager
 
Posts: 454
Joined: Fri Sep 03, 2010 1:48 am
Location: Rock Hill, SC, USA
Has thanked: 128 times
Been thanked: 202 times

PreviousNext

Return to Addons, Extensions, and Scripts

Who is online

Users browsing this forum: No registered users