NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Bottom Trawl Survey OW1 Catch Subscribe RSS
Institution:  Rutgers University   (Dataset ID: bottom_trawl_survey_ow1_catch)
Information:  Summary ? | License ? | 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: 
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 ? )
    [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 {
  index {
    Float64 _FillValue 9223372036854775807;
    Float64 actual_range 0, 1180;
    String ioos_category "Unknown";
    String long_name "Index";
  }
  cruise {
    String description "unique identifier for cruise";
    String ioos_category "Identifier";
    String long_name "cruise id";
  }
  station {
    String comment "C/I- stands for Control and Impact and designates the type of station we are at, Control being the open sand bottom that won’t get turbines placed there, and Impact being the OW1 Wind Farm lease area.";
    String ioos_category "Identifier";
    String long_name "station id";
  }
  species_common_name {
    String ioos_category "Taxonomy";
    String long_name "Species Common Name";
  }
  size_class {
    String comment "If, during the process of sorting the catch, there are distinct/noticeable differences in the sizes of the same species (see longfin squid (503) in BT2301 for an example), we sort them separately to avoid biasing the randomly selected length measurements (ie if there’s a bunch of medium size ones, those are more likely to get picked for length frequency than the small ones but we still want the size ranges of that size class as well). There’re no exact length limits separating the classes so there will be some overlap between classes and selecting size classes will have to come with experience.";
    String ioos_category "Unknown";
    String long_name "Size Class";
  }
  total_weight {
    Float64 _FillValue -999.0;
    Float64 actual_range 0.0, 192.3;
    Float64 colorBarMaximum 200.0;
    Float64 colorBarMinimum 0.0;
    String comment "This is the weight in kgs of anything we took measurements for where we didn’t measure every individual of that species, with the exception of anything sorted into size classes (50 count/class). If there are over 100 individuals of one species and not everything got measured, then everything that got measured gets reweighed and put here. For example, if there’s 20 kgs and well over 100 count of Northern Sea Robins, we measure 100 and get the weight of the 100 we measured. Things are recorded a bit differently if they were assigned a size class. If there is a size class for a species, ALWAYS take the weight of what was measured (by size class) regardless of the count";
    String ioos_category "Unknown";
    String long_name "Total Weight";
    String units "kg";
  }
  total_count {
    Float64 _FillValue -999;
    Float64 actual_range 1, 4570;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Total Count";
  }
  length_type {
    String comment "FL: fork length, TL: total length, DW: disk width (for large stingrays), CW: carapace width (for crabs, horseshoe crabs, and species with a carapace), ML: mantle length (for squid, measuring just the length of the mantle tissue), SW: shell width (for general bivalves and clams), SH: shell height (for scallops)";
    String ioos_category "Unknown";
    String long_name "Length Type";
  }
  mean_length {
    Float64 _FillValue -999.0;
    Float64 actual_range 11.0, 1956.0;
    String ioos_category "Statistics";
    String long_name "Mean Length";
    String units "mm";
  }
  std_length {
    Float64 _FillValue -999.0;
    Float64 actual_range 0.0, 242.54;
    String ioos_category "Unknown";
    String long_name "Std Length";
    String units "mm";
  }
 }
  NC_GLOBAL {
    String acknowledgement "Funding provided by Orsted.";
    String cdm_data_type "Other";
    String comment "Survey performed aboard F/V Darana R with Captains Robert Rhule and James Rhule";
    String contributor_name "Jason Morson, Doug Zemeckis, Thomas Grothues, Joey O'Brien, Sam Chew Chin, Jamie Wilson, Helaina McKeon, Andre Ascura, Kaycee Coleman, Laura Nazzaro";
    String contributor_role "Project Co-Principal Investigator, Project Co-Principal Investigator, Project Lead Principal Investigator and Project Fisheries Scientist, Lab Manager, Fisheries Scientist, Fisheries Observer, Fisheries Observer, Technician, Project Management, Data Management";
    String Conventions "ACDD 1.3, COARDS, CF-1.6";
    String creator_email "ecosystemdata@marine.rutgers.edu";
    String creator_institution "Rutgers University";
    String creator_name "Rutgers Marine Ecosystem Data Team";
    String creator_type "group";
    String creator_url "https://marine.rutgers.edu/main/";
    String geospatial_bounds_crs "EPSG:6347";
    String geospatial_vertical_positive "up";
    String history 
"2025-06-21T17:58:55Z (local files)
2025-06-21T17:58:55Z https://rowlrs-data.marine.rutgers.edu/tabledap/bottom_trawl_survey_ow1_catch.das";
    String id "bottom_trawl_survey_ow1_catch";
    String infoUrl "https://rowlrs.marine.rutgers.edu/";
    String institution "Rutgers University";
    String keywords "array, array-data, bottom, catch, class, common, comprehensive, count, cruise, data, depth, identifier, index, large, length, length_type, mean, mean_length, name, ow1, profiler, rutgers, salinity, salinity-temperature-depth, size, size_class, species, species_common_name, station, statistics, std, std_length, stewardship, survey, system, taxonomy, temperature, total, total_count, total_weight, trawl, type, university, weight";
    String license "see Data Use Agreement";
    String platform_name "F/V Darana R";
    String program "Ocean Wind 01 Fisheries Monitoring Plan";
    String project "Ocean Wind 01 Fisheries Monitoring Plan, Bottom Trawl";
    String publisher_email "ecosystemdata@marine.rutgers.edu";
    String publisher_institution "Rutgers University";
    String publisher_name "Rutgers Marine Ecosystem Data Team";
    String publisher_type "group";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Fisheries Monitoring in Ocean Wind 01. Two seasonal pre-construction surveys. Twenty tows conducted in the lease area and twenty in the control area each season (160/year total). Tows conducted at three knots for 20 minutes. Trawl data will inform relative biomass (kg/tow) by species, size frequency by species, condition index (length-weight) by species, community assemblage, and gut content of a subset of species.";
    String title "Bottom Trawl Survey OW1 Catch";
  }
}

 

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