opengeospatial / opengeospatial/CoverageJSON
Should ParameterGroup be split
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
ParameterGroup has two main use cases:
- to group values that are really a single vector or tensor value, rather than scalar. such as Wind Velocity expressed as Wind Speed and Wind Direction, or Surface Wind Stress;
- to group a value with some derived statistical values, such as standard deviation.
ParameterGroup addresses both of these use cases effectively, but in the future, should the two above patterns be explicitly identified?
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 ParameterGroup definition and the examples or schema locations that represent its two documented use cases: composite vector/tensor values and derived statistics. Compare how each pattern is currently expressed, then document a decision on whether they need explicit identification or separate concepts, including the affected examples and schema wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100