Hi, Eli,
Here's an example for this very station:
http://www.ngdc.noaa.gov/thredds/fileServer/nos_coops/wl_1min/rawdata/9414290/9414290_20120101to20121231.nc
The value of the cf_role attribute of the timeSeries coordinate
variable is the string "timeseries_id." The allowed values are discussed
in the CF Conventions Document v1.6, section 9.5: "Coordinates and
Metadata."
<
http://cfconventions.org/cf-conventions/v1.6.0/cf-conventions.html#coordinates-metadata>
This indicates that the role of this coordinate variable is to identify or
distinguish the particular time-series, in cases where you have many
time-series in the same file. In this specific example, there is only one
(dimension of timeSeries is 1).
Regarding how to capture the station ID "9414290" and station name
"San Francisco," I've addressed these by the approach taken in the NCEI
netCDF templates to which Kyle referred you. I've defined a geophysical
variable "waterlevel_unassessed" to hold the data values. I also have a
variable "platform_info" and a variable "sensor_info" and associated or
connected these with the geophysical variable "waterlevel_unassessed" via
it's attributes "platform" and "instrument."
Please have a look at the example above for more details.
Cordially,
Aaron
--
Aaron D. Sweeney, Ph. D.
Water Level Data Manager
Cooperative Institute for Research in Environmental Sciences (CIRES)
University of Colorado at Boulder
and
NOAA National Centers for Environmental Information
*formerly NOAA's National Geophysical Data Center*
325 Broadway, E/NE42
Boulder, CO 80305-3328
Phone: 303-497-4797, Fax: 303-497-6513
DISCLAIMER: The contents of this message are mine personally and do not
necessarily reflect any position of NOAA.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cgd.ucar.edu/pipermail/cf-metadata/attachments/20161110/e631e497/attachment.html>
Received on Thu Nov 10 2016 - 11:55:02 GMT
