[Script] WME Junction Node Fixer v0.1.4 2016-05-26

[kentsmith9]

I didn't realize that:

a. You can load JNF into Tampermonkey.

and

b. I had JNF loading through an extension AND Tampermonkey.

That discovery seems to have addressed both problems/questions.

[james890526]

I get the error sometimes when already logged in, actually. I'm not sure what the problem is, but I believe it started happening only after I installed the Chrome Web Store version.

I've had the problem before the Chrome Web Store version was released, but it has presented itself more frequently since then.

Login status does not make a difference in my case. I never really log out, and when WME loads, following this API check message, I get the user greeting, and current points status, et cetera, confirming that I'm indeed logged in.

I too experienced this error. I'm currently using Firefox 31.0 and GreaseMonkey 2.1. The error pops up even when I'm signed in (never logged out). Can anyone confirm whether it works 100% with FF+GM?

[james890526]

I somehow managed to dramatically reduce the error pop up message by choosing "Execute first" in the script option. I guess it has something to do with the API object check.

[bgodette]

Updated and Chrome Webstorized.
Read the details, there's changed behavior and required action needed for closed loops when there's house numbers.

Version 0.0.9.0
This is now a Chrome Webstore Extension
Chrome Webstore

Checks WME's API to make sure used objects and functions exist and are the correct type. This works as long as function argument order doesn't change. Next step is to regex match on function contents to confirm arg order.

Makes cameras visible at zoom 0.
Updates keyboard pan amount by 1/4th the map view height.
Saves and persists turn arrow visibility and clickability between reloads/permalinks.
Saves and persists Full-screen mode.

Hooks into replaces 'q' (Disable All Turns) and does these actions on the selected node:

• Enables U-Turn and locks all turns at dead-end nodes. Changed Behavior
• Fixes any self and reverse connectivity issues
• Converts single node roundabouts (lollipops) and loops into a three segment loop. Any existing house numbers will be associated with the middle segment and MUST BE EDITED after save to update their stop point.
• If two or more segments are connected to the same two segments, it will split one of them. Same rules as SameNode.js bookmarklet.
• Terminates dead-ends
• Makes dead-ends two-way (only if both ends of the segment are visible)
• Sets the Type of a roundabouts using lowest of two highest rule and sets country/state if needed
• For UK sets Type of roundabouts using highest type excluding Freeway rule.
• Removes revcon (turns into wrong-direction of one-way), and selfcon (U-Turns at non-dead ends). Once the app has real support for U-Turns selfconf will be left alone
• Locks all turns at selected node.

[ditchi56]

Updated and Chrome Webstorized.

Is this update available for Firefox?

[Timbones]

Could you make it DISable dead-end U-turns in the UK? We have asked Waze to disable all of them for us. Thanks.

[doctorkb]

Could you make it DISable dead-end U-turns in the UK? We have asked Waze to disable all of them for us. Thanks.

And if we're going to get on this -- Canada, too?

[Olestas]

Can someone pkease explain why are you asking to disable uturns? What are the issues? And why these issues happen only in UK or Canada?

[doctorkb]

We've had really bad experiences with routing -- basically, when Waze wants to have a user turn around, with these dead-end segments having u-turns enabled, the user would be directed to turn down the street, turn around at the end, then go back the way they came.

Until Waze will respect a u-turn at any intersection (i.e. not just dead ends), it causes user complaints to have any of them turned on.

[CBenson]

But that's the same situation as the US.