Skip to content

Commit b544854

Browse files
authored
Add explanation of coverage dimensions in documentation
Clarify the limits of coverage domain dimensions in CoverageJSON. Addresses Issue #220
1 parent 6c55dad commit b544854

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

standard/clause_0_front_material.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ The next simplest use case is to put data values for each variable (parameter) i
3434

3535
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.
3636

37+
The abstract, conceptual, definition of a coverage allows its Domain to have any number of coordinate dimensions, such 1 (e.g. timeseries), 2 (e.g. an area), 3 (e.g. a volume), 4 (e.g. an animated, multi-band, satellite image) or more. The coverageJSON Standard is currently restricted to 4 spatio-temporal dimensions (x,y,z,t).
38+
3739
[keywords]
3840
[[keywords]]
3941
== Keywords

0 commit comments

Comments
 (0)