Skip to content

RFC: more generic DataPoint values #65

Description

@ignatz

Hi,

I've been toying with the idea of using tstorage for a series of location data, i.e. 3D positions (latitude, longitude, altitude) for different devices.
If I understand correctly, using tstorage I'd have to model the various serious and values belonging to the same "measurement" as something like:

[
(DataPoint(now, 42), Label("id", "device0"), Label("latitude", "")),
(DataPoint(now, 23), Label("id", "device0"), Label("longitude", "")),
...
]

Is my understanding correct? If so and it's probably a big ask, but would it be possible/make-sense to generalize the data representation to e.g. a byte array? In that case, I could store all related measures as a single point. Does the storage format currently require fixed value/data-point sizes?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions