info.timerTime and info.elapsedDistance

I have a question about reliability of info.elapsedDistance in the simulator (or FIT-file). If I, at the same call to compute in a simple data field,store both info.timerTime and info.elapsedDistance and then later do the same and use those to calculate speed ( d2 - d1 ) / ( ( t2 - t1 ) / 1000 ) I get a speed that is much faster then the average speed (info.currentSpeed) during the same period.

Do I miss something obviously or misinterpret the time/distance properties of the info class?

What I want to do in the end is to show the pace over the last, rolling, km/mile which will require an array of time and distance readings large enough to get t1, d1 and t2, d2 where the distance difference is at least 1000 meters or 1609.344 meters.

Using SDK 3.1.4-2019-09-17

Best regards,
Tobias

TobiasLj over 5 years ago

No one that has any input?

As a not I exported the fit file to CSV (FIT SDK) and if I use the time and distance info recorded every second I get a reasonable speed (and pace) but I can't find any relationship between distance in the FIT-file and elapsedDistance in the simulator.

Best regards,
Tobias

GHG23 over 5 years ago

Average speed isn't represented by info.currentSpeed; check the SDK docs. In my Datarun premium datafield I use an array to enable users to have a rolling pace up to 300 seconds, but for last lap pace I just catch distance and time at the moment a lap ends. That is enough to have last lap pace, be it in miles or km

TobiasLj over 5 years ago in reply to GHG23

Thanks for your reply GHG23. I realize that I wasn't clear in my questions. I know that currentSpeed isn't an average but if I store currentSpeed during one minute in an array and calculate an average that will give me a reasonable average.

If I store time and distance and then do the same about one minute later and use those to get the average speed that will give me different (much faster) average.

I now know that elapsedDistance is wrong in the simulator. I I replay a FIT file of a 10k run the elapsedDistance in the end will be about 12.5k.