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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [2019 BAIT / GApr13 Dissolved Iron Concentration and Isotopes] - Dissolved
iron concentrations and stable isotope ratios from water column samples
collected during four Bermuda Atlantic Iron Time-series (BAIT) cruises EN631,
AE1909, AE1921, AE1930 in the Western Subtropical North Atlantic Gyre in
2019 (NSFGEO-NERC: Collaborative Research: Using Time-series Field Observations
to Constrain an Ocean Iron Model)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_936824_v1)
Range: longitude = -64.815 to -63.58°E, latitude = 31.177 to 32.151°N, depth = 0.5 to 1677.5m
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_ID {
    String long_name "Cruise_id";
    String units "unitless";
  }
  Station_ID {
    String long_name "Station_id";
    String units "unitless";
  }
  Start_Date_UTC {
    String long_name "Start_date_utc";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 31.177, 32.151;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Start_latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -64.815, -63.58;
    String axis "X";
    String ioos_category "Location";
    String long_name "Start_longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Sample_ID {
    String long_name "Sample_id";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.5, 1677.5;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Sample_depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Fe_56_54_D_DELTA_BOTTLE {
    Float32 actual_range 0.23, 1.21;
    String long_name "Fe_56_54_d_delta_bottle";
    String units "per mil (‰)";
  }
  SD1_Fe_56_54_D_DELTA_BOTTLE {
    Float32 actual_range 0.05, 0.18;
    String long_name "Sd1_fe_56_54_d_delta_bottle";
    String units "per mil (‰)";
  }
  Flag_Fe_56_54_D_DELTA_BOTTLE {
    Int32 actual_range 2, 9;
    String long_name "Flag_fe_56_54_d_delta_bottle";
    String units "unitless";
  }
  Fe_D_CONC_BOTTLE {
    Float32 actual_range 0.09, 0.819;
    String long_name "Fe_d_conc_bottle";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  SD1_Fe_D_CONC_BOTTLE {
    Float32 actual_range 0.002, 0.016;
    String long_name "Sd1_fe_d_conc_bottle";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  Flag_Fe_D_CONC_BOTTLE {
    Int32 actual_range 2, 9;
    String long_name "Flag_fe_d_conc_bottle";
    String units "unitless";
  }
  Fe_56_54_D_DELTA_BOAT_PUMP {
    Float32 actual_range 0.3, 0.51;
    String long_name "Fe_56_54_d_delta_boat_pump";
    String units "per mil (‰)";
  }
  SD1_Fe_56_54_D_DELTA_BOAT_PUMP {
    Float32 actual_range 0.05, 0.05;
    String long_name "Sd1_fe_56_54_d_delta_boat_pump";
    String units "per mil (‰)";
  }
  Flag_Fe_56_54_D_DELTA_BOAT_PUMP {
    Int32 actual_range 2, 2;
    String long_name "Flag_fe_56_54_d_delta_boat_pump";
    String units "unitless";
  }
  Fe_D_CONC_BOAT_PUMP {
    Float32 actual_range 0.793, 1.181;
    String long_name "Fe_d_conc_boat_pump";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  SD1_Fe_D_CONC_BOAT_PUMP {
    Float32 actual_range 0.016, 0.024;
    String long_name "Sd1_fe_d_conc_boat_pump";
    String units "nanomoles per kilogram (nmol/kg)";
  }
  Flag_Fe_D_CONC_BOAT_PUMP {
    Int32 actual_range 2, 2;
    String long_name "Flag_fe_d_conc_boat_pump";
    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.936824.1";
    Float64 Easternmost_Easting -63.58;
    Float64 geospatial_lat_max 32.151;
    Float64 geospatial_lat_min 31.177;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -63.58;
    Float64 geospatial_lon_min -64.815;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 1677.5;
    Float64 geospatial_vertical_min 0.5;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-01-15T19:43:15Z (local files)
2025-01-15T19:43:15Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_936824_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/936824";
    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 32.151;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 31.177;
    String summary "These data include dissolved iron (Fe) concentrations and stable isotope ratios (δ56Fe relative to IRMM-014) from water column samples collected during four Bermuda Atlantic Iron Time-Series (BAIT) cruises (GApr13) in the Bermuda Atlantic Time-series Study (BATS) region in March, May, August, and November 2019. Analyses were carried out at the University of South Florida.";
    String title "[2019 BAIT / GApr13 Dissolved Iron Concentration and Isotopes] - Dissolved iron concentrations and stable isotope ratios from water column samples collected during four Bermuda Atlantic Iron Time-series (BAIT) cruises EN631, AE1909, AE1921, AE1930 in the Western Subtropical North Atlantic Gyre in 2019 (NSFGEO-NERC: Collaborative Research: Using Time-series Field Observations to Constrain an Ocean Iron Model)";
    Float64 Westernmost_Easting -64.815;
  }
}

 

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