Make A Graph

Dataset Title:	EMODnet - Regional sea level trends are derived from the GLORYS12v1 delayed- time (DT-2018 version)
Institution:	Canadian Meteorological Centre (Dataset ID: EMODNET_CMCC_ASLV_GLORYS12v1_GLO_TRENDMAP_v2019)
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 {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5764976e+9, 1.5764976e+9;
    String axis "T";
    String calendar "gregorian";
    String ioos_category "Time";
    String long_name "Time (hours since 1950-01-01)";
    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";
    Float32 actual_range -80.0, 90.0;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -180.0, 179.9167;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  zos {
    Float32 _FillValue -32767.0;
    String cell_methods "area: mean";
    String long_name "Sea surface height";
    Float32 missing_value -32767.0;
    String standard_name "sea_surface_height_above_geoid";
    String unit_long "Meters";
    String units "mm/yr";
  }
  NC_GLOBAL {
    String CDI "Climate Data Interface version 1.9.8 (https://mpimet.mpg.de/cdi)";
    String cdm_data_type "Grid";
    String CDO "Climate Data Operators version 1.9.8 (https://mpimet.mpg.de/cdo)";
    String citation "A. Cherchi, P. G. Fogli, T. Lovato, D. Peano, D. Iovino, S. Gualdi, S. Masina, E. Scoccimarro, S. Materia, A. Bellucci, A. Navarra - 2018";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 179.9167;
    Float64 geospatial_lat_max 90.0;
    Float64 geospatial_lat_min -80.0;
    Float64 geospatial_lat_resolution 0.08333333333333333;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 179.9167;
    Float64 geospatial_lon_min -180.0;
    Float64 geospatial_lon_resolution 0.08333334105116925;
    String geospatial_lon_units "degrees_east";
    String history 
"Thu Apr  7 10:33:26 2022: C:\\ETT\\nco\\ncatted.exe -a scale_factor,zos,d,f,0 .\\trend_199301_201912_MERCATOR--ASLV-GLORYS12v1-GLO.nc
Wed Mar 09 17:11:08 2022: cdo -mulc,3.662221 slope_199301_201912_MERCATOR--ASLV-GLORYS12v1-GLO.nc trend_199301_201912_MERCATOR--ASLV-GLORYS12v1-GLO_v2.nc
Tue Dec 28 11:08:43 2021: ncatted -a ,global,d,, /work/opa/das/Ree/EMOD-PACE/WP5/data_mod/trend/slope_199301_201912_MERCATOR--ASLV-GLORYS12v1-GLO.nc
2025-11-02T07:33:00Z (local files)
2025-11-02T07:33:00Z http://erddap.emodnet-physics.eu/griddap/EMODNET_CMCC_ASLV_GLORYS12v1_GLO_TRENDMAP_v2019.das";
    String infoUrl "https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2018MS001369";
    String institution "Canadian Meteorological Centre";
    String keywords "above, canadian, centre, data, earth, Earth Science > Oceans > Sea Surface Topography > Sea Surface Height, Earth Science > Solid Earth > Geodetics/Gravity > Geoid Properties, geodetics, geoid, gravity, height, latitude, local, longitude, meteorological, ocean, oceans, properties, science, sea, sea_surface_height_above_geoid, solid, source, surface, time, topography, zos";
    String keywords_vocabulary "GCMD Science Keywords";
    String license "CC-BY 4.0";
    String NCO "netCDF Operators version 4.9.3 (Homepage = http://nco.sf.net, Code = https://github.com/nco/nco)";
    Float64 Northernmost_Northing 90.0;
    String owner_name "EMODnet Physics";
    String owner_url "https://emodnet.ec.europa.eu/en/physics";
    String product_DOI "https://doi.org/10.1029/2018MS001369";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -80.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "EMODnet - Regional sea level trends are derived from the GLORYS12v1 delayed-time (DT-2018 version) altimeter gridded maps of sea level anomalies based on a stable number of altimeters (two) in the satellite constellation";
    String time_coverage_end "2019-12-16T12:00:00Z";
    String time_coverage_start "2019-12-16T12:00:00Z";
    String title "EMODnet - Regional sea level trends are derived from the GLORYS12v1 delayed-time (DT-2018 version)";
    Float64 Westernmost_Easting -180.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.