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:  Forecast, Point Atkinson, Sea Surface Height, 10min, v17-02 Subscribe RSS
Institution:  UBC EOAS   (Dataset ID: ubcSSfPointAtkinsonSSH10mV17-02)
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
 
Graph Type:  ?
X Axis:  ?
Y Axis:  ?
Color:  ?
 
Dimensions ?    Start ?    Stop ?
time (UTC) ?
    << - +
    - >>
< slider >
longitude (degrees_east) ?     specify just 1 value →
   
< <
latitude (degrees_north) ?     specify just 1 value →
   
< <
 
Graph Settings
Marker Type:   Size: 
Color: 
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.)
 
Optional:
Then set the File Type: (File Type information)
and
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.5288483e+9, 1.5294741e+9;
    String axis "T";
    String bounds "time_counter_bounds";
    String calendar "gregorian";
    String comment "time values are UTC at the centres 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";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float32 actual_range -123.2495, -123.2495;
    String axis "X";
    String bounds "bounds_lon";
    String colorBarMaximum "-121.0";
    String colorBarMinimum "-127.0";
    String coverage_content_type "modelResult";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float32 actual_range 49.33216, 49.33216;
    String axis "Y";
    String bounds "bounds_lat";
    String colorBarMaximum "52.0";
    String colorBarMinimum "46.0";
    String coverage_content_type "modelResult";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  ssh {
    Int32 _ChunkSizes 1, 1, 1;
    Float32 _FillValue 1.0e+20;
    Float64 colorBarMaximum 4.0;
    Float64 colorBarMinimum -4.0;
    String coverage_content_type "modelResult";
    String ioos_category "sea_level";
    String long_name "sea surface height";
    Float32 missing_value 1.0e+20;
    String standard_name "sea_surface_height_above_geoid";
    String units "m";
  }
  NC_GLOBAL {
    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 "10min interval SSH for tides";
    String drawLandMask "over";
    Float64 Easternmost_Easting -123.2495;
    Float64 geospatial_lat_max 49.33216;
    Float64 geospatial_lat_min 49.33216;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -123.2495;
    Float64 geospatial_lon_min -123.2495;
    String geospatial_lon_units "degrees_east";
    String history 
"2018-06-18T19:10:16Z (local files)
2018-06-18T19:10:16Z https://salishsea.eos.ubc.ca/griddap/ubcSSfPointAtkinsonSSH10mV17-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 "10min, earth, Earth Science > Oceans > Sea Surface Topography > Sea Surface Height, geodetics, geoid, ocean, oceans, sea, sea surface height above geoid, sea_surface_height_above_geoid, sossheig, ssh, surface, tides, time_counter, 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";
    Float64 Northernmost_Northing 49.33216;
    String project "Salish Sea MEOPAR NEMO Model";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 49.33216;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary 
"Forecast, Point Atkinson, Sea Surface Height, 10min, v17-02

Rolling daily forecast of sea surface height values averaged over 10 minute intervals from
Salish Sea NEMO model runs with physics and biology. The values are calculated at the model grid point
closest to the Point Atkinson tide gauge station on the north side of English Bay,
near Vancouver, British Columbia.
The time values are UTC. They are the centres 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 ubcSSnBathymetry2V17-02 dataset.

This dataset is updated daily to move it forward 1 day in time.
It starts at 00:05:00 UTC 5 days prior to the most recently completed forecast run,
and extends to 11:55:00 UTC on the 2nd day after the forecast run date.
So, for example, after completion of the 10-Nov-2017 forecast run,
this dataset included data from 2017-11-05 00:05:00 UTC to 2017-11-12 11:55:00 UTC.

v17-02: NEMO-3.6; ubcSSnBathymetry2V17-02 bathymetry; see infoUrl link for full details.";
    String time_coverage_end "2018-06-20T05:55:00Z";
    String time_coverage_start "2018-06-13T00:05:00Z";
    String timeStamp "2018-Jun-17 19:05:53 GMT";
    String title "Forecast, Point Atkinson, Sea Surface Height, 10min, v17-02";
    String uuid "e1ce7588-1d1a-49c3-92fe-e2a7b60b6cbd";
    Float64 Westernmost_Easting -123.2495;
  }
}

 

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