README: format descriptions in smaller font size
This commit is contained in:
parent
c02e23fb3e
commit
41f8701c06
34
README.md
34
README.md
@ -70,43 +70,43 @@ Supported export formats:
|
|||||||
|
|
||||||
- ``gpx``: activity GPX file (XML).
|
- ``gpx``: activity GPX file (XML).
|
||||||
|
|
||||||
[GPX](https://en.wikipedia.org/wiki/GPS_Exchange_Format) is an open
|
<sub>[GPX](https://en.wikipedia.org/wiki/GPS_Exchange_Format) is an open
|
||||||
format, mainly for storing GPS routes/tracks. It does support extensions
|
format, mainly for storing GPS routes/tracks. It does support extensions
|
||||||
and Garmin appears to annotate the GPS data with, for example, heart-rate
|
and Garmin appears to annotate the GPS data with, for example, heart-rate
|
||||||
and cadence, when available on your device.
|
and cadence, when available on your device.</sub>
|
||||||
|
|
||||||
- ``tcx``: an activity TCX file (XML).
|
- ``tcx``: an activity TCX file (XML).
|
||||||
*Note: a ``.tcx`` file may not always be possible to export, for example
|
*Note: a ``.tcx`` file may not always be possible to export, for example
|
||||||
if an activity was uploaded in gpx format. In that case, Garmin won't try
|
if an activity was uploaded in gpx format. In that case, Garmin won't try
|
||||||
to synthesize a tcx file.*
|
to synthesize a tcx file.*
|
||||||
|
|
||||||
[TCX](https://en.wikipedia.org/wiki/Training_Center_XML) (Training Center
|
<sub>[TCX](https://en.wikipedia.org/wiki/Training_Center_XML) (Training
|
||||||
XML) is Garmin's own XML format. It is, essentially, an extension of GPX
|
Center XML) is Garmin's own XML format. It is, essentially, an extension
|
||||||
which includes more metrics and divides the GPS track into "laps" as
|
of GPX which includes more metrics and divides the GPS track into "laps"
|
||||||
recorded by your device (with "lap summaries" for each metric).
|
as recorded by your device (with "lap summaries" for each metric).</sub>
|
||||||
|
|
||||||
- ``fit``: activity FIT file (binary format).
|
- ``fit``: activity FIT file (binary format).
|
||||||
*Note: a ``.fit`` file may not always be possible to export, for example
|
*Note: a ``.fit`` file may not always be possible to export, for example
|
||||||
if an activity was entered manually rather than imported from a Garmin device.*
|
if an activity was entered manually rather than imported from a Garmin device.*
|
||||||
|
|
||||||
The [FIT](https://www.thisisant.com/resources/fit/) format is the "raw
|
<sub>The [FIT](https://www.thisisant.com/resources/fit/) format is the
|
||||||
data type" stored in your Garmin device and should contain all metrics
|
"raw data type" stored in your Garmin device and should contain all
|
||||||
your device is capable of tracking (GPS, heart rate, cadence, etc). It's a
|
metrics your device is capable of tracking (GPS, heart rate, cadence,
|
||||||
binary format, so tools are needed to read its content.
|
etc). It's a binary format, so tools are needed to read its content.</sub>
|
||||||
|
|
||||||
- ``json_summary``: activity summary file (JSON).
|
- ``json_summary``: activity summary file (JSON).
|
||||||
|
|
||||||
Provides summary data for an activity. Seems to lack a formal schema and
|
<sub>Provides summary data for an activity. Seems to lack a formal schema
|
||||||
should not be counted on as a stable data format (it may change at any
|
and should not be counted on as a stable data format (it may change at any
|
||||||
time). Only included since it *may* contain additional data that could be
|
time). Only included since it *may* contain additional data that could be
|
||||||
useful for developers of analysis tools.
|
useful for developers of analysis tools.</sub>
|
||||||
|
|
||||||
- ``json_details``: activity details file (JSON).
|
- ``json_details``: activity details file (JSON).
|
||||||
|
|
||||||
Provides detailed activity data in a JSON format. Seems to lack a formal
|
<sub>Provides detailed activity data in a JSON format. Seems to lack a
|
||||||
schema and should not be counted on as a stable data format (it may change
|
formal schema and should not be counted on as a stable data format (it may
|
||||||
at any time). Only included since it *may* contain additional data that
|
change at any time). Only included since it *may* contain additional data
|
||||||
could be useful for developers of analysis tools.
|
that could be useful for developers of analysis tools.</sub>
|
||||||
|
|
||||||
All files are written to the same directory (``activities/`` by default).
|
All files are written to the same directory (``activities/`` by default).
|
||||||
Each activity file is prefixed by its upload timestamp and its activity id.
|
Each activity file is prefixed by its upload timestamp and its activity id.
|
||||||
|
Loading…
Reference in New Issue
Block a user