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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Benthic DO and nutrient fluxes from sediment core incubations] - Benthic
dissolved oxygen and nutrient fluxes from sediment core incubations conducted
aboard the R/V Oceanus and R/V Robert G. Sproul during nine cruises from 2018-
2022 from the Oregon and Washington shelf (Benthic Biogeochemical Exchange
Dynamics on the Oregon Shelf)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_940414_v1)
Range: longitude = -124.529 to -124.031°E, latitude = 44.568 to 46.449°N, depth = 26.0 to 142.8m, time = 2018-02-27T20:54:00Z to 2022-09-18T20:52: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 {
  Cruise_ID {
    String long_name "Cruise_id";
    String units "unitless";
  }
  Core_number {
    Int32 actual_range 1, 3;
    String long_name "Core_number";
    String units "unitless";
  }
  Site_name {
    String long_name "Site_name";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.51976484e+9, 1.66353432e+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";
  }
  ISO_DateTime_PST {
    String long_name "Iso_datetime_pst";
    String units "unitless";
  }
  Julian_day {
    Float32 actual_range 10.98264, 276.7014;
    String long_name "Julian_day";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 44.568, 46.449;
    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 -124.529, -124.031;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 26.0, 142.8;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Temp_mean {
    Float32 actual_range 7.56, 12.15;
    String long_name "Temp_mean";
    String units "degrees Celsius";
  }
  Temp_std {
    Float32 actual_range 0.1, 1.9;
    String long_name "Temp_std";
    String units "degrees Celsius";
  }
  DO {
    Float32 actual_range -7.75, 0.02;
    String long_name "Do";
    String units "millimoles per square meters per day (mmol/(m^2 day))";
  }
  DIC {
    String long_name "Dic";
    String units "millimoles per square meters per day (mmol/(m^2 day))";
  }
  NOx {
    Float32 actual_range -1.6, 0.07;
    String long_name "Nox";
    String units "millimoles per square meters per day (mmol/(m^2 day))";
  }
  NO2 {
    Float32 actual_range -0.023, 0.042;
    String long_name "No2";
    String units "millimoles per square meters per day (mmol/(m^2 day))";
  }
  NH4 {
    Float32 actual_range -0.147, 2.973;
    String long_name "Nh4";
    String units "millimoles per square meters per day (mmol/(m^2 day))";
  }
  PO4 {
    Float32 actual_range -0.032, 0.561;
    String long_name "Po4";
    String units "millimoles per square meters per day (mmol/(m^2 day))";
  }
  Si {
    Float32 actual_range -0.46, 11.97;
    String long_name "Si";
    String units "millimoles per square meters per day (mmol/(m^2 day))";
  }
  TDN {
    Float32 actual_range -1.33, 2.69;
    String long_name "Tdn";
    String units "millimoles per square meters per day (mmol/(m^2 day))";
  }
  Notes {
    String long_name "Notes";
    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.940414.1";
    Float64 Easternmost_Easting -124.031;
    Float64 geospatial_lat_max 46.449;
    Float64 geospatial_lat_min 44.568;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -124.031;
    Float64 geospatial_lon_min -124.529;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 142.8;
    Float64 geospatial_vertical_min 26.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T06:00:17Z (local files)
2024-11-08T06:00:17Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_940414_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/940414";
    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 46.449;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 44.568;
    String summary "Continental shelf sediments are sinks for dissolved oxygen and sources of many major and minor nutrients required for oceanic surface primary production, resulting in a strong coupling between benthic and pelagic biogeochemical cycling. However, the influence and spatiotemporal variability of benthic remineralization on bottom-water chemistry and the supply of nutrients to surface waters has received minimal study on the Oregon-Washington (OR-WA) shelf. To expand knowledge of these areas, benthic flux measurements were made approximately quarter-annually at inner-shelf and mid-shelf sites on the Newport Hydrographic (NH) Line at 44.6˚N between December 2017 and July 2019, and again between 44.5˚N and 46.5˚N along the mid-shelf during July and September of 2022. The benthic fluxes were determined using a novel set-up for ex situ core incubations. The dataset described here details all benthic fluxes measured during sediment incubation experiments, conducted during the cruises from February 2018 to July 2019, at the sites on the NH Line, and during July and September of 2022. The paired bottom water dataset is located in a separate BCO-DMO dataset (dataset ID 793115). Additionally, during the 2022 cruises, community composition data were collected using box corers. These data are also located in a separate BCO-DMO dataset (dataset ID 880760).";
    String time_coverage_end "2022-09-18T20:52:00Z";
    String time_coverage_start "2018-02-27T20:54:00Z";
    String title "[Benthic DO and nutrient fluxes from sediment core incubations] - Benthic dissolved oxygen and nutrient fluxes from sediment core incubations conducted aboard the R/V Oceanus and R/V Robert G. Sproul during nine cruises from 2018-2022 from the Oregon and Washington shelf (Benthic Biogeochemical Exchange Dynamics on the Oregon Shelf)";
    Float64 Westernmost_Easting -124.529;
  }
}

 

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