Erroneous summary stats with gpsmap 67i

Can't account for issues with the elevation profile. Typically, problems with distance are due to logging track points insufficiently frequently. You clearly spent a lot of time standing still. If you are using the default "smart" logging intervals, that might be part of the problem.

Do you have auto pause enabled? See Menu > Setup > Recording.

Judging from the screenshot and as twolpert notices, your moving time is only 58m47s from a total elapsed time of 3h49m07s, which could be explained when Auto Pause is enabled and your pace / speed is not fast enough for the GPSMAP to un-pause.

Thank you (as well as twolpert) for your feedback. Auto pause was disabled, but smart logging was enabled. Moreover, the device went into "Expedition Mode" several times, recording positions at 10 minute intervals. The elevation/distance graph looks okay however, as well as the activity shown on the map. So I don't understand why the total distance and total ascent can be wrong by such a margin. During the walk already, the total ascent didn't seem to advance normally, even though I think the altitude readings were correct.

I have converted the fit file to cvs using

https://gotoes.org/strava/convert_fit_files_to_csv.php

The recorded altitude is constant equal to 65535 throughout the activity. Is that normal ? Heart rate, cadence (no sensors) and speed are constant as well. On the device, altitude readings are correct.

You might also want to try https://www.fitfileviewer.com/ which lets you view the contents of the FIT file online. It could be that the tool you used converted the FIT file improperly. But 65535 for altitude does not seem like a correct value.

Thanks for pointing out that site, the FIT file is correctly decoded, including altitude and speed data. It shows that when in expedition mode, the device only records position data every 10 minutes (or until woken up). This is the expected behaviour but it seems that elevation gain during these periods is not taken into account for the total ascent. Deactivating expedition mode should solve the problem, but I still consider it a bug.

Don't know about "normal". But 65536 is one of those magic binary numbers. Probably means it was not recorded at all.

Correct.