- Install TamperMonkey addon
- Add scripts to TamperMonkey
- ???
- Profit!
Q then W
Q on its own will fix reverse connections etc
Q then W will also change roundabouts following generally accepted rules and add end nodes and 2way traffic where missing from dead ends. Be careful though, as it will remove all turn restrictions too.
An excellent script I use every time I edit.
Sir,
i tried but when i press Q nothing happens, but when i press W it works.
âQâ will appear to have no effect, if there is nothing to fix. Hitting âQâ will NOT disable and turn restrictions.
One way to check if it is working is to: find an existing road. Create a new road junctioned to it. Set it with a city/name and set it to Unknown direction, or 1-way direction. Save.
Now select the junction created with that new segment and hit âqâ. The road should now be set to 2-way. If it is, then JNF is working as expected.
I thought I saw somewhere⌠but I could be imagining it:
Is there a keyboard shortcut or utility that will apply the JNF to all visible junctions? Itâs very tedious in a metro city area with hundreds of iffy junctions (RevCon, SoftTurn, etc) to have to select each one and press Q. Obviously any such shortcut would have to be used with care.
If so, I hope itâs only available to CMs. I, for one, would not want anyone not familiar with the side effects and pitfalls of en masse QW editing to be able to do this.
In fact, I would suggest that for any non-AM editor, you shouldnât be able to use JNF at all on any junction that has at least 1 hard-disabled turn on it, while AMâs should have to click past a warning. This way itâs harder to JNF bomb peopleâs edits.
Agreed for sure. But now that the default action for âQâ with JNF preserves hard disables, itâs much less of a concern. If you were to zoom to an area that has say, 50 RevCons⌠applying a global âQâ action would fix the RevCons and preserve all of the hard-disabled turns.
WME Toolbox incorporates the features youâre talking about for Rank 5+ editors.
super. i guess iâll just suffer for now 
I guess â unless you can make a case to your Champs to have OyyoDams make an exception â not even sure theyâd do that, but thatâs your only route.
??? the only side effects of the currently released version vs what an editor should be doing are:
It will disable U-Turns, which may not be desirable in certain areas. But since thereâs still no client support, itâs not desirable for a driver unfamiliar with the area to have them to begin with. This has been the case since JNFâs first release.
It doesnât split one side of a two segment loop/eye.
It doesnât handle parking lot/private stubs that only connect to the main road and nothing else that are one-way and converts them to two-way.
I had trouble following this part of the discussion as well, but I do think I figured it out.
Their concern surrounds the manner in which WMET will let you apply JNF fixes to all visible nodes with one keystroke/click â and that feature should be restricted to CMs. I donât understand it to be a question of JNFâs application.
The difference is that itâs fair to assume that someone going node-by-node will be checking each node before JNFing it, whereas someone mass-JNFing all nodes in view will almost certainly be doing so without checking each node. (The toolbox mass-JNF tool is available to me, yet I use it very sparingly for this reason.)
JNF fixes soft turns. A mass-JNF tool has the potential to harden a lot of incorrect soft turns in areas that havenât yet been edited properly (youâd be surprisedâa lot of the Detroit area is still like this). These are areas where turns should remain soft so the merger process can go about enabling more of them, and so editors are alerted to the presence of these areas.
The vast majority of subdivision neighborhoods all over NJ still have soft turn rules. Any changes made with JNF automatically harden soft rules at any junctions edited with its Q keystrokes. The result is that when Waze receives conflicting data against a hard rule, it creates an MP, vs with a soft rule it just might change it. Frankly, I think urban and suburban subdivisions are far easier to manage like this. Used screenwide, however, particularly at the higher (farther out) zoom levels, an editor can easily corrupt large swaths of the map, so we certainly donât want anyone less than R5 - who might be eager just to pick up mass amounts of edits with minimal keystrokes/clicks just to advance in rank - to be able to do this.
Fair enough. Iâm fairly certain merger still works on original nodes, but am unsure about anything weâve created in the last 9 months or so, and that just goes back to the old discussion about WME defaults and incomplete work.
Well, I mean, the whole point of soft turns is to have a way for the editor to know which junctions havenât been completely edited. Running JNF on all of them obviates the purpose of soft turns entirely.
An MP may alert you to an incorrectly-set turn, but a soft turn can alert you to an incorrectly-set turn without anyone ever having to drive through it.
I am getting the following error on the beta version of WME for the USA:
WME Junction Node Fixer has failed to load due to API check: wazeModelIâm running the latest version of Chrome for MacOS and version 0.0.7.6 of JNF. FYI, I do not see the error on the regular version of WME.
Look in the WME beta testing forum.
Sent from my iPhone using Tapatalk 2
Junction node fixer 0.0.7.8 is no longer working on my system. It look like the latest WME update has preempted the âqâ in a way that JNF is no longer intercepting.
Now it is doing what the q would do without JNF installed.
EDIT: It is broken again, disregard the following EDIT: maybe âsomething strangeâ was going on, because it is working fine now.
I started getting an error this morning stating "WME Junction Node Fixer has failed to load due to API check: aboutToLoseChanges
Also, the Toolbox menu doesnât show up on the right hand side now.
It was working fine late last night.