Inconsistent data between overview and runalyze calculated data

[Finaleris]

Hello,

My running activities are imported from Strava automatically. The data for runalyze overview is pulled directly from Strava: distance, time, elapsed time, pace. I like that, because Strava seems to calculates the differences between time and elapsed time well, for example if you need to pause to pick up a headphone, tie a lace etc. However the other data runalyze calculates does not match up to this, laps, best segments etc.

Going forward I wonder if it would be better for runalyze to calculate the overview data, or for the other data calculated by runalyze to match the overview data from Strava?

Perhaps this has already been discussed somewhere?

[mipapo]

Not quite sure what you mean. We take the data as we get it from Strava via the API. We recommend not to use Strava if possible, because Strava may not provide the complete data and we may not get the details of the activities as it is in the case of direct connections to the individual manufacturers.

Best hint we can give: Try to avoid Strava if possible

[bbh]

same issue, but I get the data through Polar. Strava gets the same data, and subtracts from the total time (verstrichene Zeit in German) the pausing time. Therefore, the calculated velocity neglects the pause. Is this possible in Runalyze, too?

[mipapo]

same issue, but I get the data through Polar. Strava gets the same data, and subtracts from the total time (verstrichene Zeit in German) the pausing time. Therefore, the calculated velocity neglects the pause. Is this possible in Runalyze, too?

For Polar: Switch sync file format: https://runalyze.com/connect/polar/settings
By default we are using the tcx, because there are some minor problem with the fit in combination with Runalyze (don't remember what is was)