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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Water Column Nitrate d15N Cocos Ridge Upper 1000m] - Average nitrate d15N
values from the upper 1000 meters of the water column at four stations sampled
in the Eastern Tropical North Pacific on R/V Sally Ride cruise SR2113 in
December 2021 (Collaborative Research: New approaches to study calcium
carbonate dissolution on the sea floor and its impact on paleo-proxy
interpretations)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_933292_v1)
Range: longitude = -88.261 to -86.696°E, depth = 16.369 to 1000.386m
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 ? )
    [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 {
  Station_ID {
    String long_name "Station_id";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 16.369, 1000.386;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth_m";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  WC_NO3 {
    Float32 actual_range 0.89, 42.64;
    String long_name "Wc_no3";
    String units "micromoles per kilogram (umol/kg)";
  }
  WC_d15N {
    Float32 actual_range 6.12, 12.37;
    String long_name "Wc_d15n";
    String units "permille vs air";
  }
  WC_d15N_1sd {
    String long_name "Wc_d15n_1sd";
    String units "permille vs air";
  }
  Latitude {
    Float32 actual_range 5.9596, 6.7849;
    String long_name "Latitude";
    String units "degrees_east";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -88.261, -86.696;
    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";
  }
 }
  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.933292.1";
    Float64 Easternmost_Easting -86.696;
    Float64 geospatial_lon_max -86.696;
    Float64 geospatial_lon_min -88.261;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 1000.386;
    Float64 geospatial_vertical_min 16.369;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-11-23T08:02:53Z (local files)
2024-11-23T08:02:53Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_933292_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/933292";
    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 "We report nitrate isotope data at four stations (CR01, CR02, CR03, and CR05) in the Eastern Tropical North Pacific (ETNP). The cruise (R/V Sally Ride SR2113) occupied these four stations near the Cocos Ridge between 6.8 to 5.3 degrees North latitude and 86.6 to 88.26 degrees West longitude. Sampling occurred between December 2-14, 2021. A 24-bottle Niskin rosette and CTD were used to collect 30-milliliter (mL) water samples that were later analyzed using the denitrifier method. The data were collected by Kameko Landry in the Stable Isotope Biogeochemistry Laboratory at Boston College.";
    String title "[Water Column Nitrate d15N Cocos Ridge Upper 1000m] - Average nitrate d15N values from the upper 1000 meters of the water column at four stations sampled in the Eastern Tropical North Pacific on R/V Sally Ride cruise SR2113 in December 2021 (Collaborative Research: New approaches to study calcium carbonate dissolution on the sea floor and its impact on paleo-proxy interpretations)";
    Float64 Westernmost_Easting -88.261;
  }
}

 

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