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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [AE1913 Macronutrients, dissolved and particulate trace metals] -
Macronutrients and dissolved and particulate trace metals collected from the R/
V Atlantic Explorer cruise AE1913 in the Sargasso Sea in June of
2019 (Collaborative Research: Direct Characterization of Adaptive Nutrient
Stress Responses in the Sargasso Sea using Protein Biomarkers and a
Biogeochemical AUV)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_916429_v1)
Range: longitude = -71.12321 to -64.16629°E, depth = 10.0 to 1500.0m, time = 2019-06-16T20:45:00Z to 2019-06-27T19:20:00Z
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 ? )
   
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 {
  Station {
    Int32 actual_range 1, 9;
    String long_name "Station";
    String units "unitless";
  }
  Latitude {
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -71.12321, -64.16629;
    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";
    Int32 actual_range 10, 1500;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5607179e+9, 1.5616632e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Datetime_deploy";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  DateTime_recover {
    Float64 actual_range 1.56072126e+9, 1.56167694e+9;
    String ioos_category "Time";
    String long_name "Datetime_recover";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  dFe {
    Float32 actual_range 0.09, 3.95;
    String long_name "Dfe";
    String units "nanomolar (nM)";
  }
  dFeFlag {
    Int32 actual_range 1, 6;
    String long_name "Dfeflag";
    String units "unitless";
  }
  dZn {
    Float32 actual_range 0.26, 13.96;
    String long_name "Dzn";
    String units "nanomolar (nM)";
  }
  dZnFlag {
    Int32 actual_range 1, 6;
    String long_name "Dznflag";
    String units "unitless";
  }
  dCd {
    Float32 actual_range 0.0013, 0.394;
    String long_name "Dcd";
    String units "nanomolar (nM)";
  }
  dCdFlag {
    Int32 actual_range 1, 6;
    String long_name "Dcdflag";
    String units "unitless";
  }
  dNi {
    Float32 actual_range 1.87, 4.27;
    String long_name "Dni";
    String units "nanomolar (nM)";
  }
  dNiFlag {
    Int32 actual_range 1, 1;
    String long_name "Dniflag";
    String units "unitless";
  }
  dCu {
    Float32 actual_range 0.62, 1.84;
    String long_name "Dcu";
    String units "nanomolar (nM)";
  }
  dCuFlag {
    Int32 actual_range 1, 1;
    String long_name "Dcuflag";
    String units "unitless";
  }
  dMn {
    Float32 actual_range 0.1, 5.92;
    String long_name "Dmn";
    String units "nanomolar (nM)";
  }
  dMnFlag {
    Int32 actual_range 1, 1;
    String long_name "Dmnflag";
    String units "unitless";
  }
  PO4 {
    Float32 actual_range 0.1, 1.84;
    String long_name "Po4";
    String units "micromolar (uM)";
  }
  NO2_NO3 {
    Float32 actual_range 0.0, 26.2;
    String long_name "No2_no3";
    String units "micromolar (uM)";
  }
  Si {
    Float32 actual_range 0.0, 15.1;
    String long_name "Si";
    String units "micromolar (uM)";
  }
  NO2 {
    Float32 actual_range 0.0, 0.16;
    String long_name "No2";
    String units "micromolar (uM)";
  }
  NH4 {
    Float32 actual_range 0.0, 0.51;
    String long_name "Nh4";
    String units "micromolar (uM)";
  }
  pMn {
    Float32 actual_range 1.75, 109.25;
    String long_name "Pmn";
    String units "picomolar (pM)";
  }
  pFe {
    Float32 actual_range -20.45, 567.92;
    String long_name "Pfe";
    String units "picomolar (pM)";
  }
  pNi {
    Float32 actual_range 0.09, 13.19;
    String long_name "Pni";
    String units "picomolar (pM)";
  }
  pCu {
    Float32 actual_range 2.42, 62.41;
    String long_name "Pcu";
    String units "picomolar (pM)";
  }
  pZn {
    Float32 actual_range -50.69, 121.74;
    String long_name "Pzn";
    String units "picomolar (pM)";
  }
  pCd {
    Float32 actual_range 0.02, 3.19;
    String long_name "Pcd";
    String units "picomolar (pM)";
  }
 }
  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.916429.1";
    Float64 Easternmost_Easting -64.16629;
    Float64 geospatial_lon_max -64.16629;
    Float64 geospatial_lon_min -71.12321;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 1500.0;
    Float64 geospatial_vertical_min 10.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T05:51:08Z (local files)
2024-11-08T05:51:08Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_916429_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/916429";
    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 includes macronutrients and dissolved and particulate trace metals collected from the AE1913 expedition on the R/V Atlantic Explorer in June 2019. Seawater was collected with a trace metal rosette and filtered through a 0.2 um filter. Filtrate was used for nutrients and dissolved trace metals, and the filter was saved for the particulate metal analysis at select sites. Instruments used were a Alpkem Rapid Flow Analyzer, Technicon AutoAnalyzer II, and iCAP Q inductively coupled plasma mass spectrometer (ICP-MS). The goal of this analysis was to explore the relationship between trace metal/macronutrient availability and microbial metabolism across a section of the North Atlantic Ocean. This data was collected by Mak Saito and Natalie Cohen.";
    String time_coverage_end "2019-06-27T19:20:00Z";
    String time_coverage_start "2019-06-16T20:45:00Z";
    String title "[AE1913 Macronutrients, dissolved and particulate trace metals] - Macronutrients and dissolved and particulate trace metals collected from the R/V Atlantic Explorer cruise AE1913 in the Sargasso Sea in June of 2019 (Collaborative Research: Direct Characterization of Adaptive Nutrient Stress Responses in the Sargasso Sea using Protein Biomarkers and a Biogeochemical AUV)";
    Float64 Westernmost_Easting -71.12321;
  }
}

 

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