.. the resampling code caused issues (not 100% sure why) so
reimplemented using the resampling method from Txt file
processing (also for Computrainers).
.. we know that approach is accurate since it accumulates
work and resamples to 1s intervals precisely.
.. two regression impacts; we no longer import the virtual
altitude and sample rate is 1s not 250ms.
Samples of swimming type are used to update distance and speed
of periodic samples, cadence is computed counting Stroke events.
Includes test file contributed by Serban Mestecaneanu
It generates both record and length messages for
each length, we use length messages to recognize
lap swimming and filter out record messages.
Includes test file contributed by Jonathan Beverley
.. caused v3.2 to crash on interval discovery and
contains out of bound values for power, speed and
cadence.
.. good for testing code doesn't make assumptions about
data values.
.. thanks to Neil Jones for the test file and permission
to distribute for testing
Based on TCX/GPX support
Includes laps and no-gps support for indoor activities, but not lap swimming.
Test files were contributed by forum members Frederic and Servan
Fixes#1559
Smart recording interpolation fills the gaps in pwx files present
when the original .fit or .tcx files had them.
Test files for running: 1 activity in .fit, .tcx and .pwx formats
Lap swimming expands the sample-per-length and pause to 1-sec sampling.
Test files for lap swimming: 2 activities in .pwx format,
one from Garmin 910xt other from Finis SwimSense.
When Sport="Other", there is no GPS data but there is distance information
it is assumed the file cames from lap swimming.
They have one Trackpoint per length, which are expanded to one point per second
in similar way to Smart Recording and laps without Trackpoints to signal pauses
which are expanded to one point per second up to 10x Smart Recording HWM.
Added contributed Garmin FR910xt pool swim file to test/rides folder
.. add some sample files with calibration messages to the
test/rides directory
.. remove the calibration marker color config (we can add it
back if needed, but was in the wrong 'sequence' and is
probably just a little bit *too* fine grained).
