search

WCRP-CORDEX / cordex-cmip6-cmor-tables

JSON Tables for CMOR3 to create CORDEX-CMIP6 datasets
https://wcrp-cordex.github.io/cordex-cmip6-cmor-tables
BSD 3-Clause "New" or "Revised" License
1 stars 1 forks source link

Name of grid_mapping variable set by CMOR #100

Open sol1105 opened 6 days ago

sol1105 commented 6 days ago

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?

P.S.: @larsbuntemeyer I see in your CMORized test file that variable is labeled rotated_latitude_longitude as well.

larsbuntemeyer commented 6 days ago

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)...

larsbuntemeyer commented 4 days ago

It seems like it's hardcoded after all. I'll check with PCMDI: