Which FIT Data Fields does GOTOES support?
Posted: Sat May 04, 2024 4:51 pm
People will often ask me if GOTOES will export a certain data field that they really want into their FIT file. Here is a list of the currently supported FIT FILE fields that GOTOES can process. Keep in mind that this is an evolving list. As I receive feature requests or new fields are added, I try to keep up. GOTOES is mostly targeted at Cyclists, Runners, and Swimmers - so I try to prioritize fields that are pertinent to these sports.
List Last Updated May 4, 2024
Supported Native Garmin Fields
Supported FIT Record Fields
Supported FIT Session Fields
To ensure that these fields are transferred from your import to your export, you want to make sure that the "Parse Rarely Used FIT fields" checkbox is checked as illustrated below:
Supported FIT Developer Data Fields
GOTOES currently supports ALL PROPERLY ENCODED Developer Data Record and Session Fields. A Record Field is like a stream of data. Think of power, heart rate, or vertical oscillation. This is data that occurs over a period of time. Note that when I say "properly encoded" data that many nascent manufacturers have not registered their ID with ThisIsAnt and they just leave the Developer ID field blank. Furthermore, I have received quite a few files with the Session Data improperly placed in the Record fields. At this time, GOTOES does its best to process these files.. but technically, they are not formatted correctly. Garmin does it correctly (of course: They designed the spec).. but quite a few 3rd party apps like Coros and Stryd still do not do it correctly. GOTOES will tell you what it can (and cannot) insert if you load your files and check the "ConnectIQ" stream checkbox.
List Last Updated May 4, 2024
Supported Native Garmin Fields
Supported FIT Record Fields
Code: Select all
timestamp
position lat
position long
altitude
heart rate
cadence
distance
power
temperature
enhanced speed
enhanced altitude
developer data
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
total hemoglobin conc
saturated hemoglobin percent
left platform center ofsset
right platform center ofsset
left power phase
left power phase peak
right power phase
right power phase peak
step length (stride length)
performance condition
enhanced respiration rate
grit
flow
jumps (distance, height, hang time, score)
potential
stamina
Code: Select all
timestamp
start time
sport
sub sport
total elapsed time
total timer time
total distance
total ascent
total calories
total training effect
total anaerobic training effect
primary benefit
training stress score
intensity factor
normalized power
avg heart rate
max heart rate
avg speed
max speed
avg cadence
max cadence
avg power
max power
threshold power
total cycles
training load peak
total grit
avg flow
jump count
calories consumed
est sweat loss
fluid consumed
To ensure that these fields are transferred from your import to your export, you want to make sure that the "Parse Rarely Used FIT fields" checkbox is checked as illustrated below:
Supported FIT Developer Data Fields
GOTOES currently supports ALL PROPERLY ENCODED Developer Data Record and Session Fields. A Record Field is like a stream of data. Think of power, heart rate, or vertical oscillation. This is data that occurs over a period of time. Note that when I say "properly encoded" data that many nascent manufacturers have not registered their ID with ThisIsAnt and they just leave the Developer ID field blank. Furthermore, I have received quite a few files with the Session Data improperly placed in the Record fields. At this time, GOTOES does its best to process these files.. but technically, they are not formatted correctly. Garmin does it correctly (of course: They designed the spec).. but quite a few 3rd party apps like Coros and Stryd still do not do it correctly. GOTOES will tell you what it can (and cannot) insert if you load your files and check the "ConnectIQ" stream checkbox.