Wednesday, February 15, 2017

A quick comparison of Runkeeper and Polar A360 data

I've recently done a bit of interval training/walking again, and I've remembered to set Runkeeper going to record my efforts. I also have my trusty Polar A360 activity monitor strapped to my wrist. Perhaps I should have stuck my old pedometer in my pocket too, just for completeness!

Anyway, I thought it would be interesting to compare the data from both the A360 and Runkeeper. Here's the raw data:

The top screenshot is from Runkeeper, the lower one from the A360. There's clearly a discrepancy between the two, but there's also an obvious explanation. Runkeeper uses the GPS facility in my iPhone to map the route, the A360 does not have GPS capability. Consequently it has to use some form of algorithm to calculate distance which in turn impacts the calorie estimate and pace data too.

The point is simple. If you're going to buy an activity monitor then make sure you get something that suits the main type of exercise you do. If you're a runner or walker, then you really ought to consider something that has GPS if accurate distance is important. If like me, most of your activity takes place in a confined space like a tennis court, then GPS is irrelevant. I don't do enough running/walking to warrant a GPS enabled watch. It's all possible that if I activated the app on my phone form Polar (Polar Beat) it might se the GPS and compensate for the difference. I don't know, but it might be worth investigating. 

Activity monitors are simply that-monitors of activity. Some allow you to set the type of activity, the A360 has various sport/training modes that you can set, but generally speaking it's all about trends and making sure you get up and active on a daily basis. My Polar Flow did that and the A360 just gives me a bit more flexibility and a little more data (heart rate mostly).

Anyway, I just thought it was interesting to see the difference and be reminded that nothing is perfect and the data out is only every going to be as good as the data in.

No comments: