ERDDAP
Easier access to scientific data

Make A Graph

Dataset Title:	NEFSC Sea Scallop Biomass
Institution:	Rutgers University (Dataset ID: NEFSC_SCALLOP)
Range:	longitude = -75.63333 to -65.916°E, latitude = 35.55 to 42.16667°N
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| 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 : 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 {
  index {
    Int16 actual_range 0, 16056;
    String ioos_category "Unknown";
    String long_name "Index";
  }
  year {
    Float64 actual_range 1966.0, 2015.0;
    String ioos_category "Time";
    String long_name "Year of survey";
    String units "year";
  }
  biomass {
    Float32 _FillValue -999999.0;
    Float32 actual_range 0.0, 1549.18;
    Float64 colorBarMaximum 200.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Unknown";
    String long_name "Total biomass.";
    String units "kg";
  }
  abundance {
    Float32 _FillValue -999999.0;
    Float32 actual_range 1.0, 63589.0;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Number of individuals";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 _FillValue -999999.0;
    Float32 actual_range -75.63333, -65.916;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 _FillValue -999999.0;
    Float32 actual_range 35.55, 42.16667;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String comment "This layer displays scallop biomass (meat weights in kilograms) from all NOAA Northeast Fisheries Science Center NEFSC scallop dredge surveys from 1966 to 2014.";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    Float64 Easternmost_Easting -65.916;
    Float64 geospatial_lat_max 42.16667;
    Float64 geospatial_lat_min 35.55;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -65.916;
    Float64 geospatial_lon_min -75.63333;
    String geospatial_lon_units "degrees_east";
    String history 
"Created by Eli Hunter (hunter@marine.rutgers.edu),20-May-2020 13:47:57
2025-02-21T16:41:19Z (local files)
2025-02-21T16:41:19Z https://nybsand.marine.rutgers.edu/tabledap/NEFSC_SCALLOP.das";
    String infoUrl "https://portal.midatlanticocean.org/";
    String institution "Rutgers University";
    String keywords "abundance, biomass, center, data, fisheries, index, individuals, latitude, longitude, nefsc, nmfs, noaa, northeast, number, scallop, science, sea, statistics, survey, time, total, year";
    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 42.16667;
    String source "https://www.northeastoceandata.org/data-explorer/?fish,  FISH.zip";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 35.55;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "This dataset contains survey points for scallop catches from NOAA Northeast Fisheries Science Center (NEFSC) scallop dredge surveys during the years 1966 to 2014. The NEFSC scallop survey program began in 1960 and had a major gear change in 1979. Since 1979 there have been other gear and vessel changes, for which the effects are generally small (Hart 2015). The survey collected information on total scallop biomass and meat weight biomass. Meat weight is calculated from shell height-to-meat weight ratios from Hennen and Hart (2012)";
    String title "NEFSC Sea Scallop Biomass";
    Float64 Westernmost_Easting -75.63333;
  }
}

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