dev.sensorthings.observationFrame
The new or changed readings from one collector tick, for many Datastreams in the same repo. Created once and never updated. After the correction horizon has passed, the readings are sealed into dev.sensorthings.observationBatch day records and the frame is deleted. Apply frames in record key order: a later entry for the same datastream and phenomenonTime replaces an earlier one. The record key is the tick time to the millisecond and a three-digit shard number, for example 20260925T100700000Z-000.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | sensorthings.dev |
| Indexed |
Record
record · key anyProperties
maxLength: 10000
Time of the collector tick that wrote this frame
#frameEntry
objectProperties
Record key of a dev.sensorthings.datastream record in the same repo
q
stringknownValues: dev.sensorthings.quality#good | dev.sensorthings.quality#suspect | dev.sensorthings.quality#missing
Observation result, same union as dev.sensorthings.observation
phenomenonTime
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
A batch of observations for a single Datastream, covering a contiguous time window. Trades individual addressability for reduced commit overhead.
-
dev.sensorthings.observation
recordA single act of observation. The result type is determined by the $type discriminator on the result object.
-
A composite observation bundling multiple co-produced results from a single act of sensing. Each entry carries its own ObservedProperty, unit, and scale metadata. Use this instead of separate Observations when the results are genuinely co-produced (e.g. wave statistics from spectral processing) and have no independent existence.