EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data
log in    
Brought to you by EMODnet Physics    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  EMODnet Physics - TEMPERATURE ANOMALY 20 YEARS Subscribe RSS
Institution:  EMODnet Physics   (Dataset ID: ERD_EP_TEMP_ANO_20Y)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
 
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) ?
    +
    -
< slider >
longitude (degrees_east) ?
    +
    -
< slider >
 
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 6.46704e+8, 1.5618528e+9;
    String axis "T";
    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";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 19902009, 20002019;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range -77.0104751586914, 89.8962631225586;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -180.0, 179.5;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  ANOMALY {
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String ep_parameter_group "Water Temperature";
    String long_name "ANOMALY";
    String units "degree_Celsius";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 179.5;
    Float64 geospatial_lat_max 89.8962631225586;
    Float64 geospatial_lat_min -77.0104751586914;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 179.5;
    Float64 geospatial_lon_min -180.0;
    Float64 geospatial_lon_resolution 0.5;
    String geospatial_lon_units "degrees_east";
    String history 
"2021-09-21T14:27:01Z (local files)
2021-09-21T14:27:01Z https://erddap.emodnet-physics.eu/griddap/ERD_EP_TEMP_ANO_20Y.das";
    String infoUrl "https://portal.emodnet-physics.eu/";
    String institution "EMODnet Physics";
    String keywords "anomaly, data, latitude, local, longitude, source, time";
    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.";
    Float64 Northernmost_Northing 89.8962631225586;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -77.0104751586914;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "Data from a local source.";
    String time_coverage_end "2019-06-30T00:00:00Z";
    String time_coverage_start "1990-06-30T00:00:00Z";
    String title "EMODnet Physics - TEMPERATURE ANOMALY 20 YEARS";
    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.

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.


 
ERDDAP, Version 2.12
Disclaimers | Privacy Policy | Contact