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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Northern Gulf of Mexico electrochemical data Fall 2020] - Electrochemical
data from sediment cores collected on the Louisiana Shelf of the Northern Gulf
of Mexico during November 2020 on R/V Savannah cruise SAV-20-07 (Importance of
Riverine Discharge on the Benthic Flux of Alkalinity to Continental Margins) Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_904782_v1)
Range: longitude = -90.30405 to -89.59939°E
Information:  Summary ? | License ? | 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: 
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 ? )
    [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 {
  Year {
    String long_name "Year";
    String units "unitless";
  }
  Month {
    String long_name "Month";
    String units "unitless";
  }
  Day {
    String long_name "Day";
    String units "unitless";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  Collection_Type {
    String long_name "Collection_type";
    String units "unitless";
  }
  Station {
    String long_name "Station";
    String units "unitless";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -90.30405, -89.59939;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Lat {
    Float32 actual_range 28.60353, 28.91338;
    String long_name "Lat";
    String units "degrees_north";
  }
  Sediment_depth {
    Float32 actual_range -3.2, 27.8;
    String long_name "Sediment_depth";
    String units "centimeters (cm)";
  }
  pH {
    Float32 actual_range 7.12451, 8.1;
    String long_name "Ph";
    String units "unitless (pH scale)";
  }
  O2 {
    Float32 actual_range 0.0, 247.3359;
    String long_name "O2";
    String units "micrometers (uM)";
  }
  sd_O2 {
    Float32 actual_range 0.0, 120.3073;
    String long_name "Sd_o2";
    String units "micrometers (uM)";
  }
  Mn_II {
    Float32 actual_range 0.0, 1108.084;
    String long_name "Mn_ii";
    String units "micrometers (uM)";
  }
  sd_Mn_II {
    Float32 actual_range 0.0, 119.1596;
    String long_name "Sd_mn_ii";
    String units "micrometers (uM)";
  }
  Fe_II {
    Float32 actual_range 0.0, 0.0;
    String long_name "Fe_ii";
    String units "micrometers (uM)";
  }
  sd_Fe_II {
    Float32 actual_range 0.0, 0.0;
    String long_name "Sd_fe_ii";
    String units "micrometers (uM)";
  }
  SH2S {
    Float32 actual_range 0.0, 0.0;
    String long_name "Sh2s";
    String units "micrometers (uM)";
  }
  sd_SH2S {
    Float32 actual_range 0.0, 0.0;
    String long_name "Sd_sh2s";
    String units "micrometers (uM)";
  }
  S2O3 {
    Float32 actual_range 0.0, 0.0;
    String long_name "S2o3";
    String units "micrometers (uM)";
  }
  sd_S2O3 {
    Float32 actual_range 0.0, 0.0;
    String long_name "Sd_s2o3";
    String units "micrometers (uM)";
  }
  Org_Fe_III {
    Float32 actual_range 0.0, 133.14;
    String long_name "Org_fe_iii";
    String units "nanoampere (nA)";
  }
  sd_Org_Fe_III {
    Float32 actual_range 0.0, 83.8063;
    String long_name "Sd_org_fe_iii";
    String units "nanoampere (nA)";
  }
  FeS_aq {
    Float32 actual_range 0.0, 0.0;
    String long_name "Fes_aq";
    String units "nanoampere (nA)";
  }
  sd_FeS_aq {
    Float32 actual_range 0.0, 0.0;
    String long_name "Sd_fes_aq";
    String units "nanoampere (nA)";
  }
 }
  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.904782.1";
    Float64 Easternmost_Easting -89.59939;
    Float64 geospatial_lon_max -89.59939;
    Float64 geospatial_lon_min -90.30405;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-09-21T17:22:40Z (local files)
2024-09-21T17:22:40Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_904782_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/904782";
    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 data set reports sediment depth profiles of dissolved O2, Mn2+, Fe2+, and total dissolved sulfide (SH2S) concentrations, as well as pH and current intensities of organic-Fe(III) complexes and aqueous clusters of FeS (FeS(aq)) that cannot be quantified directly. These data were obtained by profiling intact sediment cores using voltammetric and pH microelectrodes deployed on a computer-operated micromanipulator. Sediment cores were collected at five different stations on the Louisiana Shelf on the Northern Gulf of Mexico during the week of November 3-6, 2020 using an MC-800 multi-corer. These stations extend from the middle of the shelf offshore from Cocodrie, LA to the mouth of the Mississippi River North West Pass. All depth profiles were started within 30 minutes after collection. The field sampling was conducted during R/V Savannah cruise SAV-20-07.";
    String title "[Northern Gulf of Mexico electrochemical data Fall 2020] - Electrochemical data from sediment cores collected on the Louisiana Shelf of the Northern Gulf of Mexico during November 2020 on R/V Savannah cruise SAV-20-07 (Importance of Riverine Discharge on the Benthic Flux of Alkalinity to Continental Margins)";
    Float64 Westernmost_Easting -90.30405;
  }
}

 

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