|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| − | {{WCS Glossary
| |
| − | |Glossary Domain=WCS
| |
| − | |TermDesc=CF-netCDF is the Climate and Forecast Metadata Convention for NetCDF Files. Names in NetCDF don't have any meaning associated in them, [[CF Conventions]] standardizes the semantic meaning of names, and physical dimensions. CF-netCDF files can be read with semantic meaning associated to the data.
| |
| − | |Links=[[CF Conventions]] [[Data_Configuration_for_Cubes|Data Configuration for Cubes]]
| |
| − | }}
| |
| − | NetCDF file format contains four kinds of information:
| |
| | | | |
| − | * Global attributes
| + | This spelling is obsolete. Please go to [[CF-netCDF]] |
| − | ** Simple name=value pairs
| |
| − | | |
| − | * Dimensions
| |
| − | ** Only declares the length of the dimension
| |
| − | ** Contains no dimension data.
| |
| − | | |
| − | * Variables
| |
| − | ** Array data with any number of dimensions.
| |
| − | ** Zero dimensions meaning scalar data.
| |
| − | | |
| − | * Variable Attributes:
| |
| − | ** Simple name=value pairs associated to a variable.
| |
| − | | |
| − | While these are enough to describe any data, it's not easy to interpret what the data actually means. What is self-evident for humans is difficult for a computer program to reason. If you have a NetCDF viewer, it should be possible just open the file and display the data on a geographic map. But making a program that can automatically get the geographic dimensions from a NC file, is very difficult.
| |
| − | | |
| − | Conventions come to rescue. CF Standardizes many things:
| |
| − | | |
| − | * Standard name: what is the measure data about
| |
| − | * Units
| |
| − | * How to tell, that a variable is one of the following:
| |
| − | ** Data Variable, containing real data.
| |
| − | ** Dimension Coordinate Variable, containing dimension coordinates.
| |
| − | ** Dimension Bounds Variable, containing lower and upper bounds of a dimension coordinate.
| |
| − | * Projection
| |
| − | | |
| − | With this part standardized, your program can list the data variables for you and tell you exactly what you can filter by.
| |
| − | | |
| − | Links:
| |
| − | | |
| − | CF 1.0 - [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.5/cf-conventions.html 1.5] contain conventions for cube data and 1.5 contains some station data.
| |
| − | | |
| − | [https://cf-pcmdi.llnl.gov/trac/wiki/PointObservationConventions Unofficial CF-1.5] contains point data encoding. '''Expired certificate''', add security exception. | |
| − | | |
| − | [http://www.cfconventions.org/ CF Conventions]
| |
| − | | |
| − | [http://www.unidata.ucar.edu/software/netcdf/conventions.html NetCDF Conventions]
| |
| − | | |
| − | [http://www.unidata.ucar.edu/software/netcdf/ Unidata NetCDF documentation]
| |
| − | | |
| − | [http://wiki.esipfed.org/index.php/Creating_NetCDF_CF_Files Creating NetCDF CF Files]
| |
| − | [[Category:Cube]][[Category:Server]]
| |
