Hi all! In the following table the first lap lasts 14,7 sec. and the distance is 50m, the pace should be 4:54, why GARMIN calculation is 5:15?
I have thought that in GARMIN CONNECT the distance 50m is "approximated", a bit different from the reality. In fact, if it was 46 meters the pace is right 5:15.
If this is correct, it means that GARMIN approximates 46m to 50m. What do you think?
Thanks!
Thanks, I opened the .fit file with fitfileviewer.com, and I get the below result. I am not able to find the average pace. Could you tell me where this data is located? Thanks
it's not possible to set 50 meters run, just 400m as standard. Is this true?
I do not quite understand what you exactly mean by "set 50 meters run". If you mean to record a run that is 50m long, then you can certainly do it. You can even record just a 1m long run (though it will be rather challenging 
). If you mean changing the track length at the Track Run activity, then it can be indeed only 400m. However, you can still change the auto-lap length to a short distance. The exact minimal distance may differ from model to model, but in my case (Instinct 3), the minimal auto-lap distance is 20m. And, of course, you can set manual laps for as short distances as you want.
TL;DR the original recorded activity data has activity and lap distances to the nearest 0.01 m.
You are correct that the lap pace you see in Connect is based on a more precise distance than what's normally shown. (What's normally shown is distance to the nearest 0.01 km = 10 m).
But if your activity type is Track Running, Connect *should* show lap distances to the nearest metre. The website will show activity distance to the nearest metre, but the app will show 2 decimals (for some reason).
I am not able to find the average pace. Could you tell me where this data is located? Thanks
I was actually suggesting using fitfileviewer to determine the exact recorded *distance* for each lap, to see that they're not exactly 50-60 metres, as per your original question.
It might be much easier to simply change the type of the activity to Track Running in Connect, which should change the display so that you see distances to the nearest metre.
Click on the activity type in the top-left corner:
But it does sound like you're already using track run mode? If so, it's strange that it's not showing distances in metres for you.
Here's an example where I changed a (somewhat) steady state run with some strides at the end to Track Running:
You can see that:
- distances are displayed in metres
- The data for the 1st stride is displayed as 94 m, 19.2 seconds, with an average pace of 3:24.
19.2 s / 0.094 km = ~204.255 s / km = ~3:24 min:secs / km
The average pace indeed roughly matches the more precise distance of 94 m.
If I switch back to Running, the distance will be shown as 0.09 km, which ofc would not produce an average pace of 3:24.
19.2 / 0.09 km = ~213.33 = 3:33 min:secs / km
If look in fitfileviewer, I can see that the lap distance was actually recorded with an even greater precision: 94.29m
I can also see that while there are columns (field definitions) for session/lap average speed and session/lap max speed, these are not populated for my device (FR955). This is because Connect typically calculates average speed/pace and max speed/pace for a lap/activity from the data (based on the recorded time and distance). (If you edit your activity distance, you will see the average pace change.)
Speaking of the Session table (which has activity summary data), you can also see that your run distance is recorded there, to the nearest 0.01 metre:
