Additional FIT file fields exported by GOTOES|Strava Tools (like left_right_balance or vertical_oscillation)
Posted: Sun Nov 07, 2021 11:02 pm
Hey guys -
Last week, I added the option to read extra data fields from your FIT files (and subsequently export them into your output FIT files). Please note that these fields are NOT displayed on Strava - so if your only platform is Strava, you can stop reading here. If you use Garmin Connect, Training Peaks, or some other data analysis software, here are the additional fields I added last week:
accumulated_power, left_right_balance, vertical_oscillation, stance_time_percent, stance_time, left_torque_effectiveness, right_torque_effectiveness, left_pedal_smoothness, right_pedal_smoothness, fractional_cadence, left_pco, right_pco, left_power_phase, left_power_phase_peak, right_power_phase, right_power_phase_peak
You may ask why I don't just all every single field that a FIT file has embedded.
There are a few reasons for that. The primary reason is that I'm trying to make this tool work for all of my users. It gets pretty heavy use, and can sometimes slow down during popular times (i.e. weekends). The tool only reads-in and exports-out the pertinent data. Previously, that use to just be the Strava stuff - but more and more people are using the GOTOES|Strava Tools for Garmin Connect and Training Peaks and I'd like to accommodate their needs as well.
Another reason for this is that this tool builds FIT Files from scratch. This is different from taking an existing FIT file and modifying it. The reason this tool builds files from scratch is because that way I can "guarantee" that they won't be corrupted on export. I can make sure that only valid values are entered in each field. The tool validates each field to make sure you're not trying to cram some impossible value where it should not be (which would render the file unreadable by Garmin Connect or Strava). Many of my users come here simply to repair the corrupted FIT file that came from their device.
PARSE RARELY USED FIELDS
In the image above, you can see the checkbox that lets you read-in additional fields to your merge. They will be read into memory, and once you get to the merge page you can even see them if you click the "Click to download Raw Data" link. The data is in tab-delimited format, so best viewed in an app like Excel, Google Sheets, Apple Numbers, or Open Office. The only reason you'd want to check the box above, though, is if you're going to be exporting in the FIT format. If you plan to export as GPX or TCX, there is nowhere to embed that type of information, so it will simply be discarded.
Hope you enjoy these additional fields... and yes, I do have plans to add more fields over time.
Last week, I added the option to read extra data fields from your FIT files (and subsequently export them into your output FIT files). Please note that these fields are NOT displayed on Strava - so if your only platform is Strava, you can stop reading here. If you use Garmin Connect, Training Peaks, or some other data analysis software, here are the additional fields I added last week:
accumulated_power, left_right_balance, vertical_oscillation, stance_time_percent, stance_time, left_torque_effectiveness, right_torque_effectiveness, left_pedal_smoothness, right_pedal_smoothness, fractional_cadence, left_pco, right_pco, left_power_phase, left_power_phase_peak, right_power_phase, right_power_phase_peak
- Here is what your Garmin Connect Activity Page will look like if some of these additional fields have been included.
You may ask why I don't just all every single field that a FIT file has embedded.
There are a few reasons for that. The primary reason is that I'm trying to make this tool work for all of my users. It gets pretty heavy use, and can sometimes slow down during popular times (i.e. weekends). The tool only reads-in and exports-out the pertinent data. Previously, that use to just be the Strava stuff - but more and more people are using the GOTOES|Strava Tools for Garmin Connect and Training Peaks and I'd like to accommodate their needs as well.
Another reason for this is that this tool builds FIT Files from scratch. This is different from taking an existing FIT file and modifying it. The reason this tool builds files from scratch is because that way I can "guarantee" that they won't be corrupted on export. I can make sure that only valid values are entered in each field. The tool validates each field to make sure you're not trying to cram some impossible value where it should not be (which would render the file unreadable by Garmin Connect or Strava). Many of my users come here simply to repair the corrupted FIT file that came from their device.
PARSE RARELY USED FIELDS
- Where to click if you need to include any of the additional data fields mentioned above.
In the image above, you can see the checkbox that lets you read-in additional fields to your merge. They will be read into memory, and once you get to the merge page you can even see them if you click the "Click to download Raw Data" link. The data is in tab-delimited format, so best viewed in an app like Excel, Google Sheets, Apple Numbers, or Open Office. The only reason you'd want to check the box above, though, is if you're going to be exporting in the FIT format. If you plan to export as GPX or TCX, there is nowhere to embed that type of information, so it will simply be discarded.
- You can see your "extra data fields" in raw format by clicking this link on the download page.
Hope you enjoy these additional fields... and yes, I do have plans to add more fields over time.