Cell methods: Handle the more general CF convention for statistics applying to portions of cells
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 13
- Avg merge
- 7d 22h
- Merged PRs (30d)
- 1
Description
Currently, it has always been the case that the more general CF convention for statistics applying to portions of cells is not catered for in cfdm cell methods.
I.e. when a where, or an over after a "where", references a coordinate variable name (such as "my_area_types", rather than a area types CV value (such as "sea_ice").
See https://github.com/orgs/cf-convention/discussions/450 (Missing connection in the CF data model: Cell Method -> Coordinate) for further discussion.
We need to fix this.
PR to follow.
As an aside, one reason this was missed was, I think, because there is a line missing in the CF data model UML (!), that should connect "Cell Method" to "Generic Coordinate Construct".
Contributor guide
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 tracing how cfdm represents and parses cell methods, using the CF convention section on statistics applying to portions and discussion 450 for the intended relationship. Support where and post-where over references to coordinate variable names, and verify that existing value-based references still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100