Skip to content
Merged
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions standard/clause_0_front_material.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@ The next simplest use case is to put data values for each variable (parameter) i

A sophisticated use case is to use tiling objects, where the data values are partitioned spatially and temporally, so that a single variable’s data values would be split among several documents. A simple example of this use case is encoding each time step of a dataset into a separate file, but the tiles could also be divided spatially in a manner similar to a tiled map server.

The abstract, conceptual, definition of a coverage allows its Domain to have any number of coordinate dimensions, such 1 (e.g. a timeseries), 2 (e.g. an area), 3 (e.g. a volume), 4 (e.g. an animated, multi-band, satellite image) or more. Similarly, a coverage can have multiple ranges or parameters (e.g. pressure, temperature and humidity across a domain). The CoverageJSON Standard supports this definition but the convenient, predefined Domain Types are currently restricted to 4 spatio-temporal dimensions (x,y,z,t).
Comment thread
chris-little marked this conversation as resolved.
Outdated

[keywords]
[[keywords]]
== Keywords
Expand Down
Loading