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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [GP17-ANT Fe-binding humic-like substances] - Concentrations of iron bound to
humic-like substances and total iron-binding capacity of humic-like substances
from discrete samples collected on the GP17-ANT RVIB Palmer cruise NBP24-01 in
the Amundsen Sea from Nov 2023 to Jan 2024 (Collaborative Research: U.S.
GEOTRACES GP17-OCE and GP17-ANT: Characterizing iron-binding organic ligands in
the Southern Ocean and implications for iron cycling in the global ocean) Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_969502_v1)
Range: depth = 2.0 to 4659.1m, time = 2012-12-12T20:31:00Z to 2024-01-13T12:52: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 {
  CRUISE_ID {
    String long_name "Cruise_id";
    String units "unitless";
  }
  SECT_ID {
    String long_name "Sect_id";
    String units "unitless";
  }
  STNNBR {
    Int32 actual_range 3, 29;
    String long_name "Stnnbr";
    String units "unitless";
  }
  PLATFORM {
    String long_name "Platform";
    String units "unitless";
  }
  CASTNO {
    Int32 actual_range 1, 11;
    String long_name "Castno";
    String units "unitless";
  }
  SAMPNO {
    Int32 actual_range 1, 23;
    String long_name "Sampno";
    String units "unitless";
  }
  EVENT_NO {
    Int32 actual_range 1016, 1287;
    String long_name "Event_no";
    String units "unitless";
  }
  GEOTRC_SAMPNO {
    Int32 actual_range 18824, 21018;
    String long_name "Geotrc_sampno";
    String units "unitless";
  }
  BTLNBR {
    String long_name "Btlnbr";
    String units "unitless";
  }
  DATE {
    String long_name "Date";
    String units "unitless";
  }
  time_unitless {
    String long_name "Time";
    String units "unitless";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.35534426e+9, 1.70515032e+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";
  }
  LATITUDE {
    Float32 actual_range -74.3892, -66.9774;
    String long_name "Latitude";
    String units "degrees_north";
  }
  LONGITUDE {
    Float32 actual_range -133.0225, -99.6837;
    String long_name "Longitude";
    String units "degrees_east";
  }
  DEPTH {
    Int32 actual_range 317, 4699;
    String long_name "Depth";
    String units "meters (m)";
  }
  CTDPRS {
    Float32 actual_range 7.86, 4758.28;
    String long_name "Ctdprs";
    String units "decibars (db)";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 2.0, 4659.1;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Sampdepth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  BTL_DATE {
    String long_name "Btl_date";
    String units "unitless";
  }
  BTL_TIME {
    String long_name "Btl_time";
    String units "unitless";
  }
  BTL_ISO_DateTime_UTC {
    Float64 actual_range 1.7020068e+9, 1.705152e+9;
    String ioos_category "Time";
    String long_name "Btl_iso_datetime_utc";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  BTL_LAT {
    Float32 actual_range -74.3816, -66.9775;
    String long_name "Btl_lat";
    String units "degrees_north";
  }
  BTL_LON {
    Float32 actual_range -133.0231, -99.6837;
    String long_name "Btl_lon";
    String units "degrees_east";
  }
  HSFe_D_CONC {
    Float32 actual_range 0.06, 0.8;
    String long_name "Hsfe_d_conc";
    String units "nanomoles Fe equivalents per liter (NMOL_FE_EQ/L)";
  }
  HSFe_D_STDEV {
    Float32 actual_range 0.0, 0.12;
    String long_name "Hsfe_d_stdev";
    String units "nanomoles Fe equivalents per liter (NMOL_FE_EQ/L)";
  }
  HSFe_D_COUNT {
    Int32 actual_range 1, 4;
    String long_name "Hsfe_d_count";
    String units "unitless";
  }
  HSFe_D_FLAG {
    Int32 actual_range 1, 9;
    String long_name "Hsfe_d_flag";
    String units "unitless";
  }
  THSFe_D_CONC {
    Float32 actual_range 0.12, 3.91;
    String long_name "Thsfe_d_conc";
    String units "nanomoles Fe equivalents per liter (NMOL_FE_EQ/L)";
  }
  THSFe_D_STDEV {
    Float32 actual_range 0.0, 0.15;
    String long_name "Thsfe_d_stdev";
    String units "nanomoles Fe equivalents per liter (NMOL_FE_EQ/L)";
  }
  THSFe_D_COUNT {
    Int32 actual_range 1, 4;
    String long_name "Thsfe_d_count";
    String units "unitless";
  }
  THSFe_D_FLAG {
    Int32 actual_range 1, 9;
    String long_name "Thsfe_d_flag";
    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 defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.969502.1";
    Float64 geospatial_vertical_max 4659.1;
    Float64 geospatial_vertical_min 2.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-08-02T17:30:20Z (local files)
2025-08-02T17:30:20Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_969502_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/969502";
    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 dataset includes the concentrations of iron (Fe) bound to humic-like substances and total iron-binding capacity of humic-like substances from discrete depth profile and towfish samples collected on the GP17-ANT cruise NBP24-01 on the R/V IB Nathaniel B. Palmer in the Amundsen Sea from 29 November 2023 to 28 January 2024.

This project investigates the impact of Fe-binding humic-like substances on Fe biogeochemistry in the Amundsen Sea. The project used a combination of depth profile and surface towfish samples to characterize the contributions of humic-like substances to Fe biogeochemistry across gradients in primary production, water masses, and bathymetric features in the Amundsen Sea. Understanding the distributions of Fe-binding humic-like substances provides insight into the impact of compositional changes of the Fe-binding ligand pool on Fe biogeochemistry and may help elucidate specific sources of these ligands.";
    String time_coverage_end "2024-01-13T12:52:00Z";
    String time_coverage_start "2012-12-12T20:31:00Z";
    String title "[GP17-ANT Fe-binding humic-like substances] - Concentrations of iron bound to humic-like substances and total iron-binding capacity of humic-like substances from discrete samples collected on the GP17-ANT RVIB Palmer cruise NBP24-01 in the Amundsen Sea from Nov 2023 to Jan 2024 (Collaborative Research: U.S. GEOTRACES GP17-OCE and GP17-ANT: Characterizing iron-binding organic ligands in the Southern Ocean and implications for iron cycling in the global ocean)";
  }
}

 

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