Easier access to scientific data
log in    
Brought to you by NOAA NMFS SWFSC ERD    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  Hake Survey ADCP (1998) Subscribe RSS
Institution:  OSU   (Dataset ID: nwioosAdcp1998)
Range: longitude = -126.3846 to -121.9212°E, latitude = 36.5353 to 45.8057°N, depth = 22.0 to 406.0m
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form
Graph Type:  ?
X Axis: 
Y Axis: 
Constraints ? Optional
Constraint #1 ?
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 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.)
Then set the File Type: (File Type information)
or view the URL:
(Documentation / Bypass this form ? )
    Click on the map to specify a new center point. ?
[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 {
  year {
    Int32 actual_range 98, 98;
    String Description "A Date and time string, 2 digit year, 19XX";
    String ioos_category "Time";
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -126.38459777832031, -121.92120361328125;
    String axis "X";
    Float64 colorBarMaximum -115.0;
    Float64 colorBarMinimum -135.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 36.535301208496094, 45.80569839477539;
    String axis "Y";
    Float64 colorBarMaximum 55.0;
    Float64 colorBarMinimum 30.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 22, 406;
    String axis "Z";
    Float64 colorBarMaximum 500.0;
    Float64 colorBarMinimum 0.0;
    String Description "The center of the depth bin.  Depth bins are 8m wide.  The shallowest depth bin center is 22m.";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  yearday {
    Float64 actual_range 188.99070739746094, 208.5124969482422;
    Float64 colorBarMaximum 250.0;
    Float64 colorBarMinimum 150.0;
    String Description "A Date and time string, i.e. 1 January 1200 = 1.5";
    String ioos_category "Time";
    String standard_name "time";
    String Timezone "GMT";
  eastv {
    Float64 actual_range -1.069, 0.627;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String ioos_category "Currents";
    String long_name "Eastward Sea Water Velocity";
    String standard_name "eastward_sea_water_velocity";
    String units "m s-1";
  northv {
    Float64 actual_range -1.065, 0.712;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String ioos_category "Currents";
    String long_name "Northward Sea Water Velocity";
    String standard_name "northward_sea_water_velocity";
    String units "m s-1";
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting -121.92120361328125;
    Float64 geospatial_lat_max 45.80569839477539;
    Float64 geospatial_lat_min 36.535301208496094;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max -121.92120361328125;
    Float64 geospatial_lon_min -126.38459777832031;
    String geospatial_lon_units "degrees_east";
    Float64 geospatial_vertical_max 406.0;
    Float64 geospatial_vertical_min 22.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
    String infoUrl "";
    String institution "OSU";
    String keywords "adcp, atmosphere, circulation, currents, depth, Earth Science > Oceans > Ocean Circulation > Ocean Currents, eastward, eastward_sea_water_velocity, hake, height, northward, northward_sea_water_velocity, ocean, oceans, osu, sea, seawater, station, survey, time, velocity, water, year";
    String keywords_vocabulary "GCMD Science Keywords";
    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.";
    Float64 Northernmost_Northing 45.80569839477539;
    String sourceUrl "";
    Float64 Southernmost_Northing 36.535301208496094;
    String standard_name_vocabulary "CF Standard Name Table v55";
    String subsetVariables "year, longitude, latitude, yearday";
    String summary 
"Shipboard acoustic Doppler current profiler data collected during the
Integrated Acoustic and Trawl Surveys of Pacific Hake.
Processing by:  Stephen Pierce, Oregon State University
(P. M. Kosro also performed some processing steps in the 1998 case)
Date:  16 August 2006
Data quality: Good in general
Missing or poor-quality data have been omitted.

This dataset has a simple simple version of observed velocities, useful
for most purposes.  The complete data sets with all configuration and
processing details and diagnostic data (e.g. error velocity, AGC,
spectral width) are available from the NODC Joint Archive for Shipboard
ADCP, or by request from S. Pierce.

Processing steps included:  editing of the data using various
diagnostics, calibration of the phase and amplitude errors of the
ADCP/navigation/gyrocompass system by covariability analysis between
currents and ship velocity, reference layer velocity smoothing, and
final production of earth-referenced velocities.  For more details
regarding methods, see:  Pierce et al. (2000), DSR II 47, 811-829.

Contact: Dr. Stephen D. Pierce,";
    String title "Hake Survey ADCP (1998)";
    Float64 Westernmost_Easting -126.38459777832031;


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{?query}
For example,,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.02
Disclaimers | Privacy Policy | Contact