ERDDAP > griddap > Data Access Form

Dataset Title:	Great Lakes Bathymetry - NOAA Coastal Relief (3 arc sec)
Institution:	???   (Dataset ID: GLOS_BATH)
Information:	Summary | License | FGDC | ISO 19115 | Metadata | Background | Make a graph

 

Dimensions	Start	Stride	Stop	Size	Spacing
time (UTC)				1	(just one value)
latitude (degrees_north)				10801	-8.333333E-4 (even)
longitude (degrees_east)				21601	8.333333E-4 (even)

Grid Variables (which always also download all of the dimension variables)

topo (Topography, meters)

File type: (more information) .asc - View OPeNDAP-style ISO-8859-1 comma-separated text. .csv - Download a ISO-8859-1 comma-separated text table (line 1: names; line 2: units; ISO 8601 times). .csvp - Download a ISO-8859-1 .csv file with line 1: name (units). Times are ISO 8601 strings. .csv0 - Download a ISO-8859-1 .csv file without column names or units. Times are ISO 8601 strings. .das - View the dataset's metadata via an ISO-8859-1 OPeNDAP Dataset Attribute Structure (DAS). .dds - View the dataset's structure via an ISO-8859-1 OPeNDAP Dataset Descriptor Structure (DDS). .dods - OPeNDAP clients use this to download the data in the DODS binary format. .esriAscii - Download an ISO-8859-1 ESRI ASCII file (latitude longitude data only; longitude must be all below or all above 180). .fgdc - View the dataset's UTF-8 FGDC .xml metadata. .graph - View a Make A Graph web page. .help - View a web page with a description of griddap. .html - View an OPeNDAP-style HTML Data Access Form. .htmlTable - View a UTF-8 .html web page with the data in a table. Times are ISO 8601 strings. .iso19115 - View the dataset's ISO 19115-2/19139 UTF-8 .xml metadata. .itx - Download an ISO-8859-1 Igor Text File. Each axis variable and each data variable becomes a wave. .json - View a table-like UTF-8 JSON file (missing value = 'null'; times are ISO 8601 strings). .jsonlCSV1 - View a UTF-8 JSON Lines CSV file with column names on line 1 (mv = 'null'; times are ISO 8601 strings). .jsonlCSV - View a UTF-8 JSON Lines CSV file without column names (mv = 'null'; times are ISO 8601 strings). .jsonlKVP - View a UTF-8 JSON Lines file with Key:Value pairs (missing value = 'null'; times are ISO 8601 strings). .mat - Download a MATLAB binary file. .nc - Download a NetCDF-3 binary file with COARDS/CF/ACDD metadata. .ncHeader - View the UTF-8 header (the metadata) for the NetCDF-3 .nc file. .ncml - View the dataset's structure and metadata as a UTF-8 NCML .xml file. .nccsv - Download a NetCDF-3-like 7-bit ASCII NCCSV .csv file with COARDS/CF/ACDD metadata. .nccsvMetadata - View the dataset's metadata as the top half of a 7-bit ASCII NCCSV .csv file. .ncoJson - Download a UTF-8 NCO lvl=2 JSON file with COARDS/CF/ACDD metadata. .odvTxt - Download time,latitude,longitude,otherVariables as an ODV Generic Spreadsheet File (.txt). .timeGaps - View a UTF-8 list of gaps in the time values which are larger than the median gap. .tsv - Download a ISO-8859-1 tab-separated text table (line 1: names; line 2: units; ISO 8601 times). .tsvp - Download a ISO-8859-1 .tsv file with line 1: name (units). Times are ISO 8601 strings. .tsv0 - Download a ISO-8859-1 .tsv file without column names or units. Times are ISO 8601 strings. .wav - Download a .wav audio file. All columns must be numeric and of the same type. .xhtml - View a UTF-8 XHTML (XML) file with the data in a table. Times are ISO 8601 strings. .geotif - View a grayscale GeoTIFF .tif file (for latitude longitude data; longitude must be all below or all above 180). .kml - View a Google Earth .kml file (for latitude, longitude data only). .smallPdf - View a small .pdf image file with a graph or map. .pdf - View a standard, medium-sized .pdf image file with a graph or map. .largePdf - View a large .pdf image file with a graph or map. .smallPng - View a small .png image file with a graph or map. .png - View a standard, medium-sized .png image file with a graph or map. .largePng - View a large .png image file with a graph or map. .transparentPng - View a .png image file (just the data, without axes, landmask, or legend).

(Documentation / Bypass this form)
 
Submit (Please be patient. It may take a while to get the data.)

 

---

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.internal.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
2023-03-31T08:46:45Z (local files)
2023-03-31T08:46:45Z http://erddap.axiomdatascience.com/erddap/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 "https://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 Data Access Protocol (DAP) and its projection constraints.

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.

• (easy) You can get data by using the dataset's Data Access Form. It makes the URL for you.
• (easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
• (not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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