NOAA ERDDAP
Easier access to scientific data

Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  ARGO gridded Temperature data Subscribe RSS
Institution:  UCSD/Scripps   (Dataset ID: temp_e657_971e_6245)
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 →
    |< - >|
< <
PRESSURE (dbar) ?     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 1.0742112e+9, 1.4845248e+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";
  }
  PRESSURE {
    Float32 actual_range 2.5, 1975.0;
    String axis "Z";
    String long_name "Depth";
    String point_spacing "uneven";
    String positive "down";
    String standard_name "depth";
    String units "dbar";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range -64.5, 64.5;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String point_spacing "even";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range 20.5, 379.5;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    Float64 modulo 360.0;
    String point_spacing "even";
    String standard_name "longitude";
    String units "degrees_east";
  }
  ARGO_TEMPERATURE_ANOMALY {
    Float32 _FillValue -999.0;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum -10.0;
    String history "From RG_ArgoClim_Temperature_2016";
    String long_name "ARGO TEMPERATURE ANOMALY defined by Jan 2004 - Dec 2015 (12.0 year) RG CLIMATOLOGY";
    Float32 missing_value -999.0;
    String units "degree celcius (ITS-90)";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    Float64 Easternmost_Easting 379.5;
    Float64 geospatial_lat_max 64.5;
    Float64 geospatial_lat_min -64.5;
    Float64 geospatial_lat_resolution 1.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 379.5;
    Float64 geospatial_lon_min 20.5;
    Float64 geospatial_lon_resolution 1.0;
    String geospatial_lon_units "degrees_east";
    String history 
"FERRET V6.842   11-Jan-17FERRET V5.51    8-Mar-17
2024-03-29T08:43:38Z (local files)
2024-03-29T08:43:38Z https://data.pmel.noaa.gov/generic/griddap/temp_e657_971e_6245.das";
    String infoUrl "???";
    String institution "UCSD/Scripps";
    String keywords "anomaly, argo, ARGO_TEMPERATURE_ANOMALY, array, climatology, data, defined, geostrophic, LATITUDE, local, LONGITUDE, oceanography, PRESSURE, real, real time, real-time, realtime, source, temperature, time, year";
    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 64.5;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing -64.5;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary "ARGO gridded Temperature data";
    String time_coverage_end "2017-01-16T00:00:00Z";
    String time_coverage_start "2004-01-16T00:00:00Z";
    String title "ARGO gridded Temperature data";
    Float64 Westernmost_Easting 20.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.18
Disclaimers | Privacy Policy | Contact