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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [POC from RIPPLE cruises] - Particulate organic carbon data from cruises EN667
in the Gulf of Maine in June 2021, SR2310 along the Oregon Coast in May 2023,
and AE2320 in the Sargasso Sea in September 2023 (RIPPLE1, RIPPLE2, and
RIPPLE3) (Production and Fate of Fats in the Upper Ocean)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_997837_v1)
Range: longitude = -125.0735 to -64.14667°E, latitude = 31.66367 to 44.5265°N, depth = 5.0 to 150.0m, time = 2021-06-14T09:19:00Z to 2023-09-10T10:02:00Z
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: 
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";
  }
  Cruise_Name {
    String long_name "Cruise_name";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 31.66367, 44.5265;
    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 -125.0735, -64.14667;
    String axis "X";
    String ioos_category "Location";
    String long_name "Long";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.62366234e+9, 1.69434012e+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";
  }
  Cast {
    Int32 actual_range 4, 37;
    String long_name "Cast";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 5, 150;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  POC {
    Float32 actual_range 9.78833e-4, 0.3133105;
    String long_name "Poc";
    String units "milligrams per liter (mg/L)";
  }
 }
  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.997837.1";
    Float64 Easternmost_Easting -64.14667;
    Float64 geospatial_lat_max 44.5265;
    Float64 geospatial_lat_min 31.66367;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -64.14667;
    Float64 geospatial_lon_min -125.0735;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 150.0;
    Float64 geospatial_vertical_min 5.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-09-15T08:03:01Z (local files)
2026-09-15T08:03:01Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_997837_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/997837";
    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 44.5265;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 31.66367;
    String summary "This dataset includes particulate organic carbon (POC) data from samples collected on three research cruises in 2021 and 2023. In the Gulf of Maine, samples were collected on R/V Endeavor (cruise EN667) from 13 June to 21 June, 2021. Off the Oregon Coast, samples were on the R/V Sally Ride (cruise SR2310) from 18 May to 25 May, 2023. In the Sargasso Sea, samples were collected on R/V Atlantic Explorer (cruise AE2320) from 5 September to 11 September, 2023. Water was collected by CTD and samples for POC analysis were collected via vacuum filtration onto 0.7 micrometer (um) GF/F filters. The goal of these cruises was to investigate diel carbon cycling in the surface ocean, led by Chief Scientist Ben Van Mooy.";
    String time_coverage_end "2023-09-10T10:02:00Z";
    String time_coverage_start "2021-06-14T09:19:00Z";
    String title "[POC from RIPPLE cruises] - Particulate organic carbon data from cruises EN667 in the Gulf of Maine in June 2021, SR2310 along the Oregon Coast in May 2023, and AE2320 in the Sargasso Sea in September 2023 (RIPPLE1, RIPPLE2, and RIPPLE3) (Production and Fate of Fats in the Upper Ocean)";
    Float64 Westernmost_Easting -125.0735;
  }
}

 

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