I’m using AutoLap on my Garmin.
Data is coming From Garmin → Intervals (as well as Strava)
(Privacy circle shouldn’t be an issue since I’m connected w/ Garmin)
Some of my runs will have these odd 1meter or something like that laps within it.
Note: I’m on “use laps”…
Tx…
This is almost certainly related to the way Garmin devices treat lap times. Garmin devices truncate lap times and do not round. A lap ends and starts at a GPS point. If the last GPS point is eg at 20.9 sec, the end time of the lap becomes 20sec. If the next GPS point is at 22.1 sec, the next lap starts at 22 sec. Thus leaving one second as something that Intervals considers a 'in between ’ work laps and results as a recovery lap of one sec.
I guess there are not a whole lot of those, so best way to get rid of them is to edit the previous or next lap to end/start one second later/earlier.
Isn’t “use laps” means intervals will use the data from the lap records rather than calculate the laps from the raw data?
Output from FitFileViewer.com, all looks fine.
if you’re right about the truncation of time etc, essentially what I should be seeing as error / rounding errors would be the pace right?
When you do “use laps” Intervals.icu uses those to get the start time and duration of each interval. It still calculates everything from the raw data instead of using the summary info for each lap from the device. This is to support editing data on Intervals.icu and so on.
Intervals.icu also does start times, durations and so on in whole seconds so there could be some rounding issues. Maybe thats where that 1s recovery interval came from.
Tx. I see.
I guess there are way many more fields on each split than what is recorded by the device. Hence these situations you’re referring to calculate those fields.
A case of too many options. 
