Data Format and Submission

To account for the continuous growth of the bio-optical data set and the wide variety of supported data types, the NASA Ocean Biology Processing Group felt it essential to develop efficient data ingestion and storage techniques. While this requires a specific data file format, the data protocols were designed to be as straightforward and effortless as possible on the part of the contributor, while still offering a useful format for internal efforts. The system was intended to meet the following conditions: simple data format, easily expandable and flexible enough to accomodate large data sets; global portability across multple computer platforms; and Web accessible data holdings with sufficient security to limit access to authorized users.

Data submission policy

All data collected under the auspices of the NASA Ocean Biology and Biogeochemistry (OB&B) program are to be submitted to SeaBASS within 1-year of the date of collection.

Guidance for OCB scientists (those with funding from NSF OCE)

Data format

Please consider the following while preparing data sets:

° SeaBASS data files are flat, two-dimensional ASCII text files.
° Data are presented as a matrix of values, much like a spreadsheet.
° Columns may be delimited by spaces, tabs, or commas.
° Use consistent field delimiters.
° Data are preceded by a series of predefined metadata headers.
° The headers provide decriptive information about the data file, e.g., cruise name, date, and cloud cover.
° All SeaBASS field names and units (e.g., CHL, AOT) have been standardized.
° SeaBASS field names and units are not case sensitive.
° Headers may be arranged in any order provided that the first and last are /begin_header and /end_header.
° Most headers are required. Use a value of NA (not applicable) if information is unavailable.
° Use numeric blanks, such as -999, for missing data.
° List latitude in decimal degrees, with coordinates north of the equator positive and south negative.
° List longitude in decimal degrees, with coordinates east of the Prime Meridian positive and west negative.
° List times in GMT (UTC).
° Entries for date, time, and location headers are the extreme value for the file (e.g., farthest north).
° Only the time and location headers require bracketed ([]) units. No other headers should include brackets.
° Headers should not include any white space. Separate words with an underscore.

Examples of SeaBASS data files:

° a CAST data file
° a PIGMENT data file
° a SCAN data file
° a MATCH-UP data file
° a MICROTOPS data file
° a SIMBAD data file
° a MOORING data file

Additional information:

° A description of the SeaBASS metadata headers.
° A header template to assist with SeaBASS file generation.
° A list of the the SeaBASS standard field names and units.
° Tips generating SeaBASS files from Microsoft Excel worksheets.

Format checking and submission

The OBPG maintains feedback software, FCHECK, to evaluate the format of data files.

° All data files should be tested using FCHECK prior to submission to SeaBASS.
° Data files, calibration files, and documentation are submitted to SeaBASS via FTP (File Transfer Protocol).
° The contributor should create a directory at ftp://samoa.gsfc.nasa.gov/seabass/incoming.
° The contributor should upload the data files to this newly created directory.
° The SeaBASS Administrator will collect the files and evaluates the data set.
° Note: a username and password are required to access the FTP site.
° Note: failure to use "PASSIVE" ftp mode in your client will result in a connection error.

Documentation

The following requirements must be met:

° Supporting documentation and calibration files must be included in the submission.
° The documentation and calibration files must match those listed in the appropriate headers in each file.
° The OBPG requires that documentation include cruise and instrument reports or logs.

Examples of SeaBASS cruise reports and calibration files:

° a station sheet from the Arc00 campaign
° a bridge log from the MIRC2 campaign
° a chief scientist report from the HOT-101 cruise
° a methods report from the AL9807 experiment
° a methods report from the MOCE5 campaign
° a station log from the CAL9809 cruise
° a MicroTops calibration file

Cruise reports and logs come in many shapes and sizes. The latter are examples which identify the type of information in which the OBPG is interested. The OBPG will accept all forms of documentation and all instrument calibration files.

Available code

° The OceanColor IDL Library provides an distribution system for routines commonly used by the OBPG.

Author/Site Curator: Jeremy Werdell
Responsible NASA Official: Charles McClain
Last revised 17 April 2007