Make A Graph

Dataset Title:	EMODPACE - Sea Level monthly mean, EurAsia. This product is based, uses and reprocess the CMEMS product id. SEALEVEL_GLO_PHY_CLIMATE_L4_REP_OBSERVATIONS_ 008_057
Institution:	CMCC (Dataset ID: EMODPACE_SLEV_MONTHLY_MEAN)
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 {
    Int32 _ChunkSizes 512;
    String _CoordinateAxisType "Time";
    Float64 actual_range 7.258464e+8, 1.5751584e+9;
    String axis "T";
    String bounds "time_bnds";
    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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -6.875, 44.875;
    String axis "Y";
    String bounds "latitude_bnds";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 30.125, 129.875;
    String axis "X";
    String bounds "longitude_bnds";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  sla {
    Int32 _ChunkSizes 1, 1, 400;
    Float64 _FillValue -214748.3647;
    String cell_methods "time: mean";
    String comment "The sea level anomaly is the sea surface height above mean sea surface; it is referenced to the [1993, 2012] period; see the product user manual for details";
    String grid_mapping "crs";
    String long_name "Sea level anomaly";
    Float64 missing_value -214748.3647;
    String standard_name "sea_surface_height_above_sea_level";
    String units "m";
  }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.7.4,hdf5=1.12.0,";
    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 comment "Sea Surface Height measured by Altimetry and derived variables";
    String contact "http://climate.copernicus.eu/c3s-user-service-desk";
    String Conventions "CF-1.6";
    String creator_email "http://climate.copernicus.eu/c3s-user-service-desk";
    String creator_name "Copernicus Climate Change Service (C3S)";
    String creator_url "http://climate.copernicus.eu";
    String date_created "2019-01-24T16:52:35Z";
    String date_issued "2019-01-24T16:52:35Z";
    String date_modified "2019-01-24T16:52:35Z";
    Float64 Easternmost_Easting 129.875;
    String frequency "mon";
    Float64 geospatial_lat_max 44.875;
    Float64 geospatial_lat_min -6.875;
    Float64 geospatial_lat_resolution 0.25;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 129.875;
    Float64 geospatial_lon_min 30.125;
    Float64 geospatial_lon_resolution 0.25;
    String geospatial_lon_units "degrees_east";
    String history 
"Wed Oct 27 15:01:05 2021: C:\\ETT\\nco\\ncks.exe -d latitude,-7.0,+45.0 -d longitude,+30.0,+130.0 dt_global_twosat_phy_l4_199301_201912_vDT2018.nc -O EMODNET_PACE_SEA_LEVEL_MONTHLY_MEAN.nc
Thu Aug 05 10:20:37 2021: cdo cat /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_1993_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_1994_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_1995_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_1996_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_1997_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_1998_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_1999_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2000_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2001_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2002_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2003_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2004_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2005_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2006_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2007_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2008_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2009_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2010_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2011_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2012_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2013_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2014_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2015_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2016_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2017_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2018_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_2019_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/trend/dt_global_twosat_phy_l4_199301_201912_vDT2018.nc
Thu Aug 05 10:19:58 2021: cdo cat /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199301_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199302_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199303_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199304_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199305_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199306_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199307_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199308_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199309_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199310_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199311_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199312_mm_sla_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/ts/dt_global_twosat_phy_l4_1993_mm_sla_vDT2018.nc
Wed Aug  4 15:33:06 2021: ncks -v sla /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199301_mm_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199301_mm_sla_vDT2018.nc
Wed Aug 04 15:33:01 2021: cdo monavg /work/opa/das/Ree/EMOD-PACE/WP5/data/daily/1993/dt_global_twosat_phy_l4_199301_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/monthly/1993/dt_global_twosat_phy_l4_199301_mm_vDT2018.nc
Wed Aug 04 15:32:46 2021: cdo cat /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930101_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930102_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930103_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930104_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930105_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930106_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930107_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930108_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930109_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930110_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930111_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930112_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930113_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930114_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930115_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930116_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930117_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930118_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930119_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930120_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930121_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930122_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930123_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930124_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930125_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930126_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930127_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930128_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930129_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930130_vDT2018.nc /data/inputs/metocean/historical/obs/satellite/altimetry/CLS/twosat/L4/day/1993/01/dt_global_twosat_phy_l4_19930131_vDT2018.nc /work/opa/das/Ree/EMOD-PACE/WP5/data/daily/1993/dt_global_twosat_phy_l4_199301_vDT2018.nc
2019-01-24 16:52:37Z: Creation
2024-10-30T23:06:36Z (local files)
2024-10-30T23:06:36Z https://erddap.emodnet.eu/griddap/EMODPACE_SLEV_MONTHLY_MEAN.das";
    String infoUrl "http://climate.copernicus.eu";
    String institution "CMCC";
    String keywords "above, anomaly, centre, climate, cls, cmems, cnes, collecte, data, derived, duacs, earth, Earth Science > Oceans > Ocean Topography > Sea Surface Height, Earth Science > Oceans > Sea Surface Topography > Sea Surface Height, emodnet, emodnet_pace, etudes, glo, global, gridded, height, L4, latitude, level, localisation, longitude, mean, merged, month, monthly, national, observations, ocean, oceans, pace, phy, product, rep, satellites, science, sea, sea_surface_height_above_sea_level, sealevel, sla, spatiales, ssalto, ssh, surface, time, topography, two";
    String keywords_vocabulary "NetCDF COARDS Climate and Forecast Standard Names";
    String license "http://climate.copernicus.eu/c3s-user-service-desk";
    String Metadata_Conventions "Unidata Dataset Discovery v1.0";
    String NCO "\"4.6.3\"";
    Float64 Northernmost_Northing 44.875;
    String platform "ERS-1, Topex/Poseidon,";
    String processing_level "L4";
    String product_version "2019";
    String project "Copernicus Climate Change Service (C3S)";
    String references "http://climate.copernicus.eu";
    String software_version "6.2_DUACS_DT2018_baseline";
    String source "Altimetry measurements";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -6.875;
    String ssalto_duacs_comment "The reference mission used for the altimeter inter-calibration processing is Topex/Poseidon between 1993-01-01 and 2002-04-23, Jason-1 between 2002-04-24 and 2008-10-18, OSTM/Jason-2 between 2008-10-19 and 2016-06-25, Jason-3 since 2016-06-25.";
    String standard_name_vocabulary "NetCDF Climate and Forecast (CF) Metadata Convention Standard Name Table v37";
    String summary "EMODPACE - Sea Level monthly mean, EurAsia. This product is based, uses and reprocess the CMEMS product id. SEALEVEL_GLO_PHY_CLIMATE_L4_REP_OBSERVATIONS_008_057";
    String time_coverage_duration "P1D";
    String time_coverage_end "2019-12-01T00:00:00Z";
    String time_coverage_resolution "P1D";
    String time_coverage_start "1993-01-01T00:00:00Z";
    String title "EMODPACE - Sea Level monthly mean, EurAsia. This product is based, uses and reprocess the CMEMS product id. SEALEVEL_GLO_PHY_CLIMATE_L4_REP_OBSERVATIONS_008_057";
    Float64 Westernmost_Easting 30.125;
  }
}

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.