Randy, Then you are free! Whatever scheme that you develop won't be a "CF" scheme (at least not for now), but all you have to do is avoid violating CF with what you do. If what you develop seems robust and general, you may end up being the parent of a new CF convention.
Grace and peace, Jim Jim Biard Research Scholar Cooperative Institute for Climate and Satellites Remote Sensing and Applications Division National Climatic Data Center 151 Patton Ave, Asheville, NC 28801-5001 jim.bi...@noaa.gov 828-271-4900 On Apr 11, 2012, at 9:52 AM, Randy Horne wrote: > > Folks: > > The GOES-R system will be generating a lightning detection product. > > This product has multiple data variables that have relationships that do not > appear to be captured with the CF "cell" or "ancillary data" constructs. > > For example, there is a one data variable that is a result of measuring the > environment (i.e. lightning events), and there is another data variable > (lightning event groups) that is calculated from the first data variable. > > The relationship between the two data variables is not one to one, Rather, > it is one to many. For example, a lightning event group is a computational > aggregation of one or more lightning events. > > One of the requirements of this lightning detection product is to capture the > relationship between specific lightning events and lightning event groups. > > There does not appear to be any CF compliant mechanism to handle this > situation. > > > very respectfully, > > randy > > ____________________________________ > > Randy C. Horne (rho...@excaliburlabs.com) > Principal Engineer, Excalibur Laboratories Inc. > voice & fax: (321) 952.5100 > url: http://www.excaliburlabs.com > > > > > _______________________________________________ > CF-metadata mailing list > CF-metadata@cgd.ucar.edu > http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
_______________________________________________ CF-metadata mailing list CF-metadata@cgd.ucar.edu http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
