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

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Files, FVCOM, Vancouver Harbour and Fraser River, Baroclinic, R12 Subscribe RSS
Institution:  UBC EOAS & DFO IOS   (Dataset ID: ubcSSFVCOM-VHFR-BaroclinicR12)
Information:  Summary ? | License ? | Metadata | Background (external link) | Subset | Data Access Form | Files
Graph Type:  ?
X Axis: 
Y Axis: 
-1 +1
Constraints ? Optional
Constraint #1 ?
Constraint #2 ?
Server-side Functions ?
 distinct() ?
? (" ")
Graph Settings
Marker Type:   Size: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Y Axis Minimum:   Maximum:   Ascending: 
(Please be patient. It may take a while to get the data.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    [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 {
 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";
    String acknowledgement "Fisheries & Oceans Canada, MEOPAR, ONC, Compute Canada";
    String cdm_data_type "Grid";
    String creator_email "Michael.Dunphy@dfo-mpo.gc.ca";
    String creator_name "Salish Sea MEOPAR Project Contributors";
    String creator_url "https://salishsea-meopar-docs.readthedocs.io/";
    String history 
"2023-06-06T16:34:15Z (local files)
2023-06-06T16:34:15Z https://salishsea.eos.ubc.ca/tabledap/ubcSSFVCOM-VHFR-BaroclinicR12.das";
    String infoUrl "https://salishsea-meopar-docs.readthedocs.io/en/latest/results_server/index.html#salish-sea-model-results";
    String institution "UBC EOAS & DFO IOS";
    String keywords "file, identifier, lastModified, model results, modified, name, size, time";
    String license 
"The SalishSeaCast 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 sourceUrl "(local files)";
    String subsetVariables "fileType";
    String summary 
"Files, FVCOM, Vancouver Harbour and Fraser River, Baroclinic, R12

Baroclinic sea surface height, currents, temperature, and salinity from
VHFR R12 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 model runs include Fraser River discharge forcing based on
daily average discharges from river gauge at Hope with a 1 day lag.
The river temperature is climatological.
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 Salish Sea NEMO model as boundary conditions, and the same ECCC HRDPS
GEM 2.5km resolution winds that are used to force the NEMO model.

R12: FVCOM-4.1; NEMO-3.6; ubcSSnBathymetryV17-02 bathymetry; see infoUrl link for full details.";
    String title "Files, FVCOM, Vancouver Harbour and Fraser River, Baroclinic, R12";


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.

Tabledap request URLs must be in the form
For example,
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.

ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact