This message came from the CF Trac system. Do not reply. Instead, enter your
comments in the CF Trac system at http://kitt.llnl.gov/trac/.
#107: CF Data Model 1.7
-----------------------------+------------------------------
Reporter: markh | Owner: cf-conventions@…
Type: task | Status: new
Priority: medium | Milestone:
Component: cf-conventions | Version:
Resolution: | Keywords:
-----------------------------+------------------------------
\
\
\
\
\
\
Comment (by markh):
A posting on behalf of my colleague:
Jim,
I am not able to post directly to the mailing list and Trac system, but I
actually liked the word 'measurement' even though this invokes the idea of
observations.
You all are talking about an abstract conceptual model, and the
distinction between an 'ob' and a NWP field value is not as great as
Jonathon seems to imply. There are many NWP products for customers that
are 'virtual forecast obs'. There are two distinct aspects: the generating
process and the topological structure of the data. It seems to me that you
are discussing the value and its relationship to the immediately
surrounding grid points, which is surely part of the second aspect.
In the underlying conceptual model, METCE, created by WMO and OGC, led by
Jeremy Tandy, all forecasts are considered estimates (measurements!) of an
underlying theoretical value.
Also NetCDF is used to represent observations on a regular grid - these
are usually called images, though this is sometime misleading too.
Can I suggest the wording:
The 'cell methods construct' describes the methods by which the data
values of the 'field construct' are derived from a source estimation field
(which may or may not be represented by an existing 'field construct').
HTH, Chris
\
\
\
--
Ticket URL: <http://kitt.llnl.gov/trac/ticket/107#comment:75>
CF Metadata <http://cf-convention.github.io/>
CF Metadata
This message came from the CF Trac system. To unsubscribe, without
unsubscribing to the regular cf-metadata list, send a message to
"[email protected]" with "unsubscribe cf-metadata" in the body of your
message.
