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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [GOHSNAP oxygen] - Dissolved oxygen time series measured on the Overturning in
the Subpolar North Atlantic Program (OSNAP) moorings within the boundary
currents of the Labrador and Irminger Seas from summer 2020 to summer
2022 (Collaborative Research: Gases in the Overturning and Horizontal
circulation of the Subpolar North Atlantic Program (GOHSNAP))
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_986667_v1)
Range: longitude = -51.9634 to -40.275°E, latitude = 52.685 to 60.07°N, depth = 40.0 to 3334.0m, time = 2020-07-01T17:00:00Z to 2022-09-14T13:45:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
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.")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   
 
(Please be patient. It may take a while to get the data.)
 
Optional:
Then set the File Type: (File Type information)
and
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
Zoom: 
Time range:    |<   -       
[The graph you specified. Please be patient.]

 

Things You Can Do With Your Graphs

Well, you can do anything you want with your graphs, of course. But some things you might not have considered are:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5936228e+9, 1.6631631e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  TEMP {
    Float32 actual_range -1.6342, 29.9399;
    String long_name "Temp";
    String units "degrees Celsius";
  }
  PTEMP {
    Float32 actual_range -1.635805, 12.92575;
    String long_name "Ptemp";
    String units "degrees Celsius";
  }
  PSAL {
    Float32 actual_range 0.9336, 38.03371;
    String long_name "Psal";
    String units "Practical Salinity Units (PSU)";
  }
  PRES {
    Float32 actual_range -0.99, 3399.7;
    String long_name "Pres";
    String units "decibars (dbar)";
  }
  DOXY {
    Float32 actual_range -281.3383, 378.9008;
    String long_name "Doxy";
    String units "micromoles per kilogram (umol/kg)";
  }
  DOXY_drift_corrected {
    Float32 actual_range 203.4475, 400.0479;
    String long_name "Doxy_drift_corrected";
    String units "micromoles per kilogram (umol/kg)";
  }
  filename {
    String long_name "Filename";
    String units "unitless";
  }
  serial_number {
    Int32 actual_range 3312, 204687;
    String long_name "Serial_number";
    String units "unitless";
  }
  mooring {
    String long_name "Mooring";
    String units "unitless";
  }
  osnap_id {
    String long_name "Osnap_id";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 40, 3334;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  location {
    String long_name "Location";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 52.685, 60.07;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -51.9634, -40.275;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  deploy_cruise_id {
    String long_name "Deploy_cruise_id";
    String units "unitless";
  }
  deploy_date {
    String long_name "Deploy_date";
    String units "unitless";
  }
  recovery_cruise_id {
    String long_name "Recovery_cruise_id";
    String units "unitless";
  }
  recovery_date {
    String long_name "Recovery_date";
    String units "unitless";
  }
  P_c {
    Float32 actual_range 0.024, 0.043;
    String long_name "P_c";
    String units "unitless";
  }
  G_1 {
    Float32 actual_range 0.9792844, 1.176915;
    String long_name "G_1";
    String units "unitless";
  }
  G_2 {
    Float32 actual_range 0.9728727, 1.205176;
    String long_name "G_2";
    String units "unitless";
  }
  reversible_drift {
    Int32 actual_range 0, 1;
    String long_name "Reversible_drift";
    String units "unitless";
  }
 }
  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 defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.986667.1";
    Float64 Easternmost_Easting -40.275;
    Float64 geospatial_lat_max 60.07;
    Float64 geospatial_lat_min 52.685;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -40.275;
    Float64 geospatial_lon_min -51.9634;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 3334.0;
    Float64 geospatial_vertical_min 40.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-04-02T06:08:38Z (local files)
2026-04-02T06:08:38Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_986667_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/986667";
    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.";
    Float64 Northernmost_Northing 60.07;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 52.685;
    String summary "This dataset contains oxygen time series collected from June 2020 - July 2022 on the Overturning in the Subpolar North Atlantic Program (OSNAP) moorings CF1, CF3, CF4, CF5, CF6, CF7, M1, M2, and M3 moorings in the western Irminger Sea, the C1_b, C2_b, C3_b, K7, K8, K9, K10, and DSOW 2 in the western Labrador Sea, and the LS1, LS3, LS4, LS5, LS6, LS7, and LS8 in the eastern Labrador Sea. Depths of oxygen data collection on the moorings range from as shallow as 50 m to as deep as 3500 m, covering the seasonally-stratified, near-surface waters, Labrador Sea Water, Northeast Atlantic Deep Water, and Denmark Strait Overflow Water masses.  These data were collected and calibrated for the Gases in the Overturning and Horizontal circulation of the Subpolar North Atlantic Program (GOHSNAP) for the purpose of calculating oxygen transports in the Labrador Sea. Data were calibrated and corrected for drift using Winkler-calibrated shipboard oxygen casts collected on the mooring recovery and deployment cruises, described in Miller et al. (2024) (Frontiers in Marine Science; 10.3389/fmars.2024.1441976).";
    String time_coverage_end "2022-09-14T13:45:00Z";
    String time_coverage_start "2020-07-01T17:00:00Z";
    String title "[GOHSNAP oxygen] - Dissolved oxygen time series measured on the Overturning in the Subpolar North Atlantic Program (OSNAP) moorings within the boundary currents of the Labrador and Irminger Seas from summer 2020 to summer 2022 (Collaborative Research: Gases in the Overturning and Horizontal circulation of the Subpolar North Atlantic Program (GOHSNAP))";
    Float64 Westernmost_Easting -51.9634;
  }
}

 

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