10-14-2016 17:42
10-14-2016 17:42
Since I've had my Blaze, I've used both the Fitbit exercise mode and RunKeper to track my runs. The Fitbit has been on average .06 miles off, but it ranges from .06 to a worst of .23 miles per mile tonight. I start, the exercise in Fitbit, see it connect to GPS, then start both it and Runkeeper simultaneously.
Here's where it gets weird. Looking between RunKeeper and Fitbit, the maps are nearly identical. Tonight's run, measured by both my car and mapmywalk show as 1.1 miles. Runkeeper shows 1.09 and Fitbit shows .86. Again, the maps between the two apps are identical, but it's like Fitbit calculates distance incorrectly or something. Is this common, or something I'm doing wrong?
08-31-2017 23:22
08-31-2017 23:22
I have to say that in the past few months the distance measured by my Blaze (with GPS connected with a Google Pixel) is very accurate. I compared it with several other solutions (applications and devices) and the difference is within 150-200 meters on a 15km run.