Waze Palo Alto Meetup topics ranking

[harling]

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

Same here: "rOOt" is a noun, and "rOWt" is a verb. And in some places they are referred to as "highway ##". To each his own. All the more reason to let each state have its own label for state highways.

[harling]

I want to say that having TTS call both state and federal highways "Route", even if that's what's done locally, is too far. There needs to be some differentiation here.

I agree. I'm only advocating state-specific labeling for state routes (or state roads, or state highways, or whatever each state likes to call them), rather than a generic "SR-##" that would be displayed (and spoken) the same in all states.

[harling]

The TTS has to differentiate between the different types of routes. Just because some locals want to hear Route-### doesn't mean that nomenclature is going to be helpful to someone from out of town. If a State Highway has a similar or identical number to a US Highway, there could be some confusion (states aren't supposed to use the numbers of any US Highways or Interstates that run through their state, but who knows).

The best case would be to get TTS to read PA-100 as "Pennsylvania 100", and so on throughout the states. It's a little more personalized than "State Route 100", it tells you what state you're in, and it's idiot proof.

I also have a problem with "Route" just because in many parts of the country, it's a word that isn't used at all, and then there's the argument of pronunciation. I go back and forth between the 'root' and 'rowt' depending on context, but I'd think that some younger people who are into computer networking might not have any idea what 'root' means.

I think we're talking at cross-purposes. I'm not hearing anyone say that US highways and state highways should be written or spoken the same, only that it would be a good idea if state routes were handled by local convention rather than a uniform standard nationwide. In other words, US-10 "you ess ten" for US highways everywhere is fine, but SR-10 "state route ten" ("state highway ten"? "route ten"? "ess are ten"?) for state highways nationwide is too restrictive.

As for per-state designations: personally, I think that speaking the name of the state would get old really fast, at least to people around here. But with distinct designations, each state can have its own TTS rule. PA-10 can be "pennsylvania ten" or "P A ten" or whatever the locals prefer, and MA-10 can be simply "root ten", or whatever the locals prefer here.

[jasonh300]

Waze = Wanda

Yes! The Waze lady will forever be Wanda Wazer!

[jasonh300]

I've asked around at work today, and everyone refers to our state roads as "root" 100, "root" 724. So if they can have PA-100 pronounced "root one hundred" and PA-724 "root seven twenty four" that would be perfect!

The TTS has to differentiate between the different types of routes. Just because some locals want to hear Route-### doesn't mean that nomenclature is going to be helpful to someone from out of town. If a State Highway has a similar or identical number to a US Highway, there could be some confusion (states aren't supposed to use the numbers of any US Highways or Interstates that run through their state, but who knows).

The best case would be to get TTS to read PA-100 as "Pennsylvania 100", and so on throughout the states. It's a little more personalized than "State Route 100", it tells you what state you're in, and it's idiot proof.

I also have a problem with "Route" just because in many parts of the country, it's a word that isn't used at all, and then there's the argument of pronunciation. I go back and forth between the 'root' and 'rowt' depending on context, but I'd think that some younger people who are into computer networking might not have any idea what 'root' means.

Just to confuse things more, I'm going to throw out a suggestion to some bands that they record a cover of the Nat King Cole/Depeche Mode song "Route 66" and pronounce it 'rowt'!

[jenncard]

Phew. That was actually harder than I thought it would be.

[jenncard]

The meeting and discussion time (Q&A) will be summarized in a separate thread within a few days.

Too curious about the following to wait:

- No longer use "Hwy" in route names, whether on ramps or the roads themselves. Agreed syntax is, for example: "US-52".

Is a space no longer required (ramps and roads) after the "-", i.e. US-52 and NOT US- 52?

- Use slashes to separate alternative road names, e.g., "US-52 / US-89", noting the need for a space on either side of the slash.

Yay, yay! Is this live now?

[jenncard]

Yes! Just ramp names should have slashes. We reiterated our desire to multi-shielded roads along with local name.

poop.

[jenncard]

Apologies, I've only been part-way present on the forums recently...

I've seen dribs and drabs of the information from the meetup trickling out here and there, but has there been a consolidated recap yet?

[jenncard]

Not sure if AlanOfTheBerg is planning a full summary since a lot of the content of the meeting has been spread throughout many posts in the forum in the past couple of weeks.

That would be unfortunate.

I'm not sure how you guys do it, but I have a tough time keeping track of all the different threads throughout the forum AND maintaining Real Life I do hope the single recap will surface soon (wasn't one of the highly requested themes "Communication"?) and will greatly appreciate it if/when it does.