[CF-metadata] [Standard name request] property changes over time
Apologies for the tardiness with response..
My whole point of suggesting the "*_change" suffix was to request a generalization, so the existing standard name list (with *_change appended, e.g. sea_water_salinity_change, sea_water_temperature_change and sea_water_density_change) could be used, rather than having to explicitly request a new standard name, and bloat the already large standard-name-table.
By having to go through the process of requesting each independent new *change* variable, it creates another job for the CF working group, whereas the generalized suffix *_change could be implemented (with appropriate specification of a climatology attribute which specifies the period over which the "change" represented), which then allows any existing standard name (sea_water_salinity -> sea_water_salinity_change, sea_water_temperature -> sea_water_temperature_change etc) to be used with the new suffix.
I personally prefer the *_change suffix to change_in_* as I can find these entries more logically in an alphabetical listing - such as the standard name table itself e.g.:
** my suggestion of "*_change" **
sea_water_pressure_at_sea_water_surface
sea_water_salinity
sea_water_salinity_change
sea_water_sigma_t
** versus the existing "change_in_*" **
change_in_atmosphere_energy_content_due_to_change_in_sigma_coordinate_wrt_surface_pressure
change_in_energy_content_of_atmosphere_layer_due_to_change_in_sigma_coordinate_wrt_surface_pressure
change_in_sea_water_salinity
change_over_time_in_atmosphere_water_content_due_to_advection
...
sea_water_pressure_at_sea_water_surface
sea_water_salinity
sea_water_sigma_t
**
Does this seem to be a reasonable request?
Cheers,
P
-----Original Message-----
From: Jonathan Gregory [mailto:j.m.gregory at reading.ac.uk]
Sent: Wednesday, March 30, 2011 11:14 PM
To: Durack, Paul (CMAR, Hobart)
Cc: CF-metadata at cgd.ucar.edu
Subject: Re: [CF-metadata] [Standard name request] property changes over time
Dear Paul
I think the quantities you want to propose are really change_in_X where X is
already or could be a standard name. So I don't believe any new syntax is
needed. All you need to do is propose new names X or change_in_X on this email
list.
Best wishes
Jonathan
Received on Thu Apr 07 2011 - 01:48:07 BST
This archive was generated by hypermail 2.3.0
: Tue Sep 13 2022 - 23:02:41 BST