On this map, if I am driving south on Powerville Rd (with directions heading towards Fanny Rd), at the split it becomes Elcock. When I approach Fanny Rd., Waze directs me to "stay to the left at Fanny Rd’. Actually, this is a left turn, not “stay to the left”.
In reverse, if I am driving North on Fanny Rd, heading towards Powerville, Waze does not show any turns - either the right onto Elcock or the left onto Powerville. These are both road changes, but yet Waze shows them as going straight.
I’m looking at the map editor and can’t figure out why this happens. Both roads appear to have turn markers at the intersections. Is this “normal”? If it is, it’s clearly wrong, especially heading northbound and there is no instruction given at the two intersections.
Did you try zooming in close and checking out what’s called the geometry of the junction - that is, at what angle “the turn” approaches the junction? If the angle is less than 45 degrees, you will get a “keep left/right” instead of a “turn left/right”, and coming the other way, you might not get any instruction if the angle is less than 45 degrees and Waze does not see a possible “straighter” way to go.
Check out the junction style guide for more information about how the TTS interperts junction angles.
Is there any way to check how Waze will respond to the updates without waiting for them to go live? I have another intersection in Rockaway Borough that I drove through today that did the same thing and I’d like to attempt to fix that one also, but would like to make sure the fix is correct without having to wait a few days.
The only way to be sure is to wait for it to go live. That takes about 2 days. Otherwise, you just have to make sure your angles are right. There is a script that shows angles that you can run if you like
Also - looking at the intersection I likined, when heading north where Elcock splits to Powerville (left) and W. Main (right), I would think “bear left onto Powerville” or “bear right onto W. Main” would be correct (although “turn” instead of “bear” would be reasonable).
In the reverse though, if heading south on either Powerville or W. Main towards Elcock, Elcock would be staying straight and no direction is needed.
If the geometry is changed to fix no instruction given when heading north, wouldn’t it also be changed to now give a direction when heading south? Would there be any way to fix this to keep it quiet going south (2 roads to 1) and give a turn direction heading north (1 road forking to 2)?
From my experience with junction angles (appears to be consistent with the Wikis):
Departing angle between 0 and 20 degrees: No instruction given in either direction
Departing angle between 20 and 45 degrees: Keep/Exit* Left/Right instruction given in the “forking” direction, no instruction given in the “merging” direction.
Departing angle between 45 and 90 degrees: Turn Left/Right instruction given in both directions.
*Choice of “Exit” vs “Keep” in the 20-45 degree configuration depends on road types and branching direction, as described in the junction style guide wikis.
Deflection angles of segments identical (i.e. departing segments overlap): No instruction given for either departing segment
Deflection angles between 0 and 45 degrees
…And segment is best continuation (e.g. has same name and type as entering segments): No instruction
…And segment is not best continuation: Keep/Exit Left/Right instruction based on road types, names and direction
Deflection angle between 45 and 180 degrees: Turn Left/Right instruction
In other words, there are some angles between 0 and 20 degrees where I do get instructions. There are also some angles between 20 and 45 degrees where I do not get an instruction.
I’m not sure the names of the segments have anything to do with anything. Is this something that’s changed recently? I don’t remember the wiki saying anything about that, nor do I recall ever witnessing a turn instruction appear/not appear because the exit path had the same name as the entrance path.
