Waze Palo Alto Meetup topics ranking

[tibble]

I want to second the idea of have it be STATE-###. Here in PA it should be PA-100. This would be the most recognizable to users.
I think we should have TTS say it as pee aie 100 as well. no need for pennsylvania 100 or anything silly like that.

[mapcat]

I want to second the idea of have it be STATE-###. Here in PA it should be PA-100. This would be the most recognizable to users.
I think we should have TTS say it as pee aie 100 as well. no need for pennsylvania 100 or anything silly like that.

Do that in Ohio and "OH-7" will come out "O AITCH SEVEN" and NOBODY will know what it's talking about.

Every state will need to settle on a standard, publicize it, and stick with it.

[tibble]

Then this brings me to my second idea.
We need a wiki page that says the naming scheme for state roads, per state.
I vote PA is PA-###

[WeeeZer14]

More or less exists here:

http://en.wikipedia.org/wiki/Numbered_highways_in_the_United_States

I started to put that info in a Google Spreadsheet and try to confirm some of it. But it isn't complete yet.

[mapcat]

More or less exists here:

http://en.wikipedia.org/wiki/Numbered_highways_in_the_United_States

I started to put that info in a Google Spreadsheet and try to confirm some of it. But it isn't complete yet.

Nah, that's just a list of what the state DOTs call them, not how drivers refer to them. Pennsylvania's says "Pennsylvania State Traffic Route". Don't think so.

It's a start, though, and if we can all agree that (1) each state should have its own way of designating highways, and (2) the TTS and shield generator can be programmed to read all of them correctly, then yes, let's create a spreadsheet (or a wiki page) that will put them all down in writing.

I think both (1) and (2) need to be true because we don't want to waste time changing names over and over.

[harling]

Around here, the DOT may differentiate between US highways and state highways (different road shields, for one thing), but everyone I know refers to them interchangeably as simply "route ##". Given that we are going to distinguish between the two, I suppose we could call US-3 "you ess three" as a common denominator without sounding too awkward to the locals (bad enough calling rotaries "roundabouts" ); MA-2 should definitely be simply "route two".

Just let me know when I should start propagating this nomenclature.

[WeeeZer14]

For MA-2, would locals be totally confused if it was labeled as SR-2 and spoken as "state route two"?

[harling]

For MA-2, would locals be totally confused if it was labeled as SR-2 and spoken as "state route two"?

The spoken part would not be too confusing, but "SR-" would look completely foreign on the display. "US-" and "MA-" would be obvious. State-specific abbreviations would allow each state to use its own TTS convention (maybe even including "rOOt" vs. "rOWt"), and make generating highway shields straightforward (no need to check the state field of each segment).

[harling]

Because "rOWt 128" would be even more intolerable than calling rotaries "roundabouts"...

[WeeeZer14]

I can't get along with myself...

Talking about roads, I use rOOt. Talking about computer networking (my job) it is a rOWt between devices.