MetadataConventions for post-processed aircraft based data files.
I have drawn on the following documents, which are netCDF-centric, but should apply to any data format.
- netCDF Best Practices
- CF Conventions
- Unidata Observation Conventions (Draft)
- Unidata Data Discovery Conventions (Draft)
I've only made a guess at the required/recommended/optional field.
Identifies this file to follow our conventions.
Something to describe the dataset
Specifies where the original data was produced.
The method of production of the original data. "Aircraft". Do we prefer "Platform"?
cdm_datatype = "Trajectory"
we choose to follow UnidataObsConvention
description of variable
if a name exists for this parameter
instrument source for this measurement
Global attributes for Data Discovery
Do we recommend the DataDiscovery Draft above?
There are several reasons for the need of variable data discovery:
- Variable names can be cryptic.
- There can be multiple measurements of the same type.
- Automation - Software which wants to find its way into a file. Any track plot or SkewT program should be able to open a file and produce their image without user intervention.
I talked with Jon Caron about the variable discovery.
- He suggested that CF conventions prefer one variable name per attribute, instead of a list of variables in one attribute.
- After more discussion we thought reversing the "standard_names" to list the variables at the global level was a good way to do it.
He suggested using a colon to add a namespace feel, so that all these attributes looked similar (if we liked).
This is true airspeed
This is true heading
Sample netCDF. I added the "reference" as an example namespace.