GPS track is correct but total mileage and splits are wrong

[pksimmang]

I've been noticing an issue tracking runs with my Google Pixel Watch.  The map is correct but two different mileages are displayed and the splits are incorrect.  Specifics from this morning's run:

Pixel Watch:  5.57 miles, 1:01:29  (This is correct)

Android App - (v4.0.1, but same issue on previous versions): Right under the map it shows 1h 1m, 5.57 miles.  (This is correct)  But scrolling down to Pace Laps, it shows total distance of 4.8 miles-- that is, laps 1-4 are showing 1.00 mi and lap 5 is showing 0.80 miles.

Fitbit.com dashboard is showing 4.8 miles and pace of 12:48 (consistent with the Pace Laps data).

Clicking into the activity from the fitbit.com dashboards shows:

• 5.57 miles in the bar above the map
• 4.80 miles at the ending point on the map
• pace of 12:49, but with a significant blank space at the right of the graph
• Pace Laps matching the android app.

Further detail: 

• Activities are set to sync with Strava.  Strava initially shows the incorrect data (4.8 miles).  When using strava.com to "correct distance", distance is corrected to 5.57 miles.
• Activities also sync to Runkeeper.  RK shows the correct distance (5.57 miles) and the correctly calculated pace.  No correction is needed.

On fitbit.com, when mousing over the graphs from left to right, there are very definite jumps as the mileage marker on the map goes along the route.  This led me to examine the TCX file at those places.

• At each of these jumps, examining the Trackpoints, the coordinates (<LatitudeDegrees> and <LongitudeDegrees>) continue updating.  <AltitudeMeters> also continues to update (red arrows).  However, <DistanceMeters> (yellow highlight) remains stuck on the prior value, for example in one instance repeating "2181.02" for the next couple of minutes.
• One jump lasted right at 3 minutes, and another was slightly over 2.5 minutes.
• Checking the distance between 2 consecutive Trackpoints that had no increase in DistanceMeters, the distance calculated between the two sets of coordinates appears consistent with other points on the run.... i.e. the pace is steady at that point.

Based on this,

• it appears that randomly throughout the activity the <DistanceMeters> value just stops updating for a while.  I don't know if the watch or the android app is responsible for calculating that value.
• it appears that the GPS signal is solid, as the coordinates continue to update properly along with the altitude.
• Strava apparently uses the <DistanceMeters> value in the header, and runs the actual point-to-point calculations when the "Correct Distance" button is used.
• Runkeeper apparently calculates the distance on importing instead of using the <DistanceMeters> value.

Adding to the issue is the fact that Fitbit (neither app nor fitbit.com) does not offer the ability to correct distances/pace.  Fitbit also doesn't allow for importing activities from a file.  Activities tracked in Strava will sync to Fitbit, but without the map data.

A solution would be greatly appreciated.  Fitbit previously told me to update the app, which I did.  When that didn't work I decided to dig deeper.  I hope this information helps lead to a resolution.

[Triletics · Accepted solution]

@pksimmang the distance and duration data consistency was always off on the Fitbit platform between the app, web dashboard and TCX file. It's nothing new and considering no attempt to fix it for years (and even making it worse by the new app removing seconds from start time and duration (at least you can get it from TCX)) I don't expect it to be corrected. It's been ignored by Fitbit for years.

[pksimmang]

Thanks for the info.  The Pixel Watch is my first experience with the Fitbit ecosystem, but I had a lot of confidence based on the Fitbit users I know.  (Of course, few of them are runners...)  I guess my expectations were just unrealistic.  It's a shame really, since the data is there and it doesn't seem like it would be that hard to have the software recalculate the total.  I may get another Runkeeper or Strava paid plan instead of keeping the Fitbit paid plan since they'll give me better data... as long as Fitbit keeps pushing the activities out to them!

[Triletics]

@pksimmang as a runner, I can tell you one thing - Fitbit platform is not designed for runners 🤷 it's basic at best.