NOAA The NOAA GEO-IDE UAF ERDDAP
Easier access to all of NOAA's data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  TCHP_D26 Fields, 0.25°, 2015-present Subscribe RSS
Institution:  USDOC/NOAA/OAR/AOML/PHOD   (Dataset ID: noaa_aoml_76dc_1bcd_7aea)
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 →
    << -
< <
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:   Ascending: 
 
(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.4391216e+9, 1.5193872e+9;
    String axis "T";
    String calendar "Gregorian";
    String CoordinateAxisType "Time";
    String ioos_category "Time";
    String long_name "Reference 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 -90.0, 90.0;
    String axis "Y";
    String CoordinateAxisType "Lat";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -180.0, 180.0;
    String axis "X";
    String CoordinateAxisType "Lon";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  Tropical_Cyclone_Heat_Potential {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 218.12;
    Float64 colorBarMaximum 250.0;
    Float64 colorBarMinimum 0.0;
    String coordsys "geographic";
    String ioos_category "Other";
    String long_name "Tropical Cyclone Heat Potential";
    String standard_name "integral_of_sea_water_potential_temperature_wrt_depth_expressed_as_heat_content";
    String units "KJcm-2";
    String variable_info "Tropical Cyclone Heat Potential";
  }
  D26 {
    Float32 _FillValue NaN;
    Float32 actual_range 0.0, 218.12;
    Float64 colorBarMaximum 250.0;
    Float64 colorBarMinimum 0.0;
    String coordsys "geographic";
    String ioos_category "Temperature";
    String long_name "D26";
    String standard_name "depth_of_isosurface_of_sea_water_potential_temperature";
    String units "m";
    String variable_info "Depth of the 26deg isotherm";
  }
  NC_GLOBAL {
    String cdm_data_type "Grid";
    String comment 
"Tropical Cyclone Heat Potential V2.1
 www.aoml.noaa.gov/phod/cyclone";
    String contact "Joaquin.Trinanes@noaa.gov";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "Joaquin.Trinanes@noaa.gov";
    String creator_name "Physical Oceanography Division at NOAA/AOML";
    String creator_type "institution";
    String creator_url "http://www.aoml.noaa.gov/phod/cyclone/data/gl.html";
    String data_source "USDOC/NOAA/OAR/AOML/PHOD ATLANTIC OCEANWATCH";
    Float64 Easternmost_Easting 180.0;
    Float64 geospatial_lat_max 90.0;
    Float64 geospatial_lat_min -90.0;
    Float64 geospatial_lat_resolution 0.25;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 180.0;
    Float64 geospatial_lon_min -180.0;
    Float64 geospatial_lon_resolution 0.25;
    String geospatial_lon_units "degrees_east";
    String history 
"2018-02-23T14:53:30Z http://cwcgom.aoml.noaa.gov/thredds/dodsC/TCHP/TCHP.nc
2018-02-23T14:53:30Z http://upwell.pfeg.noaa.gov/griddap/noaa_aoml_76dc_1bcd_7aea.das";
    String id "TCHP";
    String infoUrl "http://cwcgom.aoml.noaa.gov/thredds/dodsC/TCHP/TCHP.nc.html";
    String institution "USDOC/NOAA/OAR/AOML/PHOD";
    String keywords "altimeter, aoml, atlantic, atmospheric, commerce, content, cyclone, d26, data, department, depth, depth_of_isosurface_of_sea_water_potential_temperature, division, earth, Earth Science > Oceans > Ocean Temperature > Potential Temperature, Earth Science > Oceans > Ocean Temperature > Water Temperature, expressed, fields, heat, heat content, height, hurricane, hurricane intensification, integral, integral_of_sea_water_potential_temperature_wrt_depth_expressed_as_heat_content, isosurface, laboratory, latitude, longitude, meteorological, noaa, oar, ocean, oceanic, oceanographic, oceanography, oceans, office, phod, physical, potential, research, science, sea, seawater, ssh, sst, states, surface, tchp, temperature, time, tropical, Tropical_Cyclone_Heat_Potential, united, usdoc, water, wrt";
    String keywords_vocabulary "GCMD Science Keywords";
    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 90.0;
    String origin "USDOC/NOAA/OAR/AOML/PHOD ATLANTIC OCEANWATCH";
    String source_data "Altimeter SHA+MW SST";
    String sourceUrl "http://cwcgom.aoml.noaa.gov/thredds/dodsC/TCHP/TCHP.nc";
    Float64 Southernmost_Northing -90.0;
    String spatial_resolution "0.25 degree";
    String standard_name_vocabulary "CF Standard Name Table v32";
    String summary 
"Sea surface temperature (SST) provides a measure of the surface ocean conditions, however no information about the subsurface ocean thermal structure (approximately the upper 50 m of the ocean) can be derived from SST alone. For instance, it is known that the oceanic skin temperature erodes when the sea surface is affected by strong winds, creating a well-mixed layer that can reach depths of several tens of meters. Moreover, warm ocean features, mainly anticyclonic rings and eddies, are characterized by a deepening of the isotherms towards their centers with a markedly different temperature and salinity structure than the surrounding waters. Several studies have shown that observations of sea surface height (SSH) are strongly correlated with the thermal structure of the upper ocean (e.g. Goni et al. 1996; Gilson et al. 1998; Mayer et al. 2001; Willis et al. 2004). Based in this virtually ubiquitous relationship, we developed a methodology to estimate fields of isotherm depth from the SHA fields derived from satellite observations.
 The Tropical Cyclone Heat Potential (TCHP), is defined as a measure of the integrated vertical temperature from the sea surface to the depth of the 26°C isotherm. This parameter is computed globally from the altimeter-derived vertical temperature profiles estimates in the upper ocean (Shay et al., 2000). Different methods have been developed to calculate this vertical thermal structure of the upper ocean.
 The Tropical Cyclone Heat Potential (TCHP) is made freely available by the Atlantic Oceanographic and Meteorological Laboratory (www.aoml.noaa.gov/phod/cyclone) and has been funded by the NASA and NOAA at different stages of the project.  The sea surface height and temperature products incorporated in the TCHP are supplied by CMEMS and Remote Sensing, USA (www.remss.com/tmi/) respectively.
 For technical questions, please contact Joaquin Trinanes (joaquin.trinanes@noaa.gov). For scientific questions, contact Gustavo Goni (gustavo.goni@noaa.gov).";
    Float64 temporal_extent 86400.0;
    String temporal_extent_unit "seconds";
    String time_coverage_end "2018-02-23T12:00:00Z";
    String time_coverage_start "2015-08-09T12:00:00Z";
    String title "TCHP_D26 Fields, 0.25°, 2015-present";
    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://upwell.pfeg.noaa.gov/erddap/griddap/datasetID.fileType{?query}
For example,
https://upwell.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 1.82
Disclaimers | Privacy Policy | Contact