![]() There was no answer from GARMIN when I asked for the reason. The second time I wrote posts in the GARMIN Forum about the Max Candocia FIT to CSV Tool, they were flagged as inappropriate. There was a TWG for the FIT format at the ANT+ Symposium and these issues had a lot of discussion, the docs should improve in some areas and hopefully more examples of good practice will be made available. ![]() What Garmin fit usage style is though is not at all documented and if your trying to work it out to try and write your own fit files in a similar manner you have to try and look at Garmin generated files and work it out the hard way. Most of the parsers will work with Garmin generated data and if Garmin change there fit usage style then people normally update there parsers to cope. There are some parsers that expect data to be in a specific order where the spec makes it clear that there are options for the order in these cases. There is plenty of parsing code that expects some items that are not at all compulsory by the FIT spec. ![]() The issue is that the FIT spec has some flexibility as to order and what you can and have to put in the different file styles. ![]() low level bit twideling fit files are easy using the FIT sdk it’s hard to write one that is not valid. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |