CalCOFI CalCOFI ERDDAP
Easier access to scientific data 		| ?    
Brought to you by CalCOFI    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  CalCOFI Phytoplankton (Venrick) — sampling events Subscribe RSS
Institution:  CalCOFI   (Dataset ID: calcofi_phytoplankton_sample)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
 
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: 
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 {
  sample_key {
    String ioos_category "Identifier";
    String long_name "Sample key";
  }
  sample_type {
    String ioos_category "Other";
    String long_name "Sample type";
  }
  parent_sample_key {
    String ioos_category "Identifier";
    String long_name "Parent sample key";
  }
  cruise_key {
    String ioos_category "Identifier";
    String long_name "Cruise key";
  }
  grid_key {
    String ioos_category "Identifier";
    String long_name "Grid key";
  }
  site_key {
    String ioos_category "Identifier";
    String long_name "Site key";
  }
  order_occ {
    String ioos_category "Other";
    String long_name "Order occ";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  depth_max_m {
    String ioos_category "Location";
    String long_name "Depth max m";
  }
  tow_type {
    String ioos_category "Other";
    String long_name "Tow type";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Point";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String creator_name "CalCOFI";
    String creator_url "https://calcofi.org";
    String dataset_key "calcofi_phytoplankton";
    String db_release "v2026.08.08";
    String featureType "Point";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2026-08-11T10:40:17Z (source database)
2026-08-11T10:40:17Z http://localhost:8090/tabledap/calcofi_phytoplankton_sample.das";
    String infoUrl "https://calcofi.org/data/marine-ecosystem-data/phytoplankton-bacterioplankton/";
    String institution "CalCOFI";
    String license "CC-BY 4.0";
    String references "https://calcofi.io/workflows/publish_to-erddap.html";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF Standard Name Table v79";
    String subsetVariables "cruise_key, site_key";
    String summary "Abundance and species composition of phytoplankton (385 taxonomic categories) in the California Current, 1996-2022, by inverted-microscope counts (E. Venrick). Samples from the near-surface \"second depth\" are pooled across stations into four regions (NE, SE, Alley, Offshore; Hayward & Venrick 1998) before counting, so the grain is cruise x region, not per-station. Source: EDI knb-lter-cce.254.4. One row per sampling event, with event-level effort widened into its own columns. Use this for effort and station counting — summing effort over the observation table double-counts it. Source: CalCOFI integrated database release v2026.08.08.";
    String title "CalCOFI Phytoplankton (Venrick) — sampling events";
  }
}

 

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.30.0
Disclaimers | Privacy Policy | Contact