Hi,
Forgive me if this has been covered elsewhere, I have tried digging around and using the search (which seems to return a lot of unrelated results)
I have been looking at trying to make a kite surf app for my Fenix 3, and in the last couple of days have put together a single screen app that gives speed, distance, time etc.
There are 2 points I had wanted to improve over the built in functions.
1.
One of the common complaints on the fenix is the elevation data, GPS elevation is inherently inaccurate and polled too slowly and the baro altimeter is slow/smoothed/hysteresis, therefore never tracks jumps correctly.
My intention had been to start working on a way of calculating height using the accelerometer data (woo style), however looking into it, the limitation at the moment might be getting this data out, I had hoped that although restricted in what data we could put in a FIT file, you could at least dictate it's origin, however all I can seem to find is that you turn recording on and it is all populated from its default fields
2.
Calorie calculation - I do not wear a heart rate monitor for kiting so there is no data for it to use to calculate calories from that, again I had hoped to be able to overwrite the calorie field based on an average calorie burn per minute for kite-surfing, at the moment I have created a custom app defined as 'other' and the calorie count seems very high.
This would obviously be solved by an expansion of the available sports types built into the watch, or at least an explanation of how each calculates calories etc. seeing as kitesurfing is listed for the connect categorisation but not the watch.
Firstly am I wrong and can I feed in elevation/calorie data from where I want or is it locked down?
Second, I have seen some comments about FIT files opening up in Q2 of 2016, is this still on track? If so would this in theory give me what I want be it modifying the standard elevation data or creating a new 'jump' track within the FIT file.
Thanks for any help!
