Make A Graph

Dataset Title:	NEFSC oceanographic profile dataset
Institution:	NOAA Northeast Fisheries Science Center (Dataset ID: nefsc_ctd)
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 : 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()

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:

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 {
  year {
    String ioos_category "Other";
  }
  cruise_id {
    String ioos_category "Other";
  }
  time {
    String _CoordinateAxisType "Time";
    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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  sea_water_temperature {
    String ioos_category "Temperature";
    String long_name "Sea Water Temperature";
    String standard_name "sea_water_temperature";
    String units "degree_C";
  }
  salinity {
    String ioos_category "Salinity";
    String long_name "Salinity";
    String standard_name "salinity";
    String units "PSU";
  }
 }
  NC_GLOBAL {
    String acknowledgment "NOAA/NEFSC Oceanography Branch";
    String cdm_data_type "Point";
    String contributor_name "Paula Fratantoni";
    String contributor_role "manager";
    String creator_email "james.manning@noaa.gov";
    String creator_name "James Manning";
    String date_created "2020-11-25";
    String featureType "Point";
    String geospatial_lat_units "degrees_north";
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"data is still served via FTP and stored on in Oracle tables
2021-05-02T03:31:49Z (source database)
2021-05-02T03:31:49Z https://comet.nefsc.noaa.gov/tabledap/nefsc_ctd.das";
    String infoUrl "https://www.fisheries.noaa.gov/new-england-mid-atlantic/ecosystems/monitoring-ecosystem-northeast";
    String institution "NOAA Northeast Fisheries Science Center";
    String keywords "ocean, salinity, seawater, temperature";
    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 processing_level "3";
    String sourceUrl "(source database)";
    String summary "This is a collection of profiles on the NE Continental Shelf with temperature, salinity, and other variables at multiple depths.";
    String title "NEFSC oceanographic profile dataset";
  }
}

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