Hakai ERDDAP
Easier access to scientific data
?    
Brought to you by Hakai

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Pruth Bay Oceanographic Mooring on Calvert Island Provisional Subscribe RSS
Institution:  Hakai Institute   (Dataset ID: HakaiPruthMooringProvisional)
Range: longitude = -128.08537 to -128.08537°E, latitude = 51.6521 to 51.6521°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-1+1
 
Constraints ? Optional
Constraint #1 ?
Optional
Constraint #2 ?
       
       
       
       
       
 
Server-side Functions ?
 distinct() ?
? ("Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.")
 
Graph Settings
Marker Type:   Size: 
Color: 
Color Bar:   Continuity:   Scale: 
   Minimum:   Maximum:   N Sections: 
Draw land mask: 
Y Axis Minimum:   Maximum:   
 
(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 {
  station {
    String actual_range 
"Pruth
Pruth";
    String cf_role "timeseries_id";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 51.6521, 51.6521;
    String axis "Y";
    String description "Fixed latitude of the site";
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -128.0853667, -128.0853667;
    String axis "X";
    String description "Fixed longitude of the site";
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    String cell_methods "time: point (interval: 5.0 minutes comment: time correspond to the end of the interval)";
    String cf_role "profile_id";
    String ioos_category "Time";
    String long_name "Measurement Time";
    String source_name "measurementTime";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    String axis "Z";
    Float64 colorBarMaximum 70.0;
    Float64 colorBarMinimum -1.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  watertemp {
    String ancillary_data "watertemp_qc watertemp_uql";
    String long_name "Average Water Temperature";
    String standard_name "sea_water_temperature";
    String units "degree_Celsius";
  }
  watertemp_qc {
    String ioos_category "Quality";
    String long_name "Watertemp Qc";
  }
  watertemp_uql {
    Int32 actual_range 9, 9;
    Float64 colorBarMaximum 10.0;
    Float64 colorBarMinimum 0.0;
    String flag_meaning "PASS NOT_EVALUATED SUSPECT FAIL MISSING";
    Byte flag_values 1, 2, 3, 4, 9;
    String ioos_category "Quality";
    String long_name "Water Temperature UNESCO Q Level";
    Int32 missing_value 2;
    String standard_name "aggregate_quality_flag";
    String units "1";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "TimeSeriesProfile";
    String cdm_profile_variables "time";
    String cdm_timeseries_variables "station,latitude,longitude,depth";
    String contributor_name "Jessy Barrette";
    String contributor_role "custodian";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String date_created "2017-12-04";
    Float64 Easternmost_Easting -128.0853667;
    String featureType "TimeSeriesProfile";
    Float64 geospatial_lat_max 51.6521;
    Float64 geospatial_lat_min 51.6521;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -128.0853667;
    Float64 geospatial_lon_min -128.0853667;
    String geospatial_lon_units "degrees_east";
    String geospatial_vertical_max "60.0";
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-04-26T02:26:37Z (source database)
2024-04-26T02:26:37Z https://catalogue.hakai.org/tabledap/HakaiPruthMooringProvisional.das";
    String infoUrl "https://www.hakai.org";
    String institution "Hakai Institute";
    String instrument "Tidbits v2";
    String keywords "Calvert Island, low-cost, mooring, Provisional Dataset, pruth, seaSurfaceTemperature, subSurfaceTemperature, temperature";
    String license "Creative Commons Attribution 4.0 International licence (CC-BY 4.0)";
    Float64 Northernmost_Northing 51.6521;
    String platform "mooring";
    String platform_vocabulary "https://vocab.nerc.ac.uk/collection/L06/current/";
    String sourceUrl "(source database)";
    Float64 Southernmost_Northing 51.6521;
    String standard_name_vocabulary "CF Standard Name Table v79";
    String subsetVariables "station,latitude,longitude,watertemp_uql";
    String summary "The Pruth Bay mooring is a surface mooring deployed in a shallow coastal environment near the Hakai Institute Calvert Island field station. The mooring is a test platform were low-cost oceanographic instrumentation is deployed at different depths to record sea water temperatures at an accuracy of 0.2 degrees Celsius. The temperature sensors are attached to an auxiliary line suspended from the surface buoy and along the main anchor line. Instruments are distributed tighter near the surface to better capture the higher vertical variability near the surface. This dataset present the provisional dataset which has been automatically QCed and flagged.";
    String title "Pruth Bay Oceanographic Mooring on Calvert Island Provisional";
    Float64 Westernmost_Easting -128.0853667;
  }
}

 

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