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 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:
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.
The text was updated successfully, but these errors were encountered:
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.
I admit to be being surprised that CMIP6 explicitly controls some variables to have explicit
long_name
s ANDstandard_name
s, as does CORDEX. I somehow missed that as it happened.Here, for example is one of the CMIP5 (!) formal examples:
which is formally in the CMIP6 controlled vocabularies as:
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.The text was updated successfully, but these errors were encountered: