Waze Palo Alto Meetup topics ranking

[foxitrot]

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

I'm also using a built-in nav with Navteq SW. I've realized that the actions are not announced at fixed distance intervals, rather the current speed is taken into account (thus differing between freeway / fast road / living street) and the announcements do happen at some convenient time intervals prior to the action. And also the convenient and useful repeat button, which anytime repeats the next coming action with the true remaining distance (imagine yourself staying 60m/200ft in front of red light, or drive at 80 mph in a very dense traffic and realizing you've missed the last announcement - right? left?)

[AlanOfTheBerg]

I've often thought that the timing of turn announcements should be time-based and not distance-based. Though the Waze alerts distance do change based on speed, it's sometimes not quite enough.

[harling]

I've often thought that the timing of turn announcements should be time-based and not distance-based. Though the Waze alerts distance do change based on speed, it's sometimes not quite enough.

At the meeting, we did mention the need to tell Waze to repeat the most recent audible direction.

We did not mention the possibility (discussed here) of Waze announcing the next turn, with distance, as soon as the previous turn is completed (unless the usual speed-sensitive announcement is going to come up soon enough anyway). IMO this would solve the OP's problem, and make it a lot easier to use Waze with the display turned off--which increases the battery life a lot, I have found.

[banished]

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.

Of course, the distance to the exit is on the display, but not on the TTS as you note. Driving at 80mph, it's probably best not to take your eyes of the road to look at Waze, anyway.

The "The Book of Expert Driving" (E. D. Fales Jr., Bantam Books, 1971, p. 87, "Operational Plan for an Exit") states, "...when traffic is heavy, watch for the earlier sign that, on many pikes, says: 'Exit 2 Miles." To avoid a last-minute scramble, this is your signal to switch."

I also like the next paragraph, "Above all, guard against the dangerous "exit runner," the fellow who stays in the fast lane until the last minute, then cuts across traffic in front of you and squeezes down the exit ramp. He's caused lots of accidents."

[sketch]

I've often thought that the timing of turn announcements should be time-based and not distance-based. Though the Waze alerts distance do change based on speed, it's sometimes not quite enough.

Yeah, Waze already does this. The maximum seems to be set at 1.0 miles, however, which I think should be doubled.

[AlanOfTheBerg]

I've often thought that the timing of turn announcements should be time-based and not distance-based. Though the Waze alerts distance do change based on speed, it's sometimes not quite enough.

Yeah, Waze already does this. The maximum seems to be set at 1.0 miles, however, which I think should be doubled.

Yes, but I feel it should be 100% time-based combined with either current speed or current hour average segments speed up to the next turn. Those together should be able to get you all you need without having to stick with 1mi, .6mi, .5mi, .25mi, .1mi static alerts.

[GizmoGuy411]

While I agree with Alan that it should ultimately be time based, I think Sketch's suggestion to double the distance would be a quicker adjustment for Waze to accomplish. If we could push for that as an interim solution, the time based algorithms could be pushed for the future. Since we gave them so much to consider, adding a two mile out TTS to the prompts would be something they should they be able code easily.

Maybe quoting from banished's source would be a positive motivator for them.

Indeed I seldom took my eyes off the road while driving on thwe 101. Their we're at least 3 signs indicating which exit to take for car rental return. I missed reading the road named signed on the first two because my field of vision was blocked each time by trucks. Normally I would have studied a nav list for the last few turns, however we know why I did not do that. Alternatively I should have at least scanned the route first before I shifted out of park!

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

[jondrush]

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

[bgodette]

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

Agreed, if they add "get ready"s at 2 miles and 1.5 when traveling on a freeway segment, it would be fine. I mean freeway segment instead of speed due to the possibility of being in gridlock conditions where changing lanes can take some time/distance.

Sent from my SGH-T959V using Tapatalk