At these segments, when approaching with a navigation path that turns left from Ferntree Gully Rd into Stud Rd, the instruction given when approaching is, “Turn Left, then, Turn Left at SR9 Stud Rd”
The instruction should be “Keep Left, then Turn Left at SR9 Stud Rd”
Looking in to how to achieve this, the guidelines say to make the exit at an angle no more than 43 degrees. The current angle for some reason, is 92 degrees, which makes no sense as it doesn’t look like that angle. Could a lvl 3 or above please look into this and make the required alteration. I mean, I know where I’m going, I live in the area, but for a Wazer visiting the area, being told to “Turn Left, then Turn Left” might be a bit confusing.
The micro dog leg is valid if you consider that it is a “turn left any time with care” situation so it is reasonable to want a TURN left instruction. The problem here is that later addition of all those parking lot roads.
The turning lane needs to come after the parking lot segment # 213172192
Then it must not join at the same node as segment # 213172193
So the lane either needs to be deleted or contained within those two parking lot segments but shortening it and adjusting the parking lot segments such they come off their applicable roads at 90 degrees.
The turning lane can come after all the service station access roads, which would allow the “Keep Left” TTS command. What you may not realise as the satellite image is out of date, there are now 2 turning lanes and I’m pretty sure they start at roughly the location the turn lane currently comes out from. However, for the TTS to work as I believe it should, deleting the segment before the service station access roads, then making the turn start at an angle less than 43 degrees after the service station access roads, should allow everything to work as it should no matter where you’re coming from.
For example: Wanting to turn onto Stud Rd from Sara Rd. Making the adjustments I’ve just suggested, based on what you’ve explained, the TTS should say, “Turn Right onto SR22 Ferntree Gully Rd, then Keep Left, then Turn Left onto SR9 Stud Rd”, correct?
Currently, as you’re approaching the access roads to the service station, it tells you to turn left (Where? Into the service station?), which it then follows with, “Turn Left at SR9 Stud Rd” It should say “Keep Left”. There are 2 right turning lanes, 4 straight ahead lanes and 2 left turning lanes now at that intersection on that approach.
The way I look at it, it’s the same as if you were on a Freeway and you wanted to turn onto the next road that comes along. The TTS says to “Exit Left then Turn <whichever direction you’re going>”, not “Turn Left, then Turn <whichever direction you’re going>”
The Street View on Google Maps is out of date also. I’ll see if I can take some photos of the intersection after work today as it’s just down the road. Being a delivery truck driver, I pass this intersection multiple times a day because of my job.
I took a whole heap of photos of the intersection today, but they are all too big to upload in here and my paint program is on my PC that isn’t setup at present.
You know, I can see the problem with designing an intersection like this, it is rather messy, however, with all the turns I allowed and didn’t allow when I created that mock intersection (which I have since deleted), as far I could make out, the TTS system would function completely correctly when a Waze navigation route would pass through it in which ever direction it needed to go.
When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display, and to produce sensible verbal instructions when (and only when) they are needed.
Simplicity
It is not a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity–which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance.
Nice to be trusted. Did a post I made get deleted or just didn’t it post properly? *edit, for some reason, these last few posts didn’t show up when using my phone. No, Lakeyboy hasn’t said anything about it.
The TTS with the designed intersection above should be spot on for giving directions, as it doesn’t really mention streets/roads without a name, it just would have said, “Keep Right” or “Keep Left”, then “Turn” or “U-Turn” where applicable. If I can actually catch you in MAP CHAT, I’ll recreate the intersection and you’ll be able to see all the turns. For lvl 3 and above, it should be fairly straight forward as to what is happening with all the segments and as for the complexity, it really would only be required on divided roads anyway. The main reason I made that mock intersection is because of u-turns. It seems rare that WAZE tells you to make a U-Turn unless you’re on a dead end street. And, when it does tell you, it’s never consistent. I’m not sure if that’s to do with time of day or traffic, but from when I leave my work, if I need to head in the other direction, I’ve been told to turn at 3 or 4 different places depending on whether WAZE thinks I’m on the main road or the service lane.
As for what it would physically look like on a device, as most of the roads are the same shade in the app and the darker ones overlay the lighter ones anyway, it wouldn’t really make that much difference until the Wazer, saw the navigation route that that intersection design said to take.
Sorry for the delay for getting to this issue. Was too busy the past few days to get onto Waze to reply. How it’s been fixed up now should work fine. I had mapped it the other way previously because that was roughly where the 2 left turn lanes separated from the straight ahead lanes, but it seems doing it that way meant it created 2 prompts which I wasn’t expecting. It should work fine how it is now. A “Keep Left” instruction is probably more appropriate here considering it is a longish two lane slip lane. The only problem now is that Waze won’t let you turn right from FTG road heading East into the Shell Servo. But considering there is no turn lane, it is probably better to have Waze make drivers do a u-turn at Rosehill St instead. Should hopefully work fine from now on!
I intend on contacting Knox Council about that tomorrow. There is a No U-Turn sign facing that direction, but no No Right Turn sign and there should be. Same thing when heading towards Stud Rd, there is a No Right Turn sign, but no No U-Turn Sign and there should be.
The 2 entrance/exits to the Service Station from Stud Rd are actually 2 way available, but common sense would tell you the way it’s setup at present, is how it should be (1 way) even though there is only one way signage on the 2nd entry point on FTG Rd.
