I'm having trouble with this fit file. It's exported from Garmin Connect. It looks fine in Connect (25km run on 12 Feb). When I upload it to Strava, the route looks fine and the per-km data sees all 25km, but the summary of it is a 23.3km run on 7 Feb. Anyone able to help?
Was trying to be concise, but I guess it makes sense to clarify, the file was initially much more corrupt, including on Garmin Connect, after uploading from my ForeRunner. FitFileTools fixed some of the problems but there still seem to be these issues with the summary data.
Strava uses there own algorithm's to compute distance. Thus they will usually have a small difference between what Garmin shows and what they show.
If there was some corruption and some of the intermediate data points are missing then is it very possible for Strava to "clip" some corners, for example, in figuring distance and come up with something completely different.
Ah, thanks, that makes sense. I'd assumed the distance value was hardcoded (because it's not consistent with the splits), but given what you say I guess there's no fixing it.
Do you know if there's any way to fix the date? Seems like there's still a 7 Feb lurking somewhere that could be corrected to 12 Feb?
Ah, thanks, that makes sense. I'd assumed the distance value was hardcoded (because it's not consistent with the splits), but given what you say I guess there's no fixing it.
Do you know if there's any way to fix the date? Seems like there's still a 7 Feb lurking somewhere that could be corrected to 12 Feb?
hi Jhkelly,
The reason for your distance discrepancy is that your watch didn't get a solid GPS lock until 7min38secs into your run (or approx 0.84miles/1.36km as recorded by your SDM4).
I would hazard a guess that Garmin Connect displays the correct distance is because it is looking at the distance value as recorded by your SDM4 - Strava is most likely looking only at the recorded GPS distance.
Give this file a try - it should now show the correct distance and the correct date.
