This is probably not the first post about this issue.
When a running or walking activity is recorded with GPS, why is the data from the GPS not used to calculate the metrics like pace and distance? Even if we set the stride length to what is we usually have, we don't always run or walk with the same stride length. Especially for running, sometimes we run faster with naturally larger strides, sometimes slower with smaller strides, so why use strides at all?
For example today I went for a run with my Pixel Watch 4. GPS signal was good the whole way, the map after the run aligns well with the actual path that I took.
But after the run, Fitbit shows 4.6 KM ran. After syncing to Strava it showed 4.1 KM. Being curious I downloaded the TCX file from Fitbit, and indeed, the distance in the file is 4.1 KM for some reason. What's crazier is that I run this route often and I know that the route is 5.1 KM. Using advance mapping tools to check the distance, it's 5.1 KM.
Also another problem with this stride length based pace calculation is that when we check the watch for our pace, the natural swing of the arm is of course affected because we're trying to stabilize the arm so that we can read the watch. As a result, the calculated pace is even more inaccurate!
I understand that when there's no GPS, stride length is the only way to calculate distance and pace. But when GPS data is available, use it! It's way more accurate to use GPS data to do the calculation instead of using only stride length. GPS on modern wearables are good but the software Fitbit is not making good use of it.
This is the only reason why I still cannot see Fitbit as a serious competitor in the fitness space. The lifestyle tracking is good, but for a popular sport auch as running, it's not making any sensible decisions!
Best Answer