Data Access Form

Dataset Title:	Files, FVCOM, Vancouver Harbour and Fraser River, Barotropic, V2
Institution:	UBC EOAS & DFO IOS (Dataset ID: ubcSSFVCOM-VHFRLowFilesV2)
Information:	Summary \| License \| Metadata \| Background \| Subset \| Files \| Make a graph

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Show advanced settings : Privacy / Content settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Internet Explorer: "Tools : Internet Options : Security : Internet : Custom level :
          Sripting/ Active Scripting : Enable : OK : OK"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Variable

Optional
Constraint #1

Optional
Constraint #2

Minimum

or a List of Values

Maximum

url

name (File Name)

lastModified (UTC)

2018-01-18T22:49:58Z

2019-01-17T17:41:07Z

size (bytes)

4096.0

7.83237696E8

fileType

Server-side Functions

distinct()

(" ")

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 {
 s {
  url {
    String ioos_category "Identifier";
    String long_name "URL";
  }
  name {
    String ioos_category "Identifier";
    String long_name "File Name";
  }
  lastModified {
    String ioos_category "Time";
    String long_name "Last Modified";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  size {
    String ioos_category "Other";
    String long_name "Size";
    String units "bytes";
  }
  fileType {
    String ioos_category "Identifier";
    String long_name "File Type";
  }
 }
  NC_GLOBAL {
    String acknowledgement 
"Fisheries & Oceans Canada, 
Ocean Networks Canada (ONC), 
Digital Research Alliance of Canada";
    String cdm_data_type "Grid";
    String creator_email "Michael.Dunphy@dfo-mpo.gc.ca";
    String creator_name "SalishSeaCast Project Contributors";
    String creator_url "https://salishsea-meopar-docs.readthedocs.io/";
    String history 
"2024-04-19T20:42:25Z (local files)
2024-04-19T20:42:25Z https://salishsea.eos.ubc.ca/erddap/tabledap/ubcSSFVCOM-VHFRLowFilesV2.html";
    String infoUrl "https://salishsea.eos.ubc.ca/";
    String institution "UBC EOAS & DFO IOS";
    String institution_fullname 
"Dept of Earth, Ocean & Atmospheric Sciences, University of British Columbia, 
    Fisheries and Oceans Canada, Institute of Ocean Sciences";
    String keywords "file, identifier, lastModified, model results, modified, name, size, time";
    String license 
"The SalishSeaCast model results are copyright
by the SalishSeaCast 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 sourceUrl "(local files)";
    String subsetVariables "fileType";
    String summary 
"Files, FVCOM, Vancouver Harbour and Fraser River, Barotropic, V2

Barotropic sea surface height, and currents from VHFR low resolution V2 configuration
FVCOM model runs.
The values are calculated for an unstructured model grid that covers Vancouver Harbour,
English Bay, and the lower Fraser River on the coast of British Columbia.
The time values are UTC.

The Vancouver Harbour and Fraser River (VHFR) FVCOM model grid and configurations
were developed by Michael Dunphy, et al at the Institute of Ocean Sciences.
The VHFR FVCOM model uses currents, sea surface height, temperature, and salinity
from the SalishSeaCast NEMO model as boundary conditions, and the same ECCC HRDPS
GEM 2.5km resolution winds that are used to force the NEMO model.

V2: FVCOM-4.1; NEMO-3.6; ubcSSnBathymetryV17-02 bathymetry.";
    String testOutOfDate "now+24hours";
    String title "Files, FVCOM, Vancouver Harbour and Fraser River, Barotropic, V2";
  }
}

Using tabledap to Request Data and Graphs from Tabular Datasets

tabledap lets you request a data subset, a graph, or a map from a tabular dataset (for example, buoy data), via a specially formed URL. tabledap uses the OPeNDAP (external link)

Data Access Protocol (DAP) (external link)

and its selection 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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make 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.

Tabledap request URLs must be in the form
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/datasetID.fileType{?query}
For example,
https://coastwatch.pfeg.noaa.gov/erddap/tabledap/pmelTaoDySst.htmlTable?longitude,latitude,time,station,wmo_platform_code,T_25&time>=2015-05-23T12:00:00Z&time<=2015-05-31T12:00:00Z
Thus, the query is often a comma-separated list of desired variable names, followed by a collection of constraints (e.g., variable<value), each preceded by '&' (which is interpreted as "AND").

For details, see the tabledap Documentation.