Moving time display issue on Strava after a FIT import

[payenm]

Hello,

We are facing an issue with an activity display on Strava.

The activity was sent to Strava from a FIT file

Strava activity link: https://www.strava.com/activities/11210358816

FIT file: activity.fit 

I know that Strava have specific calculation rules in order to evaluate the activity moving time.

But in our case, we do not understand why there is a so big difference between the values from the Fit and the value calculated by Strava  

• Decathlon’s activity duration: 1716s
• Time declared in the FIT file: 1716s

• Moving time displayed by Strava after import: 2:30.
• Decathlon’s activity distance: 1401m
• Distance declared in the FIT file: 1401m
• Moving distance displayed by Strava after import: 0.2

The activity records are correctly filled in the Fit file.

The timestamps are correct, the positions seems correct, and the speed is set.

(We have some speeds that have the value 0 but even if its are not taken into account in the calculation, the total do not match).

Could you please check what calculation was made for this activity and why we obtained this values?

Note:

I tried to import manually the same file in Garmin interface: and the displayed result was correct for them.

Very thanks

[Jan_Mantau · Accepted solution]

Strava calculates the distance and moving time with gps points. The fit file seems to have too few of them.

[payenm]

Thanks for your quick replay.

Is there any information about how many points are mandatory for Strava for a given time period?
And do you know what fields are mandatory for a point (in order to be taken into account by Strava calculation)?

I can see that there is a page on strava documentation about the moving time and distance calculations, but the details about the Stava calculation is not given.

Also, the FIT file specifications do not mention any specific amount of points that are mandatory.
Strava defined is own rules on that topic and it is not really documented.