JET2000 filenaming convention

The format of the file names is as follows:

Each of the components of the filename are described below

Components of filename

• Platform prefix

  The prefix identifies the site or platform for the observation.

  Allowed values:

  Value	Description
  meteosat	Meteosat
  avhrr	ARHRR
  he	Hercules C-130
  rs	Radiosondes
  synop	surface synoptic station

• Type sufix

  Identifies the site or observation subtype.

  Allowed values:

  Value	Description
  .*	Observation subtype. Any value is excepted, but this should be asc, cns, fs1, lw1, ps1, rad, tmp, tw1, wnd, wv1, etc for aircraft measurements; ds001, ds002, ds003, etc for dropsondes; HHMM_[view] for meteosat images (e.g. 0600_d8 for 06:00 African thermal IR image); [WMO number]_[hour]z for radiosondes and synoptic stations (e.g. 65503_00z); and ndvi for avhrr data.

• Start date

  The eight character date identifies the start date of the observations in the file. The start date is in the format YYYYMMDD. The observations may span more than one day. The date in the file name is always the start date of the observations.

  e.g. '19990110' represents 10th January 1999

• Type

  Type should be used to describe the type of measurement in the file. It can be given any value, however it should adhere to the following guidelines.
  1. It should be descriptive. "time" or "temp" not "t".
  2. It should be as short as possible. Remember, this is just the filename other info is contained in the file. e.g "o3" not "ozone_from_visala_ozonesonde"
  3. It should be distinct. If you are going to submit a number of files per day of this kind then they cannot have the same type. e.g. "sonde01", ..., "sonde12" not "sonde".

• Extension

  Extension gives the format of the data.

  Allowed values:

  Value	Description
  na	Nasa-Ames file
  txt	free form metadata file
  jpg	JPEG image file
  gif	GIF image file
  hdf	HDF file