Forum menu
Just back from a quick "out and back" ride with Endomondo tracking. The return leg is exactly the same as the outward leg, except in reverse. Endo stats:
OUT:
Average Speed: 23.4 mph
Calories: 638 kcal
Distance: 13.00 miles
Duration: 33m:17s
BACK:
Average Speed: 17.4 mph
Calories: 576 kcal
Distance: 11.74 miles
Duration: 40m:25s
That's a discrepancy of 1.26 miles! Does anyone else see the same kind of variability? Is it the software or is it the GPS receiver on the phone (Desire S)? Is Endo Pro any more accurate/consistent?
mine was 1.5 miles out over 18 miles last week
were you under trees, by tall buildings? Oddest thing i found was the altitude was wrong and when physically stopped there were times when endomondo had me wandering about.
Did 114 mph on one of my rides, so pretty accurate IMHO
Route does pass under trees, but it's the same trees on the way out as on the way back. I'm guessing the phone GPS is a bit pish...
It is down to the algorithms used to calculate the distances...
it may sound odd at first, but depending on where the trees are in relation to you and the satellites, the trees can make a difference depending on which direction you are going on the same road.
Anyone know how the calories are calculated - is it real ballpark stuff or is there some level of sophistication? Like does it take climbing into account?
The route maps seem to show very infrequent sampling - I assume the algorithms do some kind of interpolation to determine the "actual" distance travelled rather than a simple cumulative straight-line distance between sample points.
Have a look at this map to see what I mean (zoom in to street level to see the "cutting corners" effect:
http://www.endomondo.com/workouts/kJFZoHOn7cg
It consistently gives me 13.1km around Cwmcarn. Although I have noticed its not very good with altitude where I live - but thats the GPS receiver itself not endomondo.
Not sure how the calories are worked out GL, but I'm guessing it's a crude estimate which will factor in distance, altitude, rider weight but leaves out other factors like heart-rate, bike + kit weight etc.
It consistently gives me 13.1km around Cwmcarn. Although I have noticed its not very good with altitude where I live - but thats the GPS receiver itself not endomondo.
which is why I wished they would include elevation correction, which motionbased (now garmin connect) does. think it uses googles terrain mapping which is pretty spot on.