The addition of core outputs from fitness and cycling sensors has been suggested.
| Name | Description |
|---|---|
| cad | Cadence - cycling (rpm), swimming / rowing (stroke rate), or running (steps per minute) |
| dist | Total distance in meters (m) |
| elegain | Total elevation gain in meters (m) |
| hr | Heart rate in beats per minute (bpm) |
| power | Power in watts (W) |
| steps | Total steps - walking, hiking, running, etc |
| strokes | Total strokes - swimming or rowing |
The type of sensor(s) used can be potentially be recorded inside the extended <src> element of this proposal:
| Name | Possible Sources |
|---|---|
| cad | crank, phone, pod, rower or watch |
| dist | gps, hybrid *, pod or wheel |
| elegain | baro or gps |
| hr | chest or watch |
| speed | gps, hybrid * or wheel |
| steps | phone, pod or watch |
| strokes | rower or watch |
* examples of hybrid could be gps + pod or gps + wheel.
Sensor information could look something like this in the <src> element:
<src>
<sensors>
<cad>pod</cad>
<dist>gps</dist>
<elegain>baro</elegain>
<hr>watch</hr>
<speed>gps</speed>
<steps>pod</steps>
</sensors>
</src>
Sensor information would supplement the device information already proposed - i.e. manufacturer, product, model, etc.
Thought: This could also be used to state how elevation was derived, if known:
<src>
<sensors>
<ele>baro</ele>
</sensors>
</src>
<xsd:complexType name="dataPointType">