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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Tidal fDOM and Heterotrophic bacteria counts] - fDOM and Heterotrophic
bacteria counts in Oregon tide pools in July - August 2019 (CAREER: Predicting
ecosystem metabolism of rocky intertidal communities in warming and acidifying
oceans.)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_1009817_v1)
Range: time = 2019-07-08T15:48:00Z to 2019-08-06T19:13:00Z
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 ? )
   
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.56260088e+9, 1.56511878e+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";
  }
  pool_id {
    String long_name "Pool_id";
    String units "unitless";
  }
  foundation_spp {
    String long_name "Foundation_spp";
    String units "unitless";
  }
  LSID {
    String long_name "Lsid";
    String units "unitless";
  }
  aphiaID {
    String long_name "Aphiaid";
    String units "unitless";
  }
  day_night {
    String long_name "Day_night";
    String units "unitless";
  }
  before_after {
    String long_name "Before_after";
    String units "unitless";
  }
  removal_control {
    String long_name "Removal_control";
    String units "unitless";
  }
  time_point {
    String long_name "Time_point";
    String units "unitless";
  }
  sampling_date {
    String long_name "Sampling_date";
    String units "unitless";
  }
  sampling_time_local {
    String long_name "Sampling_time_local";
    String units "unitless";
  }
  heterotrophic_bacterioplankton_micro_l {
    Float32 actual_range 180.76, 1531.19;
    String long_name "Heterotrophic_bacterioplankton_micro_l";
    String units "cells uL^-1";
  }
  m_c {
    Float32 actual_range 0.7406742, 2.023649;
    String long_name "M_c";
    String units "unitless";
  }
  bix {
    Float32 actual_range 0.4714429, 2.258173;
    String long_name "Bix";
    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 defaultDataQuery "&amp;time&lt;now";
    String doi "10.26008/1912/bco-dmo.1009817.1";
    String history 
"2026-10-15T09:12:49Z (local files)
2026-10-15T09:12:49Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_1009817_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/1009817";
    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 
"Benthic–pelagic coupling, the reciprocal exchange of materials between benthic and pelagic habitats, has traditionally emphasized pelagic influences on benthic systems. Yet, the role of benthic biological processes in shaping pelagic microbial dynamics
remains under explored. We investigated how surfgrass and mussels regulate nitrogen and dissolved organic matter (DOM)cycling and their cascading effects on heterotrophic bacteria in Oregon tide pools. We quantified biogeochemical fluxes and bacterial responses before and after foundation species removal during contrasting upwelling regimes. Mussel-dominated pools released high concentrations of ammonium and nitrate, while surfgrass pools transformed DOM that fueled bacterial growth; upwelling intensified these benthic–pelagic linkages. Removing foundation species dampened nutrient release in mussel pools and reduced DOM-fueled bacterial growth in surfgrass pools, ultimately decoupling benthic productivity from pelagic microbial
growth. Our results demonstrate the critical role of foundation species to pelagic microbial processes and underscore the vulnerability of coastal microbial dynamics to their global decline. Here we present the fDOM and heterotrophic bacteria data.";
    String time_coverage_end "2019-08-06T19:13:00Z";
    String time_coverage_start "2019-07-08T15:48:00Z";
    String title "[Tidal fDOM and Heterotrophic bacteria counts] - fDOM and Heterotrophic bacteria counts in Oregon tide pools in July - August 2019 (CAREER: Predicting ecosystem metabolism of rocky intertidal communities in warming and acidifying oceans.)";
  }
}

 

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