Make A Graph

Dataset Title:	Daily Southern Ocean Sea Level Anomaly And Geostrophic Currents from multimission altimetry, 2013-2019
Institution:	CLS,CNES (Dataset ID: seanoe_slev_anomaly_geostrophic_currents)
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 →

longitude (degrees_east)

latitude (degrees_north)

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.3647744e+9, 1.5645312e+9;
    String axis "T";
    String calendar "gregorian";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Int16 actual_range 0, 349;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String source_name "x";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Int16 actual_range 0, 349;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String source_name "y";
    String standard_name "latitude";
    String units "degrees_north";
  }
  sla {
    Float64 colorBarMaximum 2.0;
    Float64 colorBarMinimum -2.0;
    String ioos_category "Sea Level";
    String long_name "Sea Level Anomaly";
    String standard_name "sea_surface_height_above_sea_level";
    String units "m";
  }
  formal_error {
    Float64 colorBarMaximum 50.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Optimal Interpolation Formal Error";
    String standard_name "formal_err";
    String units "m";
  }
  U {
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String ioos_category "Currents";
    String long_name "Zonal Geostrophic Current Anomaly";
    String standard_name "zonal_geostophic_current_anomaly";
    String units "m/s";
  }
  V {
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String ioos_category "Currents";
    String long_name "Meridional Geostrophic Current Anomaly";
    String standard_name "meridional_geostophic_current_anomaly";
    String units "m/s";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String comment "Sea Level Anomaly measured by Altimetry and derived variables";
    String contact "matthis.auger@locean.ipsl.fr";
    String Conventions "CF-1.10, COARDS, ACDD-1.3";
    String creator_email "matthis.auger@locean.ipsl.fr";
    String creator_name "Matthis Auger";
    String creator_type "person";
    String creator_url "http://aviso.altimetry.fr";
    Float64 Easternmost_Easting 349.0;
    Float64 geospatial_lat_max 349.0;
    Float64 geospatial_lat_min 0.0;
    Float64 geospatial_lat_resolution 1.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 349.0;
    Float64 geospatial_lon_min 0.0;
    Float64 geospatial_lon_resolution 1.0;
    String geospatial_lon_units "degrees_east";
    String Grid "Subset of Southern Hemisphere 25km EASE2 Grid";
    String history 
"Altimetry measurements
2024-11-06T09:33:21Z (local files)
2024-11-06T09:33:21Z https://er1.s4oceanice.eu/griddap/seanoe_slev_anomaly_geostrophic_currents.das";
    String infoUrl "http://aviso.altimetry.fr";
    String institution "CLS,CNES";
    String keywords "above, anomaly, centre, cls, cnes, collecte, current, currents, data, earth, Earth Science > Oceans > Sea Surface Topography > Sea Surface Height, error, etudes, formal, formal_err, formal_error, geostophic, geostrophic, gridded, height, interpolation, level, localisation, meridional, meridional_geostophic_current_anomaly, multi, multi-satellite, national, ocean, oceans, oceans>ocean topography>sea surface height, optimal, product, satellite, satellites, science, sea, sea level, sea_surface_height_above_sea_level, sla, spatiales, statistics, surface, time, topography, zonal, zonal_geostophic_current_anomaly";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC-BY4.0";
    Float64 Northernmost_Northing 349.0;
    String platform "AL_C2_S3A";
    String processing_level "L4";
    String product_version "1.1";
    String references "http://aviso.altimetry.fr";
    String source "Altimetry measurements";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 0.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Sea Level Anomaly measured by Altimetry and derived variables";
    String time_coverage_duration "P2312.0D";
    String time_coverage_end "2019-07-31T00:00:00Z";
    String time_coverage_resolution "P1.0D";
    String time_coverage_start "2013-04-01T00:00:00Z";
    String title "Daily Southern Ocean Sea Level Anomaly And Geostrophic Currents from multimission altimetry, 2013-2019";
    Float64 Westernmost_Easting 0.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.