Jonathan: Thanks for taking the time to respond to my question.
The GOES-R system will be producing a hemispheric lightning detection product. It will be an array of lightning detection that occur within some number of seconds across the western hemisphere (i.e. it is not a gridded product). A lightning detection has a center location, and needs to be associated with an area and an interval of time. In the vein of maximizing the use of existing CF conventions: (1) Classify the data variable containing this array of lightning detections as a featureType of point. (2) Use the cell bounds construct to capture the time interval. (3) Use the cell cell_measures construct to capture area (i.e. :cell_measure = area: lightning_detection_area). very respectfully, randy ---------- Original Message ---------------------------------- From: Jonathan Gregory <[email protected]> Date: Mon, 9 Apr 2012 10:16:20 +0100 >Dear Randy > >> Is it CF compliant to use "cell" constructs for data having a featureType of >> "point" (i.e. no implied coordinate relationship to other points) ? > >I am not sure what you mean by cell constructs. Are you referring to >cell_methods, perhaps? That would be a good question. I think it should be >possible to use cell_methods, but it probably ought to refer to the physical >dimensions of the cell (lat, lon, time, etc.) i.e. the auxiliary coordinates, >rather than the index space. It should be the cell_methods that you would use >if you stored the data in the orthogonal multidimensional representation, >I think. > >Is that the right question? > >Best wishes > >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
