Wrong total distance for activities longer than 167.76 km [Bug 10]

[javawa]

I agree. The eTrex may show the correct value after you correct it in the FIT file, the problem is though that the eTrex put the wrong value in the file at the first place. That needs to be corrected first.

[Przekątny]

But the distance recorded in the FIT file is incorrect, and this is the source the eTrex SE most likely uses and Connect for sure uses.

The source for the device is the distance value in TrackStatsExtension, if there is statistics in the file the recorded data is ignored.

[javawa]

No, it's not. TrackStatsExtension is a GPX element, the eTex SE stores activities in FIT files. While it can read GPX files, it will probably ignore all statistics fields.

[Przekątny]

ked.
When modifying data of the GPX file in Basecamp, .......

I do not modify the data in Base Camp.

The stats come from the fit file.

[javawa]

The stats come from the GPX file after Basecamp converted the FIT file to GPX. That's not the same.

[Przekątny]

Statistics are created by the device and saved in the fit file as well as in the gpx file.

Base Camp does not create statistics when saving to a file if the loaded file did not contain statistics.

[JungleJim]

Statistics are created by the device and saved in the fit file as well as in the gpx file.

Base Camp does not create statistics when saving to a file if the loaded file did not contain statistics.

Exactly, and after checking the provided FIT files it is clear that both the statistics in the FIT file and the distance recorded in each Record (= track point in the FIT file) are incorrect.

So any conversion between file formats or checks in Basecamp or modification of the files are irrelevant IMHO: the source of the data is incorrect regarding recorded distance.

[javawa]

Statistics in GPX files are only relevant when these files are created by the device. I haven't seen them in this topic.

[Przekątny]

Exactly, and after checking the provided FIT files it is clear that both the statistics in the FIT file and the distance recorded in each Record (= track point in the FIT file) are incorrect.

So any conversion between file formats or checks in Basecamp or modification of the files are irrelevant IMHO: the source of the data is incorrect regarding recorded distance.

Exactly, and after checking the provided FIT files it is clear that both the statistics in the FIT file and the distance recorded in each Record (= track point in the FIT file) are incorrect.

So any conversion between file formats or checks in Basecamp or modification of the files are irrelevant IMHO: the source of the data is incorrect regarding recorded distance.

You think that fitfileviewer.com explains everything, I disagree, so let's stick to our different opinions.

A similar issue as the distance in etrex Se was about ascents and descents, also statistics had priority over the actually recorded parameters of the hike.

[JungleJim]

Exactly, and after checking the provided FIT files it is clear that both the statistics in the FIT file and the distance recorded in each Record (= track point in the FIT file) are incorrect.

So any conversion between file formats or checks in Basecamp or modification of the files are irrelevant IMHO: the source of the data is incorrect regarding recorded distance.

You think that fitfileviewer.com explains everything, I disagree, so let's stick to our different opinions.

A similar issue as the distance in etrex Se was about ascents and descents, also statistics had priority over the actually recorded parameters of the hike.

I'm not really sure what you're trying to say here?

The FIT files the thread starter provided are the only actual source data created by his eTrex SE we have access to, as the provided GPX files are created by Garmin Connect and not from the device itself.

Based on the data inside the FIT file I explained and showed that the distance in the statistics data (in FIT format this is represented by the Session message) of the provided FIT files is incorrect (167km while it should be more). This can be seen by any tool that reads FIT files and shows the session data (instead of recalculating data based on the recorded track points). Even Basecamp shows this when you import the FIT file and show the track summary. And in addition to this, the total distance recorded in the track points (Record message in FIT file) at some time in the activity becomes fixed to 167km.

So I do not really see how that would make your case for stating that "In my opinion, the file 2024-09-14 08.32.29.fit distance is registered correctly (360 km),"?