01-01-2020
18:52
- last edited on
09-28-2020
15:40
by
MatthewFitbit
01-01-2020
18:52
- last edited on
09-28-2020
15:40
by
MatthewFitbit
I run a regular route that I have tracked with a Samsung Gear S3 (GPS) and Strava app on my phone (also GPS). The run distance on both those devices is 4.46 to 4.47 kilometers.
When I use my Charge 3 to track a run (using my phones GPS) it comes out to 4.87 kilometers for the same run. This totally changes my pace times as it is a difference of 400 to 500 meters. (roughly 9 to 10%)
Is there something I am missing here? Both Strava and Fitbit are using my phones GPS and getting a 10% difference on the Fitbit. Any help/suggestions much appreciated.
Moderator edit: subject for clarity
01-02-2020 05:22
01-02-2020 05:22
Welcome to the Community, @GodfatherActual.
Thanks for the information provided. Fitbit devices calculate distance based on the device’s accelerometer data and stride length setting. Default stride length is based on your height and gender. If available, Fitbit devices use GPS data to calculate more precise distances. When you sync your device, our algorithm interprets the data from the device, and the you see your distance traveled in the Fitbit app.
Note that when your track an exercise with GPS, both GPS and accelerometer data are used to calculate the distance shown in the Fitbit app. For more information, I recommend taking a look at the help article: How accurate are Fitbit devices?.
Let me know the outcome. 🙂
01-10-2020 17:41
01-10-2020 17:41
Stride Length set....GPS on. Grossly inaccurate distance.
Did a 2.7k loop walk and Fitbit came up with 1.97k
GPS data on Strava counted 2.66k. Confirmed on Google maps it is 2.7k
This is completely useless as a fitness tracker.