I have update the “JSON” workout download to include the actual watts, bpm and mps values for power, hr and pace targets in steps. These are calculated using the zones etc for the athlete.
{
"duration": 3600,
"ftp": 290,
"target": "POWER",
"steps": [
{
"duration": 3600,
"power": {
"value": 2.0,
"units": "power_zone"
},
"hidepower": false,
"_power": {
"value": 190.0,
"start": 162.0,
"end": 218.0
}
}
],
"options": {}
}
The resolved values are in _power, _hr and _pace.
Absolute (not a range) power, pace and HR targets are converted into a range using a percentage of value (powerRange=2.5, paceRange=2.5, hrRange=1.5). You can specify these as query parameters to override.
If the workout has steps using power and/or HR and/or pace then the athletes preferences for the sport are used to choose how to execute the workout. This is in the “target” field. All targets are resolved in any case but maybe someone wants to use this.
So you don’t have to mess around with the zones to try calculate power etc…