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.
I've only made a guess at the required/recommended/optional field.
----
Name | Description | |
Conventions | required | Identifies this file to follow our conventions. |
title | highly recommended | Something to describe the dataset |
institution | required | Specifies where the original data was produced. |
source | required | The method of production of the original data. "Aircraft". Do we prefer "Platform"? |
project | highly recommended | |
cdm_datatype = "Trajectory" | required if | we choose to follow UnidataObsConvention |
units | required | udunits compatable? |
long_name | required | description of variable |
standard_name | highly recommended | if a name exists for this parameter |
data_quality | highly recommended | |
missing_value | highly recommended | |
valid_range | optional | |
source | optional | instrument source for this measurement |
Do we recommend the DataDiscovery Draft above?
There are several reasons for the need of variable data discovery:
I talked with Jon Caron about the variable discovery.
He suggested using a colon to add a namespace feel, so that all these attributes looked similar (if we liked).
latitude | highly recommended | |
longitude | highly recommended | |
altitude | highly recommended | |
wind_speed | recommended | |
wind_direction | recommended | |
upward_air_velocity | recommended | |
air_temperature | recommended | |
platform_speed_wrt_air | recommended | This is true airspeed |
dew_point_temperature | recommended | |
air_pressure | recommended | |
platform_roll_angle | recommended | |
platform_pitch_angle | recommended | |
platform_orientation | recommended | This is true heading |
ground_speed_east_west | recommended | |
ground_speed_north_south | recommended |
Sample netCDF. I added the "reference" as an example namespace.
:reference:latitude = "LATC" |