Make A Graph

Dataset Title:	Med-CORDEX RCP8.5: Temperature (projections, day)
Institution:	ECCC (Dataset ID: medcordex_rcp85_projections_votemper_day)
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 →

depth (m)

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 _FillValue NaN;
    Float64 actual_range 1.483272e+9, 4.1339376e+9;
    String axis "T";
    String calendar "gregorian";
    String ioos_category "Time";
    String long_name "Time axis";
    String source_name "time_counter";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String title "Time";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    UInt32 _ChunkSizes 72;
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 _FillValue NaN;
    Float32 actual_range 1.472102, 5334.648;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String title "deptht";
    String units "m";
    Float32 valid_max 5334.648;
    Float32 valid_min 1.4721018;
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 _FillValue NaN;
    Float32 actual_range 30.1875, 45.9375;
    String axis "Y";
    String cell_methods "longitude: mean";
    String ioos_category "Location";
    String long_name "Latitude";
    String nav_model "Default grid";
    String standard_name "latitude";
    String units "degrees_north";
    Float32 valid_max 46.0;
    Float32 valid_min 30.1875;
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 _FillValue NaN;
    Float32 actual_range -18.125, 36.25;
    String axis "X";
    String cell_methods "latitude: mean";
    String ioos_category "Location";
    String long_name "Longitude";
    String nav_model "Default grid";
    String standard_name "longitude";
    String units "degrees_east";
    Float32 valid_max 36.3125;
    Float32 valid_min -18.125;
  }
  votemper {
    Float32 _FillValue 9.96921e+36;
    Float64 colorBarMaximum 40.0;
    Float64 colorBarMinimum -10.0;
    Float32 interval_operation 480.0;
    Float32 interval_write 86400.0;
    String ioos_category "Temperature";
    String long_name "Temperature";
    String online_operation "ave(x)";
    String units "degree_C";
  }
  NC_GLOBAL {
    String adriaclim_dataset "model";
    String adriaclim_model "NEMO";
    String adriaclim_scale "global";
    String adriaclim_timeperiod "daily";
    String cdm_data_type "Grid";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String creator_name "Canadian Meteorological Centre";
    String creator_url "https://www.ec.gc.ca/scitech/default.asp?lang=En&n=61B33C26-1#cmc";
    Float64 Easternmost_Easting 36.25;
    Float64 geospatial_lat_max 45.9375;
    Float64 geospatial_lat_min 30.1875;
    Float64 geospatial_lat_resolution 0.0625;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 36.25;
    Float64 geospatial_lon_min -18.125;
    Float64 geospatial_lon_resolution 0.0625;
    String geospatial_lon_units "degrees_east";
    String history 
"2025-05-24T06:19:25Z (local files)
2025-05-24T06:19:25Z https://erddap.cmcc-opa.eu/griddap/medcordex_rcp85_projections_votemper_day.das";
    String history_of_appended_files 
"Mon Dec 13 12:13:30 2021: Appended file /work/opa/das/ERDDAP/grid/grid_T.nc had following \"history\" attribute:
Fri Dec 10 19:59:55 2021: ncatted -a ,global,d,, /work/opa/das/ERDDAP/grid/grid_T.nc";
    String infoUrl "https://www.ec.gc.ca";
    String institution "ECCC";
    String keywords "canadian, centre, counter, data, depth, latitude, local, longitude, meteorological, source, temperature, time, time_counter, votemper";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String NCO "netCDF Operators version 4.9.3 (Homepage = http://nco.sf.net, Code = https://github.com/nco/nco)";
    Float64 Northernmost_Northing 45.9375;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 30.1875;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "Med-CORDEX RCP8.5: Temperature (projections, day)";
    String time_coverage_end "2100-12-31T12:00:00Z";
    String time_coverage_start "2017-01-01T12:00:00Z";
    String title "Med-CORDEX RCP8.5: Temperature (projections, day)";
    Float64 Westernmost_Easting -18.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.