60 Mph/97 Kph

[stevenhaywood]

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

[stiab3]

Since reading this thread, I've been watching. And I've never seen it land on 60mph. 59mph, yes. 61mph, yes. Never 60mph.

Dark forces at work. . .

s3

[stiab3]

Actually, it was the missing 60mph in the UK that brought it to light.

Not sure why no-one noticed the missing kmh ones.

s3

[stiab3]

I think people tend to notice speeds around speed limits and these tend to be in round figures. . . 10s of mph or kmph.

Despite a lot of the smaller km ones missing, I would expect that 30 would be the only one that people would be interested in. . .

@Seasider, do the other satnav devices you tested against show 61mph?

s3

[stiab3]

What's the reason for using integers for such conversions? I hope Waze developers will fix this bug in the next release, because one float more will definitely not overload our high-end phones with FPUs...

EDIT: BTW if Waze would be as open-source as it claims to be there would be patches flowing at this moment to apply on the SVN/GIT repository...

4\/3!!

Does it really need to be fixed? It's just a quirk of the system. The speed taken from a GPS unit is never going to be precise, anyway.

s3

[stiab3]

To me this is not actually a bug as it doesn't affect functionality in any way. It won't hinder success either.

By all means push for open source, and for being able to fix bugs, but don't make a non-issue into something more.
s3

[support]

Hi all,

Very interesting indeed...

If one on you could send us a .csv file of one of the route for exmple,
will be very happy to look into this metter!

You can send it to alpha@waze.com.

Regards,

Amit
WAZE Support

[unwallflower]

Harling, you rock!

So do computers. I love that everything has logic behind it.

[unwallflower]

To me this is not actually a bug as it doesn't affect functionality in any way. It won't hinder success either.

By all means push for open source, and for being able to fix bugs, but don't make a non-issue into something more.
s3

You're correct, it's not a bug by definition. It's working exactly as designed. That's not to say that it was designed in the best way possible, though.

I don't think anyone is clamoring for this to be fixed. It isn't the end of the world. It seems, from THIS perspective, to possibly be poor coding... but since I haven't actually looked at the code I can't really say that with any confidence. There could be a good reason for the way they've done it (harling already mentioned one possible reason).

At any rate, I think the point is that there are a lot of really intelligent people that support Waze, and these people wish they could help Waze fix the things that they sometimes have to put off in favor of fixing more important things.

[WeeeZer14]

I just confirmed this a few minutes ago. Strange! As much as I tried I couldn't get the speed display to say 60 mph.