UBC and MEOPAR Logos SalishSeaCast ERDDAP
Public access to the SalishSeaCast model products
Brought to you by SalishSeaCast UBC EOAS MEOPAR NOAA    

ERDDAP > griddap > Data Access Form ?

Dataset Title:  Salish Sea NEMO Model Grid, Geo-location and Bathymetry, v17-02 Subscribe RSS
Institution:  UBC EOAS   (Dataset ID: ubcSSnBathymetryV17-02)
Information:  Summary ? | License ? | Metadata | Background (external link) | Make a graph
Dimensions ? Start ? Stride ? Stop ?  Size ?    Spacing ?
 gridY (Y, count) ?      898    1.0 (even)
  < slider >
 gridX (X, count) ?      398    1.0 (even)
  < slider >
Grid Variables (which always also download all of the dimension variables)
 bathymetry (Sea Floor Depth, metres) ?
 latitude (degrees_north) ?
 longitude (degrees_east) ?

File type: (more info)

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


The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  gridY {
    Int32 actual_range 0, 897;
    String coverage_content_type "modelResult";
    String ioos_category "location";
    String long_name "Y";
    String units "count";
  gridX {
    Int16 actual_range 0, 397;
    String coverage_content_type "modelResult";
    String ioos_category "location";
    String long_name "X";
    String units "count";
  bathymetry {
    Int32 _ChunkSizes 898, 398;
    Float64 _FillValue 0.0;
    Float64 colorBarMaximum 450.0;
    Float64 colorBarMinimum 0.0;
    String colorBarPalette "OceanDepth";
    String coverage_content_type "modelResult";
    String ioos_category "bathymetry";
    Float64 least_significant_digit 0.1;
    String long_name "Sea Floor Depth";
    String standard_name "sea_floor_depth";
    String units "metres";
  latitude {
    Int32 _ChunkSizes 898, 398;
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  longitude {
    Int32 _ChunkSizes 898, 398;
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
    String acknowledgement 
"MEOPAR, ONC, Compute Canada, CHS, NOAA, USGS

This product has been produced by the University of British Columbia based on Canadian Hydrographic Service charts
and/or data, pursuant to CHS Direct User Licence No. 2016-0504-1260-U

The incorporation of data sourced from CHS in this product shall not be construed as constituting an endorsement of
CHS of this product.

This product does not meet the requirements of Charts and Nautical Publications Regulations,
1995 under the Canadian Shipping Act, 2001. Official charts and publications, corrected and up-to-data,
must be used to meet the requirements of those regulations.";
    String cdm_data_type "Grid";
    String Conventions "CF-1.6, COARDS, ACDD-1.3";
    String creator_email "sallen@eoas.ubc.ca";
    String creator_name "Salish Sea MEOPAR Project Contributors";
    String creator_url "https://salishsea-meopar-docs.readthedocs.io/";
    String drawLandMask "over";
    String history 
"[2017-09-30 12:34:48] Created netCDF4 zlib=True dataset.
2018-06-18T19:11:59Z (local files)
2018-06-18T19:11:59Z https://salishsea.eos.ubc.ca/erddap/griddap/ubcSSnBathymetryV17-02.das";
    String infoUrl "https://salishsea-meopar-docs.readthedocs.io/en/latest/results_server/index.html#salish-sea-model-results";
    String institution "UBC EOAS";
    String institution_fullname "Earth, Ocean & Atmospheric Sciences, University of British Columbia";
    String keywords "bathymetry, depth, Earth Science > Oceans > Bathymetry/Seafloor Topography > Bathymetry, nav_lat, nav_lon, ocean, oceans, Salish Sea, sea floor, sea_floor_depth, seafloor, topography";
    String keywords_vocabulary "GCMD Science Keywords";
    String license 
"The Salish Sea MEOPAR NEMO model results are copyright
by the Salish Sea MEOPAR Project Contributors and The University of British Columbia.

They are licensed under the Apache License, Version 2.0. https://www.apache.org/licenses/LICENSE-2.0";
    String project "Salish Sea MEOPAR NEMO Model";
    String references "https://bitbucket.org/salishsea/nemo-forcing/raw/tip/grid/bathymetry_201702.nc";
    String source "https://bitbucket.org/salishsea/tools/src/tip/ProcessNewRiverBathymetry.ipynb";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary 
"Salish Sea NEMO Model Grid, Geo-location and Bathymetry, v17-02

Longitude, latitude, and bathymetry of the Salish Sea NEMO model grid.
The bathymetry values are those calculated by NEMO from the input bathymetry file.
NEMO modifies the input bathymetry to remove isolated holes, and too-small partial steps;
See the ubcSSn2DMeshMaskV17-02 dataset for the complete details of the calculation grid.
The model grid includes the Juan de Fuca Strait, the Strait of Georgia, Puget Sound,
and Johnstone Strait on the coasts of Washington State and British Columbia.

v1: longitude, latitude and bathymetry variables
v16-07: same variables,
        bathymetry uniformly deepened by 1 grid level,
        smoothed at Juan de Fuca & Johnstone Strait open boundaries,
        Fraser River lengthened,
        bathymetry deepened near mouth of Fraser River
v17-02: same variables,
        Bathymetry composed from 3 datasets:
        * USGS Digital elevation model (DEM) of Cascadia, latitude 39N-53N, longitude 116W-133W, Open-File Report 99-369, https://pubs.er.usgs.gov/publication/ofr99369
        * NOAA British Columbia, 3 arc-second MSL DEM, https://www.ngdc.noaa.gov/dem/squareCellGrid/download/4956
        * CHS Multibeam data and all point cloud data for the Salish Sea.
        Smoothed at Juan de Fuca & Johnstone Strait open boundaries.
        Proxy channel for Fraser River upstream of confluence with the Pitt River.
        Adjustments by Michael Dunphy to make increase resolution of Fraser River channels downstream of confluence with the Pitt River.";
    String title "Salish Sea NEMO Model Grid, Geo-location and Bathymetry, v17-02";


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
For example,
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