Make A Graph

Dataset Title:	Gulf of Mexico SSH Anomaly Grid - 2010
Institution:	Colorado Center for Astrodynamics Research (Dataset ID: gom_ssh_2010)
Information:	Summary \| License \| FGDC \| ISO 19115 \| Metadata \| Background \| Data Access Form \| Files

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 →

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 {
    UInt32 _ChunkSizes 365;
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.2623076e+9, 1.2937572e+9;
    String axis "T";
    String calendar "gregorian";
    String coverage_content_type "physicalMeasurement";
    String grid_mapping "crs";
    String ioos_category "Time";
    String long_name "time (days in seconds since 1970)";
    String standard_name "time";
    String standard_name_url "http://mmisw.org/ont/ioos/parameter/time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
    Float64 valid_max 1.2937572e+9;
    Float64 valid_min 1.2623076e+9;
  }
  latitude {
    UInt32 _ChunkSizes 53;
    String _CoordinateAxisType "Lat";
    Float64 actual_range 18.0, 31.0;
    String axis "Y";
    String comment "Positive latitude is North latitude, negative latitude is South latitude. The latitude specifies the center of the bin.";
    String coverage_content_type "coordinate";
    String ioos_category "Location";
    String long_name "Latitude";
    Float64 spacing 0.25;
    String standard_name "latitude";
    String standard_name_url "http://mmisw.org/ont/ioos/parameter/latitude";
    String units "degrees_north";
    Float64 valid_max 31.0;
    Float64 valid_min 18.0;
  }
  longitude {
    UInt32 _ChunkSizes 73;
    String _CoordinateAxisType "Lon";
    Float64 actual_range -98.0, -80.0;
    String axis "X";
    String comment "East longitude relative to the Greenwich meridian. The longitude specifies the center the bin.";
    String coverage_content_type "coordinate";
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 spacing 0.25;
    String standard_name "longitude";
    String standard_name_url "http://mmisw.org/ont/ioos/parameter/longitude";
    String units "degrees_east";
    Float64 valid_max -80.0;
    Float64 valid_min -98.0;
  }
  ssh {
    Float64 _FillValue 32767.0;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String comment "Gulf of Mexico historical gridded sea surface height anomaly above the model mean sea level. Flagged data denotes land or missing model data. For more information on the interpolation scheme please refer to the Appendix in: Leben, R.R., G.H. Born, and B.R. Engebreth. 2002. Operational altimeter data processing for mesoscale monitoring. Marine Geodesy 25:3-18, doi:10.1080/014904102753516697.";
    String coverage_content_type "physicalMeasurement";
    String ioos_category "Sea Level";
    String long_name "sea surface height";
    Float64 missing_value 32767.0;
    String platform "satellites";
    String standard_name "sea_surface_height_above_sea_level";
    String standard_name_url "http://mmisw.org/ont/cf/parameter/sea_surface_height_above_sea_level";
    String units "cm";
    Float64 valid_max 84.51581573486328;
    Float64 valid_min -144.21878051757812;
  }
  NC_GLOBAL {
    String _NCProperties "version=1|netcdflibversion=4.6.1|hdf5libversion=1.8.12";
    String acknowledgement "The historical collinear data was obtained from the Radar Altimeter Database System (RADS). For more information please see http://rads.tudelft.nl/rads/rads.shtml";
    String analysis_dates "analysis for each day from: 2010-01-01 to 2010-12-31";
    String cdm_data_type "Grid";
    String cdm_timeseries_variables "timeseries, station_id, latitude, longitude, timeseries";
    String comment "A dayly values is a interpolation from satellite swath of data from day-15 to day+16.";
    String commentT "The actual duration for the ssh year is from : 2003-12-15 00:00:00 to 2004-12-31 23:59:59";
    String contributor_country "USA";
    String contributor_role_vocabulary "unknown";
    String Conventions "CF-1.6, ACDD-1.3,IOOS-1.2, COARDS";
    String country "USA";
    String creator_address "3775 Discovery Drive";
    String creator_city "Boulder";
    String creator_country "USA";
    String creator_email "leben@colorado.edu";
    String creator_institution "Colorado Center for Astrodynamics Research";
    String creator_name "Bob Leben";
    String creator_phone "+1-303-492-4113";
    String creator_postalcode "80309";
    String creator_sector "academic";
    String creator_state "Colorado";
    String creator_type "person";
    String creator_url "https://www.colorado.edu/ccar/robert-leben";
    String date_created "2020-07-23T11:52:05Z";
    String date_issued "2020-07-23T11:52:05Z";
    String date_metadata_modified "2020-07-23T11:52:05Z";
    String date_modified "2020-07-23T11:52:05Z";
    Float64 Easternmost_Easting -80.0;
    String geospatial_bounds "Polygon (-98.00 18.00,-80.00 18.00, -80 31.00, -98.00 31.00,-98.00 18.00 )";
    String geospatial_bounds_crs "EPSG:4326";
    String geospatial_bounds_vertical_crs "EPSG:5829";
    Float64 geospatial_lat_max 31.0;
    Float64 geospatial_lat_min 18.0;
    Float64 geospatial_lat_resolution 0.25;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -80.0;
    Float64 geospatial_lon_min -98.0;
    Float64 geospatial_lon_resolution 0.25;
    String geospatial_lon_units "degrees_east";
    String history 
"Creation date: 51  49  49  53
2024-11-14T07:14:23Z (local files)
2024-11-14T07:14:23Z https://gcoos5.geos.tamu.edu/griddap/gom_ssh_2010.das";
    String id "ssha_gom_wrt_model_2010";
    String infoUrl "https://www.colorado.edu/ccar/labs-and-facilities";
    String institution "Colorado Center for Astrodynamics Research";
    String instrument "radar altimeter";
    String instrument_vocabulary "GCMD Science Keywords Version 9.1.5";
    String keywords "above, altimeter, anomalies, anomaly, astrodynamics, attribute, center, colorado, data, earth science> ocean> coastal processes> sea surface height, ers, european, experiment, gridded, gulf, gulf of mexico, height, historical, included, latitude, level, list, longitude, mean, mexico, model, near, nrt, please, radar, real, remote, research, satellite, satellites, sea, sea level, sea_surface_height_anomaly, see, sensing, ssh, surface, time, topex, topography, various";
    String keywords_vocabulary "GCMD Science Keywords Version 9.1.5, CF Standard Names v72";
    String license "Unrestricted use and distribution";
    String metadata_link "https://geo.gcoos.org/ssh/";
    String naming_authority "edu.colorado.ccar";
    Float64 Northernmost_Northing 31.0;
    String platform "satellites";
    String platform_name "satellites_included: cryosat2, saral";
    String platform_vocabulary "https://mmisw.org/ont/ioos/platform";
    String processing_center "CCAR";
    String processing_level "L4";
    String product_version "v0.0";
    String publisher_address "Eller O&M Building, 3146 TAMU, 797 Lamar St";
    String publisher_city "College Station";
    String publisher_country "USA";
    String publisher_email "mstoessel@ocean.tamu.edu (GCOOS_Contacts)";
    String publisher_institution "Gulf of Mexico Coastal Ocean Observing System (GCOOS) at Texas A&M University/ Department of Ocecanography";
    String publisher_name "Gulf of Mexico Coastal Ocean Observing Service, GCOOS, at Texas A&M University, Dept. of Oceanography";
    String publisher_phone "+1-979-862-7662";
    String publisher_postalcode "77843";
    String publisher_state "Texas";
    String publisher_type "institution";
    String publisher_url "https://geo.gcoos.org/ssh/";
    String references "Leben, R.R., G.H. Born, and B.R. Engebreth. 2002. Operational altimeter data processing for mesoscale monitoring. Marine Geodesy 25:3-18, doi:10.1080/014904102753516697.";
    String sea_name "Gulf f Mexico";
    String source "radar altimeter";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 18.0;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Since 1996, global, near-real-time maps of mesoscale anomalies derived from tandem sampling provided by altimeters aboard the Topography Experiment (TOPEX)/Poseidon and European Remote Sensing Satellite (ERS)-2 satellites have been posted on web pages hosted at the Colorado Center for Astrodynamics Research. The original, near-real-time processing system was based on a quick-look analysis that referenced the data to a high-resolution gridded mean sea surface available at the time. Recently, state-of-the-art mean sea surfaces have been derived that are based on a more complete record of altimeter observations. An updated mesoscale monitoring system based on a new mean surface is described and shown to provide improved mesoscale monitoring to the successful system implemented in 1996.";
    String time_coverage_duration "P00Y12M30DT00H00M00S";
    String time_coverage_end "2010-12-31T01:00:00Z";
    String time_coverage_start "2010-01-01T01:00:00Z";
    String title "Gulf of Mexico SSH Anomaly Grid - 2010";
    Float64 Westernmost_Easting -98.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/jplMURSST41.htmlTable?analysed_sst[(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.