Make A Graph

Dataset Title:	HYCOM Region 6 3D
Institution:	Naval Oceanographic Office via NOAA NCEI (Dataset ID: HYCOM_reg6_latest3d)
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.4275008e+9, 1.7139168e+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 10.0, 70.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    Int32 NAVO_code 1;
    String point_spacing "even";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 150.00001525878906, 210.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String modulo "360 degrees";
    Int32 NAVO_code 2;
    String standard_name "longitude";
    String units "degrees_east";
  }
  water_temp {
    String comment "in-situ temperature";
    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";
  }
  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";
  }
  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 "meters/second";
  }
  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 "meters/second";
  }
  NC_GLOBAL {
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String analysis_tau "039 hours since analysis, analysis_time_origin = 2024-04-14 12:00:00";
    String cdm_data_type "Grid";
    String comment "...";
    String contact "FNMOC, CDO";
    String Conventions "Global NCOM";
    String creator_name "kelly.r.wood@navy.mil; jeffery.rayburn@navy.mil";
    String distribution_statement "Approved for public release; distribution unlimited.";
    Float64 Easternmost_Easting 210.0;
    String field_type "instantaneous";
    String generating_model "GOFS 3.1, Global HYCOM with OSU tides";
    Float64 geospatial_lat_max 70.0;
    Float64 geospatial_lat_min 10.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 210.0;
    Float64 geospatial_lon_min 150.00001525878906;
    String geospatial_lon_units "degrees_east";
    String history 
"created on 20240415 ;
FMRC Best Dataset
2024-04-20T08:32:38Z https://www.ncei.noaa.gov/thredds-coastal/dodsC/hycom/hycom_reg6_agg/HYCOM_Region_6_Aggregation_best.ncd
2024-04-20T08:32:38Z https://www.ncei.noaa.gov/griddap/HYCOM_reg6_latest3d.das";
    String infoUrl "https://www.ncei.noaa.gov/thredds-coastal/catalog/hycom/hycom_reg6_agg/catalog.html?dataset=hycom/hycom_reg6_agg/HYCOM_Region_6_Aggregation_best.ncd";
    String input_data_source "FNMOC NAVGEM, Satellite SSH, SST, in situ";
    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:HYCOM_Region_6_Aggregation";
    String message "UNCLASSIFIED";
    String model_type "x-curvilinear lon, y-curvilinear lat, hybrid z";
    String NCO "netCDF Operators version 4.7.7 (Homepage = http://nco.sf.net, Code = https://github.com/nco/nco)";
    Float64 Northernmost_Northing 70.0;
    String operational_status "operational";
    String publisher_name "OceanNOMADS@noaa.gov";
    String reference "https://portal.fnmoc.navy.mil/";
    String source "HYCOM archive file; GOFS 3.1 GLBy0.08 expt_93.0";
    String sourceUrl "https://www.ncei.noaa.gov/thredds-coastal/dodsC/hycom/hycom_reg6_agg/HYCOM_Region_6_Aggregation_best.ncd";
    Float64 Southernmost_Northing 10.0;
    String standard_name_vocabulary "CF-1.0";
    String summary "HYCOM Region 6 Data";
    String time_coverage_end "2024-04-24T00:00:00Z";
    String time_coverage_start "2015-03-28T00:00:00Z";
    String time_origin "2024-04-15 00:00:00";
    String title "HYCOM Region 6 3D";
    Float64 Westernmost_Easting 150.00001525878906;
  }
}

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.