NetCDF Data
Data & ScienceNC commonly holds NetCDF dimensions, variables and attributes, but machine-control and other files may share the suffix. Identify the producer first. For NetCDF, establish units, time origin, coordinates and missing-value rules before interpreting values.
- What it is used for
- Multidimensional scientific data or other application-specific content
- What the file contains
- Producer-dependent
All sections, questions and sources
Content reviewed： · Editor：Kai
Opening steps
Choose your environment or purpose to see its steps.
Menu labels and support vary by app, OS and version. Preserve the original before making changes.
Troubleshooting by symptom
- Load failure: check NetCDF variant/support and incomplete transfer.
- Unexpected values: inspect fill values, scale/offset and units.
- Wrong times/map: check time origin/calendar, coordinate variables and dimension order.
- Cannot open: compare classic versus netCDF-4/HDF5 support.
- Huge values: inspect fill values and scale/offset decoding.
- Wrong time/map: inspect units, calendar, coordinates and axis order.
Selected NetCDF data → CSV / arrays
- Select variables/time/space ranges and document attributes/dimensions.
- Export subsets and compare units, locations, nulls and precision.
- Document variable, axes, units, calendar and subset alongside the output.
One CSV may lose dimensions/attributes; include documentation. NetCDF workflows do not convert machine-control NC.
Interpret units, missing values and packing
Inspect units, fill values and packing metadata and avoid applying decoding twice.
Source for these steps：Unidata / UCAR · NetCDF FAQ / Unidata · NetCDF Utilities / CF Conventions Community · NetCDF Climate and Forecast Metadata Conventions
Preserve time and coordinate semantics
Interpret time units/calendar and coordinate variables; grids need not be uniformly spaced.
Use applicable CF metadata and document variable, axes, units and selected range in exports.
Source for these steps：Unidata / UCAR · NetCDF FAQ / Unidata · NetCDF Utilities / CF Conventions Community · NetCDF Climate and Forecast Metadata Conventions
Related-format differences
| Format | Main role | What to check |
|---|---|---|
| NetCDF classic | Arrays/metadata | Reader support/dimensions |
| NetCDF-4 | HDF5-based storage | Library support |
| CSV / raster | Selected output | Axes/units/missing values |
Handling and security
Retain originals/attributes, subset large data and establish provenance before any equipment use.
Questions and answers
Is NC always NetCDF?
No; identify the producer.
Do numbers establish units?
Check attributes/producer documentation.
Can I rename to H5?
Renaming does not convert the data model.
Is NC a simple two-dimensional table?
It can hold multiple multidimensional variables and metadata.
Does ncdump -h print all values?
It inspects header structure; select variables/ranges for actual values.
Format facts: name, steward and MIME type
- Formal name
- NetCDF data / other NC uses exist
- Steward / specification
- Unidata / producing application
- MIME type
- Depends on the producer or server; an extension alone does not establish a MIME type.
Primary and official sources
- Project documentationNetCDF FAQ
Explains data models, file variants and official tools.
Unidata / UCAR · Link checked： - Official documentationNetCDF Utilities
Inspect format, variables and attributes with ncdump.
Unidata · Link checked： - Official documentationNetCDF Climate and Forecast Metadata Conventions
Coordinate, calendar, missing-value and packed-data conventions.
CF Conventions Community · Link checked：