Dear Jim I would suggest storing this information as a data variable, not designating it as an auxiliary coordinate variable. It can still be identified all right in the file by its standard name.
Cheers Jonathan ----- Forwarded message from Jim Biard <[email protected]> ----- > From: Jim Biard <[email protected]> > Date: Wed, 26 Feb 2014 10:30:12 -0500 > To: CF metadata <[email protected]> > X-Mailer: Apple Mail (2.1827) > Subject: Re: [CF-metadata] How to handle a forecast model with non-monotonic > coordinate variables > > Hi. > > If my auxiliary coordinate is measured, as opposed to computed (in a > trajectory or swath, for example), I may very well have a situation where I > have measurements of data where I don?t have a measurement of location. If I > wish to preserve the data measurements, I need to able to have fill in my > auxiliary coordinate variables without fill in my data variables. How will I > handle that given the proposed limitations? > > Grace and peace, > > Jim > > Visit us on > Facebook Jim Biard > Research Scholar > Cooperative Institute for Climate and Satellites NC > North Carolina State University > NOAA's National Climatic Data Center > 151 Patton Ave, Asheville, NC 28801 > e: [email protected] > o: +1 828 271 4900 > > > > > On Feb 26, 2014, at 5:18 AM, Hedley, Mark <[email protected]> > wrote: > > >> We could modify this to: > >> "Allowed for auxiliary coordinate variables but not allowed for coordinate > >> variables. Missing data is only permitted in auxiliary coordinate > >> varirables only at points where the data variable(s) concerned has missing > >> data." > > > > I would support this, I think there are use cases where missing data at the > > 'same location' in the data array and an auxiliary coordinate array is > > valid and sensible. > > > > Rich's case is clearly valid. I have a couple more which I can illustrate > > in further detail as we pursue this requirement. > > > > mark > > > > ________________________________________ > > From: CF-metadata [[email protected]] on behalf of Signell, > > Richard [[email protected]] > > Sent: 18 February 2014 21:01 > > To: Gregory, Jonathan > > Cc: CF metadata > > Subject: Re: [CF-metadata] How to handle a forecast model with > > non-monotonic coordinate variables > > > > Jonathan, > > > > In the very last comment in ticket #85 > > (https://cf-pcmdi.llnl.gov/trac/ticket/85) you say: > > > > "In the "Description" column of Appendix A, in the entries for > > _FillValue andmissing_value, replace "Not allowed for coordinate data > > except in the case of auxiliary coordinate varibles in discrete > > sampling geometries." with "Allowed for auxiliary coordinate variables > > but not allowed for coordinate variables." > > > > This would seem to allow missing values in auxilliary coordinates for > > grid datatypes, which is what we need for the use case I presented. > > > > We could modify this to: > > "Allowed for auxiliary coordinate variables but not allowed for > > coordinate variables. Missing data is only permitted in auxiliary > > coordinate varirables only at points where the data variable(s) > > concerned has missing data." > > > > Thanks, > > Rich > > _______________________________________________ > > CF-metadata mailing list > > [email protected] > > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > > _______________________________________________ > CF-metadata mailing list > [email protected] > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata ----- End forwarded message ----- _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
