Make A Graph

Dataset Title:	Regional NCOM US East 2D (Before Depth Change)
Institution:	Naval Oceanographic Office via NOAA NCEI (Dataset ID: NCOM_us_east_before_change_2d)
Information:	Summary \| License \| 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:

Dimensions

Start

Stop

time (UTC)

specify just 1 value →

depth (m)

specify just 1 value →

latitude (degrees_north)

longitude (degrees_east)

Graph Settings
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 {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.2340512e+9, 1.258578e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "Forecast time for ForecastModelRunCollection";
    Float64 missing_value NaN;
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float64 actual_range 0.0, 5000.0;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    Int32 NAVO_code 5;
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 20.0, 41.95102310180664;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    Int32 NAVO_code 1;
    String standard_name "latitude";
    String units "degrees_north";
    Float64 valid_range 20.0, 41.95102310180664;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 278.0, 295.9544982910156;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    Int32 NAVO_code 2;
    String standard_name "longitude";
    String units "degrees_east";
    Float64 valid_range 278.0, 295.9544982910156;
  }
  water_temp {
    String coordinates "time_run time depth lat lon";
    String ioos_category "Temperature";
    String long_name "Water Temperature";
    Int32 NAVO_code 15;
    String standard_name "sea_water_temperature";
    String units "degC";
  }
  water_u {
    String coordinates "time_run time depth lat lon";
    String ioos_category "Currents";
    String long_name "Eastward Water Velocity";
    Int32 NAVO_code 17;
    String standard_name "eastward_sea_water_velocity";
    String units "meter/sec";
  }
  water_v {
    String coordinates "time_run time depth lat lon";
    String ioos_category "Currents";
    String long_name "Northward Water Velocity";
    Int32 NAVO_code 18;
    String standard_name "northward_sea_water_velocity";
    String units "meter/sec";
  }
  salinity {
    String coordinates "time_run time depth lat lon";
    String ioos_category "Salinity";
    String long_name "Salinity";
    Int32 NAVO_code 16;
    String standard_name "sea_water_salinity";
    String units "psu";
  }
  NC_GLOBAL {
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String cdm_data_type "Grid";
    String classification_authority "not applicable";
    String classification_level "not applicable";
    String contact "NRL Code 7323";
    String Conventions "Global NCOM";
    String creator_name "kelly.r.wood@navy.mil; jeffery.rayburn@navy.mil";
    String distribution_statement "Distribution limited to Department of Defense and U.S. DOD contractors only.  Administrative/operational 2009-11-18.  Other U.S. requests must be referred to the Commanding Officer, Naval Oceanographic Office.";
    String downgrade_date "not applicable";
    Float64 Easternmost_Easting 295.9544982910156;
    String generating_model "NCOM NOKI";
    Float64 geospatial_lat_max 41.95102310180664;
    Float64 geospatial_lat_min 20.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 295.9544982910156;
    Float64 geospatial_lon_min 278.0;
    String geospatial_lon_units "degrees_east";
    String history 
"not applicable ;
FMRC Best Dataset
2024-12-10T04:49:48Z https://www.ncei.noaa.gov/thredds-coastal/dodsC/ncom_us_east_before_depth_change_agg/US_East_Feb_2009_to_November_18_2009_best.ncd
2024-12-10T04:49:48Z https://www.ncei.noaa.gov/griddap/NCOM_us_east_before_change_2d.das";
    String infoUrl "https://www.ncei.noaa.gov/thredds-coastal/catalog/ncom_us_east_before_depth_change_agg/catalog.html?dataset=ncom_us_east_before_depth_change_agg/US_East_Feb_2009_to_November_18_2009_best.ncd";
    String initial_time "2000010100";
    String input_data_source "not_applicable";
    String institution "Naval Oceanographic Office via NOAA NCEI";
    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 location "Proto fmrc:US_East_Feb_2009_to_November_18_2009";
    String model_type "NCOM_2.3";
    Float64 Northernmost_Northing 41.95102310180664;
    String operational_status "development";
    String publisher_name "OceanNOMADS@noaa.gov";
    String sourceUrl "https://www.ncei.noaa.gov/thredds-coastal/dodsC/ncom_us_east_before_depth_change_agg/US_East_Feb_2009_to_November_18_2009_best.ncd";
    Float64 Southernmost_Northing 20.0;
    String standard_name_vocabulary "CF-1.0";
    String summary "NCOM US East data before November 19, 2009";
    String time_coverage_end "2009-11-18T21:00:00Z";
    String time_coverage_start "2009-02-08T00:00:00Z";
    String title "Regional NCOM US East 2D (Before Depth Change)";
    Float64 Westernmost_Easting 278.0;
  }
}

Using griddap to Request Data and Graphs from Gridded Datasets

griddap lets you request a data subset, graph, or map from a gridded dataset (for example, sea surface temperature data from a satellite), via a specially formed URL. griddap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its projection 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. It makes 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.

griddap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/griddap/erdBAssta5day.htmlTable?sst[(2007-10-21T00:00:00)][0][(-75):100:(75)][(180):100:(360)]
Thus, the query is often a data variable name (e.g., sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][altitude][latitude][longitude]).

For details, see the griddap Documentation.