Dear John
I generally agree with your summary.
I think it's fair to say that the Standard Name only implies a format
restriction in the context of a COARDS/CF file.
Yes.
'time' is a representation of any chronological parameter, even if
just a day or a year; typically it represents a
Dear Martina
In summary, am I right that we agreed on:
tendency_of_atmosphere_mass_content_of_X_due_to_respiration : kg.m-2.s-1
tendency_of_mole_concentration_of_X_in_air_due_to_chemical_gross_production
:
mol.m-3.s-1
Dear Martin and Philip
I am not quite sure I understand options (i) and (ii). I think that the
standard name (mole concentration, mass concentration, etc.) defines the
physical units. The species does not; it just fills the gaps in the standard
name where species are allowed. If any species could
Hi Martina,
thanks for your valuable comments.
2. Martin/Jonathan concerning syntax definition for chemical
quantities
basically the physical_quantity_of_X_in_medium_as_identity
level of Martina's
proposal
Actually, for me the 'as_identity' was part of the constituent X,
e.g.
Dear Martin
What you would propose, if I understand correctly, is to continue to decide
on each chemically related standard name individually, in order to make sure
they are all valid. (That is what I meant by preventing nonsense in a
previous email.) Is that right? This would not then be a
Dear Jonathan and Martin,
This is why I was trying to point out that CF doesn't need to keep
separate lists for X, A, G, or any other set of species. We will only
need a single list of species: X.
Where is the information then for a physical quantity for an aerosol
that only part
Dear Thomas
eastward_sea_ice_displacement [m] (length of [lon0,lon1] on Earth
surface)
northward_sea_ice_displacement[m] (length of [lat0,lat1] on Earth
surface)
sea_ice_x_displacement[m] (length from P0 to P1, taken along
the grid's X axis)
sea_ice_y_displacement
Uh, to an observing systems/cyberinfrastructure person, ALL time
values have errors, _especially_ those from devices. (As if the system
time isn't originally from a device, for that matter. But I
digress.) So actually, I find reported_time to be more suggestive of
absolute real-world
For the case where there are multiple variables with different sensor times
in a NetCDF file, the 'sensor time' standard name somehow needs to be
tied to the data variable produced by that sensor - can this be a compound
term that includes the standard name of another variable?