State Highway Names
This is a "LONG" overdue post from me. I stirred the pot up amongst your SMs (SuperDave1426 and MojaveCactusMonkey) and your RC (jemay). My point was to standardize the usage and naming convention of and for the state highways. I happened to be driving and had an exit prompt and was shocked to hear a working TTS for something I was expecting otherwise. So it prompted me to request we as a whole agree to make Nevada state highways one form to make it special not only for the state, but for roads that cross borders to be able to have distinct state lines in forms of the map reflecting that.
For years, the default state highway naming convention across the board before TTS was even thought of for spoken directions, was State Hwy XXX. That is of course to the best of my knowledge of what I remember from the old editor version cartouche days. Then TTS became a feature of the app, we then started wanting to fine tune the default TTS where there were issues, then we realized we could shorten the street names on the screen which is already short on real estate for all of the features as it is, so we now have US-XX instead of having to use US Hwy XX or SR-XX and even SH-XX as naming conventions. Some states, such as Kansas, when referring to the state highways, say it is Kansas Highway 7, everyone refers to it simply as K-7. So agreed amongst a high level champ, myself and maybe a few others, every state highway adopted the standard naming convention of K-XXX in Kansas a couple years ago now.
Come my move to Nevada and my local daily driving. I don't even think the freeway sign was one that I had touched, I don't go around editing everything, only the obvious things that stick out to need fixing. Aside from that, I heard "Exit right to Exit 41: Nevada 159 / Charleston Blvd" which is "Exit 41: NV-159 / Charleston Blvd" It of course has my edits recently, as I edited geometry related issues there. Now, what the surprise to me was the TTS of Nevada clearly and quite shockingly. I didn't expect it as it wasn't a known working TTS to me at the time. So it got me thinking to ask to make a statewide adoption of "NV-XXX" as the naming convention for the state highways.
I ask this because of the success I saw in it working, and figured it would help reduce screen text for the limited real estate by reducing the text characters but still providing the TTS audio feedback. I propose we adopt this or SR-XXX as the secondary to not using NV but you'll get TTS to say State Route XXX instead of Nevada XXX. The reason it is being asked is to get a common agreement amongst the community that can become a part of revising the Wiki here for the simplified reference: https://wiki.waze.com/wiki/Highway_naming/USA
And more specific to the state wiki if it gets added to it: https://wiki.waze.com/wiki/Nevada
So look forward to your feedback, all is welcome. I don't prefer any way in particular, as long as we have a common standardized naming convention that can be set in digital stone of the Wiki. I favor one, yes, but I will see both sides and I am not the one to make this decision, it will be the community as a whole.
For years, the default state highway naming convention across the board before TTS was even thought of for spoken directions, was State Hwy XXX. That is of course to the best of my knowledge of what I remember from the old editor version cartouche days. Then TTS became a feature of the app, we then started wanting to fine tune the default TTS where there were issues, then we realized we could shorten the street names on the screen which is already short on real estate for all of the features as it is, so we now have US-XX instead of having to use US Hwy XX or SR-XX and even SH-XX as naming conventions. Some states, such as Kansas, when referring to the state highways, say it is Kansas Highway 7, everyone refers to it simply as K-7. So agreed amongst a high level champ, myself and maybe a few others, every state highway adopted the standard naming convention of K-XXX in Kansas a couple years ago now.
Come my move to Nevada and my local daily driving. I don't even think the freeway sign was one that I had touched, I don't go around editing everything, only the obvious things that stick out to need fixing. Aside from that, I heard "Exit right to Exit 41: Nevada 159 / Charleston Blvd" which is "Exit 41: NV-159 / Charleston Blvd" It of course has my edits recently, as I edited geometry related issues there. Now, what the surprise to me was the TTS of Nevada clearly and quite shockingly. I didn't expect it as it wasn't a known working TTS to me at the time. So it got me thinking to ask to make a statewide adoption of "NV-XXX" as the naming convention for the state highways.
I ask this because of the success I saw in it working, and figured it would help reduce screen text for the limited real estate by reducing the text characters but still providing the TTS audio feedback. I propose we adopt this or SR-XXX as the secondary to not using NV but you'll get TTS to say State Route XXX instead of Nevada XXX. The reason it is being asked is to get a common agreement amongst the community that can become a part of revising the Wiki here for the simplified reference: https://wiki.waze.com/wiki/Highway_naming/USA
And more specific to the state wiki if it gets added to it: https://wiki.waze.com/wiki/Nevada
So look forward to your feedback, all is welcome. I don't prefer any way in particular, as long as we have a common standardized naming convention that can be set in digital stone of the Wiki. I favor one, yes, but I will see both sides and I am not the one to make this decision, it will be the community as a whole.
Re: State Highway Names