Hi all,
I think Steve has got to the heart of the issue with his comment, IMHO it is
the client libraries that hold the answer to this question.
However you choose to peer into your netCDF files you are seeing them through
the lens of a client library. And it's worth noting that date/times
Hello Jim
you present an interesting case, thank you
I can see how I can relate
energy deposited(x,y,z,t)
to an ancillary variable of
model atmosphere density profile(x,y,z)
In this case, for any value in my energy deposited data array I can retrieve
an appropriate value for my
Mark,
I'm looking at this from the standpoint of the use of an ancillary variable to
provide metadata about the individual values of another data variable. The
way I think of it, the atmosphere profile used to produce a given energy
deposited value falls under the category of metadata for the
Dear Allison,
Thank you for your comments. I'd propose some further changes to the
definitions:
1. specific_turbulent_kinetic_energy_of_sea_water (m2 s-2)
As turbulent kinetic energy is not necessary equivalent to model's
subgrid scale eddy kinetic energy, I'd formulate the definition as:
'
Hi All:
Ok, its friday afternoon so ill bite on this, and wax philosophical even
before the beer.
An insidious mistake is to think that problems should be fixed in
software libraries. Actually the deep mistake is to mistake the
reference software with the file encoding. Why bother fixing
1) Set the time values to the midpoint of the time interval.*
2) Set a cell_methods attribute on the data variable with a
value of time: mean (interval: 1 month).
3) Create a time_bounds variable with dimensions (time,2)
whose values are the start and end points of each time interval.
4) Set
