Huge stats distance difference
Distances travelled in stats seem way off from reality, and even contradict distances shown on the map :
Here for the month of July 21 the stats indicate 51459 kilometers, even though it says 439 kilometers when displaying the month on the map (which is the real distance).
It seems to occur for almost all months, as the stats indicate Ive travelled 932,854 kilometers which is way too much. I tried clearing inaccurate points and 0;0 points but it only dropped the total by about 50 000 kilometers.
Tried updating stats with the Update stats button but it did not change anything.
I have the same problem. It's suggesting that I traveled 1,500 km in the month of December 2024. In reality, I've walked about 82 km in the last 5 days according to my fitness tracker. And via metrorail I've traveled maybe 90 km (Dubai Internet City to Dubai Mall (35 km) and back and then to Mall of the Emirates twice).
I'm having these as well, but on closer inspection it turns out it's because of inaccurate and just plain wrong locations.
I'm spending time somewhere with no clear GPS signal. The phone uses the phone networks and wifi to guess its location. Every once in a while it sees a wifi network it recognizes like half a world away, and puts one point there. Next moment it realizes I'm back where I'm supposed to be. A few minutes later another point thousands of km away. Repeat this for a few hours, and suddenly I've travelled millions of km's that month.
I'm in the process of removing these points. I'm going through all of these obviously inaccurate travel distances and manually removing those points that cause the travel distance to balloon.
Same issue for me here Map shows 720km Stats show 721195.11km
I downloaded the points for that day and no point is really off so I dont think its inaccurate points.
I only have 4 days with this issue with location data from 2016-now (immich pictures), 11/2023-now Owntracks Android app.
0.21.0 introduces buttons to update year and month stats individually, you may want to try that and see if it helps
This should be resolved in 0.32.0