Losing faith in HR monitor for calories burnt
This morning I went a long bike ride (66.7 miles; 3h47m) and was looking forward to a nice big number of calories burned to eat into throughout the day. However, my Garmin gives me a pretty feeble 1678 calorie burn estimate. In contrast, Strava gives me a much more rewarding 2219 calories (so a 25% difference). The difference between the two is that Garmin uses HR data to estimate calories burnt, whilst Strava uses the elevation profile to estimate power required to maintain a given speed.
So why the difference? I suspect that because it was pretty cold (34F/1C), my HR was pretty low, thus the Garmin thinks I wasn't really exerting myself - but I was - honest!
I don't think it's just that Garmin's estimates are just lower. Normally I find Garmin and Strava estimates to be pretty similar. Furthermore, I looked at a similar ride in the summer (77F/25C)and calculated the calories per mile at 35, whilst today's was 25, despite being of similar topography and speed (today's was actually both more hilly and faster). My average HR for the warm ride was 158 whilst today it was 131.
So the question? Partly just sharing my wisdom - going out for runs in the cold might give you a lower calorie estimate than the 'true value'. Also, has anyone had similar problems? Should I just use the Strava estimate and not worry that I might be eating into my deficit for the day?
Potentially niche topic I know, apologies.