I took a look and it looks great to me!

sketch wrote:
Forgive me if I'm misunderstanding, but, you don't get a "keep left" instruction before any other 90° left-hand turn, why would you get one here? In other words, if you hear "In half a mile, turn left," and you're in the right lane, you're going to get into the left lane, just as you would if you heard "In half a mile, stay to the left." There's no difference. I don't understand the "issue" with the screenshot you posted.

I think the issue in the screen shot is a result of a "Turn left in XX feet" instruction, since the MUTI is oriented as two 90deg lefts. They got to Portage Rd and heard turn left, so they did.

falco_sparverius wrote: We suffer from not having a 'exit left' instruction, and have to suffice with 'keep left', which is acceptable for the time being.

And from not having a 'continue straight'. Will be interested to see how the Junction Box would handle this.

With respect to the particular situation with a right turn followed by a u-turn, I would put in a small connector so you can have complete instructions. If I'm from out of town and I know I need to head south, I would like to hear "turn right to some road north / some road south", instead of just "turn right to some road north".

Hi all,
I've been reading and following along...

I'm glad that you are discussing about this M. Turns that's very similar to our U-Turns here in NJ. I do think that there has to be an exception using ramps at grade when it comes to M.Turns and NJ U-Turns. We didn't put that under the "ramp" section on purpose. We didn't want to confuse new editors. I'm planning on updating our NJ wiki and put U-Turns as a separate section with images and detail explanations in lights of this discussion. I will certainly give my 2c and let you chime in on my draft before I update the wiki.

Oh by the way, I believe signs are different color in Massachusetts or in Connecticut. So, its wise to use sings instead of big Green sign.

Without being able to drive through those turns, I can't really say anything other than to word it in a way that is clear. However, in the last case you mentioned where you said you wanted to reverse the roads on the sign, I'm not sure that's a good option. Not only will it end up being a battle to keep them from being changed to match the sign, but it won't really be reflecting what people see on the sign. People have been following road signs for decades and I don't think anyone has any trouble dealing with a road sign that has the "TO" highway number above the street that you'll actually be on. So I don't see any reason why Waze needs to do anything different. I think it's a better idea to match the signs as closely as possible. It just makes it less confusing for drivers if the instructions match the sign in the same order as on the sign. Drivers really don't need to know when using GPS navigation that the road they'll turn on after the exit is the bottom road listed on the sign. Once they get to the turn, the instruction there will tell them that they are turning onto that road. They just need to know what the exit sign says to help them take the correct exit. Just my opinion.

sketch wrote:Yeah, that's fair. I've also been thinking of changing it to "Exit: to US-61 / Cleary Ave".

Your link doesn't highlight the exits you're talking about and I can't seem to find them, but based on your description of the sign, that looks like what I would expect (with an exit number if there is one, of course). What's there now?

sketch wrote:Anyway, that's not related. The Michigan Left signs all list the first road first and the second road second. I did take that Cleary exit yesterday, and that second "to" was pronounced quickly but clearly; it doesn't take much extra time to rattle it out, which is good.

Yeah, I don't see any problem with including "to" as far as speed of reading it goes. I just pulled up a street view and found an example. I think that it makes sense to have something like: Metro Parkway W / to Schoenherr Rd N.

Yeah, I think that if it is an actual Exit, it should say Exit: at the beginning even if it isn't numbered. It seems to be what I'm seeing elsewhere as well. You also have the issue with an exit that is just signed something like: [TO] I-75. Without using Exit: at the beginning, you're left with verbal instructions saying "Exit right at to I-75" instead of "Exit right at Exit: to I-75". Unless the TTS is set up to remove the "at" if it starts with "to", it just makes it sound bad. And even if you remove the "at", you're left with a question of whether "to" means you're exiting onto that road or exiting toward that road. Including Exit: just seems best, I think.

Ah, I didn't think about the entrance ramps. Do we have a Wiki article that details the different wording for turns? I think we should have one, even if it's just part of another article. Basically something that not only explains when you'll see Exit right vs. Keep right vs. Turn right, but also the wording used for TTS. It seems clear to a veteran editor, but I am sure it isn't so clear to a new editor. I know there's a small detail commenting on Exit right vs. Keep right, but it doesn't comment on turns and doesn't tell you the wording. I think being able to see how the TTS is going to read the instruction can be valuable when deciding on how to best word a ramp. Just a thought.

Thanks. I didn't realize they all said "at". I almost never have audio on except for alerts, so I haven't learned all of the TTS verbage yet.

I'm okay with this, but you'll want to make sure that every one of these has angles greater than 45 degrees. We don't want people getting "Stay to the left" instructions (or "Exit left" whenever that is added to Waze). With ramps, that's a concern.