Waze forum

It should only change dead end segments to 2-way.

the1who wrote:

AlanOfTheBerg wrote:It should only change dead end segments to 2-way.

Well I didn't know that part of it too, but realizing it the more I use it, which is a great resource for that in neighborhoods.

Perhaps you should read the op then so you're familiar with what jnf does.


Tapatalk made me do it.

Doesn't the original post explain that it simply overrides the Q key shortcut function? It reads that way in the quote that you included in your post. Seems pretty clear to me.


Tapatalk made me do it.

doctorkb wrote:I'll let you know how that works out.

Waze may or may not, at this time, use it. And if it does, it certainly won't say "u-turn" or anything helpful like that. Waze already does u-turns at junctions, but to the app, it is as if the turn doesn't exist. No guidance is given.

This is the expected state of the situation until new routing code and an update to the app, spoken instructions, and TTS is made available whereby Waze can take advantage of the u-turns (selfcon) we are working on.

esochan wrote:There seems to be an issue with JNF0.0.7.5 today. With it on, I cannot enable/disable individual turn restrictions. With it off, I have no problems doing so.

Is anyone else having this problem?

Nope. I was editing on both infrastructures this morning with no problems. I'll clear cache and check again later.

NorfolkMustard wrote:Tried pressing the A key on they keyboard?

Normally I'd agree, but why does it change when the script is active or not? That's what's odd. But perhaps the person did accidentally tap 'a' between the testings.

JNF was specifically designed to NOT enable the u-turn at the dead-end junction due to the way Waze overuses them. When the routing engine is fixed to stop doing this, then I'd agree that JNF could change.

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

arbaot wrote:to allow JNF to work with localized WME
please add:

Code: Select all

// @include             https://*.waze.com/*/editor/*

That's a good point. I didn't realize it wasn't working with the language localizations, where the language code is in between the hostname and /editor.

imran222120 wrote:use tampermonkey

I'm on Chrome 32 and don't use tampermonkey and loaded JNF .user.js file just fine. Probably do have to be in developer mode....