NetCDF Utilities Metadata Handling
Introduction
There are a many netCDF utilities that can generate new data products from existing ones. In the process, they may or may update the metadata attributes so that they are not misleading in the new product. (This applies to metadata attributes from any convention. While a given utility can't possibly understand all conventions, it should not be passing attributes from unaltered from an existing document to a newly generated one, unless it knows the attribute remains valid.)
Other utilities may analyze an existing netCDF file and report information about it. (Here we are considering local applications or libraries distributed to the community, not individual deployed web services.)
This page defines the metadata handling status of those utilities.
Key
- Contact: The person or other contact point to ask questions/propose changes about the software.
- Metadata update mode: What software does with existing metadata attributes when writing new file; one of 'update', 'delete', or 'copy'
- Writes history info: Does the software update the history attribute as recommended?
- Proposal(s): Text details of changes proposed for this software
Table of Data Product Utilities
| Utility Name | Version | Contact | Metadata update mode | Writes history info | Proposal(s) |
|---|---|---|---|---|---|
| LAS | version | contact | mode | history | proposal |
| THREDDS | version | contact | mode | history | proposal |
| HYRAX | version | contact | mode | history | proposal |
| ERRDAP | version | contact | mode | history | proposal |
| name | version | contact | mode | history | proposal |
Table of Analysis Utilities
| Utility Name | Version | Contact | Metadata analysis mode | Proposal(s) |
|---|---|---|---|---|
| ncISO | version | contact | mode | proposal |
| ncdump | version | contact | mode | proposal |
| name | version | contact | mode | proposal |
| name | version | contact | mode | proposal |
| name | version | contact | mode | proposal |
