If I would work out such a solution and try to figure out on how to best add support for multisport files and how to split the sessions in either ways, would that be accepted? IMHO the license would be easy to fulfill and the project's usage and support for fit files already implies to agree with their license, so why not use their code to deal with such file? It would also make it easier to maintain and/or upgrade fit file coding. What if we replace the custom variant recently used and import the Garmin (thisisant) SDK code to parse fit files. I had a quick look at the fit file spec and the activity spec mentioned earlier and I also had a look at the SDK code provided by Garmin. is that true for the o_synce files can you tell me if there is any plan on what functionality should be supported for such a feature? 2.2, D00001309 FIT File Types Description Rev 2.2.pdf) and at page 52, Figure 9-2 it seems that - as with interleaved file format - session entries appear too in the non-interleaved format. I had a quick overview of the fit file spec (Rev. I think it is needless to mention that kona is one of the most important event for any triathlete in the world. I do think this would fit almost all use-cases as the following statistics for sports watches used at ironman kona shows. We can easily add a check in there to support only Garmin created files for this feature.
But, if we already know that Garmin files are working like this wouldn't it be a good idea to support at least files from them? We already know the vendor/product of the file.