@pond-ts/fit API Reference
    Preparing search index...

    Interface SwimData

    What a swim watch records beyond the streams.

    movingSeconds is the time spent swimming. When present (finite and above 0) the summary takes it as the activity's moving time, held to the elapsed time, without checking it further. Readers fill it with the summed timer time of the laps that covered distance (swimMovingSeconds), which leaves out the rests between sets; on 20 real FIT swims (pool and open water) that matched Strava's moving time to within a second. Working it out from the samples instead (as for a run or ride) comes out far too low on a pool swim, which logs one sample per length: a length timed together with its rest at the wall reads as too slow to be moving.

    Only the whole-activity moving time uses it: a lap, split or range() inside a swim still works its moving time out from the samples.

    interface SwimData {
        lengths?: SwimLength[];
        movingSeconds: number;
        pool?: { lengthMeters: number; unit: "m" | "yd" };
    }
    Index

    Properties

    lengths?: SwimLength[]
    movingSeconds: number
    pool?: { lengthMeters: number; unit: "m" | "yd" }

    Pool swims only (open water has neither).