opengeospatial / opengeospatial/CoverageJSON
How best to support Ensembles of data
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
@m-burgoyne tried to create CoverageJSON of some NWP ensemble forecast data using a fifth custom dimension. Failed schema check. @jonblower @letmaik Could the schema be enhanced to support more dimensions, and remain backward compatible?
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 reviewing the CoverageJSON schema and its current dimension constraints, then examine the reported NWP ensemble example with a fifth custom dimension. The issue does not name files or tests; done would require a backward-compatible schema approach that supports additional dimensions and passes schema validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100