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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [ETNP 2012 McClane Pump POM] - Suspended Organic Particle concentration and
stable C and N isotopes (collected with McClane Pumps and GF/F filters) from
the Eastern Tropical North Pacific on the R/V Thompson cruise TN278 in April
2012 (The role of cryptic nutrient cycling within sinking particles on trace
element transport in oxygen minimum zones)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_948746_v1)
Range: longitude = -107.17 to -105.99°E, latitude = 16.51 to 20.19°N, depth = 15.0 to 2500.0m
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 {
  Sample {
    String long_name "Sample";
    String units "unitless";
  }
  St {
    String long_name "St";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 16.51, 20.19;
    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 -107.17, -105.99;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Date {
    String long_name "Date";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 15, 2500;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  Nitrogen {
    Float32 actual_range 0.01, 1.11;
    String long_name "Nitrogen";
    String units "micromolar (uM)";
  }
  Carbon {
    Float32 actual_range 0.05, 9.81;
    String long_name "Carbon";
    String units "micromolar (uM)";
  }
  d15N_Air {
    Float32 actual_range 7.72, 17.54;
    String long_name "D15n_air";
    String units "permil (0/00)";
  }
  d13C_VPDB {
    Float32 actual_range -26.82, -22.29;
    String long_name "D13c_vpdb";
    String units "permil (0/00)";
  }
  C_to_N {
    Float32 actual_range 6.05, 11.43;
    String long_name "C_to_n";
    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.948746.1";
    Float64 Easternmost_Easting -105.99;
    Float64 geospatial_lat_max 20.19;
    Float64 geospatial_lat_min 16.51;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -105.99;
    Float64 geospatial_lon_min -107.17;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 2500.0;
    Float64 geospatial_vertical_min 15.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-02-10T06:40:08Z (local files)
2025-02-10T06:40:08Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_948746_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/948746";
    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 20.19;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 16.51;
    String summary 
"Suspended organic carbon and nitrogen concentrations and stable isotopes were obtained on the R/V Thompson cruise TN278 at St P2 (16.5 N 107.1 W; known as BB2 on this cruise) and at St P1 (20.1 N 106.0 W; known as BB1 on this cruise) in the Eastern Tropical North Pacific Oxygen Deficient Zone in April 2012. The Oxygen Deficient Zone extended from 105 m to 820 m at St P2 and from 95 to 800 m at St P1. Water was filtered onto 142 mm pre-combusted GF/F filters in situ using McClane pumps (on average ~300-500 L) in a depth profile. Two 21 mm diameter punches were obtained from each 142 mm filter and used for organic matter analysis. Sample punches were wafted with HCl overnight to remove carbonate and sent to the UC Davis Stable Isotope Facility (Davis, CA) for C and N analysis. 

The purpose of this sampling was to quantify suspended organic matter in an offshore Oxygen Deficient Zone. 

Jacquelyn Neibauer and Rick Keil of the University of Washington deployed the McClane pumps on the cruise. Jacquelyn Neibauer was in charge of prepping the samples. Megan Duffy and Clara Fuchsman of the University of Washington analyzed the data.";
    String title "[ETNP 2012 McClane Pump POM] - Suspended Organic Particle concentration and stable C and N isotopes (collected with McClane Pumps and GF/F filters) from the Eastern Tropical North Pacific on the R/V Thompson cruise TN278 in April 2012 (The role of cryptic nutrient cycling within sinking particles on trace element transport in oxygen minimum zones)";
    Float64 Westernmost_Easting -107.17;
  }
}

 

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