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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Bottle-calibrated Dissolved Oxygen Profiles] - Bottle-calibrated dissolved
oxygen (DO) profiles from US Overturning in the Subpolar North Atlantic
Program (OSNAP) cruises in 2020 and 2022 (AR45 and AR69-03) (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_933743_v1)
Range: longitude = -68.522 to -27.6994°E, latitude = 41.9062 to 62.6272°N
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: 
[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 {
  Cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  Station {
    Int32 actual_range 1, 214;
    String long_name "Station";
    String units "unitless";
  }
  Down_Up {
    String long_name "Down_up";
    String units "unitless";
  }
  Date_UTC {
    String long_name "Date_utc";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 41.9062, 62.6272;
    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 -68.522, -27.6994;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  CTDPRES {
    Float32 actual_range 2.0, 3146.0;
    String long_name "Ctdpres";
    String units "dbar";
  }
  CTDTEMP_ITS90 {
    Float32 actual_range -0.849, 20.514;
    String long_name "Ctdtemp_its90";
    String units "degrees Celsius";
  }
  CTDTEMP_flag {
    Int32 actual_range 1, 2;
    String long_name "Ctdtemp_flag";
    String units "unitless";
  }
  CTDSAL_PSS78 {
    Float32 actual_range 18.68, 36.023;
    String long_name "Ctdsal_pss78";
    String units "unitless";
  }
  CTDSAL_flag {
    Int32 actual_range 1, 2;
    String long_name "Ctdsal_flag";
    String units "unitless";
  }
  CTDOXYCUR {
    Float32 actual_range 0.0, 4.7306;
    String long_name "Ctdoxycur";
    String units "volts";
  }
  CTDOXYCUR_flag {
    Int32 actual_range 2, 3;
    String long_name "Ctdoxycur_flag";
    String units "unitless";
  }
  CTDOXY {
    Float32 actual_range -71.3, 637.5;
    String long_name "Ctdoxy";
    String units "umol/kg";
  }
  CTDOXY_flag {
    Int32 actual_range 2, 3;
    String long_name "Ctdoxy_flag";
    String units "unitless";
  }
  file_name {
    String long_name "File_name";
    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 doi "10.26008/1912/bco-dmo.933743.1";
    Float64 Easternmost_Easting -27.6994;
    Float64 geospatial_lat_max 62.6272;
    Float64 geospatial_lat_min 41.9062;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -27.6994;
    Float64 geospatial_lon_min -68.522;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T06:17:15Z (local files)
2024-11-08T06:17:15Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_933743_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/933743";
    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 62.6272;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 41.9062;
    String summary "This dataset contains bottle-calibrated dissolved oxygen (DO) profiles collected from Conductivity Temperature Depth (CTD) casts during cruises in 2020 (AR45) and 2022 (AR69-03) to recover and redeploy Overturning in the Subpolar North Atlantic Program (OSNAP) moorings in the Labrador Sea and western Irminger Sea. DO profiles were used in conjunction with oxygen bottle measurements (Winklers) to produce a post-cruise oxygen-calibrated CTD product for scientific use as part of Gases in the Overturning and Horizontal circulation of the Subpolar North Atlantic Program (GOHSNAP), which has added moored oxygen sensors to the OSNAP mooring array, beginning in 2020. This documentation contains overviews of CTD data collection and processing and of the oxygen sensor calibration method. For each cruise, we provide a summary of relevant cruise events, oxygen sensor calibration results, and issues/problems associated with oxygen data collected.";
    String title "[Bottle-calibrated Dissolved Oxygen Profiles] - Bottle-calibrated dissolved oxygen (DO) profiles from US Overturning in the Subpolar North Atlantic Program (OSNAP) cruises in 2020 and 2022 (AR45 and AR69-03) (Collaborative Research: Gases in the Overturning and Horizontal circulation of the Subpolar North Atlantic Program (GOHSNAP))";
    Float64 Westernmost_Easting -68.522;
  }
}

 

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