Waze Palo Alto Meetup topics ranking

[AlanOfTheBerg]

Fully time-based would be nice but more difficult to program (vis-à-vis changes in speed, especially). We'd also have to consider that this would increase the number of sound files necessary to accommodate those who prefer not to have TTS or "Full" navigation guidance enabled.

True. Another one for 2mi when traveling > 55mph?

[gettingthere]

On my return trip to SFO, at 80 mph, I realized that I REALLY would have appreciated some TTS info a lot sooner than 1 mile.

80 mph + is common on California freeways, if not traffic loaded...

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

[gettingthere]

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

No longer required. Shielding is still not fully automated so it is likely you will have to work with support to shield / re-shield anyway.

[WeeeZer14]

- 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?

This just referred to naming ramps though, right? Road segments themselves should still use alt names to hold additional names and we made it clear that we'd like control over shields so we could have multiple if needed.

[AlanOfTheBerg]

- 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?

This just referred to naming ramps though, right? Road segments themselves should still use alt names to hold additional names and we made it clear that we'd like control over shields so we could have multiple if needed.

Yes! Just ramp names should have slashes. We reiterated our desire to multi-shielded roads along with local name. I'd really like to see "Primary Name" morph into "Local Name" and the alt name fields to be used for specifying the highway/interstate shield-generating fields, along with any other actual alternate names.

[jenncard]

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

poop.

[bgodette]

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?

Basically it boiled down to is the editing community comes up with a workable naming guideline and Waze will adapt TTS (apparently not that hard to change) and shield generation to handle the format.

With that said, we may or may not get state shields for state routes anytime soon if at all and certainly after ROTW gets shields. We also need to work out how we want TTS to handle all those abbreviation cases like Jr and St.

Sent from my SGH-T959V using Tapatalk

[sketch]

Fully time-based would be nice but more difficult to program (vis-à-vis changes in speed, especially). We'd also have to consider that this would increase the number of sound files necessary to accommodate those who prefer not to have TTS or "Full" navigation guidance enabled.

True. Another one for 2mi when traveling > 55mph?

That should do it for the prerecorded prompts.

It should be noted that this is a proposal to space existing prompts further out, and not simply to add more prompts before existing ones. The recent write-up received mentioned "too many voice directions" as a gripe, and while I don't agree ENTIRELY, I certainly don't think we need any MORE, and I do see room for optimization (especially with groups of subsequent ramps).

[AggieJM]

- No longer use "Hwy" in route names, whether on ramps or the roads themselves. Agreed syntax is, for example: "US-52". With less certainty, I believe that agreement extends to State Routes, e.g., SR-52, and County Routes, e.g., CR-52.

Most of my area is rural so 80% of the road are county roads that are currently named as "Co Rd 94". Since I don't use TTS in Waze most of the time (can't hear it in my vehicle), I didn't realize that it was pronouncing this as "co road ninety-four". Should all of these roads be change to the CR format (i.e. CR-94) to make TTS work correctly and conform to the new agreement? Or is there a pending change to TTS to make it work for "Co Rd". I don't want to start changing a bunch of roads that I'll have to change back later.