.. check looks at autoimport too (e.g. when checking a
directory that is mounted when connecting device).
.. changed the titles to make it clearer which are about
activities and which are about measurements.
.. to support importing rides on download from a
web page, we now support files that are compressed
using gzip or zip.
.. the file name will still need to have the correct
file format encoded in the suffix but will be
deflated before being passed to the readers.
.. for example files downloaded from TrainingPeaks
via their webapp will likely end in .wko.gz.
... in addition to DateTime in the .json File name (which is in local Time), also check for duplicates using UTC from RideCache to avoid duplicate imports if user changes his PC TimeZone (e.g. when travelling)
... the problem e.g. occurs in Autoimport where the same files would be imported again, if the PC TimeZone changes
.. a data processor can now be configured to run on save
.. in addition, the data processor is now passed the operation
that is triggering it: "Manual", "ADD", "UPDATE", "DELETE",
"IMPORT".
.. a new data processor has been added to write a JSON file to
the snippet directory (added to the athlete structure).
.. this is so we can output a snippet every time an activity is
added, updated or deleted (i.e. runs "on save").
.. these JSON snippets can be used to update external datastores
where coaches use other analytic software but don't want to
manually sync GC changes with there external stores.
