From Ocean Teacher Library

GTSPP file naming convention

Contents 1 GTSPP file naming 2 Reference 3 Subsections of this Article 4 Information about this article 5 Contact

GTSPP file naming

The GTSPP NetCDF filenames can be up to 255 characters in length and are composed of four fields separated by „_‟ (underscore) characters. The filenames always begin with „gtspp‟ to indicate the data files are produced by the GTSPP and end with an extension of „.nc‟ to indicate they are stored in the NetCDF format. All filenames are lowercase and can be a combination of letters and numbers. The NetCDF file name format is:

                 gtspp_<station_identification>_<data_type>_<q_pos><q_date_time><b_record>.nc

All six (6) fields are mandatory and must conform to the following contents:

1. gtspp: Name of the programme
2. <station_identification>: GTSPP continuously managed database identification number
3. <data_type>: list of data type codes (two alphabetical letters) from the GTSPP data type reference table.
4. <q_pos>: Position Quality Flag,
5. <q_date_time>: Date-Time Quality Flag, and
6. <b_record>: Best Quality Flag.

As an example, a data file with filename of “gtspp_11741662_te_111.nc”, indicates itself:

1. “gtspp” : a GTSPP data,
2. “11741662”: derived from the GTSPP CMD database identification number,
3. “te”: the data type is TESAC message,
4. “1”: the position quality code of the record is “1”, ,
5. “1”: the date-time quality code of the record is „1‟, and
6. “1”: the best quality flag of the record is „1‟.

Reference

Global Temperature and Salinity Profile Programme (GTSPP). Data User's Manual, First Edition, 2011

Subsections of this Article

No subsections available

Information about this article

Short title: GTSPP file naming convention

Description: Convention for GTSPP netCDF file naming

Expertise level: intermediate

Author: Greg Reed

Approval status: approved

Approved by: Greg Reed

Last change: 2011-12-2

Subsection of: General File-Naming Convention for Earth Science Datasets

Contact

If you have any direct comments or suggestions for the author of this page then please feel free to send an email to the author (listed above). For discussions on this page please use the discussions page.,