[Script] WME Junction Angle Info

[PesachZ]

@FZ69617

@Arnoniem

I just noticed one of my tests showing a “turn left” at the 168.45 angle. It could be the bug that gives a left instead of uturn, but I don’t think so, since the livemap gives the same result. Have a look here:
https://www.waze.com/editor/?env=row&lon=6.04126&lat=52.01167&layers=453&zoom=7&segments=274372385,274372422

Thanks for finding this another anomaly.
Foreseeing other unknown cases the gray zone has been extended into 1 degree (i.e. 168.24 ± 0.5).

@Arnoniem

Oh, and i noticed another thing:
On a 2 segment uturn at 170degr+, JAI gives a Best continuation, however the actual instruction is also a uturn:
https://www.waze.com/editor/?env=row&lon=6.03940&lat=52.01139&layers=453&zoom=8&segments=280755690

Hmm, another interesting change to the algorithm. Previously, no instruction was the only option in case of just one s-out.

This JAI development version fixes the problems.

Thank you Arnoniem for the reports.

Considering that a self connected U-turn (only one segment) is able to generate a prompt, it seems to reason they adjusted the algorithm even for two segments in the case of a U-turn prompt.

We will have to update the algorithm in the wiki to account for these changes to.
Can you please list the criteria as you know it for the algorithm to generate this 2 segment uturn prompt, I will try to incorporate it into the algorithm and flowchart in the wiki.
Thanks
Sent using Tapatalk for Android 4.4.2

[EWK15]

Hi, is there a way for this script to not automatically be active when WME loads?

Thanks

[sketch]

@EWK333

Hi, is there a way for this script to not automatically be active when WME loads?

Thanks

Just disable it in Tampermonkey or Chrome.

[milkboy]

@EWK333

Hi, is there a way for this script to not automatically be active when WME loads?

Thanks

Or hide the corresponding map layer?

[EWK15]

maybe i didnt word my question very well…

when WME starts, this script is always visible as a map layer.
I would like to start WME and it to not automatically be a visible map layer.

Thanks

[PesachZ]

@EWK333

maybe i didnt word my question very well…

when WME starts, this script is always visible as a map layer.
I would like to start WME and it to not automatically be a visible map layer.

Thanks

When wme starts it remembers your layer settings from your last session, unless you had you are using a link to open wme which includes the &layers=### parameter.

If the layer is off when you last closed wme on that browser, and you open it with a blank URL http://www.waze.com/editor/ with nothing after that it should stay off.

Is this not the case?

Sent using Tapatalk for Android 4.4.2

[EWK15]

@PesachZ

When wme starts it remembers your layer settings from your last session, unless you had you are using a link to open wme which includes the &layers=### parameter.

If the layer is off when you last closed wme on that browser, and you open it with a blank URL http://www.waze.com/editor/ with nothing after that it should stay off.

Is this not the case?

No, I uncheck it in the drop down layers menu, then it is checked again every time WME is reloaded. I just click on the ‘Edit The Map’ link from Live Map, so the only parameters are Lon, Lat, and Zoom

[milkboy]

@EWK333

@PesachZ

No, I uncheck it in the drop down layers menu, then it is checked again every time WME is reloaded. I just click on the ‘Edit The Map’ link from Live Map, so the only parameters are Lon, Lat, and Zoom

Probably something to do with the fact that the layer is added only after WME is loaded already… Maybe would be possible to store a value once the layer is shown/hidden, and then use the stored value to programmatically hide the layer if desired…

I do recall the layer visibility was working correctly at some point though, as I was wondering why the script would not load (turned out is was simply not checked) [emoji12]

[Olestas]

Can you please publish your latest version script?

[milkboy]

@Olestas

Can you please publish your latest version script?

sure Unfortunately it will have to wait until tomorrow…

[FZ69617]

For those who would like to try a new JAI feature called “disallowed U-turns indicator” there is the latest development version available supporting this:
https://github.com/FZ69617/WME-ja/raw/master/wme_junctionangle.user.js

The indicator is displayed only for 15m or less long segments with disallowed U-turn as documented in U-turn avoidance conditions in Wiki.

Example:

Here the yellow bubbles displayed next to the green ones indicates disallowed U-turns.

Hope incoming official JAI version will also include this new feature.

[taco909]

Very cool!

[Timbones]

@PesachZ

Can you please list the criteria as you know it for the algorithm to generate this 2 segment uturn prompt, I will try to incorporate it into the algorithm and flowchart in the wiki.

Do we know yet whether this prompt takes into account the segment name, the directionality, and whether it’s a right-hand or left-hand drive country? I can think of some scenarios where it would be undesirable to have a U-turn instruction, and we should take this up with Waze if this is the case.

[Arnoniem]

@FZ69617

@Arnoniem

I just noticed one of my tests showing a “turn left” at the 168.45 angle. It could be the bug that gives a left instead of uturn, but I don’t think so, since the livemap gives the same result. Have a look here:
https://www.waze.com/editor/?env=row&lon=6.04126&lat=52.01167&layers=453&zoom=7&segments=274372385,274372422

Thanks for finding this another anomaly.
Foreseeing other unknown cases the gray zone has been extended into 1 degree (i.e. 168.24 ± 0.5).
Thank you Arnoniem for the reports.

The first one, still gives a turn left, on the livemap, @168.91 degr.

[Arnoniem]

@Timbones

@PesachZ

Can you please list the criteria as you know it for the algorithm to generate this 2 segment uturn prompt, I will try to incorporate it into the algorithm and flowchart in the wiki.

Do we know yet whether this prompt takes into account the segment name, the directionality, and whether it’s a right-hand or left-hand drive country? I can think of some scenarios where it would be undesirable to have a U-turn instruction, and we should take this up with Waze if this is the case.

Don’t know exactly. In the situations I’ve tested both segments had the same properties. The Uturn prompt was given in both directions, so a left and right uturn.
Do you have a specific construction in mind, where this would cause problems? It’s quite an extreme angle, so hard to create that NOT on purpose…

[PesachZ]

If the two segments have different names out may have an effect we should test that

Sent using Tapatalk for Android

[Arnoniem]

I’ve changed my test set up, with diff names, and diff names+ street-to-primary

EDIT: i did test that on a 3-segment uturn, and that didn’t have any effect.

[Arnoniem]

@Arnoniem

I’ve changed my test set up, with diff names, and diff names+ street-to-primary

EDIT: i did test that on a 3-segment uturn, and that didn’t have any effect.

All giving a uturn instruction. From all directions.

[Arnoniem]

@Arnoniem

@FZ69617

@Arnoniem

I just noticed one of my tests showing a “turn left” at the 168.45 angle. It could be the bug that gives a left instead of uturn, but I don’t think so, since the livemap gives the same result. Have a look here:
https://www.waze.com/editor/?env=row&lon=6.04126&lat=52.01167&layers=453&zoom=7&segments=274372385,274372422

Thanks for finding this another anomaly.
Foreseeing other unknown cases the gray zone has been extended into 1 degree (i.e. 168.24 ± 0.5).
Thank you Arnoniem for the reports.

The first one, still gives a turn left, on the livemap, @168.91 degr.

Did any of the devs pick this one up? Think it might need to be lifted over 169.00?

[sketch]

@Arnoniem

Did any of the devs pick this one up? Think it might need to be lifted over 169.00?

I don’t know, I think 170 is already a little steep. If they decided to change the angle to 160-165 I would be fine with that, we just need to test.