BCO-DMO ERDDAP
Accessing BCO-DMO data
log in    
Brought to you by BCO-DMO    

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [Mixed-layer depths - Irminger Sea] - Mixed-layer depths at the Ocean
Observatories Initiative’s Irminger Sea Array from 2014 to 2022 (CAREER:
Constraining the high-latitude ocean carbon cycle: Leveraging the Ocean
Observatories Initiative (OOI) Global Arrays as marine biogeochemical time
series)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_998890_v1)
Information:  Summary ? | License ? | Metadata | Background (external link) | Files
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 Date (unitless) ?          "2015-01-02"    "2022-08-31"
 MLD (decibar (db)) ?          10    1414
 
Server-side Functions ?
 distinct() ?
? ("Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Date {
    String long_name "Date";
    String units "unitless";
  }
  MLD {
    Int32 actual_range 10, 1414;
    String long_name "Mld";
    String units "decibar (db)";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "info@bco-dmo.org";
    String creator_name "BCO-DMO";
    String creator_url "https://www.bco-dmo.org/";
    String doi "10.26008/1912/bco-dmo.998890.1";
    String history 
"2026-08-04T15:54:11Z (local files)
2026-08-04T15:54:11Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_998890_v1.html";
    String infoUrl "https://osprey.bco-dmo.org/dataset/998890";
    String institution "BCO-DMO";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String sourceUrl "(local files)";
    String summary "This dataset contains a mixed-layer depth (MLD) time series for the Ocean Observations Initiative (OOI) Global Irminger Sea Array (59.97°N, 39.51°W) from September 2014 to July 2022. Mixed-layer depths are determined for this site using a combination of OOI wire-following profiler, glider, and fixed depth mooring data, with Argo data used to fill late summer gaps. For full details see Text S9 in Yoder et al. (2024).";
    String title "[Mixed-layer depths - Irminger Sea] - Mixed-layer depths at the Ocean Observatories Initiative’s Irminger Sea Array from 2014 to 2022 (CAREER: Constraining the high-latitude ocean carbon cycle: Leveraging the Ocean Observatories Initiative (OOI) Global Arrays as marine biogeochemical time series)";
  }
}

 

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link) Data Access Protocol (DAP) (external link) and its selection constraints (external link).

The URL specifies what you want: the dataset, a description of the graph or the subset of the data, and the file type for the response.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.


 
ERDDAP, Version 2.22
Disclaimers | Privacy Policy | Contact