Heartrate is not merged into single file

[SebaGnich]

Hello all! Very nice and handy tool you've built :)

I have one small issue though. My setup is kind of weird:

HR-Monitor via Garmin Watch, Indoor Cycling Bike (Elite Direto) connected to myWhoosh app on Android.

It's not possible (currently at least for me) to connect my HR to the app, so I got two files - one from Garmin (HR), one from myWhoosh (Power, "GPS", etc).

Your tool doesn't include the HR into one file. I can see the graph, when I select the file only, but in combined view (and exported), it isn't included.

Is there a way to fix it?

Thanks very much!

[muktihari]

Hi @SebaGnich, would you like to share your files so we can take a look? We can't do much without knowing how the data is structured.

[SebaGnich]

Hi, yes of course, here they are. Thanks for replying so fast!

openivity.zip

[muktihari]

Hi @SebaGnich, after looking at the files, I have workaround for this which requires multi-stage processes:

1. Open your_file.tcx file (HR file) -> Tools tab -> scroll down to Remove Fields -> check Distance to remove distance from the file, then export as FIT file (Target Device can be anything, it's just a temporary file).

2. Open exported_file_1.fit and your_file.fit -> Tools tab -> select Combine Multiple Activities into One, select your desired Target Device e.g. Mywhoosh with product_id 3570. Also make sure both session sports are the same Cycling, then export as FIT file.

   This will append the record of both files like this.

   timestamp	distance	position_lat	...	heart_rate	originally from file
   1137947267	-	-	...	56	tcx
   1137947267	400	564734848	...	-	fit
   1137947268	-	-	...	54	tcx
   1137947268	553	564734848	...	-	fit
   ...	...	...	...	...

   But it's still not complete just yet, we need to merge records having the same timestamp into one record in the next process.

3. Open the exported_file_2.fit, openivity by default will do a preprocessing like merging records with the same timestamp into one if it's in the same session (during opening). Export the FIT file again, let's call it exported_file_3.fit. The resulting FIT file will be like this:

   timestamp	distance	position_lat	...	heart_rate
   1137947267	400	564734848	...	56
   1137947268	553	564734848	...	54
   ...	...	...	...

   Done. Now you can use the exported_file_3.fit

I know it isn't intuitive, as we didn't consider this use case when developing the app. At the moment, I don't have the bandwidth to start a new feature development and only handle bug fixing only if it's trivial. I hope this workaround helps resolve the issue, let me know if you need further guidance.