Operation IceBridge File Naming Conventions
This page contains information on the file naming conventions required for Operation IceBridge data files.
- File name must begin with the IceBridge data set shortname (e.g. ILATM1B). The shortname must be all capital letters.
- As a general rule, file names contain fields descriptive of the data file.
- Fields must be separated (delimited) by an underscore.
- A Date field must be included in the file name. Preferred date formats are: YYYYMMDD or YYYYDOY
Additional information should be included in the filename to uniquely identify the file and provide suitable information to data users, including:
- Time of data collection
- Version identification
- Any additional information that might be needed to uniquely identify the data file. (e.g. sensor type, platform information, etc.)
Filename example:
ILATM1B_V01_20100421_09452366_A.dat
Where:
| File Name Field | Description |
|---|---|
| ILATM1B | Data set shortname |
| V01 | Data version identifier |
| 20100421 | Date. Format YYYYMMDD. YYYY = four character year, MM = two-character month, DD = two character day |
| 09452366 | Time. Format HHMMSShh. HH = hours, MM = minutes, SS = seconds, hh = hundredths |
| A | Place holder for additional relevant information to identify the data file |
| .dat | Data file type. For example: .txt, .qi, .bin, .nc, etc. |
Table 2 provides examples of file name extensions for related files that further describe or supplement data files.
| Extensions for Related Files | Description |
|---|---|
| .premet example: ILATM1B_V01_04212010_09452366_A.premet |
File created containing metadata extracted from the data file. |
| .spatial example: ILATM1B_V01_04212010_09452366_A.spatial |
File created with longitude/latitude pairs for the creation of spatial metadata. |
| .brws example: ILATM1B_V01_04212010_09452366_A.brws |
Browse data |
| .qa example: ILATM1B_V01_04212010_09452366_A.qa |
Quality assurance information |
| .ph example: ILATM1B_V01_04212010_09452366_A.ph |
Product history data |
Contact NSIDC User Services for more information.
Page last updated: 02/06/13
