AdriaClim ERDDAP | ?    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  AdriaClim RESM - Indicators - NEMO - OHC 40m 1992-2011 Annual mean Subscribe RSS
Institution:  CMCC   (Dataset ID: adriaclim_resm_indicators_ohc_nemo_2011_time)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form | Files
 
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
time (UTC) ?
    |< -
   
< slider >
latitude (degrees_north) ?     specify just 1 value →
   
< <
longitude (degrees_east) ?     specify just 1 value →
   
< <
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
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 ? )
    Time range:  |<  -            
[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.94224e+8, 1.29384e+9;
    String axis "T";
    String calendar "proleptic_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";
    Float64 actual_range 42.5, 42.5;
    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 16.5, 16.5;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  ohc {
    String ioos_category "Time";
    String long_name "Annual mean Ocean Heat Content (OHC) time variation";
    String standard_name "ohc";
    String units "J/m**2";
  }
  ohca {
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String ioos_category "Time";
    String long_name "Annual mean Ocean Heat Content anomaly (OHCa) time variation";
    String standard_name "ohca";
    String units "J/m**2";
  }
  NC_GLOBAL {
    String adriaclim_dataset "indicator";
    String adriaclim_model "NEMO";
    String adriaclim_scale "adriatic";
    String adriaclim_timeperiod "20y";
    String adriaclim_type "timeseries, anomaly, trend";
    String cdm_data_type "Grid";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creation_date "2023/04/11 11:49";
    String creator_name "Euro-Mediterranean Centre for Climate Change - CMCC";
    String creator_type "institution";
    String creator_url "https://www.ec.gc.ca/scitech/default.asp?lang=En&n=61B33C26-1#cmc";
    String description "Created with create_OHC_metrics_AdriaClim.py";
    Float64 Easternmost_Easting 16.5;
    Float64 geospatial_lat_max 42.5;
    Float64 geospatial_lat_min 42.5;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 16.5;
    Float64 geospatial_lon_min 16.5;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-09-18T10:24:27Z (local files)
2024-09-18T10:24:27Z https://erddap-adriaclim.cmcc-opa.eu/griddap/adriaclim_resm_indicators_ohc_nemo_2011_time.das";
    String infoUrl "https://cmcc.it";
    String institution "CMCC";
    String keywords "40m, adriaclim, annual, anomaly, centre, change, climate, cmcc, conservation, content, data, euro, euro-mediterranean, habitat, heat, integrated, mean, mediterranean, metrics, nemo, nmfs, noaa, ocean, office, ohc, ohca, time, variation";
    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 42.5;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 42.5;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String summary "AdriaClim RESM - Indicators - NEMO - OHC 40m 1992-2011 Annual mean";
    String time_coverage_end "2011-01-01T00:00:00Z";
    String time_coverage_start "1992-01-01T00:00:00Z";
    String title "AdriaClim RESM - Indicators - NEMO - OHC 40m 1992-2011 Annual mean";
    Float64 Westernmost_Easting 16.5;
  }
}

 

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.23
Disclaimers | Privacy Policy | Contact