Make A Graph

Dataset Title:	CPS Trawl Life History Nearshore Set Catch Data
Institution:	NOAA-Fisheries/Southwest Fisheries Science Center (Dataset ID: FRDCPSNearshoreSetCatch)
Range:	longitude = -125.2271 to -117.1407°E, latitude = 32.55662 to 48.35898°N, time = 2019-06-21T18:28:00Z to (now?)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| 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:

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:

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 {
  cruise {
    Int32 actual_range 201907, 202407;
    String description "Six-digit cruise number fixed by year and predominant month of cruise, often with overlapping information in the CalCOFI Database.";
    String ioos_category "Identifier";
    String long_name "Cruise";
  }
  ship {
    String description "Three-character ship code.";
    String ioos_category "Identifier";
    String long_name "Ship";
  }
  date {
    String description "Date in Pacific Daylight Time a set occurred";
    String ioos_category "Time";
    String long_name "Date (PDT)";
  }
  time_PDT {
    String description "Time in Pacific Daylight Time when a set occurred";
    String ioos_category "Time";
    String long_name "Time (PDT)";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.56114168e+9, NaN;
    String axis "T";
    String description "Date-Time when the set occurred (UTC)";
    String ioos_category "Time";
    String long_name "Set Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  set {
    Int32 actual_range 1, 81;
    String description "Set number, usually consecutively from 1 within a date and ship of a cruise";
    String ioos_category "Identifier";
    String long_name "Set Number";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 32.55662, 48.35898;
    String axis "Y";
    String description "Latitude position at Time, when the set occurs";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -125.2271, -117.1407;
    String axis "X";
    String description "Longitude position at Time, when the set occurs";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  state {
    String description "U.S. state where the set occurred";
    String ioos_category "Identifier";
    String long_name "State";
  }
  gearType {
    String description "The gear type that was used during the set";
    String ioos_category "Identifier";
    String long_name "Gear Type";
  }
  itis_tsn {
    Int32 actual_range 49255, 692068;
    String description "Intergrated Taxomomic Information System Taxonomic Serial Number.";
    String ioos_category "Identifier";
    String long_name "ItisTSN";
  }
  scientific_name {
    String description "Scientific name of species.";
    String ioos_category "Identifier";
    String long_name "Scientific Name";
  }
  totalNumber {
    Int32 actual_range 0, 4474;
    String description "Number of individuals weighed or counted in the sample for the species.";
    String ioos_category "Other";
    String long_name "Total Number";
  }
  totalWeightkg {
    Float32 actual_range 0.0, 39.00895;
    String description "Weight of the sample of the species. When individuals are not counted this corresponds to the total weight of the species in the catch.";
    String ioos_category "Other";
    String long_name "Total Weight";
    String units "kg";
  }
 }
  NC_GLOBAL {
    String acknowledgment "National Oceanic and Atmospheric Administration, Southwest Fisheries Science Center";
    String cdm_data_type "Point";
    String contributor_name "Fisheries Resources Division";
    String Conventions "CF-1.6, ACDD-1.3, COARDS, NCCSV-1.2";
    String creator_email "swfsc.cps-lht@noaa.gov";
    String creator_name "Coastal Pelagic Species Life History Program";
    String creator_url "https://swfsc.noaa.gov/FRD/";
    String date_created "2025-04-22";
    String date_issued "2025-04-22";
    String date_modified "2025-04-22";
    String defaultGraphQuery "longitude,latitude,time&scientific_name=\"Sardinops sagax\"&.draw=markers&.marker=5|5&.color=0x000000&.colorBar=|||||";
    Float64 Easternmost_Easting -117.1407;
    String featureType "Point";
    Float64 geospatial_lat_max 48.35898;
    Float64 geospatial_lat_min 32.55662;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -117.1407;
    Float64 geospatial_lon_min -125.2271;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-05-05T19:15:26Z (local files)
2025-05-05T19:15:26Z https://coastwatch.pfeg.noaa.gov/tabledap/FRDCPSNearshoreSetCatch.das";
    String infoUrl "https://www.fisheries.noaa.gov/science-data/california-current-ecosystem-survey";
    String institution "NOAA-Fisheries/Southwest Fisheries Science Center";
    String keywords "life history, Oceans >Coastal pelagic species, trawl";
    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 48.35898;
    String project "Coastal Pelagic Species Surveys";
    String publisher_email "swfsc.cps-lht@noaa.gov";
    String publisher_name "Coastal Pelagic Species Life History Program";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 32.55662;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "cruise, ship, state,gearType, set, scientific_name";
    String summary "Weight in kilograms for all species (identified to lowest taxonomic criteria) caught during the nearshore portion of the SWFSC-FRD fishery independent survey of coastal pelagic species.  Sets  were targeted for coastal pelagic species (e.g., sardine, anchovy, mackerels) using a purse seine on the surface at position and times listed. Additional information for a subset of individuals from some species can be found in the CPS Trawl Life History Nearshore Specimen dataset.";
    String time_coverage_start "2019-06-21T18:28:00Z";
    String title "CPS Trawl Life History Nearshore Set Catch Data";
    Float64 Westernmost_Easting -125.2271;
  }
}

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