waze.com

sketch wrote:

bummerdude69 wrote:Two questions
1) what does the various beeps mean? Seems to have a purpose, but haven't figured it out.
2) How do you turn that NOISE OFF?!?

1) One beep per "screen", with a higher-pitched beep at the end.
2) Gear, wrench, uncheck "Enable sounds".

1) I'd guess the longer between pages (beeps), the more segments to check?
2) Thanks, never noticed the Gear.

- Should there be a check for elevation? I'm thinking everything 'should' be Ground (0), unless it's actually going over/ under something (except railroads, etc).

- I'm using custom Template ${elevation} and RegExp D!/0/ Is there a better way to check for elevation?

Thanks

Is it possiable to identify the geometric nodes (not the end points, but the ones in the middle) that are at 180 degrees? Would be good candidates for cleaning up.

berestovskyy wrote:

khaytsus wrote:I've tried disabling all other scripts, yet this one still doesn't seem to "validate" anything. It shows up, I click the Play button, it pans around, finishes scanning, then nothing. No report (button stays greyed out).

There is a chance you have a perfectly mapped area

I've always scanned large areas, so never ran into this. Could some indication of a clean report be added. I'm thinking maybe change the grayed out 'Show Report' to 'Nothing to Report'. A report with a Summary of Zero Findings would work too, but that seems a bit overkill.

Thortok2000 wrote:Then perhaps make that idea an option;

Not sure which idea you were referring to, but an option to create the report without the layers would work well, I think.

Nice Touch!

BUG: Someone got the a out of there.
BETA: No street nme on Place (#251)

Is the Validator encrypted or only minify?

https://www.waze.com/editor/?zoom=7&lat=29.76326&lon=-95.37197&mapUpdateRequest=3404412&env=usa&layers=1925&segments=47698044


Validator flags the segment with a 'turn too sharp' at the north end when that end has the restricted turn (yellow) 24/7, but passes it when the turn is forbidden (red).

I am not sure this behavior is bad, but it seemed a bit strange.

jemay wrote:....
Why set it as TBTR (24/7) when it should be just a red arrow?

In the hope that someone 'killing red arrows' would be less likely to 'enable all turns' there.
(yeah, I know I can just lock it, but 'stuff happens' sometimes. And I wanted to see how well the idea works. When I noticed the slightly strange validator action, I thought I'd report it.)