NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?To make a graph of data from this grid dataset, repeatedly:
  1. Change the "Graph Type" and the variables for the graph\'s axes.
  2. Change the "Dimension Ranges" to specify a subset of the data.
  3. Change the "Graph Settings" as desired.
  4. Press "Redraw the Graph".
This Make A Graph web page just simplifies the creation of griddap URLs with graphics commands.
If you want, you can create these URLs by hand or have a computer program do it.
Then you don\'t have to use this form to get data. See the "Bypass this form" link below.

')" onmouseout="UnTip()" >
Dataset Title:  HYCOM Region 1 2D   RSS
Institution:  Naval Oceanographic Office via NOAA NCEI   (Dataset ID: HYCOM_reg1_latest2d)
Information:  Summary ?HYCOM Region 1 Data

cdm_data_type = Grid
VARIABLES (all of which use the dimensions [time][latitude][longitude]):
surf_el (Water Surface Elevation, meter)
')" onmouseout="UnTip()" > | 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.')" onmouseout="UnTip()" > | Metadata | Background | Data Access Form
 
Graph Type:  ?Graph Type
lines draws lines on a graph where X=a dimension and Y=a data variable.

linesAndMarkers draws lines and markers on a graph where X=a dimension and Y=a data variable. If a Color variable is specified, the markers are colored.

markers plots markers on a graph where X=a dimension and Y=a data variable. If a Color variable is specified, the markers are colored.

sticks is usually used to plot time on the x axis, with the sticks being drawn from the x component and y component of currents or wind data.

surface plots a longitude/latitude grid of data as a colored surface on a map.

vectors plots vectors on a map. Currently, this requires that X=longitude and Y=latitude. The other variables provide the vector\'s x component and y component. So it is often used for currents or wind data.

Changing the Graph Type or variables automatically submits this form.
For the remainder of this form: make changes, then press Redraw the Graph below.')" onmouseout="UnTip()" >

X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
time (UTC) ?  Float64 time[25654] {
    String _CoordinateAxisType "Time";
    Float64 actual_range 9.466848e+8, 1.7254836e+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";
  }
')" onmouseout="UnTip()" >
    specify just 1 value →
    |< -
< <
latitude (degrees_north) ?  Float64 latitude[876] {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 0.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";
  }
')" onmouseout="UnTip()" >
    +
    -
< slider >
longitude (degrees_east) ?  Float64 longitude[626] {
    String _CoordinateAxisType "Lon";
    Float64 actual_range 260.0000305175781, 310.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";
  }
')" onmouseout="UnTip()" >
    +
    -
< slider >
 
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: Bypass This Form
griddap lets you request a graph or data by sending a specially formed URL to the server. The URL identifies a dataset, the desired file type for the response, the subset of data that you want to view, and other graph specifications. This form simplifies this task: when you click on Redraw the Graph, the URL is generated and sent to the server. The URL that you see here is the URL that the form generated to create the image at right.

If you learn how to form the URLs, you won\'t have to use this form to get data.
You can write a computer program or script that automatically generates URLs, sends them to ERDDAP, and gets the data or images. For more information on forming the URLs, click on the Bypass this form link to see the griddap documentation.')" onmouseout="UnTip()" size="60" maxlength="1000" >
(Documentation / Bypass this form ?Bypass This Form
griddap lets you request a graph or data by sending a specially formed URL to the server. The URL identifies a dataset, the desired file type for the response, the subset of data that you want to view, and other graph specifications. This form simplifies this task: when you click on Redraw the Graph, the URL is generated and sent to the server. The URL that you see here is the URL that the form generated to create the image at right.

If you learn how to form the URLs, you won\'t have to use this form to get data.
You can write a computer program or script that automatically generates URLs, sends them to ERDDAP, and gets the data or images. For more information on forming the URLs, click on the Bypass this form link to see the griddap documentation.')" onmouseout="UnTip()" > )

    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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 9.466848e+8, 1.7254836e+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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 0.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 260.0000305175781, 310.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";
  }
  surf_el {
    String coordinates "time_run time lat lon";
    String ioos_category "Other";
    String long_name "Water Surface Elevation";
    Int32 NAVO_code 32;
    String units "meter";
  }
  NC_GLOBAL {
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String analysis_tau "033 hours since analysis, analysis_time_origin = 2024-09-02 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 310.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 0.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 310.0;
    Float64 geospatial_lon_min 260.0000305175781;
    String geospatial_lon_units "degrees_east";
    String history 
"created on 20240903 ;
FMRC Best Dataset
2025-04-29T15:51:10Z http://www.ncei.noaa.gov/thredds-coastal/dodsC/hycom/hycom_reg1_agg/HYCOM_Region_1_Aggregation_best.ncd
2025-04-29T15:51:10Z http://www.ncei.noaa.gov/griddap/HYCOM_reg1_latest2d.das";
    String infoUrl "http://www.ncei.noaa.gov/thredds-coastal/catalog/hycom/hycom_reg1_agg/catalog.html?dataset=hycom/hycom_reg1_agg/HYCOM_Region_1_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_1_Aggregation";
    String message "UNCLASSIFIED";
    String model_type "x-curvilinear lon, y-curvilinear lat, hybrid z";
    Float64 Northernmost_Northing 70.0;
    String operational_status "operational";
    String publisher_name "OceanNOMADS@noaa.gov";
    String reference "http://portal.fnmoc.navy.mil/";
    String source "HYCOM archive file; GOFS 3.1 GLBy0.08 expt_93.0";
    String sourceUrl "http://www.ncei.noaa.gov/thredds-coastal/dodsC/hycom/hycom_reg1_agg/HYCOM_Region_1_Aggregation_best.ncd";
    Float64 Southernmost_Northing 0.0;
    String standard_name_vocabulary "CF-1.0";
    String summary "HYCOM Region 1 Data";
    String time_coverage_end "2024-09-04T21:00:00Z";
    String time_coverage_start "2000-01-01T00:00:00Z";
    String time_origin "2024-09-03 00:00:00";
    String title "HYCOM Region 1 2D";
    Float64 Westernmost_Easting 260.0000305175781;
  }
}

 

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.

griddap request URLs must be in the form
http://coastwatch.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
http://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.


 
ERDDAP, Version 2.23
Disclaimers | Privacy Policy | Contact