Incorrect mileage/ETA when adding a stop

[AggieJM]

I was on a long trip on Sunday and I added a stop along the route. The first time I added the stop, the distance to the stop was shown incorrectly. It also zoomed the map out to maximum distance and would not put the focus back on my position.




After I removed the stop and tried again, the mileage and ETA were correct initially. But as I neared the stop, the mileage was off as shown in the next screen cap. At that point, my stop was at the exit 8 miles ahead, but it showed 19 miles at 8 mins.

[AggieJM]

Just to make sure - you are aware that the top nav bar is the distance to the next turn and the bottom ETA ticker is the total distance, right?

Understood. I was heading north on I-45 and my final destination was about 200 miles up the road. The stop I added was for a gas station right off the side of the interstate.

In the first screenshot, it shows that I have 64 miles till the exit in the top bar. The bottom bar shows 57mins to the stop, but only 0.3 miles. This is also where it would not zoom back in no matter where I touched on the screen. I finally had to remove the stop to get the display to show correctly, then add the stop again.

In the second screenshot as I was getting closer to the destination, the top bar shows I have 8.8 miles till the exit, which corresponds to the 8 mins to destination. But the bottom mileage shows 19 miles, which was not correct. To reach the stop, it was just exit in 8.8 miles and turn right into the parking lot. At that point, 19 miles was not the correct distance to either my stop or my destination.

[perlin]

Just to make sure - you are aware that the top nav bar is the distance to the next turn and the bottom ETA ticker is the total distance, right?

[Twister_UK]

Been seeing similar behaviour for the past few weeks when planning a new route with no intermediate stops. These screengrabs were taken earlier today:




On the initial screen, the mileage is completely wrong - it's neither the total route distance nor the distance to the next junction of interest. After accepting the route, the correct mileage is then shown at the bottom of the screen.

However, in both cases, the ETA is also way off...



The alternate route screen shows that the three route options are all free of traffic, yet the ETAs for all three seem to have been calculated using a lower average speed than used to be the case - I've done this journey countless times since joining Waze, and it always used to be pretty close to reality no matter what the traffic conditions were, yet these past few weeks it's been consistently over-estimating the ETA by about half an hour. These grabs were taken on my Android client, but my wife's iPhone client was also showing the same values, so it's not client-specific.

[Twister_UK]

Interesting, both mine and my wife's clients have just had a sudden drop in ETA, the tone shown in the above screengrab is about what I'd expect to see, given that in the time between taking the previous grabs and this one, we stopped for fuel which added about 10 minutes to the journey time...