Hi Peter,
TBH this isn't necessarily a Fedora Server specific thing, it
could also be Fedora IoT or general Fedora.
Fair enough. It may well be suited better for Fedora IoT, which I'm not familiar.
I would change a lot of the above, like why SQL, a time series DB may
be better for that sort of data.
True. The choice of database engine will be much affected by types of data (time and
geospatial) and data pipeline. I need to work with XML data.
There's even interest in removing the closed ecosystem such as
Strava for health data entirely so why just limit it to the ability to visualise data from
a proprietary service/stack.
My goal is to bypass the service provider/manufacturer's data collection and
processing. I should explore a little more about open-source visualization tools.
There's PineTime [1] with an open source firmware called
IniniTime [2] with an open GTK3 app to run on Linux [3] so why not go the whole way?
Good point.