opengeospatial / opengeospatial/CoverageJSON
Representation of multiple time axes
Open
Nobody has claimed this yet.
enhancement
Priority 1
V1.1
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Copied from the original specification:
The following items are (major) outstanding issues to be resolved for the first version: #45 Representation of multiple time axes
I suggest we do this after adoption by OGC as an enhancement.
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 linked original CoverageJSON specification and the issue's reference to OGC adoption. Determine how multiple time axes should be represented for the first version, then document the agreed representation and verify it against the specification's requirements.
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
- 30/100