Metadata Headers

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.


Table of Contents


Example Header

/begin_header
/investigators=John_Smith,Mary_Johnson
/affiliations=State_University
/contact=jsmith@state.edu
/experiment=CalCOFFEE
/cruise=cal0101
/station=93.26
/data_file_name=CalCOFFEE_cal0101_pigments_20010314_R1.sb
/original_file_name=pigments_cal0101.xls
/documents=cal0101_readme.txt
/calibration_files=turner_cals_0012.txt
/calibration_date=20001212
/instrument_model=10AU_Field_Fluorometer
/instrument_manufacturer=Turner_Designs
/data_type=pigment
/data_status=final
/start_date=20010314
/end_date=20010314
/start_time=16:01:30[GMT]
/end_time=16:30:45[GMT]
/north_latitude=42.135[DEG]
/south_latitude=42.055[DEG]
/east_longitude=-72.375[DEG]
/west_longitude=-72.420[DEG]
/water_depth=250
/measurement_depth=NA
/secchi_depth=4.5
/cloud_percent=50
/wind_speed=5.0
/wave_height=1.0
!
! COMMENTS
!
! Slightly overcast, with large cumulous on horizon.  Wind from NE.  
!
! Turner fluorometer last calibrated: 12 December 2000
!
! lower limit of detection = 0.001 mg/m^3
!
/missing=-9999
/below_detection_limit=-8888
/above_detection_limit=-7777
/delimiter=comma
/fields=date,time,lat,lon,depth,CHL,CHL_sd,PHAEO,PHAEO_sd,Tpg,bincount
/units=yyyymmdd,hh:mm:ss,degrees,degrees,m,mg/m^3,mg/m^3,mg/m^3
/end_header
20010314,16:01:30,42.135,-72.375,0,2.355,0.080,0.785,0.100,3.140,3       
20010314,16:03:45,42.055,-72.420,5.5,2.180,0.005,1.005,0.009,3.185,3
20010314,16:07:53,42.100,-72.378,10,1.510,0.124,-9999,-9999,-9999,3
20010314,16:15:11,42.130,-72.380,50,0.027,0.001,-8888,-9999,0.057,3
...

 The "comma" delimiter is used to separate data values (everything below /end_header) in the above example. Comma should be used as the delimiter. Space or tab are supported but not recommended for new submissions.

 

Required Headers

The following headers are requird to be included in every SeaBASS file.

investigators

required

The contributors of the data file. The Principal Investigator (PI) is listed first, followed by any associate investigators, analysts, technicians, and students, etc. (comma-separated, no spaces).

 

affiliations

required

A list of affiliations (i.e., university, institution, or laboratory, etc.) whose number and ordering should match the entry or entries in the investigators header (comma-separated, no spaces).

 

contact

required

An email address for at least one of the investigators or point of contact for the data file. The email address of the PI must be included. Multiple email addresses may be listed comma-separated, no spaces.

 

experiment

required

The name of the over-arching, long-term research project or funding program. Experiment names are used to generate a dataset-specific DOI and, generally, will contain multiple cruises or deployments and encompass data spanning multiple months or years. The Experiment name should be an acronym or short name, typically limited to maximum of 25 characters (no spaces). Please be consistent with a consensus-selected name if data from the project are being submitted by multiple different investigators.

For example: CalCOFI, CARIACO, EcoHAB, BBOP, BTM

 

cruise

required

The name of the specific cruise (or deployment, or subset of the experiment) where the data in the file were collected. If possible, do not exceed a meximum length of 25 characters (no spaces). Please be consistent and use a consensus-selected name if data from the same cruise are being submitted by multiple different investigators.

Various example include: cal9802, car48, bats143, dep12, EXPORTSNP.

 

station

required (or optional, if station appears in /fields= list)

The name of the station or deployment where data in the file were obtained. If the data file contains measurements from multiple stations, use the value NA and include station as a column in your data matrix. NA may also be used if the data were not assigned station names.

 

data_file_name

required

The current name of the data file (i.e., a self-reference).

 

documents

required

A comma-separated list (no spaces) naming ancillary files such as cruise reports, station logs, digital images, and other associated documentation that are part of the dataset submission (provided in the relevant documents directory) and provide additional information about the experiment and cruise. Every SeaBASS submission must be accompanied by an instrumentation-methods-calibration report that describes methods: the instruments used, how they were calibrated and how data were collected and processed. Include any required checklists.

 

