Actions

CF-NETCDF.NC: Difference between revisions

From BAWiki

imported>Spohr Susanne
mNo edit summary
(entry for NCMERGE added)
 
(33 intermediate revisions by 7 users not shown)
Line 2: Line 2:
|name_de=CF-NETCDF.NC
|name_de=CF-NETCDF.NC
|filetype=cf-netcdf.nc
|filetype=cf-netcdf.nc
|version=March 2011
|version=April 2018
|version_descr=March 2011
|version_descr=March 2020
|significance=
|significance=
BAW instance of a [[NETCDF.CDF|NetCDF]] file.<br />
* BAW instance of a [[NETCDF.CDF|NetCDF]] file.
All NetCDF conventions, which are relevant to store the typical BAW-specific data, are
* NetCDF conventions, used to store BAW specific data, are documented in detail in the [[NetCDF|NetCDF-Pages of BAW-Wiki]].
documented in detail in the [[NetCDF|NetCDF-Pages of BAW-Wiki]].  
* 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=
|filecontents=
# '''header with metadata:'''
# '''header with metadata:'''
Line 15: Line 17:
## '''global attributes''' ('''title, history''' etc.).  
## '''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:
#:Remark: the names of attributes as well as standard variable names should be chosen according to the following given conventions:
#:* [http://cf-pcmdi.llnl.gov/ ''NetCDF Climate and Forecast (CF) Metadata Convention''], and
#:* [http://cfconventions.org ''CF Metadata Conventions''], and
#:* [http://cf-pcmdi.llnl.gov/documents/cf-standard-names/standard-name-table/15/cf-standard-name-table.html ''CF Standard Name Table''].
#:* [http://ugrid-conventions.github.io/ugrid-conventions/ ''Unstructured Grid Metadata Conventions for Scientific Datasets''].
# '''data''' for all variables stored in the file:
# '''data''' for all variables stored in the file:
## '''coordinate-variable''' data,
## '''coordinate-variable''' data,
## data for ordinary''' variables''', for which only one data record is stored in the file, and finally
## data for ordinary''' variables''', for which only one data record is stored in the file, and finally
## data for '''record-variables''' (which have one unlimited dimension, e.g.''' time'''), which can be stored several times.  
## data for '''record-variables''' (which have one unlimited dimension, e.g.''' time'''), which can be stored several times.
|nutzerprogramme=[[ArcGIS: Import data from CF-NetCDF file|ArcGIS]], [[GRIDCONVERT]]
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: 
# [http://www.unidata.ucar.edu/blogs/developer/en/entry/chunking_data_why_it_matters ''Chunking Data: Why it Matters''], and
# [http://www.unidata.ucar.edu/blogs/developer/en/entry/chunking_data_choosing_shapes ''Chunking Data: Choosing Shapes''].  
|nutzerprogramme=[[ArcGIS: Import data from CF-NetCDF file|ArcGIS]], [[DATACONVERT]], [[DISPLAY_PERCENTILES]], [[GRIDCONVERT]], [[NCAGGREGATE]], [[NCANALYSE]], [[NCAUTO]], [[NCCHUNKIE]], [[NCCUTOUT]], [[NCDELTA]], [[NCDVAR]], [[NCMERGE]], [[NCPLOT]], [[NCRCATMAT]], [[NC2TABLE]], [[NetCDF Operators]], [[PLOTPROFILZEIT]], [[QUICKPLOT]], [[TAYLORDIAGRAM]], [[UNK]], [[UNTRIM2]], [[UNTRIM2007]]
|language=Fortran90
|language=Fortran90
|fileform=UNFORMATTED
|fileform=UNFORMATTED
|fileaccess=DIRECT
|fileaccess=DIRECT
|fileextension=.nc
|fileextension=.nc
|writemodules=$PROGHOME/fortran/lib/l_grid/*/mod_p_l_grid_ui.f90
|writemodules=
$PROGHOME/fortran/lib/l_grid/*/mod_p_l_grid_ui.f90 or<br />
$PROGHOME/fortran/lib/h_grid/*/mod_p_h_grid_ui.f90 or<br />
$PROGHOME/fortran/lib/p_grid/*/mod_p_p_grid_ui.f90 or<br />
$PROGHOME/fortran/lib/io_insel/*/mod_io_insel_ui.f90 or <br />
$PROGHOME/fortran/lib/k_model/*/mod_p_k_model_ui.f90
|readmodules= ---
|readmodules= ---
|contact_original=[mailto:guenther.lang@baw.de G. Lang], [mailto:susanne.spohr@baw.de S. Spohr]
|contact_original=[mailto:guenther.lang@baw.de G. Lang], [mailto:susanne.spohr@baw.de S. Spohr]
|contact_maintenance=[mailto:guenther.lang@baw.de G. Lang], [mailto:susanne.spohr@baw.de S. Spohr]
|contact_maintenance=[mailto:guenther.lang@baw.de G. Lang], [mailto:susanne.spohr@baw.de S. Spohr]
|examplefile=
|examplefile=
$PROGHOME/examples/lib/l_grid/lg.all_CF-NetCDF_Info.nc
$PROGHOME/examples/lib/l_grid/lg.all_CF-NetCDF_Info.nc<br />
$PROGHOME/examples/lib/h_grid/g05-Content.CF-NetCDF.nc<br />
$PROGHOME/examples/lib/h_grid/UNTRIM-Content.CF-NetCDF.nc<br />
$PROGHOME/examples/lib/h_grid/UTRSUB-Content.CF-NetCDF.nc<br />
$PROGHOME/examples/lib/p_grid/profil05-Content.CF-NetCDF.nc<br />
$PROGHOME/examples/lib/io_insel/insel.netcdf-cf.nc<br />
$PROGHOME/examples/lib/k_model/2D.int.HPA.2d-hn-md.3h.xe.nc
}}
}}

Latest revision as of 10:45, 11 January 2022

Basic Information

File-Type

cf-netcdf.nc

File-Form

UNFORMATTED

Version

April 2018

Description-Date

March 2020

Significance of the File

File-Contents (in Catchwords)

  1. 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:
  2. 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:

  1. Chunking Data: Why it Matters, and
  2. Chunking Data: Choosing Shapes.

Programs using this Type of File

ArcGIS, DATACONVERT, DISPLAY_PERCENTILES, GRIDCONVERT, NCAGGREGATE, NCANALYSE, NCAUTO, NCCHUNKIE, NCCUTOUT, NCDELTA, NCDVAR, NCMERGE, NCPLOT, NCRCATMAT, NC2TABLE, NetCDF Operators, PLOTPROFILZEIT, 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

Retrieved from "http://wiki.baw.de/en/index.php?title=CF-NETCDF.NC&oldid=14580"