Corrupt FIT File Repair Requests

My FR620 stopped counting distance at 3.93km into a run that was approx 6.3km long. When I open the file in Garmin Connect the GPS track seems to be there, but the distance is wrong. Is there something wrong with this file that can be fixed?
Thanks,
Adam

Hey Don,

I lost an epic ride today.. Was able to recover it using a recovery tool, but to no avail. I read that you haven't had luck fixing any of those files, but I figured I'd let you give it a shot if you don't mind!

Thanks!

Hi
I ran the MCM last Sunday and upon upload to Garmin Connect & Strava I see that the track is odd, so I am turning to this forum to see if there potentially is a solution?

I noticed a km-split during the race that was very quick and then one very slow at about the location where the track "breaks" but I continued to get km-splits that made sense thereafter so I thought it was just "spikes" and ran on.
Then later in the race a "low batt" warning was given (2x) and a little thereafter the GPS track picks up again?

I got a relevant distance from the watch in the race so I hope the real GPS locations are there, just "slightly" corrupted? Also the watch stated a 19% battery when i put it for charge, so I hope the "low batt" warning was not disruptive?

I tried some online tools for fixing the .fit file but am not familiar enough with the topic to assess what is good/bad data.

Is anyone able to make sense of this .fit file? The real track should show that I ran on The Mall as well as through Crystal City.
rgds
/Jacob

Hello Adam,

The first 5 laps your 620 was recording at 6-7 second intervals which is fine. Then halfway thru lap6 it started using 20+sec then 30+ then by lap9 it was using 40+sec. Finally after recording the very first point of lap10 it abruptly stopped recording completely. That is the end of the data.

So....here ya go. Fixed the first 9 laps with the Fit File Repair Tool.

Hello Jacob,

At 16mi your 620 started losing satellite lock and then for some strange reason it started recording the exact same coord. That continued for 9+mi then suddenly it started recording actual coords for the last mile to the finish but they were way off.

I pulled a 10mi section of data from another runner going approx the same speed as you, corrected the time of day to fit your time and substituted the coordinates into your file. The repaired file has all your original data, speed, cadence, etc but the last 10 miles of coordinates have been replaced.

So....here ya go. Fixed with the Fit File Repair Tool.