See User Resources for more information.

data_type

required

Data_type is a single keyword label that describes the general contents of the data file. This is typically the collection method or platform, but a few keywords are more specific to measurement type (e.g., pigment). Accepted values are restricted to the following:

 

  • cast for vertical profiles (e.g. optical packages, CTD)
  • flow_thru for continuous data (e.g. shipboard, underway flow through systems)
  • above_water for above surface radiometry data (e.g. ASD, SIMBAD, Satlantic SAS)
  • scan for discrete hyperspectral measurements (e.g., spectrophotometrically derived absorption)
  • pigment for laboratory measured pigment data (e.g. fluorometry, spectrophotometry, HPLC)
  • bottle (general category) for any other types of measurements from water samples collected at discrete depths (e.g. nutrients)
  • mooring for moored and buoy data
  • drifter for drifter and drogue data

Other accepted (but less common in SeaBASS) values include:

 

  • airborne for measurements made via an aircraft
  • auv for measurements made by an autonomous underwater vehicle (auv)
  • diver for measurements made by a diver
  • experimental for measurements that have a non-geospatial aspect (e.g., incubations, other special laboratory measurements, etc.)
  • lidar for lidar and other active remote-sensing measurements (e.g. MPL)
  • net_tow for measurements captured via net (e.g., zooplankton via MOCNESS)
  • sediment_trap for measurements from a sediment trap platform
  • sunphoto for sunphotometry data (e.g. MicroTops, PREDE)
  • taxonomy for data whose purpose is the classification or annotation of phytoplankton, zooplankton, or other marine groups

 

calibration_files

required

A comma-separated list (no spaces) of supplementary file names containing coefficients and techniques used to calibrate the instruments used in data collection. The named files can be found within the relevant documents folder accompanying the submitted data files.

start_date

required

The earliest date data in the file were collected (in YYYYMMDD).


For example, a start date of March 14, 2001 would be written as /start_date=20010314

 

end_date

required

The latest date data in the file were collected (in YYYYMMDD).


For example, an end date of March 14, 2001 would be written as /end_date=20010314

 

start_time

required

The earliest time of day measurements were collected during the start_date in the file (in HH:MM:SS). Times are in Greenwich Mean Time. This header requires a [GMT] trailer.


For example: /start_time=12:30:00[GMT]

 

end_time

required

The latest time of day data data were collected during the end_date in the file (in HH:MM:SS). Times are in Greenwich Mean Time. This header requires a [GMT] trailer.


For example: /end_time=13:30:00[GMT]

 

north_latitude

required

The farthest north data in the file were collected (in decimal degrees). This header requires a [DEG] trailer. Latitudes south of the equator are negative.


For example: /north_latitude=42.750[DEG]

 

south_latitude

required

The farthest south data in the file were collected (in decimal degrees). This header requires a [DEG] trailer. Latitudes south of the equator are negative.


For example: /south_latitude=36.500[DEG]

 

east_longitude

required

The farthest east data in the file were collected (in decimal degrees). This header requires a [DEG] trailer. Longitudes west of the Prime Meridian are negative.


For example: /east_longitude=-68.500[DEG]

 

west_longitude

required

The farthest west data in the file were collected (in decimal degrees). This header requires a [DEG] trailer. Longitudes west of the Prime Meridian are negative.


For example: /west_longitude=-85.750[DEG]

 

water_depth

required

The water (bottom) depth at the station where the data were collected (in meters). Use the value NA if water depth was unknown or if the file contains data from different bottom depths.

 

missing

required

Refers to the NULL value used as a numeric placeholder for any missing data in the data file. Note that each row of data must contain the same number of columns as defined in the /fields and /units headers. Only one (1) missing value is allowed per file. This value MUST be non-zero. A common choice is -9999 or some other negative number large enough to never be accidentally confused with valid measurements. If your file includes below_detection_limit or above_detection_limit values, use different NULL values for each.

delimiter

required

Indicates how the columns of data are delimited. Accepted delimiters include comma, space, or tab. All new submissions should use comma, and must if the data matrix contains strings. Only a single (1) delimiter is permitted per data file.

 

fields

required

A list of the field names for each column of data included in the data file. Each entry describes the data in a single (1) column, and every column must have an entry.

 

units

required

A list of the units for each column of data included in the data file. Every value in /fields must have an appropriate value listed here.

 

Conditionally Required Headers

