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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Gelatinous zooplankton observations] - Gelatinous zooplankton observations
during four research cruises (SKQ202204S, MGL2207, SKQ202303S, SR2317) carried
out in the Northern California Current from March 2022 to August
2023 (Collaborative Research: Plankton size spectra and trophic links in a
dynamic ocean)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_923337_v1)
Range: longitude = -126.09 to -124.021°E
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 ? )
    [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 {
  Date {
    String long_name "Date";
    String units "unitless";
  }
  Broad_taxon_ID {
    String long_name "Broad_taxon_id";
    String units "unitless";
  }
  Lowest_taxon_ID {
    String long_name "Lowest_taxon_id";
    String units "unitless";
  }
  Life_stage {
    String long_name "Life_stage";
    String units "unitless";
  }
  Number_of_Individuals {
    String long_name "Number_of_individuals";
    String units "unitless";
  }
  Length {
    String long_name "Length";
    String units "millimeter (mm)";
  }
  Volume {
    String long_name "Volume";
    String units "milliliter(ml)";
  }
  Transect {
    String long_name "Transect";
    String units "unitless";
  }
  Station {
    Int32 actual_range 1, 6;
    String long_name "Station";
    String units "unitless";
  }
  Latitude {
    Float32 actual_range 42.501, 47.1025;
    String long_name "Latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -126.09, -124.021;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  MOC {
    Int32 actual_range 1, 4;
    String long_name "Moc";
    String units "unitless";
  }
  Net {
    String long_name "Net";
    String units "unitless";
  }
  Depth {
    String long_name "Depth";
    String units "meter (m)";
  }
 }
  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.923337.1";
    Float64 Easternmost_Easting -124.021;
    Float64 geospatial_lon_max -124.021;
    Float64 geospatial_lon_min -126.09;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-08T06:21:02Z (local files)
2024-11-08T06:21:02Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_923337_v1.das";
    String infoUrl "https://www.bco-dmo.org/dataset/923337";
    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 "These data include a list of gelatinous zooplankton species observed during four 14-day research cruises carried out in the Northern California Current from March 2022 to August 2023.  Plankton samples were collected with a coupled MOCNESS system that was towed to 100 m (or 5 m off the bottom in stations with <100 m depth).  Samples were subsequently poured into sorting tray and picked for gelatinous taxa.  This data set represents the first comprehensive list of gelatinous taxa from this region and includes ctenophores, cnidarians and pelagic tunicates, taxa that are largely omitted from studies in the NCC.";
    String title "[Gelatinous zooplankton observations] - Gelatinous zooplankton observations during four research cruises (SKQ202204S, MGL2207, SKQ202303S, SR2317) carried out in the Northern California Current from March 2022 to August 2023 (Collaborative Research: Plankton size spectra and trophic links in a dynamic ocean)";
    Float64 Westernmost_Easting -126.09;
  }
}

 

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