NOAA ERDDAP
Easier access to scientific data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  SWFSC FED Mid Water Trawl Juvenile Rockfish Survey, Surface Data, 1987-2015 Subscribe RSS
Institution:  NOAA SWFSC FED   (Dataset ID: erdFedRockfishStation)
Range: longitude = -126.0017 to -117.323°E, latitude = 32.53783 to 44.50116°N, time = 1987-05-24T02:10:00Z to 2015-06-14T11:51:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
   
- +
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
 
(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 {
  cruise {
    String cf_role "trajectory_id";
    String comment "The first two digits are the last two digits of the year and the last two are the consecutive cruise number for that particular vessel (01, 02, 03, ...).";
    String ioos_category "Identifier";
    String long_name "Cruise";
  }
  ctd_index {
    Int16 actual_range 0, 434;
    Float64 colorBarMaximum 300.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Identifier";
    String long_name "CTD Index";
  }
  ctd_no {
    Int16 actual_range 5, 100;
    Float64 colorBarMaximum 7.0;
    Float64 colorBarMinimum 1.0;
    String ioos_category "Identifier";
    String long_name "CTD Number";
  }
  station {
    Int16 actual_range 101, 6014;
    Float64 colorBarMaximum 5000.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Identifier";
    String long_name "Station";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 5.488206e+8, 1.43428266e+9;
    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";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -126.0017, -117.323;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 32.53783, 44.50116;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  bottom_depth {
    Int16 actual_range 27, 4100;
    Float64 colorBarMaximum 4000.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Location";
    String long_name "Bottom Depth";
    String positive "down";
    String units "meters";
  }
  bucket_temperature {
    Float32 actual_range 7.5, 20.8;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Temperature";
    String long_name "Bucket Temperature";
    String standard_name "sea_water_temperature";
    String units "degree_C";
  }
  bucket_salinity {
    Float32 actual_range 27.9, 34.2;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String ioos_category "Salinity";
    String long_name "Bucket Practical Salinity";
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
  ts_temperature {
    Float32 actual_range 7.35, 21.39;
    Float64 colorBarMaximum 32.0;
    Float64 colorBarMinimum 0.0;
    String comment "The intake for the water for the thermosalinomter is usually a few meters below the surface.";
    String ioos_category "Temperature";
    String long_name "Thermosalinomter Temperature";
    String standard_name "sea_water_temperature";
    String units "degree_C";
  }
  ts_salinity {
    Float32 actual_range 26.51, 34.494;
    Float64 colorBarMaximum 37.0;
    Float64 colorBarMinimum 32.0;
    String comment "The intake for the water for the thermosalinomter is usually a few meters below the surface.";
    String ioos_category "Salinity";
    String long_name "Thermosalinomter Practical Salinity";
    String standard_name "sea_water_practical_salinity";
    String units "PSU";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Trajectory";
    String cdm_trajectory_variables "cruise";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "Keith.Sakuma@noaa.gov";
    String creator_name "Keith Sakuma";
    String creator_type "person";
    Float64 Easternmost_Easting -117.323;
    String featureType "Trajectory";
    Float64 geospatial_lat_max 44.50116;
    Float64 geospatial_lat_min 32.53783;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -117.323;
    Float64 geospatial_lon_min -126.0017;
    String geospatial_lon_units "degrees_east";
    String history 
"2013-04-08 source files from Keith Sakuma (FED) to Lynn Dewitt (ERD) to Bob Simons (ERD)
2013-04-09 Bob Simons (bob.simons@noaa.gov) converted data files for 1987-2011 from .csv to .nc with Projects.convertRockfish().
2017-02-03 Bob Simons (bob.simons@noaa.gov) converted data files for 2012-2015 from xlsx to .nc with Projects.convertRockfish().
2018-07-16T16:32:42Z (local files; contact erd.data@noaa.gov)
2018-07-16T16:32:42Z http://coastwatch.pfeg.noaa.gov/tabledap/erdFedRockfishStation.das";
    String infoUrl "https://swfsc.noaa.gov/GroundfishAnalysis/";
    String institution "NOAA SWFSC FED";
    String keywords "bottom, bucket, California, coast, cruise, ctd, data, depth, FED, fisheries, fixed, fluorometer, header, hydrographic, index, juvenile, latitude, longitude, midwater, NMFS, NOAA, pacific, rockfish, salinity, species, station, survey, SWFSC, temperature, thermosalinometer, time, transimissometer, 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.";
    String naming_authority "gov.noaa.pfeg.coastwatch";
    Float64 Northernmost_Northing 44.50116;
    String sourceUrl "(local files; contact erd.data@noaa.gov)";
    Float64 Southernmost_Northing 32.53783;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "cruise,ctd_index,ctd_no,station,time,longitude,latitude";
    String summary 
"SWFSC FED Mid Water Trawl Juvenile Rockfish Survey: Station Information and Surface Data.
Surveys have been conducted along the central California coast in May/June 
every year since 1983. In 2004 the survey area was expanded to cover the 
entire coast from San Diego to Cape Mendocino.  The survey samples a series 
of fixed trawl stations using a midwater trawl. The midwater trawl survey 
gear captures significant numbers of approximately 10 rockfish species during
their pelagic juvenile stage (i.e., 50-150 days old), by which time annual
reproductive success has been established. Catch-per-unit-effort data from
the survey are analyzed and serve as the basis for predicting future 
recruitment to rockfish fisheries. Results for several species (e.g., 
bocaccio, chilipepper [S. goodei], and widow rockfish [S. entomelas]) have
shown that the survey data can be useful in predicting year-class strength
in age-based stock assessments.

The survey's data on YOY Pacific whiting has also been used in the stock
assessment process. To assist in obtaining additional northward spatial
coverage of YOY Pacific whiting off Oregon and Washington, in 2001 the
Pacific Whiting Conservation Cooperative in cooperation with the NOAA NMFS
Northwest Fisheries Science Center began a midwater trawl survey patterned
after the NOAA NMFS SWFSC Fisheries Ecology Division's (FED) existing survey. 
Both surveys work cooperatively together each year in order to resolve 
interannual abundance patterns of YOY rockfish and Pacific whiting on a 
coastwide basis, which provides expedient, critical information that can be 
used in the fisheries management process.

The large quantity of physical data collected during the surveys (e.g., CTD
with attached transimissometer and fluorometer, thermosalinometer, and ADCP)
have provided a better understanding of the hydrographic conditions off the
California coast and analysis of these data have been distributed through the
publication of NOAA NMFS Technical Memoranda.

For more information, see https://swfsc.noaa.gov/GroundfishAnalysis/ and
http://www.sanctuarysimon.org/projects/project_info.php?projectID=100118";
    String time_coverage_end "2015-06-14T11:51:00Z";
    String time_coverage_start "1987-05-24T02:10:00Z";
    String title "SWFSC FED Mid Water Trawl Juvenile Rockfish Survey, Surface Data, 1987-2015";
    Float64 Westernmost_Easting -126.0017;
  }
}

 

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