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
I might be mistaken, but to me it looks like one cannot influence the name of the grid_mapping variable when standardizing with CMOR. The variable name seems to be hard coded to the actual name of the mapping, i.e.
[...]
int rotated_latitude_longitude;
[...]
float pr;
pr: grid_mapping: "rotated_latitude_longitude";
[...]
This conflicts however with the CORDEX-CMIP6 Archive Specifications, that request crs as the variable name . Does it still count as compliant to the CORDEX-CMIP6 Archive Specifications, when having the grid_mapping variable named by CMOR or is it required to rename it to crsafterwards?
Yes, thanks for pointing it out! I think it should be possible using CMOR to adapt this but right now i am also not sure if this has to be done via the grids table or keyword arguments in cmor_set_grid_mapping. For my examples, rotated_latitude_longitude is hardcoded here. Let me figure how to adapt the variable name of the grid mapping variable (and how we have to add it to the grids table)...
I might be mistaken, but to me it looks like one cannot influence the name of the
grid_mapping
variable when standardizing withCMOR
. The variable name seems to be hard coded to the actual name of the mapping, i.e.This conflicts however with the CORDEX-CMIP6 Archive Specifications, that request
crs
as the variable name . Does it still count ascompliant to the CORDEX-CMIP6 Archive Specifications
, when having the grid_mapping variable named by CMOR or is it required to rename it tocrs
afterwards?P.S.:
@larsbuntemeyer I see in your CMORized test file that variable is labeled
rotated_latitude_longitude
as well.The text was updated successfully, but these errors were encountered: