NOAA ERDDAP
Easier access to scientific data
   
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > griddap > Make A Graph ?

Dataset Title:  Great Lakes Bathymetry - NOAA Coastal Relief (3 arc sec) Subscribe RSS
Institution:  ???   (Dataset ID: GLOS_BATH)
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.385856e+9, 1.385856e+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";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 41.0, 50.0;
    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 -93.0, -75.0;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  topo {
    Float32 _FillValue -1.0e+10;
    String ioos_category "Bathymetry";
    String long_name "Topography";
    String units "meters";
  }
  NC_GLOBAL {
    String _CoordSysBuilder "ucar.nc2.dataset.conv.CF1Convention";
    String cdm_data_type "Grid";
    String Conventions "CF-1.6, COARDS, Unidata Dataset Discovery v1.0";
    Float64 Easternmost_Easting -75.0;
    Float64 geospatial_lat_max 50.0;
    Float64 geospatial_lat_min 41.0;
    Float64 geospatial_lat_resolution 8.333333333333334e-4;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -75.0;
    Float64 geospatial_lon_min -93.0;
    Float64 geospatial_lon_resolution 8.333333333333334e-4;
    String geospatial_lon_units "degrees_east";
    String history 
"Wed Oct  1 14:40:17 2014: ncatted -O -a _CoordinateAxisType,time,c,c,Time test.nc
Wed Oct  1 14:37:07 2014: ncatted -O -a _CoordinateAxes,topo,m,c,Time Lat Lon test.nc
2018-07-22T06:54:10Z (local files)
2018-07-22T06:54:10Z http://erddap.axiomdatascience.com/griddap/GLOS_BATH.das";
    String infoUrl "???";
    String institution "???";
    String keywords "arc, bathymetry, coastal, great, great lakes, lakes, noaa, relief, sec, topography";
    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 Metadata_Conventions "CF-1.6, COARDS, Unidata Dataset Discovery v1.0";
    String metadata_link "https://www.ngdc.noaa.gov/nmmrview/metadata.jsp?id=gov.noaa.ngdc.mgg.dem:greatlakes_bathymetry&view=html";
    String naming_authority "GLOS";
    Float64 Northernmost_Northing 50.0;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 41.0;
    String standard_name_vocabulary "http://www.cgd.ucar.edu/cms/eaton/cf-metadata/standard_name.html";
    String summary "Bathymetry of Lakes Michigan, Erie, Saint Clair, Ontario and Huron has been compiled as a component of a NOAA project to rescue Great Lakes lake floor geological and geophysical data and make it more accessible. Lake Superior bathymetry partially completed. The present contours and grids have been partially derived and completely compiled here at NOAA's National Geophysical Data Center (NGDC) using a variety of sources of data including the NOS Hydrographic data base and the Canadian Hydrographic Service (CHS) smooth sheets. This project is a cooperative effort between investigators at the NGDC, the NOAA Great Lakes Environmental Research Laboratory and the Canadian Hydrographic Service. Bathymetric data used for this project have been collected from the Great Lakes in support of nautical charting for at least 150 years by the US Army Corp. of Engineers (before 1970), the NOAA National Ocean Service (after 1970), and the CHS.";
    String time_coverage_end "2013-12-01T00:00:00Z";
    String time_coverage_start "2013-12-01T00:00:00Z";
    String title "Great Lakes Bathymetry - NOAA Coastal Relief (3 arc sec)";
    Float64 Westernmost_Easting -93.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 1.82_axiom-r1
Disclaimers | Privacy Policy | Contact