Skip to content
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

Name of grid_mapping variable set by CMOR #17

Open
sol1105 opened this issue Jul 1, 2024 · 2 comments
Open

Name of grid_mapping variable set by CMOR #17

sol1105 opened this issue Jul 1, 2024 · 2 comments

Comments

@sol1105
Copy link

sol1105 commented Jul 1, 2024

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
Copy link
Contributor

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
Copy link
Contributor

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

@larsbuntemeyer larsbuntemeyer transferred this issue from WCRP-CORDEX/cordex-cmip6-cmor-tables Oct 3, 2024
@larsbuntemeyer larsbuntemeyer added this to the new archive specs milestone Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants