Skip to content

Commit 58e008a

Browse files
authored
Clarified Domain Type restrictions
Clarify coverage definition and expand on dimensions and parameters.
1 parent b544854 commit 58e008a

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

standard/clause_0_front_material.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ 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).
37+
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).
3838

3939
[keywords]
4040
[[keywords]]

0 commit comments

Comments
 (0)