Zero celsius errors in Movescount-to-Strava temperature data

My activities recorded on Suunto temperature equipped devices have dozens of erroneous 0C/32F errors when synced to Strava. See attached images:

My guess is there's simply a null or missing value for temperature on certain data points in the sync, and somewhere along the line, Strava is juggling this to a zero, which is not great data handling practice. It's particularly irritating because Strava's infrastructure internally handles temps in celsius and 0C/32F is a pretty common value in winter (and late fall and early spring) activity in the mid-latitudes.

If Strava used Kelvin, juggling to zero would still be not great, but would at least make these erroneous values easy to identify and disregard.




Please sign in to leave a comment.

Didn't find what you were looking for?

New post