The following headers are conditionally required to be included in certain SeaBASS files. Some of the most common conditionally required are: /measurement_depth (this MUST be included if a column for "depth" isn't provided) and /below_detection_limit (and its less common counterpart, /above_detection_limit). Some conditionally required headers are specific to certain types of measurements, such as absorption coefficients (see: /volfilt, /null_correction, /area) or HPLC pigment files (see: /HPLC_lab and /HPLC_lab_technician).

above_detection_limit

required IF file contains above_detection_limit values, optional otherwise

Refers to the numeric NULL value used a placeholder for measurements that were made but were above detection limits. If the file contains those types of values, this header is required and those values should be flagged (e.g., set to -7777 or another defined value). Above detection limit values convey some information and are not the same as "missing" values, as missing implies that data were either not measured or invalid.
 
/above_detection_limit=-7777
! Comments
!
! Measurements above the detection limit are assigned the value -7777
! upper limit of detection = XYZ concentration
 
If your file contains below detection limit values, then include the header "/above_detection_limit=-7777" followed by comments that describe what the detection limit was for each relevant measurement-type. See also /missing and /below_detection_limit.

area

optional

(m^2) Use this header to describe the area a sample occupies (e.g., for filter pad absorption measurements.)

associated_archives

conditionally required

The associated_archives header is mandatory for all submissions with associated metadata or files. This header provides the file name(s) of external bundles of files. It is typically used as part of the process of storing unprocessed files or imagery used for the results presented in the SeaBASS (.sb) file, such as planktonic imagery for IFCB, sig files for FCM, and sky photos for AOP measurements.  

 

The associated files should be compressed into a tar bundle (.tgz). Each TGZ file should not exceed 5Gb in size, however, each submission can provide multiple TGZ files. Multiple files can be listed similarly to the documents, separated by commas, and no spaces in the filename or list of files. The filename of the associated archive should include the experiment and cruise name, and data type, and must end with “_associated.tgz”.  

 

/associated_archives=Experiment_cruise_IFCB_202210-202212_associated.tgz,Experiment_cruise_IFCB_202310-202312_associated.tgz 

 

The submitter can compress the files using any method such as TGZ, tar.gz, or ZIP file. The files can also be uploaded individually, however, make sure they are within a folder that clearly denoted that they are associated files. The SeaBASS data manager will create the final TGZ file. Note that this header is not for general documentation (use /documents instead), and not for individual calibration files (use /calibration_files instead).

 
For additional information and examples go here 

associated_archive_types

conditionally required

The associated_archive_types header is mandatory for all submissions with associated metadata or files and should accompany the associated_archives header. This header should describe each of the associated archive TGZ files. 

/associated_archive_types=planktonic,planktonic

 

Valid entries for this header are: 

  • DNA-FASTQ 
  • DNA-FASTA (for files relating to DNA analysis) 
  • benthic 
  • planktonic (for accompanying scientific imagery files) 
  • raw (minimally processed, higher resolution data versions) 
  • unbinned (Processed or QA/QC CTD data not binned) 
  • metadata (Additional metadata information) 

Please contact the SeaBASS staff if your associated_archives do not fit into one of these types.  

associated_files

conditionally required

The “associated_files” header or field can be used to link specific files within the compressed tar bundle (TGZ; the associated_archives bundle). If one link is relevant for the entire SeaBASS files, use associated_files as a header. If the links differ by data row within the data matrix, use associated_files as a field. This header should be used in conjunction with the associated_archives header, as well as the associated_file_types and associated_archive_types. 

 

The submitter can compress the files using any method such as TGZ, tar.gz, or ZIP file. The files can also be uploaded individually, however, make sure they are within a folder that clearly denoted that they are associated files. The SeaBASS data manager will create the final TGZ file. For additional information and examples go here

 

Example using the associated_files header:
/associated_archives=Experiment_cruise_IFCB_202210-202212_associated.tgz
/associated_archive_types=planktonic_imagery
/associated_files=Experiment_cruise_IFCB_image1.png,Experiment_cruise_IFCB_image2.png
/associated_file_types=planktonic_imagery,planktonic_imagery

associated_file_types

conditionally required

Include this header if a SeaBASS file has an accompanying auxiliary or ancillary file that is being reported with the /associated_files header. For multiple entries, separate with a comma. 

NOTE: This header MUST be used in conjunction with the /associated_files header.

 

Valid entries for this header are: 

below_detection_limit

required IF file contains below_detection_limit values, optional otherwise
 
Refers to the numeric NULL value used as a placeholder for measurements that were made but were below detection limits. If the file contains those types of values, this header is required and those values should flagged (e.g., set to -8888 or another negative number that is distinct from the range of valid measurements). Below detection limit values convey some information and are not the same as "missing" values, as missing implies that data were either not measured or invalid for other reasons.
 
/below_detection_limit=-8888
! Comments
!
! Measurements below the detection limit are assigned the value -8888
! lower limit of detection = XYZ concentration
 
If your file contains below detection limit values, then include the header "/below_detection_limit=-8888" followed by comments that describe what the detection limit was for each relevant measurement-type. You do not need to list the limit of detection for every measurement-type in your file, only those that use the below detection limit value (i.e. -8888.) Also, you may consolidate information where practical, for example, if the limit of detection for all HPLC pigments is the same concentration (e.g. 0.001 mg/m^3) then a comment like "! HPLC pigments limit of detection = 0.001 mg/m^3" will suffice rather than listing every pigment individually. See also /above_detection_limit and /missing.

BRDF_correction

conditionally required (for some radiometry measurements)

This value is an abbreviation (from the table below) specifying which, if any, method of bi-directional reflectance distribution function (BRDF) correction was applied to all relevant radiometry fields. e.g.,
/BRDF_correction=noBRDF
Alternately, one or more specific pairings of <fields-name>:<BRDF-abbreviation> may be listed comma-separated, e.g.,
/BRDF_correction=Rrs:noBRDF

 

Table of standardized NIR_residual_correction method abbreviations

BRDF method abbreviation

BRDF method

Default, if not specified

noBRDF or NA

No BRDF applied

Default for all .sb files

M02

Morel et al. 2002

Default for SeaBASS Validation files

L11

Lee et al. 2011

 

What if files do not contain this header? Unless contradicted by more specific documentation, assume the defaults in the BRDF table above, i.e., .sb files = “noBRDF” and any results from SeaBASS Validation web-tools = “M02”.

 

Note: Original SeaBASS data submissions must not be BRDF corrected. BRDF may be used in alternate versions of data, or in validation outputs. See radiometry submission requirements or contact SeaBASS staff with any questions.

chemical_formula

 conditionally required

The chemical formula of a reported compound, typically associated with the PTR-TOF/MS instrument measuring VOCC concentrations.

Use the syntax "/chemical_formula=...,(C3H6O)H+,(C5H8)H+,...", where each relevant "/fields=...,C3H6O_H,C5H8_H,..." entry has its true chemical formula expressed.

If it is necessary to list multiple chemical formulas, then list all the values in a row, separated by commas.

data_use_warning

conditionally required
This header must be included using specific keywords to alert users if the file contains one or more data points that were measured under atypical conditions, or derived experimentally (see below for more information). If a SeaBASS file contains this header, then users should consult the comments in the metadata header or the documentation to learn more and to decide if it is appropriate to use such data for their specific application.
 
Allowed keywords include: optically_shallow, experimental
 
  • optically_shallow: one or more data points were known or suspected to be in optically shallow conditions where the bottom reflectance would impact water leaving values
  • experimental: data are either non-geospatial (e.g., non-field measurements derived under laboratory conditions) or subjectively non-geospatial (e.g., derived from measured water samples but with adjusted light levels or other experimental parameters)
  • negative_data_values: the file contains one or more negative values for types of data that are nominally positive. This warning is used when calibrations or data corrections yielded negative values. Investigators generally must remove or flag negative values prior to submitting to SeaBASS, but there are cases when it is helpful to preserve (slightly) negative values.
  • negative_depths: data contains one or more negative depth or pressure values, which are only allowed if it is necessary and meaningful to retain measurements above the sea-surface
If multiple keywords are applicable, the correct syntax is to list the multiple keywords separated by commas and no spaces (e.g., /data_use_warning=optically_shallow,experimental)
 
To Submitters: Since most of these headers deal with special cases, discuss details with SeaBASS staff before submitting these types of data

HPLC_lab

conditionally required

Applicable (and required) for HPLC data. This header should contain the name of the lab where the HPLC analysis was run.

Example: /HPLC_lab=NASA_GSFC

 

Use in conjunction with the /HPLC_lab_technician header.

HPLC_lab_technician

conditionally required

Applicable (and required) for HPLC data. This header should contain the name of the lab technician who ran the HPLC analysis.

Example: /HPLC_lab_technician=Crystal_Thomas

 

Use in conjunction with the /HPLC_lab header.

id_fields_definitions

conditionally required

This header is a list of one or more user-defined classification categories that modify field names. This header is required if the _id modifier is used in fields.

 

Use the syntax "/id_fields_definitions=#id:<definition>" by listing numbered id suffix followed by the user definition. Multiple definitions may be provided; list them separated by commas. Here is an example of this metadata header paired with its use in /fields:

 

/id_fields_definitions=1id:nanoeukaryotes,2id:picoeukaryotes

/fields=u_ph_1id,u_ph_2id,...

 

 

mass_to_charge

conditionally required

The numeric expression of the mass to charge ratio for a chemical compound, typically associated with the PTR-TOF/MS instrument measuring VOCC concentrations.

Use the syntax "/mass_to_charge=...,mz33.0335,mz34.0335,...", where each relevant "/fields=...,C3H6O_H,C5H8_H,..." entry has its mass to charge (m/z) ratio expressed.

If it is necessary to list multiple mass to charge raatios, then list all the values in a row, separated by commas.

 

measurement_depth

conditionally required (value must be provided if depth is omitted from /fields)

The constant measurement depth (in meters) that applies to all data rows. Only provide a numerical value if all data in the file were collected at the same discrete depth, and the file omits the equivalent field named depth. For example, this is often applicable (and required) for files containing bottle samples, buoys, and moored radiometers. This header should be excluded or have the value "NA" if a single measurement depth does not apply to the file.

The default value is 0, which is also applicable for measurements made at or just above the sea surface.

 

NIR_residual_correction

conditionally required (for some radiometry measurements)

This value is an abbreviation (from the table below) specifying which, if any, method of Near Infrared (NIR) residual correction is applied to all relevant radiometry fields. Alternately, one or more specific pairings of <fields-name>:<method-abbreviation> may be listed comma-separated.

 

Table of standardized NIR_residual_correction method abbreviations

NIR residual correction method abbreviation

NIR residual correction method

R06

Ruddick et al. 2006

MA95

Mueller and Austin 1995

 

null_correction

conditionally required

Only required if a null correction was applied while calculating absorption coefficients. Generally, null corrections should be performed using absorbance, also known as optical density measurements (unitless). Please note that absorbance data should be submitted without null correction applied. List a null correction by pairing a field name with its null correction value separated by a colon. To report multiple null corrections, separate them by commas. Units are assumed to be the same as the fields used for null correction. Examples

/null_correction=abs_ag:0.005,abs_ap:0.001,abs_ag:0.005

/null_correction=ag:0.005 

 

 

optical_depth_warning (deprecated)

conditionally required

This header (/optical_depth_warning=true) was used if a file contained measurements known or suspected to be in optically shallow conditions where the bottom reflectance would impact water leaving values. Using default SeaBASS search settings, files with this header will be excluded from results.
 
NOTE: This header is no longer supported. It has been replaced by "/data_use_warning=optically_shallow" (additional warnings may also be listed as a comma-separated list).

rho_correction

conditionally required (for some radiometry measurements)

This value is an abbreviation (from the table below) specifying which, if any, method of Near Infrared (NIR) residual correction is applied to all relevant radiometry fields. Alternately, one or more specific pairings of <fields-name>:<method-abbreviation> may be listed comma-separated.

 

Table of standardized rho_correction method abbreviations

Rho correction method abbreviation

Rho correction method

M99

Mobley 1999

Z17

Zhang 2017

volfilt

conditionally required

The volume filtered (in units of liters) corresponding to one or more fields in a file. This header is only applicable for files with measurement(s) from a discrete sample (for example, to indicate the volume of water filtered for the ap absorption coefficient.)

Use the syntax "/volfilt=FIELD_NAME:#" by listing the field name and volume separated by a colon. For example, /volfilt=ap:0.1

If it is necessary to list multiple volumes filtered for different fields, separate the pairings with a comma.

 

Optional (but recommended) Headers

 While not mandatory, it is recommended that you include as many of the following headers as possible if the relevant information can be provided.

calibration_date

optional

The most recent relevant calibration date for the primary instrument (as YYYYMMDD, e.g., 20190122). This header is optional but highly recommended, or may be set to "NA" if not applicable.

 

cloud_percent

optional

Percent cloud cover for the entire sky.


For example: 0 indicates no clouds and 100 indicates completely overcast.

 

data_status

optional

The condition, or status, of the data file. The value preliminary is used when the data are new and the investigator intends to analyze the data further. The value update indicates the data are being resubmitted and informs users that an additional resubmission will occur in the future. The value final is used when the investigator has no intention of revisiting the data set.

 

instrument_manufacturer

optional

The instrument manufacturer of the measurements that are being reported (e.g., Biospherical_Instruments_Inc.) Replace any spaces in the name with underscores. If the file contains measurements from multiple sources, list them comma separated.

 

instrument_model

optional

The model of the instrument whose measurements are being reported (e.g., PRR-800). Replace any spaces in the names with underscores. If the file contains measurements from multiple instruments, list them comma separated.

 

secchi_depth

optional

The secchi depth at the station where the data were collected (in meters).

 

wave_height

optional

The wave height at the station where the data were collected (in meters).

 

wind_speed

optional

The wind speed at the station where the data were collected (in meters per second).

 

Optional Headers

The following headers are optional for inclusion in every SeaBASS file.

Restricted Use Headers

The following headers are created by SeaBASS staff after the files have been submitted to the SeaBASS archive. Data submitters should NOT add these headers to their SeaBASS files.

identifier_product_doi

assigned and entered by SeaBASS staff

The DOI (Digital Object Identifier; see http://www.doi.org/) associated with the experiment.

 

received

assigned and entered by SeaBASS staff

The date that the files were submitted to SeaBASS.

 

comments

optional

A space for additional comments. Common comments include additional ancillary information about the data file, sea and sky states, difficulties encountered during data collection, methods of data collection, instruments used, and a description of nonstandard SeaBASS field names included in the data file. Comments must always be preceded by a exclamation point (!).

 

original_file_name

optional

The original name of the data file, if different from the current /data_file_name.

Designed to be a reference for the contributor.

 

number_of_data_rows

 optional
The number of data rows in the the data matrix (i.e. - the length of the data matrix).
Designed to be a reference for additional functionality (used by OCSSW's l2gen).

 

station_alt_id

optional, (use ONLY if station header is already in use)

An alternate name or identifier for the station or deployment where data were obtained.

 

biotic_setting

optional

Biotic Setting, Biotic Component, level 1. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

biotic_class

optional

Biotic Class, Biotic Component, level 2. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

biotic_subclass

optional

Biotic Subclass, Biotic Component, level 3. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

biotic_group

optional

Biotic Group, Biotic Component, level 4. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

biotic_community

optional

Biotic Community, Biotic Component, level 5. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

geoform_tectonic_setting

optional

Geoform Component Tectonic Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

geoform_physiographic_setting

optional

Geoform Component Physiographic Setting Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

geoform_origin

optional

Geoform Origin, Geoform Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

geoform

optional

Geoform, Geoform Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

geoform_type

optional

Geoform Type. Geoform Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

r2r_event

optional

The Rolling Deck to Repository (R2R) unique sample event number that applies to the entire data matrix. If multiple events apply to the data matrix, don't use this header. Instead, provide a column of those data values using the field name "R2R_event".

 

s_ag

optional
Slope of gelbstoff absorption spectra. If there is one s_ag data value per dataset, please use the following format: /s_ag=s_ag_#nmmin_#nmamax:value, where # is wavelength and value is your data value.
 

substrate_origin

optional

Substrate Origin, Substrate Component level 1. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

substrate_class

optional

Substrate Class, Substrate Component level 2. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

substrate_subclass

optional

Substrate Subclass, Substrate Component level 3. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

substrate_group

optional

Substrate Group, Substrate Component level 4. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

substrate_subgroup

optional

Substrate Subgroup, Substrate Component level 5. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

water_column_biogeochemical_feature

optional

Water Column Biogeochemical Feature Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

water_column_hydroform_class

optional

Water Column Hydroform Subcomponent level 1. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

water_column_hydroform

optional

Water Column Hydroform Subcomponent level 2. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

water_column_hydroform_type

optional

Water Column Hydroform Subcomponent level 3. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

water_column_layer

optional

Water Column Layer Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

water_column_salinity

optional

Water Column Salinity Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

water_column_temperature

optional

Water Column Temperature Subcomponent. CMECS Units, with no spaces, use underscores instead.

Refers to a data classifier in the Coastal and Marine Ecological Classification Standard (CMECS, https://www.cmecscatalog.org/).

 

Last edited by David Norris on 2023-11-30
Created by Chris Proctor on 2012-08-29