CF-NETCDF.NC: Difference between revisions

Revision as of 11:01, 5 March 2016

Basic Information

File-Type

cf-netcdf.nc

File-Form

UNFORMATTED

Version

March 2016

Description-Date

March 2016

Significance of the File

BAW instance of a NetCDF file.
NetCDF conventions, used to store BAW specific data, are documented in detail in the NetCDF-Pages of BAW-Wiki.
Basic metadata according to CF Metadata Conventions.
I.e. extensions for unstructured grids based on Unstructured Grid Metadata Conventions for Scientific Datasets.
Since May 2011 NetCDF-4/HDF5 is supported (see Unidata, NetCDF).

File-Contents (in Catchwords)

header with metadata:
1. list of dimensions (name and length),
2. list of variables (name, type and dimension(s)) for which data are stored in the file,
3. attributes related to variables (long_name, units etc.), and
4. global attributes (title, history etc.).
Remark: the names of attributes as well as standard variable names should be chosen according to the following given conventions:
- CF Metadata Conventions, and
- Unstructured Grid Metadata Conventions for Scientific Datasets.
data for all variables stored in the file:
1. coordinate-variable data,
2. data for ordinary variables, for which only one data record is stored in the file, and finally
3. data for record-variables (which have one unlimited dimension, e.g. time), which can be stored several times.

READ performance for large CF-NetCDF data files may strongly depend on the inner structure of the data file. The size of a data block (or chunk) which is accessed by one READ is significant in this context. A file can be considered as well structured if time series access as well as spatial access can be executed with similar effort (number of READs required). This can be achieved using appropriate chunk sizes for the variables stored. More informations can be found here:

Programs using this Type of File

ArcGIS, DATACONVERT, GRIDCONVERT, NCAGGREGATE, NCANALYSE, NCAUTO, NCDELTA, NCPLOT, NetCDF Operators, QUICKPLOT, TAYLORDIAGRAM, UNK, UNTRIM2, UNTRIM2007

Example-File

$PROGHOME/examples/lib/l_grid/lg.all_CF-NetCDF_Info.nc
$PROGHOME/examples/lib/h_grid/g05-Content.CF-NetCDF.nc
$PROGHOME/examples/lib/h_grid/UNTRIM-Content.CF-NetCDF.nc
$PROGHOME/examples/lib/h_grid/UTRSUB-Content.CF-NetCDF.nc
$PROGHOME/examples/lib/p_grid/profil05-Content.CF-NetCDF.nc
$PROGHOME/examples/lib/io_insel/insel.netcdf-cf.nc
$PROGHOME/examples/lib/k_model/2D.int.HPA.2d-hn-md.3h.xe.nc

back to: File Descriptions

Overview

@@ Line 2: / Line 2: @@
 |name_de=CF-NETCDF.NC
 |filetype=cf-netcdf.nc
-|version=September 2015
+|version=March 2016
-|version_descr=November 2015
+|version_descr=March 2016
 |significance=
 * BAW instance of a [[NETCDF.CDF|NetCDF]] file.
 * NetCDF conventions, used to store BAW specific data, are documented in detail in the [[NetCDF|NetCDF-Pages of BAW-Wiki]].
-* CF compliance verified using the [http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl NCAS ''CF Compliance Checker''].
+* Basic metadata according to [http://cfconventions.org ''CF Metadata Conventions''].
+* I.e. extensions for unstructured grids based on [http://ugrid-conventions.github.io/ugrid-conventions/ ''Unstructured Grid Metadata Conventions for Scientific Datasets''].
 * Since May 2011 NetCDF-4/HDF5 is supported (see [http://www.unidata.ucar.edu/software/netcdf/ Unidata, NetCDF]).
 |filecontents=
@@ Line 16: / Line 17: @@
 ## '''global attributes''' ('''title, history''' etc.).
 #:Remark: the names of attributes as well as standard variable names should be chosen according to the following given conventions:
-#:* [http://cf-convention.github.io/ ''NetCDF Climate and Forecast (CF) Metadata Convention''], and
+#:* [http://cfconventions.org ''CF Metadata Conventions''], and
-#:* [http://www.nodc.noaa.gov/data/formats/netcdf/v1.1/ ''NODC NetCDF Template Guide''].
+#:* [http://ugrid-conventions.github.io/ugrid-conventions/ ''Unstructured Grid Metadata Conventions for Scientific Datasets''].
 # '''data''' for all variables stored in the file:
 ## '''coordinate-variable''' data,