-
Notifications
You must be signed in to change notification settings - Fork 1
Real Time File Description
netCDF file
CF 1.6 Discrete Sampling Geometry (Trajectory)
Attribute Conventions for Dataset Discovery (link)
Main objective is aggregation of these files for web service distribution via THREDDS Data Server.
The Global Attributes that are included in the real time glider files are listed and defined below. Many of the attributes are taken from the Attribute Conventions for Dataset Discovery. (NOTE: there is a new host for this convention as of 2013-05-08; V1.0a and the working document) Additional global attributes are taken from the IMOS/ANFOG glider file format version 3.1. Finally, additional attributes were added based on discussions in the IOOS glider community.
- acknowledgement
- A place to acknowledge various type of support for the project that produced this data.
- cdm_data_type
- The THREDDS data type appropriate for this dataset.
- comment
- Miscellaneous information about the data.
- contributor_name
- The name and role of any individuals or institutions that contributed to the creation of this data.
- contributor_role
- creator_email
- creator_name
- The data creator's name, URL, and email. The "institution" attribute will be used if the "creator_name" attribute does not exist.
- creator_url
- date_created
- The date on which the data was created.
- date_issued
- The date on which this data was formally issued.
- date_modified
- The date on which this data was last modified.
- geospatial_bounds
- Describes geospatial extent using any of the geometric objects (2D or 3D) supported by the Well-Known Text (WKT) format.
- geospatial_lat_max
- The values of geospatial_lon_min and geospatial_lon_max reflect the actual longitude data values. Cases where geospatial_lon_min is greater than geospatial_lon_max indicate the bounding box extends from geospatial_lon_max, through the longitude range discontinuity meridian (either the antimeridian or Prime Meridian), to geospatial_lon_min.
- geospatial_lat_min
- Describes a simple latitude/longitude bounding box. geospatial_lat_min specifies the southernmost latitude; geospatial_lat_max specifies the northernmost latitude; geospatial_lon_min specifies the westernmost longitude; geospatial_lon_max specifies the easternmost longitude of the bounding box.
- geospatial_lat_resolution
- geospatial_lat_units
- Further refinement of the geospatial bounding box can be provided by using these units and resolution attributes.
- geospatial_lon_max
- geospatial_lon_min
- For a more detailed geospatial coverage, see the suggested geospatial attributes.
- geospatial_lon_resolution
- geospatial_lon_units
- geospatial_vertical_max
- geospatial_vertical_min
- Describes a simple vertical bounding box. For a more detailed geospatial coverage, see the suggested geospatial attributes.
- geospatial_vertical_positive
- geospatial_vertical_resolution
- geospatial_vertical_units
- history
- Provides an audit trail for modifications to the original data.
- id
- The combination of the "naming authority" and the "id" should be a globally unique identifier for the dataset.
- institution
- keywords
- A comma separated list of key words and phrases.
- keywords_vocabulary
- If you are following a guideline for the words/phrases in your "keywords" attribute, put the name of that guideline here.
- license
- Describe the restrictions to data access and distribution.
- naming_authority
- platform
- The platform attribute contains a pointer to one or more platform container variables which describe the attributes of the entire glider.
- processing_level
- A textual description of the processing (or quality control) level of the data.
- project
- The scientific project that produced the data.
- publisher_email
- publisher_name
- The data publisher's name, URL, and email. The publisher may be an individual or an institution.
- publisher_url
- standard_name_vocabulary
- The name of the controlled vocabulary from which variable standard names are taken.
- summary
- A paragraph describing the dataset.
- time_coverage_duration
- time_coverage_end
- time_coverage_resolution
- time_coverage_start
- Describes the temporal coverage of the data as a time range.
- title
- A short description of the dataset.
The following examples show how this would be used for each of the three primary glider types [spray|seaglider|slocum]:
Spray e.g.:
platform:"spray"which would point to a dimensionless platform container variable called spray such as
int spray
spray:wmo_id = "sp111" ;
spray:comment = "Spray Glider sp111" ;
spray:id = "sp111" ;
spray:long_name = "Spray Glider sp111" ;The following list specifies the 4 file types which will be accepted by the IOOS National Glider Data Acquisition Center and the proposed naming conventions for each:
- glider-SN_yyyymmddTHHMMSS_rt0.nc: Real-time data with no QC. This is the minimum processing level accepted by the DAC and contains the raw data values with no operator provided quality control.
- glider-SN_yyyymmddTHHMMSS_rt1.nc: Real-time data with operator provided QC
- glider-SN_yyyymmddTHHMMSS_delayed0.nc: Delayed-mode data with no QC
- glider-SN_yyyymmddTHHMMSS_delayed1.nc: Delayed-mode data with operator provided QC
where
- glider: Identifying name or type abbreviation for the glider
- SN: vehicle serial number as provided by the manufacturer
- yyyymmddTHHMMSS: [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) formatted date representing the start time of the data acquisition
- 'rt' or 'delayed': string specifying real-time (during deployment) or delayed mode (post-recovery) data acquisition
- 0 or 1: quality control level where 0 corresponds to none and 1 corresponds to some level of operator applied quality control
Ideally, the glider-SN_yyyymmddTHHMMSS_rt1.nc files will be provided by the individual operators during the deployment and the glider-SN_yyyymmddTHHMMSS_delayed1.nc files will be provided after the glider has been recovered and the full data set processed. It is expected that all files containing operator QC'd data will provide the appropriate VARIABLE_qc variables with corresponding attributes from the CF specification.
Trajectory
QC Codes
Platform Types