State Hwy 80 vs Ky-80

I’m just trying to figure out which naming convention is standard for KY. I’ve read the wiki post on State highways and it looks like the preferred way is “State Hwy 80”, but I would like to get a little more insight before I go through renaming the whole road.

Also the TTS appears to be pronouncing Ky as “chi” so at the very least it should probably be KY, but I think that I’m still leaning towards State Hwy.

Thoughts on this?

For a references, here is one of the places that the naming convention changes in the middle of the road.
https://www.waze.com/editor/?zoom=4&lat=37.11076&lon=-84.9693&layers=BFTFFTTTTTTFTTTTTTTTTFT

There are a ton of these all over and tts makes it worse :slight_smile: State Hwy ## is good, I fix them when I see it.

http://www.waze.com/wiki/index.php/Road_Naming_(USA)#State_Highways

Be sure to read the wiki :slight_smile:

Yeah, I took a look at the wiki, it was talking about how different states use either the State Hwy ##, SR-##, or even the postal code-##. I just wanted to make sure that I was sticking to the correct standard and not fighting the work that’s already been done.

I think that I’ve probably at least skimmed over the whole US wiki. I tend to over-research a bit. :geek:

I happened across this - pardon an outsider for commenting. What’s your local use? Up here in central NY we usually just say the number, and if we say anything in front it would be “route”, so we’ve converged on SR-xx. I think in Los Angeles they would like “the”, as in “the 405”. Wouldn’t that look great on maps? :slight_smile: Anyway, sometimes usage varies in different parts of a state. So what do your real people say and want to hear?

Long history short: US-xx, SR-xx, CR-xx take significantly less room in these small smartphone screens and are correctly interpreted by TTS. Using a state abbreviation is dubious from a TTS perspective, but either US Hwy xx or US-xx is acceptable depending on where you are editing. Usually, the AMs in a state have resolved use one or the other, so the advice to check the wiki – as best as you can – holds.

Good point, most people here seem to either say just the number “80”, or maybe just Highway 80. So I guess that the best middle ground would be to stick with the wiki and say “State Hwy 80”.

I don’t really hear most people using route so SR probably wouldn’t be as familiar (even though I would prefer taking less space :slight_smile: )

Also I have looked around a bit and have observed that most of the edited roads are fairly consistent with the “State Hwy ##” usage so I think that I’ll stick with that. Good news is that will fix my weird TTS pronunciation of Ky as “chi” as well!

Well, it’s also worth considering what’s on signage.

In my travels from Lexington to Louisville to Indianapolis to Cincinnati and back to Lexington yesterday, I saw three states’ usage of signage.

I don’t have any recollection of what was in Indiana, but Ohio definitely signed their roads with “SR-xxx”, and Kentucky routes were signed “KY xxxx”.

Typically, the rule of thumb on Waze has been to go with what is on the signs, not what is colloquial… so, these should probably be “KY-xxxx”.

I’ve also noticed that most of the state routes here are named (Frankfort Rd / Georgetown Rd), and rarely referred to by number. If we’re not going to go with the “KY-xxx” model, perhaps we could standardize on the SR-xxxx for the simple fact that it should also produce the shields?

Since tts mangles KY, Kentucky - ## would have to be used but Imo State Hwy ## is fine.

“State Hwy xx” uses a lot of screen real estate when you’re describing exits correctly…

As for TTS, it’s a work in progress. Louisiana uses “LA-xx” and I’m not sure that it is pronounced correctly either.

The big thing is to match signage, as the driver needs to interface the virtual (waze) world with the physical by matching up these things. The less imagination they have to apply, the safer they are on the roads.

The “LA-##” format is pronounced “Ell-Ay”, which is how the locals refer to the road.

We’ve been trying (for quite a while now) to get all the US State Abbreviations to work correctly in TTS, as well as the abbreviation with a dash on the end - but we want better control over the ones with the dashes. For example in most of the NorthEast all the roads are referred to as “Routes”, so we would want to see “CT-##” or “NY-##” on the display, but hear “Route ##” from both on TTS. I think this is going to have to wait a bit as we are still tying to get US Shielding to work properly.