[CF-metadata] station name and ID

[Ateljevich, Eli@DWR]

I have scalar time series from USGS and NOAA, both of which use an integer code 9414290 and a readable name "San Francisco, CA".

Any suggestions how to list them both and which is preferred for timeseries_id? Can anyone give me an example of what typically goes in "station_info", something that is in many of the examples but not with any kind of serious content ... the examples are just "any kind of station info".

Thanks. I realize there must be a standard answer or example, but I can't seem to find them.

[Kyle Wilcox]

I would encourage you to follow the NCEI NetCDF templates:
http://www.nodc.noaa.gov/data/formats/netcdf/v2.0/index.html

Post by Ateljevich, ***@DWR
I have scalar time series from USGS and NOAA, both of which use an integer
code 9414290 and a readable name “San Francisco, CA”.
Any suggestions how to list them both and which is preferred for
timeseries_id? Can anyone give me an example of what typically goes in
“station_info”, something that is in many of the examples but not with any
kind of serious content 
 the examples are just “any kind of station info”.
Thanks. I realize there must be a standard answer or example, but I can’t
seem to find them.
_______________________________________________
CF-metadata mailing list
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata

[Ateljevich, Eli@DWR]

Thanks Kyle. I’m happy taking guidance from this template, but the time series example there seems very dense. It is far more complex than the NOAA NDBC data I’ve worked with and yet provides no simple answers to my questions about the station number and name. Either 9414290 or San Francisco is the name of a shack and so probably insufficient to uniquely define the data set without additional specification of a variable or instrument. Is there an example (header is fine) of how this might be applied to simple PORTS data?



From: Kyle Wilcox [mailto:***@axiomdatascience.com]
Sent: Monday, November 07, 2016 6:38 AM
To: Ateljevich, ***@DWR; cf-***@cgd.ucar.edu
Subject: Re: [CF-metadata] station name and ID

I would encourage you to follow the NCEI NetCDF templates: http://www.nodc.noaa.gov/data/formats/netcdf/v2.0/index.html

On Wed, Nov 2, 2016 at 12:30 AM Ateljevich, ***@DWR <***@water.ca.gov<mailto:***@water.ca.gov>> wrote:
I have scalar time series from USGS and NOAA, both of which use an integer code 9414290 and a readable name “San Francisco, CA”.

Any suggestions how to list them both and which is preferred for timeseries_id? Can anyone give me an example of what typically goes in “station_info”, something that is in many of the examples but not with any kind of serious content 
 the examples are just “any kind of station info”.

Thanks. I realize there must be a standard answer or example, but I can’t seem to find them.
_______________________________________________
CF-metadata mailing list
CF-***@cgd.ucar.edu<mailto:CF-***@cgd.ucar.edu>
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata

[Aaron Sweeney - NOAA Affiliate]

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: [phone], Fax: [phone]

DISCLAIMER: The contents of this message are mine personally and do not
necessarily reflect any position of NOAA.

[Ateljevich, Eli@DWR]

Great example. Thanks this clears up a lot of my questions.

From: Aaron Sweeney - NOAA Affiliate [mailto:***@noaa.gov]
Sent: Thursday, November 10, 2016 10:55 AM
To: CF Metadata List; Ateljevich, ***@DWR
Subject: Re: [CF-metadata] station name and ID

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: [phone], Fax: [phone]

DISCLAIMER: The contents of this message are mine personally and do not necessarily reflect any position of NOAA.