60 Mph/97 Kph

[sandman82]

Well... I'm from Argentina, and I also noticed this a few days after i started using the app...
Here, the highway limit is 80 kph... and i never saw that number, but did saw 77, 79 and 81...

The minute i saw this behavior, i knew it had something to do with conversion...
I would have never guessed that it was converting from knots to kilometers... I thought it was doing it from miles to kilometers....

Cheers.

[Seasider]

Esteemed Wazing friends

Over the last 4 or 5 weeks an anomaly has presented itself to myself and several other Wazers whilst using this brilliant app on the road.

It would appear that Waze is completely unable to display 60 Mph on phone clients, certainly in the North West of England.

I know this is not really a massive glitch in the grand scheme of all things waziness, but it has been bugging me and a fellow wazer who I work with greatly. To the extent that we have tried 4 different mobile phone handsets in 8 different cars (6 of which have cruise control) whilst running 2 and sometimes 3 stand alone Sat Nav devices.

The results of our extensive geekery are thus - Waze doesn't do either 60mph or 97 kph. With cruise control set at 60 Mph and 2/3 sat navs displaying a constant 60 Mph and 2 mobile phones running waze in the vehicle, the client devices display a speed that jumps between 59 and 61 Mph (or 96 and 98 Kph, we tested both speed displays).

We have looked for possible explanations in numerology even, but can find no reason why this would be.

Has anyone else noticed this phenom, or can anyone explain to us why Waze doesn't display 60, as it (as a point of principle now) is DOING OUR HEADS IN!!!!!

Thanks gang

[Seasider]

Same here using Android. Could not make it hit 60. Odd that no one noticed this before. Makes me wonder if there are other numbers it won't show.

Not wishing to admit too much, but as part of our testing process (high geekdom indeed), we've studied the speed display and can confirm it displays all other speeds except 60 up to and including low 3 figure values.

Sent from my Dell Streak using Tapatalk

[Seasider]

That would be telling, but long night shifts and totally empty and straight motorway may have had some part to play, and of course I was referring to our testing of the kmh display, your honour.

Sent from my Dell Streak using Tapatalk

[Seasider]

On a related note I couldnt find 60km/h either?

Can confirm waze does display 60kmh lol

Sent from my Dell Streak using Tapatalk

[Seasider]

Just to clear something up, we discovered the lack of 60mph purely because it is our standard motorway patrol speed, and set the cruise to that on the calibrated car speedo, then discovered waze showed either 59 or 61 mph so tried to make it show 60mph. Couldn't do it, hence this topic.

Sent from my Dell Streak using Tapatalk

Sent from my Dell Streak using Tapatalk

[segfaultex]

So is this ever going to be fixed.... I mean seriously this is a nav app that doesn't properly display speed...

[segfaultex]

I'm not trying to flame but the nav aspect is even worse, i've been giving waze a chance for years now and just hoping it would improve but it still gets my route to work wrong. The same route i drive with waze almost every day. Half the time it cant even find addresses of places to drive to.

I really really love the whole community idea and being able to see live traffic/hazards and thats the only reason I have kept using it but i'm seriously just getting sick of it. If i need to get somewhere I don't know how to, google nav is so much better.

Anyway the speed is a nice second check but its always off by quite a bit (not my phone I compared it to other speed apps) which half the time its off to where i'm speeding by almost 4 mph if i follow what waze says.

What I guess really bugs me is the fact that the responses to a known bug/problem that has been around for a very long time is pretty much "get over it". That's not support or even helpful so with that I think I will be saying goodbye to waze. I had high hopes I really did.

[Spil]

Well said, Gordonski ... except one minor flaw in the formula:

...

Code: Select all

(long1-long2)*60*cos((lat1+lat2)/2))

...

You've got an extra closing parenthesis in there -- the computer will return an error instead of a distance. But yes, the rest of your explanation is excellent. There's no need for Waze to waste time trying to fix a non-issue like this when there are so many other known real bugs and problems and issues that we need to have them address instead.

[StephenCB]

I lost my sense of humor in a terrible industrial accident about three years ago. I'm kind of sensitive about it. Jerk.

This made me actually laugh out loud.

I was reading this thread with interest. It shows some of the underpinnings of an application I am quickly getting attached to. I've been using Waze for about a week.

This comment thrown in tells me I'm in the right place for humor too.