Common Data Format

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
m (Links)
Line 5: Line 5:
 
|mimetypes={{mimetype|application/x-cdf}}
 
|mimetypes={{mimetype|application/x-cdf}}
 
}}
 
}}
The '''Common Data Format''' (CDF) is a file format and associated APIs designed by NASA for multi-dimensional datasets. It has largely been supplanted by the (mostly unrelated, except in name) [[netCDF]].
+
The '''Common Data Format''' (CDF) is a scientific data file format and associated APIs designed by NASA for multi-dimensional datasets, and most commonly used in Heliophysics. CDF was designed and developed in 1984 by the National Space Science Data Center (NSSDC) at NASA/GSFC. CDF was originally written in FORTRAN, and rewritten in 1990 in C (version 2). In the mean time, netCDF [[netCDF]] was developed in C, based on the CDF conceptual model. Both models and existing software have matured substantially since, and share common goals. CDF libraries in Java, Python, and C++ have been developed independently, based on the Internal Formats document. Internal metadata generally follows the ISTP Metadata Guidelines [https://github.com/IHDE-Alliance/ISTP_metadata].
  
 
== Identification ==
 
== Identification ==

Revision as of 02:55, 6 December 2022

File Format
Name Common Data Format
Ontology
Extension(s) .cdf
MIME Type(s) application/x-cdf

The Common Data Format (CDF) is a scientific data file format and associated APIs designed by NASA for multi-dimensional datasets, and most commonly used in Heliophysics. CDF was designed and developed in 1984 by the National Space Science Data Center (NSSDC) at NASA/GSFC. CDF was originally written in FORTRAN, and rewritten in 1990 in C (version 2). In the mean time, netCDF netCDF was developed in C, based on the CDF conceptual model. Both models and existing software have matured substantially since, and share common goals. CDF libraries in Java, Python, and C++ have been developed independently, based on the Internal Formats document. Internal metadata generally follows the ISTP Metadata Guidelines [1].

Contents

Identification

The version 3 examples start with byte sequence CD F3 00 01, the middle ranged versions (2.6 and 2.7) begin with CD F2 60 02 and older versions 2.5 or earlier start with byte sequence 00 00 FF FF.

Specifications

Software

Sample files

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox