BCO-DMO ERDDAP
Accessing BCO-DMO data

Make A Graph

Dataset Title:	[Zooplankton In Situ Videos] - In Situ Amphipod and Copepod Video Output Captured by the Hoodsport ORCA Profiling Mooring Mounted SPC-2 Zoocam in the Hood Canal, Puget Sound, Washington from August to September 2018 (Zooplankton Swimming project) (Causes and consequences of hypoxia and pH impacts on zooplankton: Linking movement behavior to vertical distribution.)
Institution:	BCO-DMO (Dataset ID: bcodmo_dataset_928222_v1)
Range:	depth = 6.79033 to 100.8278m
Information:	Summary \| License \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:

X Axis:

Y Axis:

Color:

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.

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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  vid_id {
    Int32 actual_range 1534432153, 1537966443;
    String long_name "Vid_id";
    String units "unitless";
  }
  datetime_utc {
    String long_name "Datetime_utc";
    String units "unitless";
  }
  total_frames {
    Int32 actual_range 77, 1196;
    String long_name "Total_frames";
    String units "frames";
  }
  avg_frm_rate {
    Float32 actual_range 19.06343, 20.47889;
    String long_name "Avg_frm_rate";
    String units "frames per second";
  }
  nearest_ctd_cast {
    String long_name "Nearest_ctd_cast";
    String units "unitless";
  }
  nearest_ctd_offset {
    String long_name "Nearest_ctd_offset";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 6.79033, 100.8278;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  oxygen {
    Float32 actual_range 1.397794, 3.386604;
    String long_name "Oxygen";
    String units "milligrams per liter (mg/L)";
  }
  temperature {
    Float32 actual_range 9.685058, 10.90912;
    String long_name "Temperature";
    String units "degrees Celcius";
  }
 }
  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.928222.1";
    Float64 geospatial_vertical_max 100.8278;
    Float64 geospatial_vertical_min 6.79033;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-09-24T09:12:46Z (local files)
2024-09-24T09:12:46Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_928222_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/928222";
    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 "This dataset consists of videos of zooplankton swimming taken by an in-situ camera system (the SPC UW ZooCam) that was deployed on the Hoodsport ORCA profiling mooring in Hood Canal (Puget Sound), WA in summer 2018. Understanding zooplankton population dynamics is challenging, largely because traditional methods for quantifying zooplankton distributions are costly, limited in scope, and require extended analysis by trained analysts. We developed a novel methodology that combined remotely deployed camera systems, Machine Learning-based identification of zooplankton, and video-based tracking technology to quantify copepods' and amphipods' in situ swimming behaviors in a seasonally hypoxic and acidified fjord.";
    String title "[Zooplankton In Situ Videos] - In Situ Amphipod and Copepod Video Output Captured by the Hoodsport ORCA Profiling Mooring Mounted SPC-2 Zoocam in the Hood Canal, Puget Sound, Washington from August to September 2018 (Zooplankton Swimming project) (Causes and consequences of hypoxia and pH impacts on zooplankton: Linking movement behavior  to vertical distribution.)";
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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