*UPDATED* Ramp naming convention proposal

[jasonh300]

I agree with Banished in that this should be called to a vote. It's simple enough to set up a poll in the forums.

As far as the 'publicize for two weeks', we've been doing that for 2 months now in this case. I think we've got it down to two options...leave it the way it is, or change it to the way it's been outlined in the past few posts.

Put up a poll and leave it for two weeks. Make sure it gets bumped to the top of the 'new posts' list a couple of times a day so that everybody can see it.

Addendum: Okay, looks like a regular user can't set up a poll. But AlanoftheBerg has set them up before, so he has permission, and knows how to. We could enlist his help in this one.

[jondrush]

The standard has always only included the word "Exit" for exits from a freeway (limited access)—either "Exit xxx: Road" or "Exit to Road". Ramps onto freeways from roads that are not limited-access have always just been "to Road".

Why? Why is a ramp from a non-freeway to a freeway not worthy of an "Exit Right" announcement? I'm not talking about turning lanes here, true ramps.

[AlanOfTheBerg]

The standard has always only included the word "Exit" for exits from a freeway (limited access)—either "Exit xxx: Road" or "Exit to Road". Ramps onto freeways from roads that are not limited-access have always just been "to Road".

Why? Why is a ramp from a non-freeway to a freeway not worthy of an "Exit Right" announcement? I'm not talking about turning lanes here, true ramps.

For unnumbered "Exits" from US or state routes, I also often use "Exit to <city>" or "Exit to <road>" as it is the best way to be clear to the driver in TTS.

I also still disagree with the use of the second colon. I don't like how it looks and I don't like the TTS for it. It is still most clear to use "to" instead of ":" but I do understand the need for some brevity, screen real estate/width available for characters, etc. Conversely, with good TTS, we shouldn't have to look at the screen for the info but just be able to drive and listen to the announcement, which is where having the "to" is better. If we could get Waze to announce every ":" after the first one which is combined with the word "Exit," as a "to" instead of a pause, that would be ideal(er). That all being said, I would fall in the with majority vote as this isn't a HUGE deal.

[jondrush]

I put a colon after the "exit to" for the same reason we put it after the exit number. TTS runs the words together if you don't. It's been working very well in my area.

[sketch]

The standard has always only included the word "Exit" for exits from a freeway (limited access)—either "Exit xxx: Road" or "Exit to Road". Ramps onto freeways from roads that are not limited-access have always just been "to Road".

Why? Why is a ramp from a non-freeway to a freeway not worthy of an "Exit Right" announcement? I'm not talking about turning lanes here, true ramps.

For unnumbered "Exits" from US or state routes, I also often use "Exit to <city>" or "Exit to <road>" as it is the best way to be clear to the driver in TTS.

I also still disagree with the use of the second colon. I don't like how it looks and I don't like the TTS for it. It is still most clear to use "to" instead of ":" but I do understand the need for some brevity, screen real estate/width available for characters, etc. Conversely, with good TTS, we shouldn't have to look at the screen for the info but just be able to drive and listen to the announcement, which is where having the "to" is better. If we could get Waze to announce every ":" after the first one which is combined with the word "Exit," as a "to" instead of a pause, that would be ideal(er). That all being said, I would fall in the with majority vote as this isn't a HUGE deal.

Actually, I did test the "to" in a couple places around town, one of which is an exit I use at least three times a week, usually more. The "to" sort of tends to make everything before and after it run together. I much prefer the pause inflicted by the colon.

There isn't really any need to put "Exit" on the name of any ramp off the side of any highway, because the TTS instruction is "Exit to the right", anyway. It's sort of redundant and wastes time. To be honest, I think it would be better if unnumbered exits from freeways also did not include the word, because "Exit to the right, at exit to Carondelet Street / St Charles Avenue" adds nothing but time to the announcement, where "Exit to the right, at Carondelet Street / St Charles Avenue" conveys the message perfectly (with the segment named "to Carondelet St / St Charles Ave"). However, starting the segment name with "Exit" does provide visual congruence, especially in situations where only three or four exits are not numbered, sandwiched between an interstate and another freeway with 7 or 8 numbered exits.

As for "Exit to: Road" vs. "Exit to Road", now that I'm looking at it this way, I think "Exit: Road" is actually more sensible and more in line with "Exit 228: Street".

[Timbones]

Is this naming convention specific to ramps in the United States?
If so, can the discussion/voting be moved to an appropriate forum?

Ta.

[jasonh300]

The standard has always only included the word "Exit" for exits from a freeway (limited access)—either "Exit xxx: Road" or "Exit to Road". Ramps onto freeways from roads that are not limited-access have always just been "to Road".

Why? Why is a ramp from a non-freeway to a freeway not worthy of an "Exit Right" announcement? I'm not talking about turning lanes here, true ramps.

Wait...we're talking about two completely different things.

The "Exit Right" comes from Waze internally. It normally comes from having a Ramp segment veering off to the right. Nothing you put into the naming is going to have any effect on that.

If you're on a non-freeway, approaching an onramp (Ramp type) on the right that is labeled "to I-10 W", your TTS is going to say "Exit Right at I-10W". If you name it "Exit to I-10 W", TTS will say "Exit Right at Exit to I-10 W".

[bgodette]

If you're on a non-freeway, approaching an onramp (Ramp type) on the right that is labeled "to I-10 W", your TTS is going to say "Exit Right at I-10W". If you name it "Exit to I-10 W", TTS will say "Exit Right at Exit to I-10 W".

Which is exactly why I don't like unnumbered exits from freeways to be of the form: "Exit to Road" or "Exit: Road", but would rather have "to Road". It sounds terrible from TTS and makes it overly wordy.

[andrewfatcat]

In my area, I am currently using "Exit xx: xxx Rd, xxx St", and it works pretty well. This uses less character than "Exit xx: xxx Rd / xxx St". I justify this because it is not necessary to be "or" in this case. It can also be "and". Therefore, using ", " should be literally correct.

I strongly oppose using double-colon for the highway directions because it really looks bad and not logical. If I am going to put the city after the highway, I will be using "Exit xxx: I-10 East (San Antonio)" or "Exit xxx: I-10 East - San Antonio" because they look much better than the double colon and more logical. And I doubt the need to add city name in some cases because it should be already enough for people to understand the directions if there is only the highway name. Putting too much information does not help much and just making the TTS more verbose.

About the entrance ramps in my area, I am currently using "To I-10 North" instead of "to I-10 North". "To" makes the whole thing looks better than using "to", and it is also more literally correct. If one looks closely to some of the highway signs, sometimes there is a "TO" on the top of the highway badge. Therefore, I think capitalize the "T" should not be a problem. The TTS works the same in both cases.

[jondrush]

The standard has always only included the word "Exit" for exits from a freeway (limited access)—either "Exit xxx: Road" or "Exit to Road". Ramps onto freeways from roads that are not limited-access have always just been "to Road".

Why? Why is a ramp from a non-freeway to a freeway not worthy of an "Exit Right" announcement? I'm not talking about turning lanes here, true ramps.

Wait...we're talking about two completely different things.

The "Exit Right" comes from Waze internally. It normally comes from having a Ramp segment veering off to the right. Nothing you put into the naming is going to have any effect on that.

If you're on a non-freeway, approaching an onramp (Ramp type) on the right that is labeled "to I-10 W", your TTS is going to say "Exit Right at I-10W". If you name it "Exit to I-10 W", TTS will say "Exit Right at Exit to I-10 W".

But it doesn't for me. It says "keep right at exit to I-76" That's why I do it. "keep right at to I-76 doesn't' work.