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: station data Subscribe RSS
Institution:  Rutgers University   (Dataset ID: station_data_20250815)
Range: longitude = -74.3392 to -74.31234°E, latitude = 39.3482 to 39.36915°N, time = 2022-11-22T14:01:00Z to 2024-11-18T19:32: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() ?
? ("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 {
  row {
    Int32 _FillValue 2147483647;
    Int32 actual_range 1, 125;
    String ioos_category "Unknown";
    String long_name "Row";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.66912566e+9, 1.73195832e+9;
    String axis "T";
    String calendar "gregorian";
    String ioos_category "Time";
    String long_name "Date Time Utc";
    String source_name "dttm_utc";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  yr {
    Int32 _FillValue -9999;
    Int32 actual_range 2022, 2024;
    String description "year";
    String ioos_category "Time";
    String long_name "year";
    String units "EST/UTM 18N";
  }
  mo {
    Int32 _FillValue -9999;
    Int32 actual_range 6, 11;
    String description "month";
    String ioos_category "Time";
    String long_name "month";
    String units "EST/UTM 18N";
  }
  da {
    Int32 _FillValue -9999;
    Int32 actual_range 6, 22;
    String description "day";
    String ioos_category "Time";
    String long_name "day of month";
    String units "EST/UTM 18N";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue -9999.0;
    Float64 actual_range -74.3392, -74.31234;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String description "trawl midpoint longitude";
    String ioos_category "Location";
    String long_name "Longitude Trawl Midpoint";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue -9999.0;
    Float64 actual_range 39.3482, 39.36915;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String description "trawl midpoint latitude";
    String ioos_category "Location";
    String long_name "Latitude Trawl Midpoint";
    String standard_name "latitude";
    String units "degrees_north";
  }
  stationID {
    String description "unique trawl idenfier by date and survey cumulative trawl number: YYYYMMDD-NN";
    String ioos_category "Identifier";
    String long_name "trawl_station_ID";
    String units "identifier";
  }
  survey {
    String description "survey identifier by season and year";
    String ioos_category "Time";
    String long_name "Trawl Survey";
    String units "season year";
  }
  common {
    String ioos_category "Unknown";
    String long_name "Common";
  }
 }
  NC_GLOBAL {
    String acknowledgement "Funding provided by Bureau of Ocean Energy Management";
    String cdm_data_type "Point";
    String contributor_name "Thomas Grothues; Doug  Zemeckis; Josh Kohut; Deena Hansen; Stephen Potts";
    String contributor_role "Principal Investigator; Co-Principal Investigator; Co-Principal Investigator; BOEM Coordinator; Postdoctoral fellow";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String creator_email "stephen.potts@marine.rutgers.edu";
    String creator_institution "Rutgers University";
    String creator_name "Stephen Potts";
    String creator_type "person";
    String creator_url "https://marine.rutgers.edu/main/";
    Float64 Easternmost_Easting -74.31234;
    String featureType "Point";
    String geospatial_bounds_crs "EPSG:3424";
    Float64 geospatial_lat_max 39.36915;
    Float64 geospatial_lat_min 39.3482;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -74.31234;
    Float64 geospatial_lon_min -74.3392;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-10-13T22:47:55Z (local files)
2025-10-13T22:47:55Z https://rowlrs-data.marine.rutgers.edu/tabledap/station_data_20250815.das";
    String infoUrl "https://rowlrs.marine.rutgers.edu/";
    String institution "Rutgers University";
    String keywords "bottom, common, data, date, day, identifier, latitude, longitude, midpoint, month, row, rutgers, station, stationID, survey, time, trawl, university, year";
    String license "see Data Use Agreement";
    Float64 Northernmost_Northing 39.36915;
    String project "NY Bight Fish, Fishers and Sand Features: Phase 2";
    String project_institution "Rutgers University; Bureau of Ocean Energy Management (BOEM)";
    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)";
    Float64 Southernmost_Northing 39.3482;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "stationID, survey, common";
    String summary "Trawl survey station data for bottom fish and invertebrates at an offshore sand borrow site in offshore New Jersey. 5 seasonal surveys were conducted over 3 years, with 4 days of collections each of within survey. Trawls were randomized over 7 cluster areas.";
    String time_coverage_end "2024-11-18T19:32:00Z";
    String time_coverage_start "2022-11-22T14:01:00Z";
    String title "Bottom trawl survey: station data";
    Float64 Westernmost_Easting -74.3392;
  }
}

 

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