2.5 km and 4 km/h in 11 minutes!!!!

[islupepa]

As I have been saying in other threads, Waze is underestimating time in traffic jams a lot!!!
Because of this, Waze fools you to drive straight into traffic jams!!!
And yes there were alot of opurtunities for waze to choose other routes where it would take half the time to get home!!

[dmcconachie]

Are there many wazers in your area? It can't do much without info from other drivers

via Tapatalk

[islupepa]

Are there many wazers in your area? It can't do much without info from other drivers

Around 2100 according to the waze function "near you now"!
It was nicely marked in red and 4 km/h on the map!
Many wazers nearby!!

[jasonh300]

Are there many wazers in your area? It can't do much without info from other drivers

Around 2100 according to the waze function "near you now"!
It was nicely marked in red and 4 km/h on the map!
Many wazers nearby!!

Did you drive it? How long did it actually take? I've always found the time to be pretty close.

[islupepa]

Are there many wazers in your area? It can't do much without info from other drivers

Around 2100 according to the waze function "near you now"!
It was nicely marked in red and 4 km/h on the map!
Many wazers nearby!!

Did you drive it? How long did it actually take? I've always found the time to be pretty close.

Don't know exactly how long time it took, but the whole route took 50 minutes (5.3 km)!! I guess that this part of the route took 30-35 minutes (far from 11 minutes).

[jasonh300]

Did you drive it? How long did it actually take? I've always found the time to be pretty close.

Don't know exactly how long time it took, but the whole route took 50 minutes (5.3 km)!! I guess that this part of the route took 30-35 minutes (far from 11 minutes).

So you probably did average about 4 km/h.

They fixed this in the U.S. a while back after I noticed that the math was wrong between the reported speed and the distance.

There are other places in the app where the erroneous Waze conversion between feet and meters is to leave the number the same and change the word "meters" to "feet", which obviously doesn't work. I wonder if there's some kind of error in the metric formula to compute how long it takes based on km/h rather than MPH. 4 MPH is around 7 km/h, but that still doesn't add up.

[islupepa]

They fixed this in the U.S. a while back after I noticed that the math was wrong between the reported speed and the distance.

There are other places in the app where the erroneous Waze conversion between feet and meters is to leave the number the same and change the word "meters" to "feet", which obviously doesn't work. I wonder if there's some kind of error in the metric formula to compute how long it takes based on km/h rather than MPH. 4 MPH is around 7 km/h, but that still doesn't add up.

Must be something like this! The math is completely wrong!!
Normaly you won't see a thing like this but when the traffic jam envolve a long part of the route it estimated time gets completely wrong!
During the time in traffic jam I tried to make waze avoid this route and I inserted start point, end point and intermediate point and I could avoid the traffic jam. This route would have taken me 21 minutes instead of 50 min!!!!

[islupepa]

Think the problem is even worse!
Waze doesn't consider the traffic jams at all!
I saw a traffic jam, 2 km long, and 14 km/h, today and waze estimated the time to 1 minute!!!!
The traffic jam didn't even show up in the route preview, but it was on the map allright!