DNET Naming Convention

File naming convention


The individual elements that make up the naming convention are described in detail below. First of all however it is important that you consider the following points

  1. All terms in the filename should be upper case apart from the file ending which should be lower case
  2. An underscore is used to separate the different ‘elements’ of the filename. An underscore should therefore not be used elsewhere within the filename
  3. Do not use illegal characters within a filename, e.g. / ? < > : * | ” as well as a ‘space’.
  4. The file naming convention has been constructed to balance the amount of useful detail in the name, the need to ensure file uniqueness, as well as to keep the filename as short as possible.
  • DNET: Official HIE facility code to represent data sourced from the DroughtNet facility (all data from the DroughtNet facility should be prefixed by use of the code ‘DNET’).
  • Experiment: Which of the official DNET experiments this data file is associated with, e.g. ‘TEMP’ (‘Temperature’ experiment). In the event that the data was from an automated sensor, ‘AUTO’ is used for the experiment code
  • PLOT: Which plot(s) data has been sourced from. This can include data sourced from a single DNET plot (using P followed by the 2 digit plot number, e.g. P02, P08, P15) or from multiple plots (using PM – details about which chambers are included will be included in the file metadata).
  • VARIABLE COLLECTION CODE: A collection code that represents a particular grouping of variables contained within a file. A list of variables contained within different variable collection codes can be found in the ‘Variable Collection Codes’ section below.
  • DATA PROCESSING: The level of post-processing operated on the data. The definitions of the different levels of post-processing can be found below.
  • DATE or DATERANGE: The date range which a dataset covers (for automated timeseries data for example) or the single date on which a sample, for example, was taken. Note that dates are in the YYYYMMDD format (with a hyphen used to split the start and end date of a date range).
  • VERSION: An optional version number of the form _Vx. This can be utilised when a new version of a file already existing within HIEv has been updated/corrected (maintaining the same data processing level).
  • extension: The format of the data file, e.g. .csv, .dat (for toa5 data) etc.


  • A dataset containing tree diameters and heights, measured between 2013-3-19 and 2013-12-24 on all plots. Data have not been thoroughly quality checked, but some checking has been done after data entry. (the version number is optional and I have omitted it here).


  • A dataset containing spot measurements of leaf gas exchange on 8 October 2013 on plot 9 only. The data are raw and have not been quality checked.


Data Processing Codes

The meanings of the different data processing codes used in WTC filenames are as follows:

  • R (Raw Data): Data that has been directly extracted from an instrument and that has not been subjected to any data cleaning or postprocessing
  • L1 (Level One Data): Data that has been cleaned and processed, but in a cursory manner. Some erroneous data may be included.
  • L2 (Level Two Data): Data that has been rigorously cleaned, processed, and checked for quality control.
  • L3 (Level Three Data): Archive of published datasets.

Collection codes

Please edit the table as you see fit! This is a quick draft.

Collection code Description
TREEMEAS Periodic tree height and diameter measurements
SPOTGAS Leaf gas exchange campaigns, including spot measurements.
ACIGAS Leaf A-Ci curves.
BIOMASS All biomass or related measurements, including final harvest biomass, SLA measurements, leaf counting
SOILS Soil chemistry, soil respiration, etc.
TDL Any tuneable diode laser related measurements.
MICROMET Any data related to micro-meteorology related measurements, including PAR and LAI.