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

ERDDAP > tabledap > Data Access Form ?

Dataset Title:  [EN683 FLA-Bead Data and ULake] - Detection of polysaccharide enzymatic
hydrolysis using a novel detection method from waters taken aboard the R/V
Endeavor in the Western North Atlantic (EN683 in May and June, 2022), and from
a freshwater lake in North Carolina in 2025 (Substrate structural complexity
and abundance control distinct mechanisms of microbially-driven carbon cycling
in the ocean)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_988643_v1)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Files | Make a graph
 
Variable ?   Optional
Constraint #1 ?
Optional
Constraint #2 ?
   Minimum ?
 
   Maximum ?
 
 deployment (unitless) ?          "EN683"    "U.Lake"
 station (unitless) ?          "21-A"    "crew dock"
 latitude (degrees_north) ?          33.74342    42.8701
  < slider >
 longitude (degrees_east) ?          -79.0935    -53.8678
  < slider >
 sample_date (unitless) ?          "2022-05-24"    "2025-08-11"
 sample_time (unitless) ?          "10:07"    "9:55:00"
 ISO_DateTime_Local (unitless) ?          "2022-05-24T21:50:00"    "2025-08-11T09:55:00"
 source (unitless) ?          "Bicarbonate"    "surface_105 um_fil..."
 depth (Depth_actual, m) ?          0.2    4092.0
  < slider >
 temperature (degrees Celsius) ?          2.3    27.0
 salinity (grams per liter (g/L)) ?          0.036    36.68
 incubation_time (hours) ?          0.0    697.9
 live1 (fluorescence units) ?          -2.95    95.13
 live2 (fluorescence units) ?          -3.9    98.99
 live3 (fluorescence units) ?          -2.58    83.59
 kill1 (fluorescence units) ?          -11.7    52.2
 kill2 (fluorescence units) ?          -13.5    45.0
 kill3 (fluorescence units) ?          -12.2    50.0
 live_avg (fluorescence units) ?          -0.45    78.07
 live_avg_std (fluorescence units) ?          0.0    26.12
 kill_avg (fluorescence units) ?          -12.37    49.07
 kill_avg_std (fluorescence units) ?          0.0    4.19
 
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.Hover here to see a list of options. Click on an option to select it.")

File type: (more information)

(Documentation / Bypass this form ? )
 
(Please be patient. It may take a while to get the data.)


 

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  deployment {
    String long_name "Deployment";
    String units "unitless";
  }
  station {
    String long_name "Station";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 33.74342, 42.8701;
    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 -79.0935, -53.8678;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  sample_date {
    String long_name "Sample_date";
    String units "unitless";
  }
  sample_time {
    String long_name "Sample_time";
    String units "unitless";
  }
  ISO_DateTime_Local {
    String long_name "Iso_datetime_local";
    String units "unitless";
  }
  source {
    String long_name "Source";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.2, 4092.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth_actual";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  temperature {
    Float32 actual_range 2.3, 27.0;
    String long_name "Temperature";
    String units "degrees Celsius";
  }
  salinity {
    Float32 actual_range 0.036, 36.68;
    String long_name "Salinity";
    String units "grams per liter (g/L)";
  }
  incubation_time {
    Float32 actual_range 0.0, 697.9;
    String long_name "Incubation_time";
    String units "hours";
  }
  live1 {
    Float32 actual_range -2.95, 95.13;
    String long_name "Live1";
    String units "fluorescence units";
  }
  live2 {
    Float32 actual_range -3.9, 98.99;
    String long_name "Live2";
    String units "fluorescence units";
  }
  live3 {
    Float32 actual_range -2.58, 83.59;
    String long_name "Live3";
    String units "fluorescence units";
  }
  kill1 {
    Float32 actual_range -11.7, 52.2;
    String long_name "Kill1";
    String units "fluorescence units";
  }
  kill2 {
    Float32 actual_range -13.5, 45.0;
    String long_name "Kill2";
    String units "fluorescence units";
  }
  kill3 {
    Float32 actual_range -12.2, 50.0;
    String long_name "Kill3";
    String units "fluorescence units";
  }
  live_avg {
    Float32 actual_range -0.45, 78.07;
    String long_name "Live_avg";
    String units "fluorescence units";
  }
  live_avg_std {
    Float32 actual_range 0.0, 26.12;
    String long_name "Live_avg_std";
    String units "fluorescence units";
  }
  kill_avg {
    Float32 actual_range -12.37, 49.07;
    String long_name "Kill_avg";
    String units "fluorescence units";
  }
  kill_avg_std {
    Float32 actual_range 0.0, 4.19;
    String long_name "Kill_avg_std";
    String units "fluorescence units";
  }
 }
  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.988643.1";
    Float64 Easternmost_Easting -53.8678;
    Float64 geospatial_lat_max 42.8701;
    Float64 geospatial_lat_min 33.74342;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -53.8678;
    Float64 geospatial_lon_min -79.0935;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 4092.0;
    Float64 geospatial_vertical_min 0.2;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-09-02T12:10:10Z (local files)
2026-09-02T12:10:10Z https://erddap.bco-dmo.org/erddap/tabledap/bcodmo_dataset_988643_v1.html";
    String infoUrl "https://osprey.bco-dmo.org/dataset/988643";
    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 42.8701;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 33.74342;
    String summary 
"A key focus of this project's field work is investigating the potential of marine heterotrophic microbial communities from different water masses and under differing conditions of organic matter availability to hydrolyze six well-characterized high-molecular-weight (HMW) polysaccharides (arabinogalactan, chondroitin sulfate, fucoidan, laminarin, pullulan, and xylan). However, the current method is extremely work-intensive, and results are usually acquired months after initial sampling. Having a proxy to determine real-time enzymatic activity would be useful for scientists doing field work because it would provide a guide as to when and where optimal conditions are located to conduct water column sampling. In an effort to improve field detection techniques, a novel and relatively rapid detection method was developed to detect the hydrolysis of fluorescently-labeled laminarin that is linked to epoxy-activated-agarose beads. Laminarin was used because it is commonly found throughout the surface water of the ocean (Becker et al. 2020). Our goal is to detect potential enzymatic activity within 48 hours using minimal lab equipment while maintaining an accuracy similar to the current standard method used in previous research. Furthermore, we hope the method will provide real-time information for scientists in the field. 
 
This dataset includes the detection of polysaccharide enzymatic hydrolysis using a novel and relatively rapid detection method from waters taken aboard the R/V Endeavor in the Western North Atlantic during the research cruise EN683 in May and June, 2022, and from a local freshwater lake.";
    String title "[EN683 FLA-Bead Data and ULake] - Detection of polysaccharide enzymatic hydrolysis using a novel detection method from waters taken aboard the R/V Endeavor in the Western North Atlantic (EN683 in May and June, 2022), and from a freshwater lake in North Carolina in 2025 (Substrate structural complexity and abundance control distinct mechanisms of microbially-driven carbon cycling in the ocean)";
    Float64 Westernmost_Easting -79.0935;
  }
}

 

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