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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [EMB276 Baltic Sea iodine depth profiles 2021] - Iodine speciation depth
profile measurements from the Gotland Deep and Fårö Deep, Baltic Sea, collected
aboard R/V Elisabeth Mann Borgese cruise EMB276 in Sep 2021 (Collaborative
Research: Manganese Cycling and Coupling Across Redox Boundaries within
Stratified Basins of the Baltic Sea)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_1000767_v1)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 sample_ID (unitless) ?          "EMB276-S1-D1"    "EMB276-S7-D9_C2"
 station_number (unitless) ?          "TF260"    "go32"
 depth (m) ?          14.75    130.5
  < slider >
 iodide_concentration (nanomole/kg) ?          32.7    217.9
 iodate_concentration (nanomole/kg) ?          8.57    40.98
 iodate_concentration_flag (unitless) ?          "<10"    "<10"
 DOI_concentration (nanomole/kg) ?          13.06    18.82
 DOI_concentration_flag (unitless) ?          "<10"    "<10"
 Total_I_concentration (nanomole/kg) ?          27.92    212.09
 time (Iso_datetime_collected_utc, UTC) ?          2021-09-20T15:03:00Z    2021-09-27T12:58:00Z
  < slider >
 latitude (degrees_north) ?          56.6334    58.0004
  < slider >
 longitude (degrees_east) ?          19.1831    20.6501
  < slider >
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  sample_ID {
    String long_name "Sample_id";
    String units "unitless";
  }
  station_number {
    String long_name "Station_number";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 14.75, 130.5;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  iodide_concentration {
    Float32 actual_range 32.7, 217.9;
    String long_name "Iodide_concentration";
    String units "nanomole/kg";
  }
  iodate_concentration {
    Float32 actual_range 8.57, 40.98;
    String long_name "Iodate_concentration";
    String units "nanomole/kg";
  }
  iodate_concentration_flag {
    String long_name "Iodate_concentration_flag";
    String units "unitless";
  }
  DOI_concentration {
    Float32 actual_range 13.06, 18.82;
    String long_name "Doi_concentration";
    String units "nanomole/kg";
  }
  DOI_concentration_flag {
    String long_name "Doi_concentration_flag";
    String units "unitless";
  }
  Total_I_concentration {
    Float32 actual_range 27.92, 212.09;
    String long_name "Total_i_concentration";
    String units "nanomole/kg";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.63215018e+9, 1.63274748e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "Iso_datetime_collected_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 56.6334, 58.0004;
    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 19.1831, 20.6501;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  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 defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.1000767.1";
    Float64 Easternmost_Easting 20.6501;
    Float64 geospatial_lat_max 58.0004;
    Float64 geospatial_lat_min 56.6334;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 20.6501;
    Float64 geospatial_lon_min 19.1831;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 130.5;
    Float64 geospatial_vertical_min 14.75;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-09-15T12:00:18Z (local files)
2026-09-15T12:00:18Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_1000767_v1.html";
    String infoUrl "https://osprey.bco-dmo.org/dataset/1000767";
    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 58.0004;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 56.6334;
    String summary "The Baltic Sea samples were collected from depth profiles including the surface layer and chemocline at 6 stations in the Gotland Deep and 1 station from the adjacent Fårö Deep, during the R/V Elisabeth Mann Borgese EMB276 cruise September 17 to 29, 2021. The samples focused on these intervals to understanding the cycling of iodine and other redox-sensitive elements at low but present oxygen conditions. Measurements for iodine speciation were made at Michigan State University within 1 year of sampling. Methods specifically applied iodine exchange chromatography to separate and individually measure each total dissolved iodine, dissolved iodate, dissolved iodide, and dissolved organic iodine with inductively coupled plasma mass spectrometry.";
    String time_coverage_end "2021-09-27T12:58:00Z";
    String time_coverage_start "2021-09-20T15:03:00Z";
    String title "[EMB276 Baltic Sea iodine depth profiles 2021] - Iodine speciation depth profile measurements from the Gotland Deep and Fårö Deep, Baltic Sea, collected aboard R/V Elisabeth Mann Borgese cruise EMB276 in Sep 2021 (Collaborative Research: Manganese Cycling and Coupling Across Redox Boundaries within Stratified Basins of the Baltic Sea)";
    Float64 Westernmost_Easting 19.1831;
  }
}

 

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