There is no technical reason to store the data on your own hardware.
You "only" have to take it in hand.
The head unit (like a cycling computer that is connected to sensors) can disable
auto-upload activities. What I'm trying to do is to transfer the ride data via the
Bluetooth communications module to save on to a database. I want to bypass uploading to
the manufacturer's cloud service.
Instead of SQL scripting you might use an object-relational mapping
tool. In java it would be Hibernate, > for Python, there are equivalent libraries, I
think.
Fair enough. I mean SQL in generic terms (any data query language). Python libraries have
plenty of data tools. Ride data is saved in XML format (time and geospatial data), the
efficient way to parse XML files in Python will be considered.
There are two parts to this - parsing historical data by fitness API, which is provided by
Strava, Wahoo, and the like. The other one is to get live feed from the head unit/sensors,
which is the hard part.
Plotly provides an open-source free version and enterprise paid license. I couldn't
find the license agreement. I think depending on a choice of database engine and data
pipeline, the analytics tool is aplenty.
Thanks for sharing your insights and advice.