-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Passing NetCDF attributes into cube for CMIP data #2352
Comments
hello @pdearnshaw perhaps we could try to chat about how to handle this? I believe that a coordinate can be selected from a cube by a |
This may take some care to handle.
I assume that here you mean that we need better control over what is saved by Iris In the basic CF rules, virtually everything is optional, so we could maybe view this as adopting an 'extra convention' (like the MoNET conventions). Can you supply concrete examples of where the results are currently undesirable ? |
A concrete example could be the following: the CMOR tables for both CMIP5 and CMIP6 specify an Related issue #1404. |
Bump: we should either close this or act on it. If there's no more movement by 2022-08-31 I'll go ahead and close the issue. |
Is there a reason why it is not allowed to set certain attributes on cubes/coordinates? Maybe because they are not necessary? It might be useful to give this as input for the design of the data request for CMIP7. |
It's simply because certain specific attributes have meanings defined by CF, and so are treated as "managed" by Iris. The defining list is here |
@SciTools/peloton This is at minimum blocked by the Xarray bridge #4994. User intervention would also be needed. |
CMIP6 has a specific template of attributes that are required in variables from NetCDF files. Iris currently pulls a few of these out, e.g. axis in coords and _FillValue or missing_value for the variable. These should not be removed and allowed to pass through to the cube so that any resulting cubes conform to CMIP6 data specifications.
The text was updated successfully, but these errors were encountered: