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.

jasonh300 wrote:

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?

Where did you see these instructions? There's a script in beta testing that uses Q differently than the native function of Q in the editor.

Hover over the error text which WMECH puts on the screen.

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.

rottielover wrote: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.

Not a bug. It's a side effect of saved Objects in WME that's automatically cleared whenever Object data is reloaded (pan/zoom/permalink/F5/JNF's save hook).

BlazeTool wrote:

vickimachado wrote:I wish I knew how reverse connection and other errors are caused, so I don't create new ones!

I *believe* they are created by things that you could do in cartouche but can no longer do in WME. So, while they are out there on existing roads, newly created roads should not have them.

RevCon is easy to create in WME by starting with a 2 way segment, using allow-all-turns and then setting it to one way. SelfCon however seems to have been cased by automatic turn opening, from people actually doing u-turns, or GPS wobble that makes them look like they've turned around (anywhere on the segment), which is why it's important to clear the soft-turns as well.

SelfCon has not resurfaced on any segment where it's been cleared from and the soft-turns eliminated as well.

vickimachado wrote:I wish I knew how reverse connection and other errors are caused, so I don't create new ones!

I *believe* they are created by things that you could do in cartouche but can no longer do in WME. So, while they are out there on existing roads, newly created roads should not have them.

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?

Where did you see these instructions? There's a script in beta testing that uses Q differently than the native function of Q in the editor.

vickimachado wrote:I wish I knew how reverse connection and other errors are caused, so I don't create new ones!

QW any junctions you create and then explicitly set restrictions after that. It's the only way.

We have those littering our area, in spots. I remove them where I have the permission levels in the hopes that it will help some of our goofy routing. I also assume that Waze tries to route around areas like this, but it would be cool to understand the effect of errors like this.

I wish I knew how reverse connection and other errors are caused, so I don't create new ones!

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?