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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [GP15 Iron Ligands in Particles] - Iron ligand concentration in particles (1-
51 μm) analyzed by liquid chromatography-mass spectrometry from samples
collected on the US GEOTRACES Pacific Meridional Transect (PMT) cruise
RR1814 (GP15) on R/V Roger Revelle in October 2018 (Trace Element Organic
Speciation along the US GEOTRACES Pacific Meridional Transect)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_929884_v1)
Range: longitude = -152.0 to -151.9999°E, depth = 38.0 to 499.0m, time = 2018-10-01T20:35:00Z to 2018-10-13T15: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 {
  Sample {
    String long_name "Sample";
    String units "unitless";
  }
  Station {
    Int32 actual_range 6, 14;
    String long_name "Station";
    String units "unitless";
  }
  Lat {
    Float32 actual_range 31.99997, 51.99467;
    String long_name "Lat";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -152.0, -151.9999;
    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 38, 499;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Ferrioxamine_G {
    Float32 actual_range 0.02, 7.8;
    String long_name "Ferrioxamine_g";
    String units "picomolar (pM)";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5384261e+9, 1.53944592e+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";
  }
 }
  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.929884.1";
    Float64 Easternmost_Easting -151.9999;
    Float64 geospatial_lon_max -151.9999;
    Float64 geospatial_lon_min -152.0;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 499.0;
    Float64 geospatial_vertical_min 38.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-08T06:10:41Z (local files)
2024-11-08T06:10:41Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_929884_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/929884";
    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 iron ligand concentration in particles (1-51 μm) analyzed by liquid chromatography-mass spectrometry. Samples were collected on the US GEOTRACES Pacific Meridional Transect (PMT) cruises (GP15, RR1814 & RR1815) on R/V Roger Revelle from September to November 2018.";
    String time_coverage_end "2018-10-13T15:52:00Z";
    String time_coverage_start "2018-10-01T20:35:00Z";
    String title "[GP15 Iron Ligands in Particles] - Iron ligand concentration in particles (1-51 μm) analyzed by liquid chromatography-mass spectrometry from samples collected on the US GEOTRACES Pacific Meridional Transect (PMT) cruise RR1814 (GP15) on R/V Roger Revelle in October 2018 (Trace Element Organic Speciation along the US GEOTRACES Pacific Meridional Transect)";
    Float64 Westernmost_Easting -152.0;
  }
}

 

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