This question pertains to other kinds of data, including currents
from acoustic current meters and profilers.
I agree that the ancillary_variable attribute is a reasonable way to
tie these variables together; that doesn't define the relationship,
though, it just indicates that there is one. That might be the best
we can do, unless there's enough interest in this to justify adding
something - another standard name modifier? - to CF, to describe
this kind of variable.
Cheers - Nan
On 7/1/13 8:28 AM, [email protected] wrote:
Folks:
the GOES-R ground system generates a derived motion winds product.
Accompaning each wind speed & direction in the product is the amount
of error associated withe the vector. This error is not a
standard_error, but an error estimate based on a custom algorithm.
Because this is not a standard_error, it would seem that using a
standard_error standard_name modifier would be misleading.
Any thoughts on how to represent this product-specific error in the
NetCDF file ? (The best idead I could come up with so far is to
establish an ancillary data relationwhip between the wind
speed/direction variables and the error variable, and use the error
variable's long_name to describe the error)
very respectfully,
randy
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
--
*******************************************************
* Nan Galbraith (508) 289-2444 *
* Upper Ocean Processes Group Mail Stop 29 *
* Woods Hole Oceanographic Institution *
* Woods Hole, MA 02543 *
*******************************************************
_______________________________________________
CF-metadata mailing list
[email protected]
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
