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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  [Winter to spring transition in a fjord in the Gulf of Alaska - chlorophyll a
and flow cytometry data] - Chlorophyll a and flow cytometry data from bi-weekly
vertical profiles in Resurrection Bay, AK from January to March of 2023 from bi-
weekly vertical profiles in Resurrection Bay, AK from January to March of
2023 (Collaborative Research: Zooplankton restarts in a high-latitude marine
ecosystem: species-specific recruitment and development in early spring)
Subscribe RSS
Institution:  BCO-DMO   (Dataset ID: bcodmo_dataset_954173_v1)
Range: longitude = -149.3583 to -149.3583°E, latitude = 60.025 to 60.025°N, depth = 0.0 to 280.0m
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: 
[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 {
  cruise {
    String long_name "Cruise";
    String units "unitless";
  }
  date {
    String long_name "Date";
    String units "unitless";
  }
  station {
    String long_name "Station";
    String units "unitless";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 60.025, 60.025;
    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 -149.3583, -149.3583;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  cast {
    Int32 actual_range 1, 2;
    String long_name "Cast";
    String units "unitless";
  }
  niskin {
    Int32 actual_range 1, 6;
    String long_name "Niskin";
    String units "unitless";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 0, 280;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  chla_gt_20 {
    Float32 actual_range 0.002, 0.232;
    String long_name "Chla_gt_20";
    String units "Micrograms per liter (ug/L)";
  }
  chla_lt_20 {
    Float32 actual_range 0.002, 0.094;
    String long_name "Chla_lt_20";
    String units "Micrograms per liter (ug/L)";
  }
  chla_total {
    Float32 actual_range 0.004, 0.321;
    String long_name "Chla_total";
    String units "Micrograms per liter (ug/L)";
  }
  phaeo_gt_20 {
    Float32 actual_range 0.018, 0.192;
    String long_name "Phaeo_gt_20";
    String units "Micrograms per liter (ug/L)";
  }
  phaeo_lt_20 {
    Float32 actual_range -0.002, 0.035;
    String long_name "Phaeo_lt_20";
    String units "Micrograms per liter (ug/L)";
  }
  phaeo_total {
    Float32 actual_range 0.016, 0.227;
    String long_name "Phaeo_total";
    String units "Micrograms per liter (ug/L)";
  }
  hbact {
    Int32 actual_range 243012, 790239;
    String long_name "Hbact";
    String units "Number per milliliter (#/mL)";
  }
  syn {
    Int32 actual_range 79, 4478;
    String long_name "Syn";
    String units "Number per milliliter (#/mL)";
  }
  peuk {
    Int32 actual_range 118, 9782;
    String long_name "Peuk";
    String units "Number per milliliter (#/mL)";
  }
 }
  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.954173.1";
    Float64 Easternmost_Easting -149.3583;
    Float64 geospatial_lat_max 60.025;
    Float64 geospatial_lat_min 60.025;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -149.3583;
    Float64 geospatial_lon_min -149.3583;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 280.0;
    Float64 geospatial_vertical_min 0.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2025-04-19T13:49:43Z (local files)
2025-04-19T13:49:43Z https://erddap.bco-dmo.org/tabledap/bcodmo_dataset_954173_v1.das";
    String infoUrl "https://osprey.bco-dmo.org/dataset/954173";
    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 60.025;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 60.025;
    String summary "The Gulf of Alaska is a highly seasonal environment that is characterized by an order-of-magnitude increase in copepod biomass in the photic zone between winter and spring. The study focused on copepod recruitment to characterize species-specific naupliar production. Concurrent environmental monitoring included measurements of chlorophyll α and flow cytometry as indicators of prey field. Bi-weekly vertical profiles of temperature, salinity and fluorescence were recorded at an established station (RES2.5) in Resurrection Bay, AK. Discrete water samples were obtained for size-fractionated chlorophyll α samples and cell counts using flow cytometry. The water column was stratified by salinity with the lowest salinities recorded in the surface layer. A moderate increase in chlorophyll α concentrations occurred during March prior to the spring phytoplankton bloom.";
    String title "[Winter to spring transition in a fjord in the Gulf of Alaska - chlorophyll a and flow cytometry data] - Chlorophyll a and flow cytometry data from bi-weekly vertical profiles in Resurrection Bay, AK from January to March of 2023 from bi-weekly vertical profiles in Resurrection Bay, AK from January to March of 2023 (Collaborative Research: Zooplankton restarts in a high-latitude marine ecosystem: species-specific recruitment and development in early spring)";
    Float64 Westernmost_Easting -149.3583;
  }
}

 

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