.. extracting with a view to identifying special cases in
the FIT developer fields.
.. in this instance the Moxy series have special values of
54 and 57, but its not clear how we can handle this in a
generic fashion (the whole thing is stinky).
.. added to JSON file format, set when importing from RP3 and FIT files
.. primarily used by FIT developer fields that contain unit data
.. but we add units for file formats where we know them (as an english
language string)
.. in part 2 we will add units to the datafilter expressions and the
dialogs in the ride editor to let users edit unit names along with
value names.
A Garmin Vivoactive Sportswatch may be identified by its product code 1907.
A BSX Insight 2 Sensor may be identified by the manufacturer code 98 and the product code 2.
References #2040
please review
One record per length with 3 fields:
TYPE: 0-pause, 1-free, 2-back, 3-breast, 4-fly, 5-drill, 6-mixed, 7-IM
DURATION: seconds per length
STROKES: total strokes per length
Related to #2010
.. there was a memory leak in RideFile and FitRideFile
.. added a test file with weather data that can be used to
test XDATA processing (it has 10 weather points with
wind, humidity etc).
.. it should be calculated in a data processor rather
than in the file processor.
.. Damien is looking to add one, so commenting it out
for now (so the code can be reused if needed).
Simpler and more robust lap alignment
Fixed for empty lengths due to false starts and
pauses in some devices s.t. Garmin 910xt
Added 2 contributed test files
Use total duration for both length and lap messages to synch them,
even when using drill mode. Tested with Garmin Swim and 920xt files.
Garmin 310xt is special cased since it doesn't generate rest length messages
Add Pool Length in meters as metadata
