Add explanation of coverage dimensions in documentation#221
Open
chris-little wants to merge 3 commits intomasterfrom
Open
Add explanation of coverage dimensions in documentation#221chris-little wants to merge 3 commits intomasterfrom
chris-little wants to merge 3 commits intomasterfrom
Conversation
Clarify the limits of coverage domain dimensions in CoverageJSON. Addresses Issue #220
Clarify coverage definition and expand on dimensions and parameters.
awarde96
approved these changes
May 6, 2026
Contributor
Author
|
At CoverageJSON Community Group om 2026-05-06 agree to merge PR. |
jonblower
requested changes
May 8, 2026
|
|
||
| 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). |
Contributor
There was a problem hiding this comment.
Should probably say, "... predefined Domain Types are currently restricted to a maximum of 4 spatio-temporal dimensions..."
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarify the limits of coverage domain dimensions in CoverageJSON. Addresses Issue #220