easy-fit icon indicating copy to clipboard operation
easy-fit copied to clipboard

Parse your .FIT files easily, directly from JS

Results 14 easy-fit issues
Sort by recently updated
recently updated
newest added

I synced and updated the manufacturer list and lap type according to the list in FIT SDK v20.63.00 (latest as of this date)

avg_stance_time_percent seems to have incorrect value. supposed to denote AVG Ground Contact Time Balance but seems to be off for some reason

👋Hi! Thanks so much for this awesome library. It makes working with .FIT files a breeze. ✨ I noticed that `records` fields have [an `elapsed_time` field](https://github.com/pierremtb/easy-fit/blob/e5dc98f9d8a9671d4a92d5392038b9338cb309ed/src/binary.js#L190) that tells us how...

The left_right balance is incorrect it seems. in the fit.js file it states left_right_balance: { 0: 0, 127: 'mask', 128: 'right' }, left_right_balance_100: { 0: 0, 16383: 'mask', 32768: 'right'...

When reading a FIT file from a cycling ride without Powermeter connected, all powerdata show 65535 as value. This includes avg_power, max_power and all other related values such as training_stress_score...

### Main changes ### - [X] Due to a typo in one of the switch cases `isInvalidValue`, invalid data for `uint16` fields would not be rejected - [X] Follow-up of...

https://github.com/pierremtb/easy-fit/blob/e5dc98f9d8a9671d4a92d5392038b9338cb309ed/src/easy-fit.js#L6 I think this should be .. ``` force: options.force === false ? false : true ```

Parsing fails when record contains developer defined fields which are used by third party app developers and new in FIT 2.0 (?) spec. The parsing itself does not crash but...

@pierremtb Thanks for the library.

The offset value for altitudes should be -500, it appears to be configured as +500. When encoding altitude fit will use uint16 = 5 * (altM + 500) So decoding...