Waze Palo Alto Meetup topics ranking

[jondrush]

I consider 2 miles to be the normal alert range on a highway. I do wish Waze offered that.

[jondrush]

RT = County Route

Don't like that one. Too many places where RT is written for Route.

[jondrush]

RT = County Route

Don't like that one. Too many places where RT is written for Route.

But is that Route for State or County?

Yes.

[mapcat]

Thanks for putting in the time on it. Can you set it up so we can see the results after we vote?

[mapcat]

CR-## currently works with TTS and says County Road ##. However the community needs to come up with a shorthand for County Route, the obvious (CR) of course conflicts with County Road (CR).

That level of detail/personalization really isn't necessary IMO. Is someone expecting to hear "County Route 99" going to be confused if the instructions tell her to take "County Road 99"?

[mapcat]

Around here we usually say just, "you ess xxx".

Again, whether with or without "highway", users are unlikely to be confused by whatever is chosen. Personally I like whatever gives TTS Lady less to say.

[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.

[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.

[mapcat]

What would be superb is a way to have non-name-related fields to set up shields.

Am I too optimistic in interpreting the following as doing exactly that?

* Shield generation: we'll check the automated process and add more items such as state rte xx or state rd xx. On the editor: we'll add a way to edit the shields and add them to a street.

From Follow up - US mega-wazers meetup, January 2012. If that's the case, the details you suggested certainly could be worked in.

[mapcat]

Am I too optimistic in interpreting the following as doing exactly that?

* Shield generation: we'll check the automated process and add more items such as state rte xx or state rd xx. On the editor: we'll add a way to edit the shields and add them to a street.

From Follow up - US mega-wazers meetup, January 2012. If that's the case, the details you suggested certainly could be worked in.

I think are you. That, to me, sounds like the current state, but working on making sure the automated process catches changes to the shield without having to edit geometry to effect a tile rebuild to redo the shield graphic.

The part after "On the editor:" was what made me hopeful, since it sounded like they may be devising a new way for us to generate and/or correct shields.