Get a sneak peek at whats next for Permanent Hazards on our April 7th Office Hours!
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 HandofMadness
According to the Extensions page, I'm running JNF 0.0.7.6 on Chrome. I've run into what appears to be a rare bug, perhaps caused by using Q before all road details have loaded. Some times, when hitting Q on a red junction, I've found that one of the streets has all of its turn restrictions coming off of that segment are set to red.

I first saw this in November with a LOT of edits by a certain high ranking editor. Chalked it up to him being busy and just your normal occasional mistake, or maybe someone else messing things up since Waze doesn't record the last person to touch a turn restriction. But it was always roads showing him as the last to edit a few days before. Then in Dec I started seeing the same problem with roads last touched by a different CM. And then most recently, after I've spent a bit of time using JNF to fix red junctions, I started seeing the problem from segments last touched by me. In one case, this involved segments with a level 5 lock, and a segment I had touched just a few days before to clear up a red node. No other changes.

Usually I'm alerted to these problems by the auto-generated message from Waze that drivers are driving through a restricted turn.

I'm going to try to do more edits with shift-Z pressed, to see if I can catch it in the act.
HandofMadness
Area Manager
Area Manager
Posts: 1807
Has thanked: 15 times
Been thanked: 347 times
Send a message

Post by iainhouse
Fantastic work, sir! I didn't realise quite how much I was relying on this one until the WME update broke it. :D

Now it's working properly, there's a potential problem I came across whilst it wasn't working. I did briefly see what would happen if I re-enabled the script by hacking it: this problem convinced me that was a bad idea, so I stopped using it again. But now it's working, the problem still remains.

I had to rebuild this major interchange because part of the roundabout had turned into a normal road type. If I 'Q' on one of it's junctions, your script turns the whole roundabout into ramps. I've actually set the roundabout to be minor highway, to match the MH connecting on the SE corner.

Your post says that you are using a different rule for UK roundabouts (highest type, excluding freeways), which matches the UK Wiki. However, I'm fairly sure that ramp shouldn't be included in those types.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Post by iainhouse
Hi Brian

I would like to make a suggestion for some new functionality for this script. I don't imagine it will be particularly simple, but I suspect this script is the place to add it and you're the man with the skills to do it. :D

I'm sure many editors have come across the occasional "corrupt junction": where all the geometry and turn restrictions are correct, yet Waze still will not route correctly through the junction. The solution is to note the current turn restrictions; pull each segment (including the last) away from the junction node allowing it to disappear; rejoin the segments again; move the node back to it's original location; restore the turn restrictions.

The first part of my request is a way to automate this procedure. It wouldn't be done very often and should probably not be made easy to do (to discourage people doing it when there's no point). Perhaps only accessible through a button on the left-hand panel or an unusual key combo (ctrl+shift+Q perhaps) with a confirmation pop-up before rebuilding the junction.

The second part concerns actually identifying these nodes. I don't even know if it's possible to identify that a node is corrupt in this manner. We may well have to provide you with examples to look at. :) If it is detectable, then the above methods suggested for user access to fixing it would not be necessary: the script could simply fix the node as part of it's normal fix operation.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Post by iainhouse
doctorkb wrote:It depends on your jurisdiction.
+1

In the UK, the vast majority of currently enabled u-turns appear on single segment streets at junctions where u-turns are physically impossible. I suspect that they have all been created by users effectively doing a 3-point turn at the junction using one of the connected segments - all within too small a space for GPS resolution to see what's happened. Waze then soft-enables a u-turn.

The result is that the client will (if it wants to turn the driver around), try to route them to do a u-turn where none is possible. Of course another issue is that the client can't actually give a u-turn instruction yet, but that's a whole other discussion. ;)

At the few junctions (compared to the total number of them) where u-turns might be possible, they're specifically forbidden more often than not. That's simply because our ancient UK roads don't normally have wide enough carriageways or dividers to make it easy to do. From a UK perspective (and I fully understand that this does not apply worldwide), I would far rather JNF removed u-turns and I had to put them back afterwards - it would be the most efficient way to work here.

I'm sure we'd miss enabling some u-turns that are OK, but MPs and URs will help to alert us to the realistically small number that are actually legal here.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Post by iainhouse
Just to expand on that, even if Waze routes the correct way, the app may display the purple route line going the other way, leading to URs because the directions don't match the map. If a UR is reported, then in WME there may also be a conflict between the Waze route shown by the purple line and the instruction icons which are for the alternate route.

Also, the extra node will not affect exit counts because it isn't an exit. The exit count can only be affected if a segment is attached to the node - either a 2-way segment or 1-way away from the roundabout.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Post by iainhouse
Fredo-p wrote:I don't have JNF script or extension installed. What is causing the API failed box to keep showing up?
JNF is also incorporated into WME Toolbox - and WME Toolbox does not have this latest fix. I think that WME Toolbox may have a check that only enables the built-in version if "native" JNF is not installed, so it might be worth trying to install the standalone version.
iainhouse
EmeritusChamps
EmeritusChamps
Posts: 11143
Answers: 1
Has thanked: 2173 times
Been thanked: 8188 times
Send a message
https://storage.googleapis.com/wazeoped ... c4/AGC.pnghttps://sign.waze.tools/s2000.pnghttps://sign.waze.tools/c6.png
My scripts: WME FixUI WME Presets :ugeek:
I want to go to a commune in Vermont and deal with no unit of time shorter than a season

Post by IamtheLexx
I see an error message when I log into WME about JNF Chrome extension. I have removed and reinstalled the extension to no effect.
WME Junction Node Fixer has failed to load due to API check: W.model
IamtheLexx
State Manager
State Manager
Posts: 803
Answers: 1
Has thanked: 435 times
Been thanked: 151 times
Send a message

Post by irowiki
rivercitysyn wrote:Is there a reason permissions are set so that the extension has access to so much in Chrome?

Would it be possible to restrict them in the next release for peace of mind?
Did you cross post to the wrong thread? :lol: This isn't a chrome extension and it has website restrictions in the script itself!
irowiki
Posts: 250
Has thanked: 66 times
Been thanked: 37 times
Send a message

Post by irowiki
As I said, I think you posted in the wrong thread:
// ==UserScript==
// @name WME Junction Node Fixer
// @description Creates a new editor hotkey to lock turns, fix reverse connectivity, and restore original restricted turns.
// @updateURL https://userscripts.org/scripts/source/144939.user.js
// @include https://*.waze.com/editor/*
// @include https://*.waze.com/map-editor/*
// @include https://*.waze.com/beta_editor/*
// @include https://editor-beta.waze.com/*
// @include https://descartes.waze.com/beta/*
// @include https://descartesw.waze.com/beta/*
// @version 0.0.8.2
// ==/UserScript==
irowiki
Posts: 250
Has thanked: 66 times
Been thanked: 37 times
Send a message
Attachments

Post by irowiki
Oh is it a chrome extension now too?
irowiki
Posts: 250
Has thanked: 66 times
Been thanked: 37 times
Send a message