TimeSeriesAssociation

Package: InfrastructureTimeSeriesOpenAPIModels · Source: TimeSeries/TimeSeriesAssociation.json

Metadata linking one time series to the component or supplemental attribute that owns it — the JSON form of a row in the store’s time_series_associations catalog table. A closed set of six canonical types owned by the data layer: two static (SingleTimeSeries on a regular grid, NonSequentialTimeSeries on explicit irregular timestamps) and four forecasts. The type decides which timing fields the row carries, which is why each is its own schema rather than one row with everything nullable.

Dense values never appear here. uri names the store location that holds them; data_hash optionally carries a content hash of that array. A NonSequentialTimeSeries adds timestamps_uri, the same kind of locator for its explicit time axis, which is likewise stored rather than carried. Content hashes themselves (features_hash, timestamps_hash) remain store-internal and deliberately absent — a locator names where something is, which is not the same as exposing the store’s own address for it.

Variants

Discriminated by time_series_type.

time_series_type	Schema
SingleTimeSeries	SingleTimeSeries
NonSequentialTimeSeries	NonSequentialTimeSeries
Deterministic	Deterministic
DeterministicSingleTimeSeries	DeterministicSingleTimeSeries
Probabilistic	Probabilistic
Scenarios	Scenarios