Easier access to all of NOAA's data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  HYCOM Region 1, Best Time Series [time][lat][lon], 2013-present Subscribe RSS
Institution:  Naval Oceanographic Office   (Dataset ID: noaa_ncddc_41ff_0910_a705)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
Dimensions ?    Start ?    Stop ?
time (UTC) ?     specify just 1 value →
    << -
< <
latitude (degrees_north) ?
< slider >
longitude (degrees_east) ?
< slider >
Graph Settings
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   Ascending: 
(Please be patient. It may take a while to get the data.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
[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 1.3619232e+9, 1.521936e+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 {
    Float64 colorBarMaximum 2.0;
    Float64 colorBarMinimum -2.0;
    String ioos_category "Sea Level";
    String long_name "Water Surface Elevation";
    Int32 NAVO_code 32;
    String standard_name "sea_surface_height";
    String units "meter";
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String cdm_data_type "Grid";
    String contact "NAVOCEANO, NP31";
    String Conventions "CF-1.6, NAVO_netcdf_v1.1, COARDS, ACDD-1.3";
    String creator_email "";
    String creator_name ";";
    String creator_url "";
    String distribution_statement "Approved for public release: distribution unlimited.";
    Float64 Easternmost_Easting 310.0;
    String field_type "instantaneous";
    String generating_model "GOFS 3.0, 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 20180315 ;
FMRC Best Dataset
    String id "hycom.hycom_reg1_agg.HYCOM_Region_1_Aggregation_best.ncd";
    String infoUrl "";
    String input_data_source "FNMOC NAVGEM, Satellite SSH, SST, in situ";
    String institution "Naval Oceanographic Office";
    String keywords "best, best time series, coordinate, data, earth, Earth Science > Oceans > Sea Surface Topography > Sea Surface Height, elevation, height, hybrid, hycom, latitude, level, longitude, model, naval, ocean, oceanographic, oceans, office, region, science, sea, sea level, sea_surface_height, seawater, series, surf_el, surface, time, time series, topography, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "Approved for public release: distribution unlimited.";
    String location "Proto fmrc:HYCOM_Region_1_Aggregation";
    String model_type "x-curvilinear lon, y-curvilinear lat, hybrid z";
    Float64 Northernmost_Northing 70.0;
    String operational_status "operational";
    String publisher_name "";
    String publisher_type "institution";
    String references "";
    String source "HYCOM archive file";
    String sourceUrl "";
    Float64 Southernmost_Northing 0.0;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Best time series, taking the data from the most recent run available. Aggregation of HYbrid Coordinate Ocean Model (HYCOM) Region 1";
    String time_coverage_end "2018-03-25T00:00:00Z";
    String time_coverage_start "2013-02-27T00:00:00Z";
    String time_origin "2018-03-15 00:00:00";
    String title "HYCOM Region 1, Best Time Series [time][lat][lon], 2013-present";
    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{?query}
For example,[(2002-06-01T09:00:00Z)][(-89.99):1000:(89.99)][(-179.99):1000:(180.0)]
Thus, the query is often a data variable name (e.g., analysed_sst), followed by [(start):stride:(stop)] (or a shorter variation of that) for each of the variable's dimensions (for example, [time][latitude][longitude]).

For details, see the griddap Documentation.

ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact