Is there an issue with cross-country skiing interval pace numbers? I have couple of examples, one originating from Garmin (5 km lap intervals) and one from Apple Watch (1 km lap intervals via Strava sync):
In Garmin activity pace is displayed as ~8:30/km but it should be a bit over 5:00/km (26 mins for 5 km interval). In AW data pace is shown as 10-11 /km where it should be a bit under 7:00/km. Is this a bug or is there something I’ve overlooked?
Also, Garmin activity is read in as backcountry ski and AW activity is Nordic ski.
I don’t follow. I verified the Garmin data and the first interval is 5k with elapsed time 26:19 (actual, wall clock time) so that would include pauses (and there weren’t any). If there would be excluded pauses, the pace should be faster, right?
Sorry, didn’t pay attention well enough. Something seems wrong there.
What if you make a selection containing the whole workout? I suppose that is equally faulty?
A selection containing the whole workout should give you the total workout time including pauses/stops and the pace/speed would be lower then what the summary on top is showing. That’s because the summary excludes pauses/stops.
Can’t see a logical explanation for this case. @david
I looked at the numbers and something came to my mind: incorrect units or unit conversions, almost as if there’s miles instead of kms somewhere…
So, for the whole ski trip intervals.icu gave a pace of 8:41/km. Actual numbers are elapsed time 1:35:15, distance 17.64 km → in decimals this is 5.3997 min/km.
When I convert 8:41 to decimals and divide by 1.609 I get 5.397 so we are pretty close. Could it be?
My daughter is the athlete here so she has relevant threshold paces defined but for CC skiing I think pace is not a good parameter for defining threshold.