• State Not Answered
  • Replies 1 reply
  • Subscribers 5 subscribers
  • Views 164 views
  • Users 0 members are here
Options
Related

Make "feel" an enum

kcfwpi
1 month ago

Thanks for adding 'feel' and 'RPE' to the profile spec in 21.141.00. In a future release could 'feel' be made an enum rather than a short? As a short it's incumbent on the decoders to reverse engineer what the values mean, and there is no standardization across manufacturers.

For Garmin devices it appears to be:

0=Very Weak, 25=Weak, 50=Normal, 75=Strong, 100=Very Strong

But for SUUNTO devices it's:

1=Poor, 2=Average, 3=Good, 4=Very Good, 5=Excellent

Another company also uses the 1 to 5 point scale, but it's reversed. I.e. 1=Excellent, 5=Poor.

Seems like everyone has converged on this 5 point scale. so standardizing it in an enum would be really helpful to developers.

  • 0 14 days ago

    Unfortunately that ship may have already sailed. Even though the Feel and RPE fields were documented in v21.141 of the SDK, they have been around since 2019. More than likely there are devices that use these fields that are no longer receiving updates. So even if there was a change, these fields would still be accounted for in any code that is decoding FIT file. The best I can offer is that, we will try to do better in the future.