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

long names and standard names #6

Open
bnlawrence opened this issue Nov 4, 2022 · 3 comments
Open

long names and standard names #6

bnlawrence opened this issue Nov 4, 2022 · 3 comments
Labels
output-cf-compliance Relates to the CF compliance of the output

Comments

@bnlawrence
Copy link
Contributor

bnlawrence commented Nov 4, 2022

I admit to be being surprised that CMIP6 explicitly controls some variables to have explicit long_names AND standard_names, as does CORDEX. I somehow missed that as it happened.

Here, for example is one of the CMIP5 (!) formal examples:

float tas(time, lat, lon) ;
 tas:standard_name = "air_temperature" ;
 tas:long_name = "Near-Surface Air Temperature" ;
tas:comment = "comment from CMIP5 table: near-surface
(usually, 2 meter) air temperature." ;
 tas:units = "K" ;
 tas:original_name = "TS" ;
tas:history = "2010-04-21T21:05:23Z altered by CMOR: Treated
scalar dimension: \'height\'. Inverted axis: lat." ;
 tas:cell_methods = "time: mean" ;
 tas:cell_measures = "area: areacella" ; 

which is formally in the CMIP6 controlled vocabularies as:

!============
variable_entry:    tas
!============
modeling_realm:    atmos
!----------------------------------
! Variable attributes:
!----------------------------------
standard_name:     air_temperature
units:             K
cell_methods:      time: mean
cell_measures:     area: areacella
long_name:         Near-Surface Air Temperature
!----------------------------------

We have to decide whether we care about following the CMIP6 bindings of these variables (and whether or not we want to put the CMIP6 table names and variable names anywhere in our metadata). Given we won't have files and directories with those names, there still might be benefits in putting them in per variable metadata.

We might also want to save the stash long names directly, we could do that with something like a um_context attribute.

@bnlawrence bnlawrence added the output-cf-compliance Relates to the CF compliance of the output label Nov 4, 2022
@bnlawrence bnlawrence added this to the Pre-Production-Data-Checks milestone Nov 4, 2022
@bnlawrence
Copy link
Contributor Author

Can we add things to stash2cf? Is stash2cf complete for all our variables? Does our client community want names like tas? Does our climate community care about cmip6 long names.

@grenville
Copy link

it was a strange decision to use long_name - they could have called it cmip_long_name and not stuffed us all up

@grenville
Copy link

grenville commented Jan 11, 2023

I vote we leave our long_names (we're not out of cf-compliance by doing so) -- atmos, nemo, and cice all have non CMIP long_names

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
output-cf-compliance Relates to the CF compliance of the output
Projects
None yet
Development

No branches or pull requests

2 participants