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

[Przekątny]

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

Now I found a file from Oregon 700, which had correct statistics records in fit files, the distance after loading the file in Base Camp statistics, is 3178 km, after saving in statistics it is <gpxtrkx:Distance>3178169.5</gpxtrkx:Distance>
If the receiver creates correct statistics records, then the statistics are correct after saving to the gpx file.

[Przekątny]

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),"?

Don't you know Base Camp loads directly the data in fit files, gpx files created by garmin connect do not contain statistics so how could I refer to the records in statistics.
I was looking at the fit files from the device.
Base Camp does not create statistics by itself when writing to the file.
What the apps show is a matter of discretion .

[JungleJim]

Don't you know Base Camp loads directly the data in fit files, gpx files created by garmin connect do not contain statistics so how could I refer to the records in statistics.
I was looking at the fit files from the device.
Base Camp does not create statistics by itself when writing to the file.
What the apps show is a matter of discretion .

Yes I know Basecamp can read FIT files, I even refer to this in my post. And nowhere in the part you quoted do I state that the GPX files created by Connect contain statistics, so please don't put words in my mouth.

Can you show a screenshot of Basecamp where the correct distance (360km) is shown instead of the incorrect (168km, rounded to kms) for the FIT file 2024-09-14 08.32.29.fit? Because I'm not seeing it. But maybe I'm looking in a different place than you are.

Basecamp FIT track summary for 2024-09-14 08.32.29.fit

Screenshot 2025-01-01 at 20.54.50.png

[Przekątny]

I even refer to this in my post. And nowhere in the part you quoted do I state that the GPX files created by Connect contain statistics, so please don't put words in my mouth.

I'm not trying to convince you that you wrote that there are statistics in the Garmin Connect files, I'm just stating the fact that there are no statistics in these files.

Edit:
There are a few ways to check your Base Camp distance, you can go to the graph screen, mark your start and end point, the distance can be read at the bottom of the screen.

[gps_techie]

I checked contents of provided *.FIT files (from Sibstr post). Route data indeed looks normal with much longer than >167km actual distance, but for some reason distance accumulation is capped at ~167 km (167768.33 meters for files 1 & 2 and 167766.73 for file 3). These distances are very close (slightly smaller) than 2^24/100 = 167772.16, that's very suspicious.
Wrong distances are both in a .FIT summary data and in raw record data, thus it's showed everywhere wrong (on eTrex SE or any programs that can open *.FIT files).

Sibstr eTrex SE had SW version 4.20. I used 3.10 version for longer trips (>1400 km), but the distances were accumulated and showed properly for me. I will have to check if I have long trips with 4.20 recorded.

The only few things I see different are a) minor setup difference (Czech vs English, metric vs statute), b) sport set as driving vs hiking. These things are very minor and should not affect calculations, but that is worth checking just to be sure.


*** HTML Link formatting updated to comply with forum posting guidelines ***

[gps_techie]

Found some long activities in *.FIT format where distance is capped at 167772.16 meters exactly (=2^24/100). Recorded in hiking (each second) mode with eTrex SE software version 4.20 (the newest at the time) and hardware version 2.55.

This strongly suggests a bug with distance calculation in eTrex SE SW 4.20

[JungleJim]

Thanks for another confirmation of our suspicions, gps_techie!

[Przekątny]

Recorded in hiking (each second) mode with eTrex SE.......

You can enter information about the time of the hike.

If you remember, whether the indicated time corresponds to the actual duration of the hike.

Whether the number of recorded points corresponds to the time of the hike, taking into account the set interval.

This strongly suggests a bug with distance calculation in eTrex SE SW 4.20

To check whether Etrex Se has a problem with calculating the distance, you can load the fit file to Base Camp, then save it to a gpx file, edit the file by removing TrackStatsExtension and re-upload it to the device.

The new data will be devoid of statistics, maybe Etrex Se will calculate the distance correctly.

[gps_techie]

To check whether Etrex Se has a problem with calculating the distance, you can load the fit file to Base Camp, then save it to a gpx file, edit the file by removing TrackStatsExtension and re-upload it to the device.

The new data will be devoid of statistics, maybe Etrex Se will calculate the distance correctly.

This is one way to check this, but I didn't want to modify original *.FIT files. Other reason is that both detailed distance (recalculated each second) and summary statistics distance showed the same value (167km) in original *.FIT file with SW 4.20. Maybe summary statistics takes max (or last) value from detailed distance record, I am not concerned how that works.

The easiest test would be to take eTrex SE (with SW 4.20) on a trip at least 170 km long and see the results in real time.

IMO distance is calculated correctly in eTrex SE (as visible by some >2000km distance estimate to the trip start location form current location). Problem is with distance record number formating.

[gps_techie]

If I import *.GPX file to GPX folder via PC to eTrex SE, it is visible though eTrex SE GPX routes catalog. eTrex SE then shows correct distance for *.GPX (in this case ~3400km), but no other statistics. Statistics is a feature for *.FIT files only.