Standards primers
drogna leans on four standards, and the reason it leans on them rather than inventing message shapes is the point of the exercise: the architecture under test is one in which reads are served only through standards-based interfaces. If the standards do not fit, that is the finding.
All four are written. Each states what the standard is for, the parts drogna uses, the parts it deliberately does not, and — more usefully — the specific question drogna needs that standard to answer. Two ideas recur across all four and are worth having to hand first: a coverage, which is a function from positions in space and time to values, and a trajectory, which is a path through both.
| Primer | What drogna uses it for | Status |
|---|---|---|
| SensorThings | The observation vocabulary, from sensor to query | Written |
| OGC API-EDR | Reads against the coverage store, including trajectory | Written |
| CF conventions | Coverage storage and offload export | Written |
| CoverageJSON | The response the browser client renders | Written |
These are primers, not specifications. Each is written for a reader who has not met the standard, and each links to the authoritative document rather than paraphrasing it at length.
The one to read first is CoverageJSON, because it starts by explaining what a coverage is. The idea — a function from positions in space and time to values — is the one that makes the other three easier to follow.