opengeospatial / opengeospatial/CoverageJSON
Develop best practices for handling non-spatiotemporal dimensions
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
This issue is to discuss how to support custom extra dimensions, such as "wavelength". The custom dimensions may not even be ordered or implictly continuous, like (x, y, z, t). A collection of ensembles of forecast data is one example of a discrete and unordered dimension. (but see Issue #172 for support of ensembles specifically)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the discussion on this issue and Issue #172, which is mentioned for ensemble support. Identify the project’s current assumptions about dimension ordering and continuity, then document an agreed approach for custom dimensions and a clear boundary between this work and ensemble support.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100