Waze forum

esochan wrote:

Type: General error
Description: red light warning was behind me getting farther away in distance

Huh?

It's happened to me plenty of times. If you start out on a divided road heading away from the RLC, but the route eventually goes through the RLC, it will trigger if you are within (currently) 500m, and as you drive away, increase until it gets to 600m. If it doesn't hit 600m, it will then count down until you reach it. If it hits 600m, it will go away and not re-trigger again that I've seen.

WeeeZer14 wrote:I'd love the option of sending a response along the lines of "The GPS in your phone sucks. Get an external GPS receiver or a new phone."

But what if it's the earth doing a slightly different wobble for a few seconds?

txemt wrote:

Sign says 90 miles to Houston, app says 76 miles. What gives?

Um....Waze is more accurate than TxDOT?

OR your destination isn't actually as far away as the location that TxDOT is using for the sign?

UR for a long-standing pronunciation issue. This is local humor.

Problem: pronunciation of tualitin

City name is pronounced too-ALL-uh-tin, whereas Waze says it "too-ul-A-tin" But it's spelled "Tualatin."

heckmandm wrote:Tualatin... is that nearby the Willa-METT River? Hahahaha. I lived in Salem for a time before moving back home; it took me about 3 or 4 months to pronounce things right out there.

Yes, not too far. And yes, you pronounced it perfectly like a non-native there.

kodi75 wrote:[Really?? The street name is "Bristle Cone Circle.

Someone's messin'

Probably referring to the name of another Wazer.

Is it too close to see?

http://img838.imageshack.us/img838/5955 ... 7at502.png

mike0723 wrote:terrible turn - too many commuter trains

(I guess they want Waze to route based on the train schedule as well...)

That will be technically possible. Someday. http://www.waze.com/forum/viewtopic.php?t=10489

Ambiguous destination.

Uh, oh. I'm being an ass to drivers. Again.