Welcome to TERN Knowledge Base

Field Data Filenaming Convention

The TERN file naming convention, used for instrument files collected in the field, has been adapted from the JRSRP convention, used for satellite data.  This documentation is derived from the documentation for that convention.

The naming structure is as follows:



'What' refers broadly to what data it is, and is structured as 3 fields, each of 2 characters. They are:

sensor category

code referring to the type of sensor used to capture the data, e.g. dc = digital camera


which 'instrument' was used with the sensor, e.g. hm = hemispheric lens


which product, e.g. re = reflective


'Where' gives a unique identification of the location of the data collection site. Typically, field based data sets are located as a point location. The form of the location is in longitude and latitude to 5 decimal places. 


'When' gives the date of the data acquisition. For most data this refers to the date of the site visit as year/month/day (yyyymmdd) in local time. 


This component captures two pieces of information about what has been done with the data. The first 3 characters are the processing stage. The remaining 2 characters give the data projection information.

Optional Components

Optional components can be added after the four main components, also using the '_' to separate them. Since they are optional, they need to be tagged so we can tell what they represent. The first character of any component after the fourth will be a tag character to identify what sort of field we are talking about, and the rest of it will be its value. 


The suffix is defined here as being whatever comes after the FIRST dot in the filename, allowing for complex suffixes.




Provide your feedback about the experience with Knowledge base