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:  VFPA, Vancouver Harbour, 2nd Narrows Rail Bridge, Current, 2sec, v1 Subscribe RSS
Institution:  UCB EOAS & DFO IOS   (Dataset ID: ubcVFPA2ndNarrowsCurrent2sV1)
Range: longitude = -123.02472 to -123.02472°E, latitude = 49.293888 to 49.293888°N, time = 2017-11-21T00:00:00Z to 2019-05-23T23:58:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1 +1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? (" ")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
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 ? )
    Click on the map to specify a new center point. ?
Zoom: 
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 {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.5112224e+9, 1.55865588e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String cf_role "timeseries_id";
    String comment "time values are UTC";
    String ioos_category "Time";
    String long_name "Time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  speed {
    Float64 _FillValue -999.9000000000001;
    Float64 actual_range 0.0, 25.0;
    Float64 colorBarMaximum 5.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Currents";
    String long_name "Current Speed";
    String name "speed";
    String standard_name "sea_water_speed";
    String units "kts";
  }
  direction {
    Float64 _FillValue -999.9000000000001;
    Float64 actual_range 39.0, 319.0;
    Float64 colorBarMaximum 360.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Currents";
    String long_name "Current To Direction";
    String name "direction";
    String standard_name "direction_of_sea_water_velocity";
    String units "degree";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 _FillValue NaN;
    Float64 actual_range -123.0247222, -123.0247222;
    String axis "X";
    String ioos_category "Location";
    String long_name "Longitude";
    String name "longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 _FillValue NaN;
    Float64 actual_range 49.2938889, 49.2938889;
    String axis "Y";
    String ioos_category "Location";
    String long_name "Latitude";
    String name "latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
 }
  NC_GLOBAL {
    String acknowledgement "MEOPAR, DFO IOS, VFPA";
    String cdm_data_type "TimeSeries";
    String cdm_timeseries_variables "speed, direction";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String creator_email "sallen@eos.ubc.ca";
    String creator_name "Salish Sea MEOPAR Project Contributors";
    String creator_url "https://salishsea-meopar-docs.readthedocs.io/";
    String drawLandMask "over";
    Float64 Easternmost_Easting -123.0247222;
    String featureType "TimeSeries";
    Float64 geospatial_lat_max 49.2938889;
    Float64 geospatial_lat_min 49.2938889;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -123.0247222;
    Float64 geospatial_lon_min -123.0247222;
    String geospatial_lon_units "degrees_east";
    String history 
"2019-05-24T00:45:50Z (local files)
2019-05-24T00:45:50Z https://salishsea.eos.ubc.ca/tabledap/ubcVFPA2ndNarrowsCurrent2sV1.das";
    String infoUrl "https://salishsea-meopar-docs.readthedocs.io/en/latest/results_server/index.html#salish-sea-model-results";
    String institution "UCB EOAS & DFO IOS";
    String institution_fullname "Earth, Ocean & Atmospheric Sciences, University of British Columbia; and Fisheries and Oceans Canada, Institute of Ocean Sciences";
    String keywords "2nd Narrows Rail Bridge, ADCP, circulation, current, currents, DFO IOS, direction, Earth Science > Oceans > Ocean Circulation > Ocean Currents, latitude, longitude, ocean, oceans, sea, sea_water_direction, sea_water_speed, seawater, speed, time, UBC EOAS, Vancouver Fraser Port Authority, Vancouver Harbour, velocity";
    String keywords_vocabulary "GCMD Science Keywords";
    String license 
"The Salish Sea MEOPAR observation datasets are copyright 2013-2016
by the Salish Sea MEOPAR Project Contributors, The University of British Columbia, and Ocean Networks Canada.

They are licensed under the Apache License, Version 2.0. https://www.apache.org/licenses/LICENSE-2.0

Raw instrument data on which this dataset is based were provided by the Vancouver Fraser Port Authority.";
    Float64 Northernmost_Northing 49.2938889;
    String source "Hourly AIS email feed created by DFO IOS.";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 49.2938889;
    String standard_name_vocabulary "CF Standard Name Table v29";
    String summary 
"VFPA, Vancouver Harbour, 2nd Narrows Rail Bridge, Current, 2sec, v1

Current data from Vancouver Fraser Port Authority (VFPA) horizontal acoustic doppler current profiler (HADCP) instrument located at the 2nd Narrows Rail Bridge. The time values are UTC.

v1: current speed and direction variables";
    String testOutOfDate "now-2days";
    String time_coverage_end "2019-05-23T23:58:00Z";
    String time_coverage_start "2017-11-21T00:00:00Z";
    String title "VFPA, Vancouver Harbour, 2nd Narrows Rail Bridge, Current, 2sec, v1";
    Float64 Westernmost_Easting -123.0247222;
  }
}

 

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
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.


 
ERDDAP, Version 1.82
Disclaimers | Privacy Policy | Contact