Standard metadata headers are required in every SeaBASS file. Select a header to view its definition. Some headers are required in all SeaBASS files, some are conditionally required depending on what type of data were measured, and others are optional.
If you are getting started learning about SeaBASS file format, scroll down below the table of contents to see an example header.
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.
To assist with the standardization of SeaBASS data files, the SIMBIOS Project developed feedback software, named FCHECK, to evaluate the format of submitted data files. Since then, it has been rebuilt from the ground up by the SeaBASS development team to make it available to the end-users. There are multiple ways to access this software, as explained further below. Using FCHECK, contributors may evaluate the format of their SeaBASS-compatible files prior to submission.
FCHECK scans files for common syntax problems, missing header information, data values outside of typical ranges, nonstandard field names or units, and also detects various other issues. It will report a summary of the types of problems detected (if any) among all the files it scanned, as well as a more detailed breakdown of issues found in each individual file. Problems are classified as either errors or warnings, depending on their severity. Errors are critical problems that must be addressed before files can be archived. Warnings should be fixed if possible, but some of them are subjective or optional and may be disregarded.
These validation match-up tools allows Users to
- find relevant OB.DAAC satellite granules from in situ points or a SeaBASS data file and
- generate coincident satellite validation match-ups for those points.
These tools are downloadable for Users to run individually, external to the official SeaBASS validation search
. These tools are designed to replicate some of SeaBASS validation search's core functionality, with the exception that these tools do NOT adjust in situ data to water-leaving values.
Access to the data archived within SeaBASS follows the NASA Earth Science Data and Information Policy.
NASA's Earth Science program was established to use the advanced technology of NASA to understand and protect our home planet by using our view from space to study the Earth system and improve prediction of Earth system change. To meet this challenge, NASA promotes the full and open sharing of all data with the research and applications communities, private industry, academia, and the general public. The greater the availability of the data, the more quickly and effectively the user communities can utilize the information to address basic Earth science questions and provide the basis for developing innovative practical applications to benefit the general public. In this regard, all users incorporating SeaBASS data into their research are expected to acknowledge both their data sources (the original data contributors and SeaBASS) and NASA, and to abide by the Access Policy.
The SeaBASS sea surface temperature (SST) validation system is designed to provide ground-truth of satellite-borne measurements via comparisons with coincident in situ temperature measurements. Successful match-ups are compiled into one global file per date for each different sensor and made available via a simple web-based search engine.
This article explains how to search for and download results, how to work with validation files, and provides background information describing the steps involved in creating validation match-ups.
The NASA OBPG routinely downloads data from the AERONET-Ocean Color website for use in satellite sensor validation match-up analysis. As described by Zibordi et al. (2009), the AERONET-OC network consists of globally distributed autonomous radiometer systems maintained at fixed offshore sites. Please refer to the rest of the information in this article for details on how to acknowledge the use of AERONET-OC data and how the OBPG processes these data.
The SeaBASS Regional Time Series Tool is designed to provide comparisons over time between averaged level 2 satellite-borne ocean color instrument observations as well as in situ measurements. For a given region, one or more satellite sensors must be selected and then all available satellite and in situ data collected within the bounds of the study site will be plotted for comparison in common figures and frequency distributions. User options are available to select a measurement product of interest (e.g., Rrs, IOPs, Chl, etc.), adjust the data averaging period (weekly, monthly, seasonal), the year range, and other graph options. Each region has a brief description that includes links to extra information about the primary in situ data sources and a map that shows the boundaries used to define each region. Users may also download the data that were used to generate the figures.