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

[Przekątny]

So it is not a problem with calculating distances .
The problem is the entry in statistics.

Statistics is a feature for *.FIT files only.

Statistics are not the domain of fit files only,
statistics are also saved by the device in gpx files, if the device allows saving in gpx files.

Statistics are created in the device, Base Camp is the only program I know of that reads statistics contained in a gpx file, other programs and applications ignore the statistics records.

[javawa]

Not only BaseCamp, Connect uses the statistics too.

I see 176.76 km in eTrex and in Garmin Connect too.

[Przekątny]

What file format was sent to Garmin Connect, gpx file or fit file, I wrote about statistics in gpx file.

[JungleJim]

What file format was sent to Garmin Connect, gpx file or fit file, I wrote about statistics in gpx file.

For devices that write recorded activities as FIT files (like the eTrex SE), the FIT file is uploaded to Connect.

[Przekątny]

For devices that write recorded activities as FIT files (like the eTrex SE), the FIT file is uploaded to Connect.

I think you can also add an activity to Garmin Connect manually, which is why I asked about the format,
I did not associate the activity with any device.

One of my devices has three options for recording activities,
fit file + statistics, gpx file + statistics and gpx file without statistics.

Newer devices do not have the option of recording activities without statistics,
which is why it is more difficult for the user to draw appropriate conclusions related to the topic of statistics.

[gps_techie]

So it is not a problem with calculating distances :D .
The problem is the entry in statistics.

IMO original problem is in calculating original distance data record, which then propagates to statistics view.

*.FIT data record contains info like timestamp/lat/long/distance where distance goes 0, 0.24, 0.78, ..., 167743.86, 167766.73, 167766.73, ... (limited to 167766.73 in this case) meters. Graphical view of distance accumulation:

Limited distance at 167.77km

limited distance, 167772m.png

*.FIT file also contains session or lap statistics where total_distance is the same incorrect 167766.73 meters.

Whether or not total_distance is recalculated incorrectly or takes max/last value from incorrect distance date record is of secondary concern. Primary concern is incorrect distance data record.

[JungleJim]

I think you can also add an activity to Garmin Connect manually, which is why I asked about the format,
I did not associate the activity with any device.

One of my devices has three options for recording activities,
fit file + statistics, gpx file + statistics and gpx file without statistics.

Newer devices do not have the option of recording activities without statistics,
which is why it is more difficult for the user to draw appropriate conclusions related to the topic of statistics.

You sure can add activities manually to Connect, in FIT, GPX or TCX format.

You're right that we don't know how Sibstr uploaded his activities to Connect. I assumed via Express or Connect mobile app (which I think would result in a FIT file because the eTrex SE doesn't seem to support saving activities as GPX file), but he may have done it manually. So I hope he still reads this topic and can provide us with the answer!

[javawa]

One of my devices has three options for recording activities,
fit file + statistics, gpx file + statistics and gpx file without statistics.

What device is that?

[Przekątny]

Oregon 650t has such a possibility.

[Przekątny]

*.FIT file also contains session or lap statistics where total_distance is the same incorrect 167766.73 meters.

The limitation to 167 km has no logical justification, in the activity 2024-09-14 08.32.29.fit 167 kilometer falls on the 4478th track point.
From the information provided so far it is not possible to draw a conclusion as to why there is a limitation, if the activity is saved until the memory is full.