https://www.waze.com/editor/?env=row&lon=152.99061&lat=-27.40749&layers=1409&zoom=7
garvin Greys been at it for a bit by the looks of it and it sounds like its getten infuriating , can someone with a bit more knowhow for complex innersections please have a look
ive tried what i can for now to simplyfy it but not sure if im just making it worse,
thank you
I’ve not the time at present to assist. Perhaps over the weekend.
Ok.
The full history can be read at the site report.
Reporter said that he received two right turn instructions from Griffith Street into South Pine Road. A person should only get one. I drove through the intersection confirmed this and then asked for it to be dropped to level 1 to make this change and also make some changes to the intersection as it was a bit of a mess.
At the time of my original changes, I made a small angle change from Griffith St to Stafford Road, and ‘the reporter’ replied back that this could cause a turn left instruction.
Griffith Street to Stafford Road in both directions for the road markings are straight through, even though they are on a massive kink.
‘the reporter’ is clearly an waze editor as the degrees were only 26 and 64. I thought that to trigger the turn instruction it required more than 90 degrees, but after the next tile update, bam, I got a left turn instruction from Griffith St to Stafford Road.
This annoyed the hell out of me. ‘the reporter’ is clearly a detailed, knowledgeable waze editor and could have explained why it would trigger the left turn instruction. Not the first time this person has done this as well.
I had also added a slip lane from South Pine Road to Griffith St, but it was a dud and deleted after a day and the original turn left instruction established.
Nibby has then decided to make some changes, but a couple of them I have had to correct.
There are now a few outstanding issues.
Hi Garvin, I was the reporter.
Apologies for the lack of explanation, I’m usually short of time when I drop in to check on things.
An angle of greater than about 47 degrees will create a turn instruction. 20 to 46 degrees will lead to a keep left/keep right instruction. Less than 20 degrees will usually yield no instruction, though two roads splitting in a Y at less than 20 degrees I do not know, one of those not so defined things which exist everywhere in the computing world.
Currently the straight through section will yield Keep Left instructions. You’ll need to add two geometry nodes to straighten up the exits from Stafford Rd and Griffith St.
South-bound on South Pine Rd into Griffith St (right turn) is disabled, this will need to be enabled as well.
South Pine Rd left into Griffith St will yield a turn left instruction. The slip lane you had earlier likely caused a Keep Left instruction due to the shallow turn angle.
I personally dont like the spoken instructions. Bugs me to no end. I have learnt to quick view my iphone where it is placed in the car and look for either next turn in km or mtrs or forward directions. So keep left turn right n so forth i have no real formal experiance with this as since ive had waze the voice is mute. When it has turned on. like tonight for instance. i tried to give it another go tonight. Why turn left in 300 mtrs when im 420mts away? As Thats what i got tonight driving to 24hr woolies. Very strange. Needless to say. Voice is off again
Nibby, for me. And I think also for other editors reading this but not commenting.
This is not about whether or not I like voice instructions, but about learning the waze program and when I make a change to the map, what affects it has. If I want to move up the editing ranks, then I need to learn this stuff without needing to have my hand held so much.
And other people do use the voice instructions. A feature that seems to have changed since I first started using waze is that it used to also sometimes give measurement to location or turn point in time, not just distance. But this has either been removed, or I have changed a setting.
I have created two 19 degree nodes. That should eliminate the turn instruction. Unless you pick up I have created them on the wrong angle side :o
Enabled.
Strangely, no attempts at the slip lane generated a turn left instruction, no matter how it was drawn, or what angles were used over a couple of days. So I just gave up, deleted it and went back to the old configuration.
The actual distance between where the slip lane would be and where the current left turn node instruction is rather small, so the difference is minor and no issue.
Hopefully we have now solved all issues for this intersection, including the original report and can close it out.
Hi Garvin, yes the staight ahead angles are on the wrong axis and will now cause turn left instructions. You need the next segment to be less than 20 degrees angle from the current segment orientation to suppress an instruction.
The original report for the two right turns has been fixed and can be closed out anytime.
I have even tried to do some reading after typing in waze turn instructions into google to try and work out what I am doing wrong. I am just blatantly guessing here.
I will also admit that I am finding those instructions too short and not precise enough about what to change and to learn from. Considering we are talking about making changes at both ends, and I am not even sure if I have changed the 19 degrees in the correct direction at the Griffith St or Stafford Rd end.
It might just be easier if you make the required changes so I can actually see what it should look like, but then I get no satisfaction from working out what I was supposed to do.
I will close it out when this get fixed.
If the dual carriage was removed things gust get so much easier and more accurate (TTS)
i nearly mentioned about making it single lane there also, just for that innersection,
garvin, sorry that last post was not directed at u in any way,
sorry
just about the instructions and how the voice is annoying
go forth, u will figure it out.
Ok, I am going to ask a bold question. Why is this section of South Pine Road split? It certainly is causing a lot of problems. My lack of knowledge is not helping, but it being single lane would solve some of the issues.
But then we get into the issue of having to unsplit a split road. And how far to do it.
Excellent question.
In the beginning…when I started a few years ago the rule was if there is a barrier down the middle only then were you allowed to dual carriage. (I suspect some people were dual carriage normal roads before that.)
So most cities were dual carriage d in Australia.
Then 1 or 2 years ago some Global Champs came to Australasia with a few new concepts.
They increased the threshold for dual carriageways (see wiki for full details)
My personal policy is only dual carriage when absolutely necessary and use the GPS trace to check for a clear gap as a reference.
While we are on this topic
To reinforce this concept WazeHQ the just released to beta a new feature called “Big Junctions” for complex intersections.
In summary, the end user just draws a very simple intersection and the waze back end does some fancy maths to over come some problems.
It was split by nibby last year. clemmo did a bit of work afterwards to fix it up. I do not know what has happened since (I believe the double right instruction crept in since then).
I would support an unsplit of the entire length of South Pine Rd through here. Though it is not strictly necessary to throw away the speed data, there is no way to keep all speed and junction data during an unsplit, back end databases aren’t smart enough by definition. The recommended unsplitting practice is for the preservation of house numbers only, some speed data is maintained but all junctions will be reset.
I’ve put the angle on the correct side now. All instructions should be valid and I do ask another editor to check.
The split at the southern end begins at Elkhorn Street and so if SPR is going to be re-joined, it should start here. This area also has no road connections, until our point of concern at the start of the shopping centres.
Then in terms of SPR, nothing much changes in road geometry until the 5 way roundabout at Queens Road/Beckett Road/Rode Road etc. So either we can do a small unsplit for this area, or be consistent and unsplit the whole entire section of SPR. That is a massive amount of work.
Ahh, so it was just a matter of changing it from left side to right side. That is how it looks to me. That angles are still less than 20 degrees.
dual carriage nibby 
when baby nibby was learning the ropes, boy did i make sum boo boo`s
Whell, I remember times and posts of arguments from Shane being a very strong supporter of split roads…quite some lively discussions back then…
Anyway, beta features are basically to be discussed in beta threads and big junction won’t help in this case, it’s (currently? ) just reducing penalties down to one on junctions with more than one junction node (as i.e. on split road junctions).
I will be honest. I do not understand this quoted section.
So I just will get on with the question that is most on my mind. Are we going to unsplit SPR, and if so, how are we? I think it is obvious it starts at Elkhorn Street to the south, but how far North do we go?
To be consistent, it should be all the way to the 5 ways roundabout at Rode Road/Beckett Road, but that is a huge project.
I am asking these questions first so we can get an agreement on what is to be undertaken, as a lot of double checking of someone’s work will need to be done, especially if the unsplitting is being done by a level 1 or 2. All the turn in/turn out’s need to be checked etc.