Moving time and time_from_course

[xmedeko]

Garmin Connect is the most aggressive when calculating moving time, Strava is the most lenient ...

Can you explain it more in detail, what are differences in the moving time calculations? What about the field time_from_course - I think it should be used instead of the timestamp when presented, to calculate the the moving time.

And thanks for this analysis. FIT format suffer from lack of standardization of semantics, despite it's so widely used.

[mtraver]

What I meant is that it seems like Garmin Connect removes more samples than Strava when excising a stopped period. But I haven't compared record-by-record to see if this is the case.

Can you describe time_from_course, and/or provide a link to documentation? I see references to it in the Fit SDK but I can't find any documentation about what it means. The best I found is actually this SO answer written by you!

[xmedeko]

The problem with FIT is that the semantic rules of data is described nowhere. So, dealing with the pauses is really a black box. AFAIK time_from_course should be a net time for each record from a course start. That is, the time_from_course of the last record should be equal to the session total_moving_time. This knowledge is from my co-workers based on a reverse engineering of FITs from various devices. We do not have any doc for that, too.