Hi John,
I have seen similar situations in atmospheric chemistry. I participated in an
intercomparison in which we submitted exactly what the std_name required, only
to find out that every other group had submitted what they assumed it meant,
which was several orders of magnitude different.
I
It looks sensible to me, too, but I have to ask a stupid question. Of all the
data with "sea_water_pressure" CF standard names in the world, how many are
actually presenting what CF defines that to be? (If the answer is "very few",
maybe the answer is that the definition is just mis-stated for
Hi Roy,
This looks sensible to me.
Philip
---
Dr Philip Cameron-Smith, p...@llnl.gov, Lawrence Livermore National Lab.
---
From: CF-metadata [mailto:cf-me
On Thu, Jan 10, 2013 at 10:26 AM, Chris Barker - NOAA Federal
wrote:
> but is that the data model? or is that a particular encoding for a
> particular file format? I think the later.
Another example of encoding vs. data model:
An array of integers is a data model
The binary representation of t
Folks,
I'm posting this to the list, rather than the ticket, as the ticket
had gotten huge, and it looks like it may be closed/restarted/split up
anyway. Also, this, perhaps, a more general question/thought.
> > This illustrates my point. I am not advocating a discussion here on how
> to repre
Dear All,
It has been pointed out to me that the SeaDataNet NetCDF specification uses
'sea_water_pressure' as the Standard Name in cases where pressure is used as
the z co-ordinate in observational data such as CTD profiles. The definition
for this Standard Name is:
the pressure that exists i
Dear John
> But by main issue is that in Example 7.8 the "time" data entered in
> the file is still described as having units "days since 1960-1-1"
> which really isn't so. It is equally logically "days since 1991-1-1".
> In reality it's just "days since Jan 1 of any year".
Yes.
> This conventio
