Can these streets please be dropped to a Level-2 for a short time so that I may make some small corrections?
There has been an error reported here and I can see the issue.
Also, some of these segments have been created without a city name, and I’d like to correct these as well.
Can I also please ask a quick bit of advice here from a high level editor? Would this intersection benefit from being made into a bow-tie configuration?
do you have a permalink?
OMG I’m so sorry, I did copy it, then forgot to paste it.
dropped to L2
I wouldn’t bowtie it but leave it as it is. There will be more functionality for junctions with the Junction Boxes that will come out later and bowties can be phased out
Hey glomp I’ve just had a total brain fart…
what would you suggest would be the best way to modify this intersection without making it a bow-tie, and to stop it u-turning if you’re heading east.
I’ve made a couple quick changes, trying not to add too many extra roads and a ramp to Bennets Rd, because I think that would clutter it way too much.
Would you mind having a quick look and making suggestions?
I’m not sure what you are trying to do here, but a normal “H” intersection should achive what you want to do.
I think glomp may be right.
Delete this segment: https://www.waze.com/editor/?env=row&lon=153.06433&lat=-27.49219&layers=901&zoom=8&segments=262105539
Make this one two way: https://www.waze.com/editor/?env=row&lon=153.06433&lat=-27.49219&layers=901&zoom=8&segments=144354245
Check all turns.
*edit: delete the excess junction afterwards too.
The problem was that if you’re heading east on Old Cleveland Rd (OCR), and are trying to get to an address on the westbound side, navigation will tell you to do an illegal u-turn.
If I make this segment https://www.waze.com/editor/?env=row&lon=153.06447&lat=-27.49210&layers=453&zoom=9&segments=144354245 two way, but disallow the arrow from Bennets Rd to turn right (to avoid theu-turn), then traffic coming from Bennets Rd can’t turn right either.
Does this make sense?
Yep OK, that’s what I thought glomp meant too… problem is, that is exactly how it was before, and it gave directions to the OP to make an illegal U-turn. One of the things I understand is an issue with H-junctions in split roads…
The right turn between these two segments should be disallowed thus preventing any u-turn: https://www.waze.com/editor/?env=row&lon=153.06447&lat=-27.49210&layers=453&zoom=9&segments=144435828,144354245
Ashton St to the East is a good example of how it should be laid out.
It shouldn’t route you through a restricted turn, were all the turn restrictions correct initially?
Only time I get routed like that, is if the all the turns have been enabled and the segment in question is an actual u-turn lane, otherwise I don’t think it has given me a route to do a u-turn at an intersection like that with the appropriate turns set.
&%$! me. I could totally punch myself in the face right now. What an idiot.
Worst part is that when I “identified the issue” this is exactly what I was going to do, then when it came to it my brain said “no”.
Thanks for the help guys… perhaps a good idea to check to see that I did it right this time? :?
No glomp, the turn was allowed… but like I said, it was the one change I was going to make but brain wouldn’t cooperate.
it’s all good, sometimes these things happen 
relocked 