NOAA ERDDAP
Easier access to scientific data
| ?    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  RV Sikuliaq : Anemometer RMY Bridge Port : Relative Wind Direction : 600 s
binned
Subscribe RSS
Institution:  UAF   (Dataset ID: relativewinddirection_degrees_anemom000001_600sbin)
Information:  Summary ? | License ? | 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() ?
? ("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: 
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 ? )
   
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";
    String axis "T";
    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";
  }
  spot_time {
    String ioos_category "Time";
    String long_name "Spot Time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  spot_value {
    String ioos_category "Statistics";
    String long_name "Relative Wind Direction Spot_Value";
    String short_name "relative_wind_direction_spot_value";
    String special_notes "Binning type: circular";
    String standard_name "x_spot_value";
    String units "degrees";
  }
  mean {
    String ioos_category "Statistics";
    String long_name "Relative Wind Direction Mean";
    String short_name "relative_wind_direction_mean";
    String special_notes "Binning type: circular";
    String standard_name "x_mean";
    String units "degrees";
  }
  stddev {
    String ioos_category "Statistics";
    String long_name "Relative Wind Direction Stddev";
    String short_name "relative_wind_direction_stddev";
    String special_notes "Binning type: circular";
    String standard_name "x_stddev";
    String units "degrees";
  }
  minimum {
    String ioos_category "Statistics";
    String long_name "Relative Wind Direction Minimum";
    String short_name "relative_wind_direction_minimum";
    String special_notes "Binning type: circular";
    String standard_name "x_minimum";
    String units "degrees";
  }
  maximum {
    String ioos_category "Statistics";
    String long_name "Relative Wind Direction Maximum";
    String short_name "relative_wind_direction_maximum";
    String special_notes "Binning type: circular";
    String standard_name "x_maximum";
    String units "degrees";
  }
  median {
    String ioos_category "Statistics";
    String long_name "Relative Wind Direction Median";
    String short_name "relative_wind_direction_median";
    String special_notes "Binning type: circular";
    String standard_name "x_median";
    String units "degrees";
  }
  num_values {
    String ioos_category "Statistics";
    String long_name "Relative Wind Direction Num_Values";
    String short_name "relative_wind_direction_num_values";
    String special_notes "Binning type: circular";
    String standard_name "x_num_values";
    String units "unitless";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String contributor_name "RV Sikuliaq";
    String contributor_role "Data collector";
    String creator_name "CORIOLIX, RDESC, RCRV Project, Oregon State University";
    String creator_url "http://ceoas.oregonstate.edu";
    String history 
"2026-05-02T14:10:15Z (source database)
2026-05-02T14:10:15Z https://coriolix.sikuliaq.alaska.edu/tabledap/relativewinddirection_degrees_anemom000001_600sbin.das";
    String infoUrl "https://www.uaf.edu/cfos/sikuliaq/";
    String institution "UAF";
    String keywords "atmosphere, data, observations, ocean";
    String license 
"The data may be used and redistributed for free but is not intended
for legal use, since it may contain inaccuracies. Neither the data
Contributor, ERD, NOAA, nor the United States Government, nor any
of their employees or contractors, makes any warranty, express or
implied, including warranties of merchantability and fitness for a
particular purpose, or assumes any legal liability for the accuracy,
completeness, or usefulness, of this information.";
    String sourceUrl "(source database)";
    String standard_name_vocabulary "CF standard name";
    String summary 
"Relative Wind Direction 600 s binned time series data.
Vessel: RV Sikuliaq. Sensor Model: R.M. Young 85000 ultrasonic anemometer
Sensor S/N: unknown
Sensor Location Onboard: Port Side
Sensor Description: Bridge port anemometer. Model 85004 (heated). Component of the Ship's navigation instrumentation. Note: This sensor is not part of the pool of science maintained instrumentation.
Parameter Description: Calculated meteorological relative wind is defined as the wind vector measured relative to the ship. The relative wind direction is the direction relative to the bow of the ship from which the wind is blowing with the relative wind speed. Direction conventions are 0 deg for wind from the bow, 90 deg for wind from the starboard side, 180 deg for wind from the stern, and 270 deg for wind from the port side.";
    String title "RV Sikuliaq : Anemometer RMY Bridge Port : Relative Wind Direction : 600 s binned";
  }
}

 

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