Jonathan: We are putting in fill values for these off-earth points in the data variables.
very respectfully, randy Randy C. Horne ([email protected]) Principal Engineer, Excalibur Laboratories Inc. voice & fax: (321) 952-5100 url: http://www.excaliburlabs.com PGP Public Keys available at: A HREF="http://pgpkeys.mit.edu:11371";>MIT's Key Server</A> ---------- Original Message ---------------------------------- From: Jonathan Gregory <[email protected]> Date: Mon, 26 Mar 2012 18:35:19 +0100 >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 at non-existent >points? > >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 allow you to have missing data in Z; it permits missing >data in coordinates only where the data is also missing. > >I suppose that the pressure information is actually data in the raw obs >dataset. It would be legal to keep it in the file but not identify it as an >auxiliary coordinate variable (in the coordinates attribute). Then it would >be fine to having missing data in it. Would that be significantly less >convenient? Just a thought. > >Cheers > >Jonathan >_______________________________________________ >CF-metadata mailing list >[email protected] >http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata > ..............End of Message ...............................--> _______________________________________________ CF-metadata mailing list [email protected] http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
