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

ERDDAP > griddap > Make A Graph ?

Dataset Title:  Green, Salish Sea, 3d Near Surface v Velocity Field, 20min, v17-02 Subscribe RSS
Institution:  UBC EOAS   (Dataset ID: ubcSSgNearSurfaceVVelocity20mV17-02)
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
Dimensions ?    Start ?    Stop ?
time (UTC) ?
    << - +
    - >>
< slider >
depth (m) ?     specify just 1 value →
    << -
< <
gridY (count) ?     specify just 1 value →
    << -
< <
gridX (count) ?     specify just 1 value →
    << -
< <
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 ? )
    Time range:    <<    -              
[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 {
    Int32 _ChunkSizes 1;
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5031014e+9, 1.5291066e+9;
    String axis "T";
    String calendar "gregorian";
    String comment "time values are the centre of the intervals over which the calculated model results are averaged";
    String coverage_content_type "modelResult";
    String ioos_category "Time";
    String long_name "Time axis";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  depth {
    Int32 _ChunkSizes 5;
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Float32 actual_range 0.5000003, 4.500071;
    String axis "Z";
    String coverage_content_type "modelResult";
    String ioos_category "Location";
    String long_name "Depth";
    String name "nearsurface_V";
    String positive "down";
    String standard_name "depth";
    String units "m";
  gridY {
    Int16 actual_range 0, 539;
    String coverage_content_type "modelResult";
    String ioos_category "location";
    String long_name "Y";
    String units "count";
  gridX {
    Int16 actual_range 0, 354;
    String coverage_content_type "modelResult";
    String ioos_category "location";
    String long_name "X";
    String units "count";
  vVelocity {
    Int32 _ChunkSizes 1, 5, 540, 355;
    Float32 _FillValue 1.0e+20;
    Float64 colorBarMaximum 8.0;
    Float64 colorBarMinimum -8.0;
    String coverage_content_type "modelResult";
    String ioos_category "currents";
    String long_name "ocean current along y-axis";
    Float32 missing_value 1.0e+20;
    String standard_name "sea_water_y_velocity";
    String units "m/s";
    String acknowledgement "MEOPAR, ONC, Compute Canada";
    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 description "20min near surface V velocity";
    String drawLandMask "over";
    String history 
"2018-06-18T19:14:25Z (local files)
2018-06-18T19:14:25Z https://salishsea.eos.ubc.ca/griddap/ubcSSgNearSurfaceVVelocity20mV17-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 "circulation, current, currents, depthv, Earth Science > Oceans > Ocean Circulation > Ocean Currents, ocean, oceans, sea, sea_water_y_velocity, seawater, time_counter, v grid, v velocity component, velocity along y-axis, vomecrty";
    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 sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary 
"Green, Salish Sea, 3d Near Surface v Velocity Field, 20min, v17-02

Variable values at the 3d meridional (v) component velocity grid points
of the surface-most 5 layers, averaged over 20 minute intervals from Salish Sea NEMO model physics-only runs.
The values are for a sub-domain of the calculated model grid. The sub-domain covers only
the Juan de Fuca Strait, and the Strait of Georgia on the coasts of Washington State and British Columbia.
The time values are the centre of the intervals over which the calculated model results are averaged.
Geo-location and depth data for the Salish Sea NEMO model grid are available in the ubcSSnBathymetryV17-02 dataset.

v17-02: vVelocity variable; NEMO-3.6; ubcSSnBathymetryV17-02 bathymetry; see infoUrl link for full details.";
    String testOutOfDate "now-16hours";
    String time_coverage_end "2018-06-15T23:50:00Z";
    String time_coverage_start "2017-08-19T00:10:00Z";
    String timeStamp "2018-Jun-15 19:02:14 GMT";
    String title "Green, Salish Sea, 3d Near Surface v Velocity Field, 20min, v17-02";
    String uuid "7ebbd94f-69dd-440e-a4ef-c710d80c4b0e";


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