ioos / ioos/xarray-subset-grid
Add additional metadata to variables for UGRID/CF compliance
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 11
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 4
Description
assign_ugrid_topology() currently does (I think) everything that the subsetting code needs.
But there are other things that it would be nice to have, In particular, there's no addition of metadata to the data variables:
https://ugrid-conventions.github.io/ugrid-conventions/#data-defined-on-unstructured-meshes
which should have mesh and location attributes:
double Mesh2_waterlevel(time,nMesh2_face) ;
Mesh2_waterlevel:standard_name = "sea_surface_height_above_geoid" ;
Mesh2_waterlevel:units = "m" ;
Mesh2_waterlevel:mesh = "Mesh2"
Mesh2_waterlevel:location = "face" ;
Mesh2_waterlevel:coordinates = "Mesh2_face_x Mesh2_face_y" ;
A "make fully ugrid compliant" method would be great.
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
Read assign_ugrid_topology() and the linked UGRID section on data defined on unstructured meshes. Identify how data variables are represented and where topology metadata is currently assigned; done means the relevant variables receive the required mesh and location metadata through a fully UGRID-compliant method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100