Waze forum

Permalink: https://www.waze.com/editor/?lon=-90.87 ... s=62382737

User Problem report:

Type: General error
Description: I 70 at wentzville MO. keeps wanting me to exit again
Reported on: December 03

If you don't have WME Color Highlights, PLEASE install it! (otherwise you wont' see the reverse connection nodes in this area.)

I thought this was a pretty good example to post.

Someone resolved the user complaints without fixing the revcon nodes

Can I get a level 5 to please take this section of I-70 and clean those up (hopefully before I get more user complaints)

vickimachado wrote:Thanks.

The instructions on correcting errors displayed by the highlighter script says only to hit the "Q" to begin the reset process. Is the "W" necessary, too?

Q = keyboard shortcut for the "Disallow all turns" button
W = keyborad shortcut for "Allow all turns" button

The fix for these is to dis-allow , then allow the turns and set the proper turn restrictions.

I made a YouTube video on how to do it:
http://www.youtube.com/watch?v=IFNXGQjA4kc

https://www.waze.com/editor/?zoom=7&lat ... s=26666889

Average speed for segment
A->B: 90km/h (55.9mph)
B->A: 18km/h (11.2mph)

This is a one way segment B->A . It's 46 meters long, and has 90 deg turns at both ends. I highly doubt anyone is doing 56 mph the wrong way on this short segment.

I have noted that the WME Color Highlight script seems to have a bug that puts the decimal point in the wrong place as well. You'll see 4000 mph when it should be 40.

However I am still finding segments that have skewed speeds.

Something else I've noted in area's that have a lot of revcon nodes around. In WME Highlights look at your avg road speeds.

I've found segments reporting that wazer's were averaging way too high of speeds over short segments.

So far I find these only near U-Turn and Reverse Connection nodes. Total guess on my part, but I think when Waze sees these revcon's it's processing the data as though the user went back and forth over that segment (IE if a East West road Point A to Point B and back again). Then it processes the GPS data and calculates as though the user took A -> B ->A -> past B when in fact the user only went A -> past B.

Is it possible to ask a developer to look into that / is this already a known thing?

If so, will waze automatically fix these segments with "light speed" settings (over time as the correct data flows in), or are those numbers so far off it's un-correctable? (IE should segments with VERY bad data be deleted and re-created??)

and another just down the highway a bit...

https://www.waze.com/editor/?lon=-90.82 ... s=26680502

This user problem report came in as "wrong driving directions".

It seems to me, and this is just a guess, that when the user's GPS is off a bit AND the client runs into several RevCon nodes in a row (like we have in both examples), it causes the client to think it's on the outer road, or causes it to want to do "on / off" routing over the exit / entrance ramps.

Good to know the time I've spent clearing soft turns hasn't been wasted!

ArlenBystander wrote:The W key will enable all turns (turning the arrows green). For intersections where all turns are allowed, this is much easier than clicking on 8 (or more) arrows. Even for intersections where most of the turns are allowed, it's much easier to allow all turns and then disable the few that aren't needed.

Gotcha. Might have known I was taking the long way to accomplish the same thing!

And Blaze, hope that's right about most problems being a relic of Cartouche.

So, I click the Q key as the hover-over instructions say, the arrows turn red and I go around clicking them individually on all sides (in most cases, I'm correcting intersections allowing four-way turns).

Even when I have to pull apart the segments to purge the error (always, in the case of the U-turn errors), the arrows when reassembled default to red, and I set them individually. I'm not understanding where the W-key step is needed.