Endomondo Lied To Me
A week ago I re-started my diet and exercise plan. Since I am grossly overweight, the exercise plan is basically "walk around 5km every day, fat guy". Since I am a nerd, I wanted data so I could stop lying to myself about how much I was walking.
I had seen Endomondo mentioned in my tweeter timeline a bunch of times and the featureset looked pretty much exactly as I needed:
Track my walking
Keep history
Show it in google maps (because it's nice)
It even did things like tracking calories burnt and so on.
The only problem was... it really sucks at figuring out how much you walked. It consistently overestimates by around 50% the distances, and since it calculates the average speed based on time and distance (and the time measurement is correct) it overestimates speed by 50%, which then means it overestimates calories burnt by (I am guessing) 125%.
How did I verify that Endomondo is wrong, and avoid the obvious explanation of "your GPS is broken"?
I tracked myself using Endomondo and Google Trails at the same time.
I counted steps roman-mile style (count every "left-right", multiply by 1.6)
I measured the path I walked in Google Maps and Bing Maps
All those measurements tell me a walk of 1100m +/- 150m is measured by Endomondo as 1.68 km
Ver mapa más grande
Why does this happen? I could assume Endomondo is just crap, and probably be right, but trying to come up with a "interesting" explanation, I am leaning towards noisy measurements. For example, if Endomondo saw my position shifting randomly 10 or 15 meters left or right it would probably add enough noise to make the path 50% longer (for a much more fun example of this, read this paper (by no other than Benoit Mandelbrot!) but this doesn't explain why Google Trails works so much better (unless Trails does something smart with antialiasing and interpolation).
If you use Endomondo, care to share your experience? I am reluctant to 1-star it in Google Play without independent confirmation.
I've been using Endomondo to track my running sessions for (I think) more than a year, and I'm not seeing this behaviour. I always run more or less the same "circuits", and I have tracked those circuits with other tools (My Tracks, Sports Tracker) in the past, or have measured them in Google Maps, so I know Endomondo has not been that wrong. Endomondo estimates also match the length of some "well known" circuits (f.i., the Reserva Ecológica Costanera Sur in Buenos Aires has a bunch of different paths, and the lengths of those are documented elsewhere). Also, I have used Endomondo to track some street races in which I have participated, and the distance reported by the app was consistent with the distance of the circuit prepared by the organizers of those races.
So... Endomondo never lied to me, at least not in such a noticeable way ;-)
One interesting difference between our use cases is that you used the app to track walking, while I have been using it to track running.
I've been using CardioTrainer for a while. It has all the features you mentioned and I can tell, It works just fine!
This could just be a units issue: 1.1 miles is close to 1.68km. It's perfectly possible that the code got a unit conversion wrong, and multiplied from miles to km when it shouldn't.
Run another test, and if the error is always a factor of ~ 1.6x, then the most likely explanation is this.
"Google Trails" == "Google Tracks"? Vengo usando el segundo para caminatas, bicicleteadas y patinadas, y la verdad que está muy bueno.
Podés subir los tracks a Google Drive y guardarlos para la posteridad, para cuando les contemos a nuestros nietos que antes podiamos caminar 5km =)
Siempre me quedó la duda si la velocidad que mide es real. Tendría que compararlo contra un Garmin a ver cuanto delta hay.