File Naming

Name structure: 

<instrument_name>_<platform_name>_<YYYYMM><DD>-<HH><mm><SS>_<data_product>_<option1>_<option2>_<option3>_v<version>.nc

Components:

instrument_name: name of instrument as registered with CEDA

platform_name: where or on what (in the case of ships) was the instrument deployed

Date-Time: YYYYMMDD-HHmmSS

Example:

for a file containing 1 years (YYYY) worth of data: 2016,

for a file containing 1 months (MM) worth of data: 201604,

for a file containing 1 days (DD) worth of data: 20160401,

for a file containing 1 hours (HH) worth of data: 2016040109,

for a file containing 1 minutes (mm) worth of data: 201604010950,

for a file starting at a specific time - for example launch time of soundings: 20160401095059.

data-product: name of the defined data product

option1, option2 & option3: these are optional extras providing more information to the user.

version: version of the data set n.m: n - major revision integer, m - minor revision integer

Examples:

ncas-aws-1_ral_29001225_surface-met_30m_v0.1.nc

ncas-lidar-dop-1_ral_29001225_aerosol-backscatter-radial-winds_fixed_co_advanced_v0.1.nc

When deployed on FAAM aircraft

The exception to the above file naming rules occurs when AMOF instrumentation is deployed on the FAAM aircraft. In this case and in this case only the file naming protocol developed by FAAM is adopted. This ensures clarity and ease of use to the FAAM user community.

 Consider the deployment of the HVPS3 (associated data product is particle-size-distribution ) on the FAAM aircraft and involved in flight c174 that occured on 23rd May 2019. In this case the resultant file ould be:

ncas-hvps3-1_faam_20190523_v001_r0_c174_particle-size-distribution.nc

<instrument-name>_<platform-name>_<YYYYMMDD>_<version>_<revision number>_<FAAM flight number>_<data product>.nc

Platform The second field (the platform name) must be faam for data collected aboard the FAAM aircraft.

The version number v# (lower case v followed by an 3-digit integer greater than or equal to 0) is the version number of the processing software v001 stands for the initial version. This was first introduced in June 2007 when the processing software was transferred to a LINUX system. Not all file types include this number.

The revision number r# (lower case r followed by an integer greater than or equal to 0) is the revision of the flight constants (eg improved calibrations constants). r0 stands for the initial version, r1 for the first revision, etc.

The flight number fxxx is the flight number. It is made of a lower case letter followed by a 3-digit integer. For example, all FAAM flights from March to October 2004 are numbered b001 to b056.