smerchek / node-fit Goto Github PK

The FIT SDK claims to handle the endianness of the various fields for each message. I do see that there is some logic for this; however, running decoding the example Activity.fit file yields different results on a Windows system and a Linux system.

For example, for the first record, mesg.GetTimestamp(), on Windows returns 702940946 which seems correct based on the csv value for the same record. However, on linux, the value is 319284777. I get this same value on Windows if I swap the bytes before printing the result.

I've asked for help on who's responsibility this is in the FIT SDK forum.

The solution may just be to detect the endianness of the the environment and adjust values accordingly. I feel like the SDK should handle this though. I could also just be doing something wrong.

We're not currently taking advantage of the async capabilites of libuv. Since the c++ fit parser methods take in a stream, I think this should be feasible.

libuv filesystem reference

We shouldn't require a file to exist. This would be especially annoying should this library be used as part of a web service. No one wants to write out temp files just to use this module.

I'm interested in writing a front end (with small backend that runs your code) to edit garmin bike gps tracks.

How does the other Fit decoder compare to what you are doing? https://github.com/plus3network/fit

And is there a better way to communicate than via an 'Issue'?