Skip to content

long names and standard names #6

@bnlawrence

Description

@bnlawrence

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    output-cf-complianceRelates to the CF compliance of the output

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions