You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add proj and spatial conventions to /conditions/meteorology #353
The 21 arrays under /conditions/meteorology/cams and /conditions/meteorology/ecmwf have latitude and longitude dimensions. They have no CRS, and their groups have no zarr_conventions. The groups also carry a source attribute Conventions: "CF-1.7", which contradicts the "no CF claim" decision in #TBD-01.
Proposal
On the cams and ecmwf groups, write:
proj:code: "EPSG:4326";
spatial:dimensions: ["latitude", "longitude"];
spatial:shape, spatial:transform and spatial:bbox, from the coordinates;
the two zarr_conventions entries.
Remove the source Conventions attribute from these groups.
Use the same helper as the other groups (write_dataset_geo_metadata / grid_spatial_attrs). Check the transform when the latitude decreases.
Tests
Regenerate the S2 snapshots. Add a test that the meteorology groups have proj and spatial.
changed the title [-]#TBD-01c `proj` and `spatial` conventions on `/conditions/meteorology`[/-][+]Add proj and spatial conventions to /conditions/meteorology[/+]on Nov 12, 2026
Activity
[-]#TBD-01c `proj` and `spatial` conventions on `/conditions/meteorology`[/-][+]Add proj and spatial conventions to /conditions/meteorology[/+]Merge PR 330's port of EOPF main into the issue-349 fixes