C# FIT SDK etc have the ability to encode as well as decode FIT files.
The JavaScript SDK is only able to decode FIT files. It would be useful to be able to encode again using the JavaScript SDK.
When will this be functionality be implemented?
C# FIT SDK etc have the ability to encode as well as decode FIT files.
The JavaScript SDK is only able to decode FIT files. It would be useful to be able to encode again using the JavaScript SDK.
When will this be functionality be implemented?
There are no immediate plans to support encoding FIT files with the JavaScript SDK. Maybe in the future, but not anytime soon.
The main use-case for the JavaScript SDK is for backend systems written in Node…
How did you determine the main use case for backend systems was only to decode fit files?
Can you recommend any alternatives?
There are no immediate plans to support encoding FIT files with the JavaScript SDK. Maybe in the future, but not anytime soon.
The main use-case for the JavaScript SDK is for backend systems written in Node that need to ingest FIT activity files. In this scenario, the FIT files are passed around by device manufacturers to the various 3rd party platforms via APIs and read-only was sufficient.
What is your use-case for needing to encode FIT files?
Thanks for the reply.
The use case is to be able to decode a FIT file in order to fix it (e.g. pool swim fixing inaccurate length data, fix timestamps of activities etc.) and then encode it again back to FIT file format. If this was possible with the JavaScript SDK then it would make it possible client-side, as well as on the backend in Node.js.
Appreciate that it is not part of your roadmap, would you recommend any alternatives for this? Or any guidance on approach if I was to write my own FIT encoder using JavaScript with this use case in mind?
How did you determine the main use case for backend systems was only to decode fit files?
Can you recommend any alternatives?
Did you find a solution? Is it possible to encode the FIT file yourself?
I've been looking at the `fit-encoder` library. It seems promising, particularly in concert with the `@garmin/fitsdk` library's Profile which contains all the message interpretations. If I get something working, I'll post it here for the next poor soul who come across this thread.