ERDDAP
Easier access to scientific data

Make A Graph

Dataset Title:	NWFSC Groundfish Data for U.S. West Coast (2003-2005)
Institution:	NOAA NWFSC (Dataset ID: nwioosGroundfish)
Range:	longitude = -125.86019 to -117.27551°E, latitude = 32.535522 to 48.452477°N, time = 2003-01-01T00:00:00Z to 2006-01-01T00:00:00Z
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Subset \| Data Access Form

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Show advanced settings : Privacy / Content settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Internet Explorer: "Tools : Internet Options : Security : Internet : Custom level :
          Sripting/ Active Scripting : Enable : OK : OK"
      • 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()

(" ")

Graph Settings

Marker Type:

Size:

Color:

Color Bar: Continuity: Scale:

Min: Max: N Sections:

Draw the land mask:

Y Axis Minimum: Maximum:

(Please be patient. It may take a while to get the data.)

Optional:
Then set the File Type: and

or view the URL:
(Documentation / Bypass this form

) (File Type information)

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:

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 {
  haul_id {
    Float64 actual_range 2.003030016e+11, 2.00603025408e+11;
    String cf_role "trajectory_id";
    String ioos_category "Identifier";
    String long_name "Haul Identifier";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -125.86019134521484, -117.2755126953125;
    String axis "X";
    Float64 colorBarMaximum -115.0;
    Float64 colorBarMinimum -135.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 32.5355224609375, 48.452476501464844;
    String axis "Y";
    Float64 colorBarMaximum 55.0;
    Float64 colorBarMinimum 30.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.0413792e+9, 1.1360736e+9;
    String axis "T";
    String Description "Year the survey cycle was performed.";
    String ioos_category "Time";
    String long_name "Time (Beginning of Survey Year)";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  scientific_name {
    String ioos_category "Taxonomy";
    String long_name "Scientific Name";
  }
  common_name {
    String ioos_category "Taxonomy";
    String long_name "Common Name";
  }
  position_description {
    String Description 
"Type of position reported for the haul, typically the gear track midpoint or
the vessel track midpoint.";
    String ioos_category "Location";
    String long_name "Position Description";
  }
  catch_range_min {
    Float64 actual_range 0.0, 4530.0;
    Float64 colorBarMaximum 4500.0;
    Float64 colorBarMinimum 0.0;
    String Description "Catch range minimum (catch per unit effort in kilograms per square meter).";
    String ioos_category "Fish Abundance";
    String long_name "Catch Range Min";
    String units "kg km-2";
  }
  catch_range_max {
    Float64 actual_range 0.0, 257606.0;
    Float64 colorBarMaximum 250000.0;
    Float64 colorBarMinimum 0.0;
    String Description "Catch range maximum (catch per unit effort in kilograms per square meter).";
    String ioos_category "Fish Abundance";
    String long_name "Catch Range Max";
    String units "kg km-2";
  }
  map_legend {
    Float64 colorBarMaximum 250000.0;
    Float64 colorBarMinimum 0.0;
    String Description 
"Indicates the catch per unit effort range that characterizes the haul catch
for a species.  Catch ranges are bounded by whole number standard deviation
increments.  Zero catch is indicated in a distinct category.";
    String ioos_category "Fish Abundance";
    String long_name "Map Legend";
    String units "kg km-2";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "haul_id";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting -117.2755126953125;
    String featureType "Trajectory";
    Float64 geospatial_lat_max 48.452476501464844;
    Float64 geospatial_lat_min 32.5355224609375;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -117.2755126953125;
    Float64 geospatial_lon_min -125.86019134521484;
    String geospatial_lon_units "degrees_east";
    String history 
"2017-06-29T05:34:30Z http://nwioos.coas.oregonstate.edu:8080/dods/drds/Groundfish%20Survey%202003-2006
2017-06-29T05:34:30Z http://coastwatch.pfeg.noaa.gov/tabledap/nwioosGroundfish.das";
    String infoUrl "http://nwioos.coas.oregonstate.edu:8080/dods/drds/Groundfish%20Survey%202003-2005.info";
    String institution "NOAA NWFSC";
    String keywords 
"Biosphere > Aquatic Ecosystems > Coastal Habitat,
Biosphere > Aquatic Ecosystems > Marine Habitat,
Biological Classification > Animals/Vertebrates > Fish,
Oceans > Aquatic Sciences > Fisheries,
2003-2005, abundance, beginning, catch, coast, common, data, description,
fish, fish abundance, groundfish, haul, identifier, legend, map, max, min,
name, noaa, nwfsc, position, range, scientific, survey, taxonomy, time, u.s.,
west, west coast, year";
    String keywords_vocabulary "GCMD Science Keywords";
    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.452476501464844;
    String sourceUrl "http://nwioos.coas.oregonstate.edu:8080/dods/drds/Groundfish%20Survey%202003-2006";
    Float64 Southernmost_Northing 32.5355224609375;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String subsetVariables 
"haul_id, longitude, latitude, time, common_name, scientific_name,
position_description";
    String summary 
"The data available for downloading is summarized data from the 2003-2005
U.S. West Coast Bottom Trawl Survey (WCGTS) of Groundfish Resources off
Washington, Oregon and California.

The Northwest Fisheries Science Center's Fishery Resource Analysis and
Monitoring Division (FRAM) completed the sixth in an annual series of
groundfish bottom trawl surveys in 2003. The survey was conducted June
24 to October 23, 2003 and targeted the commercial groundfish resources
inhabiting depths of 55 to 1,280 meters [m], (30 - 700 fathoms [fm])
from the area off Cape Flattery, Washington (latitude [lat.] 48°10'N)
to the U.S.-Mexican border (lat. 32°30'N) using chartered West Coast
commercial trawlers. These ongoing series of annual surveys, conducted
by FRAM since 1998, are designed to monitor long-term trends in
distribution and abundance of west coast groundfish, especially those
species of management concern. The 2003 survey represents the first
year in which the depth range was expanded to include both the
continental shelf (55 - 183 m) and continental slope (183 - 1,280 m)
area and the first year in which a stratified-random sampling design
was adopted.

In 2003, a total of 574 successful tows were completed out of 643
attempts. Simrad ITI net mensuration data, as well as global
positioning system (GPS) navigation data and bottom contact sensor
data, used to document performance (e.g. bottom tending), were
obtained for most tows.

An Aberdeen-style net with a small mesh (2\" stretched measure or less)
liner in the codend (to retain smaller specimens) was used to sample
fish biomass.  Target duration of each tow was 15 minutes. Tow
duration was the time between touchdown and lift-off of the trawl net
from the seafloor based on readings from bottom contact sensors.

Catches were sorted to species, aggregate or other appropriate
taxonomic level and then weighed using an electronic,
motion-compensated scale.  A total of 517 species or families (fish
and invertebrates) were identified within the survey area. Although
biological sampling effort continues to include Dover sole
(Microstomus pacificus), shortspine thornyhead (Sebastolobus
alascanus), longspine thornyhead (Sebastolobus altivelis), and
sablefish (Anoplopoma fimbria), focus has increasingly shifted to
encompass all groundfish species of management concern. Up to 100
length measurements, sex determinations, and individual weights
and up to 25 age structures were collected per haul for these species.";
    String time_coverage_end "2006-01-01T00:00:00Z";
    String time_coverage_start "2003-01-01T00:00:00Z";
    String title "NWFSC Groundfish Data for U.S. West Coast (2003-2005)";
    Float64 Westernmost_Easting -125.86019134521484;
  }
}

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
http://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
http://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 1.78
Disclaimers | Privacy Policy | Contact