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.
Post by ctpoole
It appears that 0.9.2 has a small problem with Elevation. I love the ability to flag segments that are out of range or NaN for Elevation, but now when I make a change to a segment (it seems to be related to turn restrictions), the elevation of some of the adjacent (at the intersection) segments have their elevation set to NaN and I have to adjust them with another save.

Did I screw something up?
ctpoole
Posts: 399
Has thanked: 18 times
Been thanked: 156 times
Area Manager: Austin, Southeast Texas and the Panhandle
https://s.waze.tools/c5.png

Post by ctpoole
I have a problem that can't possibly be unique. Rule 78 about "Same endpoints drivable segments" correctly highlights segments that should have at least one junction point added to them for routing to perform correctly. If you add a junction point to those segments then rule 118 or 119 catches the two segments saying the junction point is unneeded.

Is there some way to correct this behavior? Am I not interpreting the results correctly?

For now, I have disabled rule 78.
ctpoole
Posts: 399
Has thanked: 18 times
Been thanked: 156 times
Area Manager: Austin, Southeast Texas and the Panhandle
https://s.waze.tools/c5.png

Post by ctpoole
berestovskyy wrote: I'll try to fix the issue, but excluding 'Unneeded node A/B' checks for segments with off-screen nodes seems to be the only way...
I appreciate all your efforts but I think maybe there is a little bit of misunderstanding. None of the nodes are "off screen".
ctpoole
Posts: 399
Has thanked: 18 times
Been thanked: 156 times
Area Manager: Austin, Southeast Texas and the Panhandle
https://s.waze.tools/c5.png

Post by ctpoole
CBenson wrote:
txemt wrote:Why is "same endpoints drivable segment" such a big deal? Case in point, this type of intersection or street layout is common, so why is it a big deal? The only answer to solve this is to create a node, which someone is going to come along later and delete that node, as it's part of "cleanup."
berestovskyy gave the reasons for a bunch of the checks here. Do we want to have this discussion again in this validator thread or should we take it somewhere else?
I agree with TXEMT. If I put in a node I eliminate the same segment warning but in its place I get an unneeded node warning. I tried to question this once before but didn't communicate the problem well.


Sent from my iPad using Tapatalk
ctpoole
Posts: 399
Has thanked: 18 times
Been thanked: 156 times
Area Manager: Austin, Southeast Texas and the Panhandle
https://s.waze.tools/c5.png

Post by czar740
Good Night Wazers:

The current script Validator no longer works in the WME editor

:( :( :( :( :( :( :(
czar740
Country Manager
Country Manager
Posts: 922
Has thanked: 1087 times
Been thanked: 794 times
Attachments

Post by crotalo
please Update soon
crotalo
PartnerCoordinator
PartnerCoordinator
Posts: 782
Has thanked: 176 times
Been thanked: 964 times
Wazeopedia Colombia
Wazeopedia Bogotá
Country Manager - Local Champ Colombia

Post by CreekOfJohn
jdelosa wrote: Validator has become an part of our everyday wme use, and to work without it is like working with one eye closed.....
I agree with your statement above 100%, which is why Waze should invest into building validation into WME. This essential editor function should not be left to unpaid volunteers.
CreekOfJohn
Coordinators
Coordinators
Posts: 174
Has thanked: 173 times
Been thanked: 53 times

Post by crazycaveman
VRF-ErwinS wrote:Hi,

Is it possible (or can it be made possible) to make a report of all the roads that have been changed since a certain date or in the last number of days?
Currently a similar functionality is available in the color highlighter script, but this only changes the color of the segments, which requires extensive zooming and panning around. I'd rather have the availability of a nice report.

Thanks in advance!

Erwin
Yes, that is already built in. If you go to the search options (click the magnifying glass in Validator's settings to switch to that tab), you can enter the date. If you want to find all segments that have been updated since a certain time, you'll need to set up a custom check, as well. Click the Gear button and enter the same text in both the template and RegExp fields (something like a and a would do it).
crazycaveman
US Waze Champs
US Waze Champs
Posts: 843
Has thanked: 229 times
Been thanked: 441 times

Post by CurtisNewton74
Places with multiple entry points are also suggested for turning from area to point, which doesn't work.
--> Error message from WME that place has to many entry points when saving.
So any place with multiple entry points should not be suggested for conversion.
CurtisNewton74
Posts: 61
Has thanked: 22 times
Been thanked: 18 times

Post by CurtisNewton74
jm6087 wrote:
CurtisNewton74 wrote:Places with multiple entry points are also suggested for turning from area to point, which doesn't work.
--> Error message from WME that place has to many entry points when saving.
So any place with multiple entry points should not be suggested for conversion.
Why not? If a place is supposed to be a point and not an area, the fact that it currently has multiple entry points does not negate that fact.
You are right, the place should still be a point and not an area, you just can't edit that in combination with multiple entries. My very personal opinion here is that I don't want to see proposals that I cannot edit anyway (at least not without removing the multiple entries, and assuming the entries are correct and usefull, that might not be the best idea)
CurtisNewton74
Posts: 61
Has thanked: 22 times
Been thanked: 18 times