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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Transparent Exopolymer Particles (TEP) CTD Bottle Measurements HRS2204] -
Transparent Exopolymer Particles (TEP) from CTD samples collected during R/V
Hugh R. Sharp cruise HRS2204 from Apr to May 2022 (Collaborative Research: The
importance of particle disaggregation on biogeochemical flux predictions)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_945964_v1)
Range: longitude = -72.2765 to -67.3996°E, latitude = 39.4554 to 41.7749°N, depth = 1.7 to 200.2m, time = 2022-04-23T21:17:57Z to 2022-05-01T15:56:44Z
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 {
  ID {
    String long_name "Id";
    String units "unitless";
  }
  Station {
    Int32 actual_range 1, 8;
    String long_name "Station";
    String units "unitless";
  }
  CTD {
    Int32 actual_range 2, 18;
    String long_name "Ctd";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 1.7, 200.2;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.650748677e+9, 1.651420604e+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 {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 39.4554, 41.7749;
    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 -72.2765, -67.3996;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  TEP_xg {
    Float32 actual_range 3.12, 375.73;
    String long_name "Tep_xg";
    String units "micrograms per liter (ug/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.945964.1";
    Float64 Easternmost_Easting -67.3996;
    Float64 geospatial_lat_max 41.7749;
    Float64 geospatial_lat_min 39.4554;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -67.3996;
    Float64 geospatial_lon_min -72.2765;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 200.2;
    Float64 geospatial_vertical_min 1.7;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-03-01T09:55:49Z (local files)
2025-03-01T09:55:49Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_945964_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/945964";
    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 41.7749;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 39.4554;
    String summary "These data include measurements of transparent exopolymer particles (TEP) from CTD bottle water samples collected during a cruise on the Northeast Continental Shelf to study particle disaggregation. One cruise was completed aboard the R/V Hugh R. Sharp from 2022-04-21 through 2022-05-02 (HRS22-04), which visited a variety of stations and hydrodynamic environments associated with the Northeast Continental Shelf of the United States. Stations ranged from Georges Bank and the Great South Channel near the Gulf of Maine, Martha's Vineyard, the mouth of the Sakonnet River near Newport, Rhode Island, and Hudson Canyon near New York. TEP measurements were performed following recently published methods relying on Alcian Blue staining protocols and spectrophotometry. These data were collected as part of a study to clarify the importance of hydrodynamic forces on the cohesion, aggregation, and breakup of marine particles. These data were collected by Dr. Kieran Curran of the University of New Hampshire on the cruise led by Dr. Matthew Rau (chief-sci) of the George Washington University.";
    String time_coverage_end "2022-05-01T15:56:44Z";
    String time_coverage_start "2022-04-23T21:17:57Z";
    String title "[Transparent Exopolymer Particles (TEP) CTD Bottle Measurements HRS2204] - Transparent Exopolymer Particles (TEP) from CTD samples collected during R/V Hugh R. Sharp cruise HRS2204 from Apr to May 2022 (Collaborative Research: The importance of particle disaggregation on biogeochemical flux predictions)";
    Float64 Westernmost_Easting -72.2765;
  }
}

 

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