This page provides examples of data files and documentation as models to help you format different types of submissions. Measurement-specific metadata, formatting, and accompanying documents are highlighted. For each data type found in the menu below, note the sections on "Special Requirements" and "Example Submission".
The Special Requirements sections indicate any conditionally required metadata headers needed for specific types of data. Additionally, check for any Required Extra Documents. Those should be filled out and submitted with your other documents and calibration files. These checklists were designed to standardize and preserve critical methods and analysis details that are needed for intercomparison, reprocessing, to make it easier for data users to assess the data quality and to consider them for satellite validation or inclusion in algorithm development datasets.
The Example Submission sections include one or more example SeaBASS data files that might be helpful as a reference for which fields and headers to include, and how to arrange your data matrix. Examples of documents and calibration files that were part of a model submission are also provided.
Over time additional examples will be added.
This page provides instructions on how to submit data to SeaBASS as well as information about the SeaBASS File Format. If you are new to this process, please scroll down the page to the "How to Submit" section and review the steps involved. More details can be found in the other sections on this page and beneath the other topics under "Contribute Data" found in the main menu of the SeaBASS website.
The SeaBASS data format and structure were designed with the following in mind: 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 accommodate large data sets; global portability across multiple computer platforms; and web-accessible data holdings with sufficient security to limit access to authorized users.
When preparing a submission, check to see if the data type is in the list below. Certain types of SeaBASS data submissions have special requirements. For example, some data files need conditionally required metadata headers, and some submissions require extra "checklist" documents. These requirements and several examples are listed below, sorted by data types. This list is growing and evolving and more data types will be added in the future.
Check if your submission type lists any required extra documents. These checklists are designed to standardize and preserve critical methods and analysis details that are needed for intercomparison, reprocessing, to make it easier for data users to assess the data quality and to consider them for satellite validation or inclusion in algorithm development datasets. We prefer you submit a plain text (.txt) document, but if multiple format versions are offered (e.g., rich text and plain text), pick your preference and fill out the necessary sections. Rename the file in a relevant way to make it unique (e.g., add the cruise name to the end of the file name), and add it to the other documents and calibration files that are part of your submission.
The special notes section for each data type highlights any necessary measurement-specific metadata (e.g., conditionally required headers), fields, or formatting.
This page also provides example submission sections containing model data files and documentation bundles to help you format different types of submissions. These files were picked from the archive or created to serve as references. Your files might look a bit different, but hopefully the examples are helpful as a starting place from which to further adapt or improve as needed.