On 3/26/12 1:35 PM, Jonathan Gregory wrote:
...
Regarding Nan's point, I would say that we do want CF to be inclusive. It
would be a mistake to impose irrelevant requirements that deterred people
from using the convention. In the case you mention, the chapter 9 convention
for profiles wouldn't al
Jonathan:
We are putting in fill values for these off-earth points in the data variables.
very respectfully,
randy
Randy C. Horne (rho...@excaliburlabs.com)
Principal Engineer, Excalibur Laboratories Inc.
voice & fax: (321) 952-5100
url: http://www.excaliburlabs.com
PGP Public Keys available
Hi all -
From a CDM developer perspective, an auxiliary coordinate is "just as
good" as a regular coordinate variable. The extra requirements on
coordinate variables are helpful in knowing when to optimize, eg
monotonicity allows one to efficiently find the index given the
coordinate value
Dear all
Regarding Randy's reply:
> In the case of GOES-R (and also Meteosat) our coordinate variable values are
> N/S elevation angle and E/W scanning angle, which can be syntactically valid
> values albeit off the disk of the earth.
In this case, are there data values, or is the data missing
Hi all:
From a CDM developer perspective, an auxiliary coordinate is "just as
good" as a regular coordinate variable. The extra requirements on
coordinate variables are helpful in knowing when to optimize, eg
monotonicity allows one to efficiently find the index given the
coordinate value.
I am working with satellite data, and I, for example, have timestamps that
arrive in the data stream along with sensor measurements. I can have
independent missing values in both my time variable and my measurement
variables. I want to preserve all the incoming data, and the restriction
on "true"
Hi Jonathan -
For underway CTD profiles (gliders and floats, too, I'd think) if the
pressure
sensor fails intermittently, you can approximate Z by interpolating over
time, assuming there are good values along the track. In "final" data,
we might
do that, but we might like to present raw data
Folks:
Regarding the geosync request for comment .
In the case of GOES-R (and also Meteosat) our coordinate variable values are
N/S elevation angle and E/W scanning angle, which can be syntactically valid
values albeit off the disk of the earth.
However, it is very possible that there will
Dear Nan and John
It's a good thing we're having this discussion! In my understanding, we have
always prohibiting missing data in aux coord vars, and in section 9 we
explicitly allowed for the first time. Evidently we should be clear, one way
or the other (which was one of the intentions of the de
On 3/26/2012 2:24 AM, Jonathan Gregory wrote:
Dear Ros
Regarding this requirement:
9.6 Where any auxiliary coordinate variable contains a missing value, all
other coordinate, auxiliary coordinate and data values corresponding to that
element should also contain missing values.
Appendix A note
I was unaware of this restriction on aux coordinate variables.
On 3/26/12 4:24 AM, Jonathan Gregory wrote:
Appendix A notes that missing data is allowed in aux coord vars only in the
case of discrete sampling geometries. This means the checker could regard it as
an error also if it finds any mis
Dear Ros
Regarding this requirement:
> 9.6 Where any auxiliary coordinate variable contains a missing value, all
> other coordinate, auxiliary coordinate and data values corresponding to that
> element should also contain missing values.
Appendix A notes that missing data is allowed in aux coord
12 matches
Mail list logo
