Waze Palo Alto Meetup topics ranking

[wroadd]

Nice idea! I voted, but I think that the US server users are in special situation, so maybe the final order should show the opinion of the US server's users.

[banished]

Recommending closing out voting Thursday afternoon and publishing the results not later than Thursday night by 9 p.m. EST. Some of us begin travel on Friday morning and it would be helpful to have the discussion items to study before then, please. Thank you!

[AlanOfTheBerg]

Sure thing. I was planning to end voting Wednesday night and putting the final tally out Thursday.

[argus-cronos]

good work, i've voted two days ago. Have a good meeting.

[AlanOfTheBerg]

The survey is now closed. Thanks to all who voted. Below is how the average scores turned out (lower score is higher priority: closer to #1). Here's a link to the google doc version.

paloalto_meetup_topic_final_votes1.png (65.67 KiB) Viewed 2075 times

paloalto_meetup_topic_final_chart.png (34.65 KiB) Viewed 2075 times

[WeeeZer14]

Thanks for taking the time to run the survey!

[AlanOfTheBerg]

The meeting and discussion time (Q&A) will be summarized in a separate thread within a few days. All attendees are encouraged to share their thoughts.

[banished]

The meeting and discussion time (Q&A) will be summarized in a separate thread within a few days. All attendees are encouraged to share their thoughts.

My summary (memory?) is as follows:

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

- 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. Without the space, I've heard TTS actually pronounce, "slash." Waze has agreed to change TTS to insert a 1/2 second (similar to a comma) delay for slashes, so when that happens I do not know if the spaces will matter, but recommend we keep it to make it easier to read on the client. I trust that 1/2 sec. TTS change will occur soon since right now a slash doesn't do anything to make TTS more understandable.

- Railroads: It wasn't unanimous, but think the majority agreed to return them to the client. Insuring they cannot be routable or impact nearby road traffic conditions under any circumstance, even if there's ten thousand Wazers riding the Long Island RR or Chicago Metro everyday, is Waze's responsibility to implement.

[WeeeZer14]

For the naming issues, I think it can be further summarized to:
1) We the community define what we want
2) Waze the company will work with it

Once We get the true debrief thread started, it may be good to have break out threads to discuss individual topics.

[GizmoGuy411]

I learned something AFTER the meetup that I never have experienced in my home area. If I had, I would have proposed it last week to add to the discussion. If we DID discuss it, then I missed it.

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. With so many lanes, and busy traffic, it can easily take more than a mile to move from the HOV to right lane to exit. Especially for someone from out of town.

The "expensive" Navigon app, gives you info at more and further intervals, plus it always announces the next action, right after you completed one. Another little bonus, is that it provides a button to force it to repeat the last thing it just said.

It would be interesting to hear if anyone else noticed this while attending the meet-up or have thought about it before.