Make A Graph

Dataset Title:	NEMO-SS Velocity Profiler - Upward facing Acoustic Doppler Current Profiler (ADCP) - 60-minute average (DEVELOPMENTAL)
Institution:	NWEM Group (Dataset ID: nemo-ss_adcp)
Information:	Summary \| License \| Metadata \| Background \| Data Access Form \| Files

To work correctly, this web page requires that JavaScript be enabled in your browser. Please:
1) Enable JavaScript in your browser:
      • Chrome: "Settings : Advanced : Privacy and security : Site Settings : JavaScript"
      • Firefox: (it should be always on!)"
      • Opera: "Settings : Websites : JavaScript"
      • Safari: "Safari : Preferences : Security : Enable JavaScript"
2) Reload this web page.

Graph Type:
X Axis:
Y Axis:
Color:

Dimensions

Start

Stop

time (UTC)

depth (m)

Graph Settings
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:

Web page authors can embed a graph of the latest data in a web page using HTML <img> tags.
Anyone can use ERDDAPs Slide Sorter to build a personal web page that displays graphs with the latest data (or other images or HTML content), each in its own, draggable slide.

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.4324148e+9, 1.6955244e+9;
    String axis "T";
    String calendar "gregorian";
    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";
  }
  depth {
    String _CoordinateAxisType "Height";
    String _CoordinateZisPositive "down";
    Int32 actual_range 0, 92;
    String axis "Z";
    String ioos_category "Location";
    String long_name "Depth";
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  eastward_sea_water_velocity {
    Float64 _FillValue -555.0;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String description "velocity of sea water in the eastward direction (westward is negative)";
    String ioos_category "Currents";
    String long_name "Eastward Sea Water Velocity";
    Float64 missing_value -555.0;
    String standard_name "eastward_sea_water_velocity";
    String units "m/s";
  }
  northward_sea_water_velocity {
    Float64 _FillValue -555.0;
    Float64 colorBarMaximum 0.5;
    Float64 colorBarMinimum -0.5;
    String description "velocity of sea water in the northward direction (southward is negative)";
    String ioos_category "Currents";
    String long_name "Northward Sea Water Velocity";
    Float64 missing_value -555.0;
    String standard_name "northward_sea_water_velocity";
    String units "m/s";
  }
  upward_sea_water_velocity {
    Float64 _FillValue -555.0;
    Float64 colorBarMaximum 0.05;
    Float64 colorBarMinimum -0.05;
    String description "velocity of sea water in the upward direction; i.e., towards the surface (downward is negative)";
    String ioos_category "Currents";
    String long_name "Upward Sea Water Velocity";
    Float64 missing_value -555.0;
    String standard_name "upward_sea_water_velocity";
    String units "m/s";
  }
  echo_intensity_average {
    Float64 _FillValue -555.0;
    String description "4-beam average echo intensity, 0-256";
    String ioos_category "Statistics";
    String long_name "Echo Intensity Average";
    Float64 missing_value -555.0;
    String units "m/s";
  }
  NC_GLOBAL {
    Int32 _FillValue -555;
    String author "Seth Travis";
    String beam_angle "20";
    String beam_pattern "convex";
    String bottom_depth "100m";
    String buoy_designation "NEMO_SS";
    String buoy_latitude "47.9667N";
    String buoy_longitude "-124.9433E";
    String cdm_data_type "TimeSeriesProfile";
    String cdm_profile_variables "time";
    String cdm_timeseries_variables "buoy_name,latitude,longitude";
    String contact "setht1@uw.edu";
    String Conventions "CF-1.10, ACDD-1.3, IOOS-1.2, COARDS";
    String creator_email "setht1@uw.edu";
    String creator_name "Northwest Environmental Moorings Group";
    String creator_type "group";
    UInt16 data_start_year 2023;
    String data_type "ADCP water velocities";
    String defaultDataQuery "eastward_sea_water_velocity[last-30:last][0:last],northward_sea_water_velocity[last-30:last][0:last],upward_sea_water_velocity[last-30:last][0:last],echo_intensity_average[last-30:last][0:last]";
    String defaultGraphQuery "eastward_sea_water_velocity[last-30:last][0:last]&.draw=surface&.vars=time|depth|eastward_sea_water_velocity&.yRange=0|100|false";
    String description "Upward facing ADCP at the NEMO-SS buoy for the nemo23a deployment";
    String featureType "TimeSeriesProfile";
    String frequency "300kHz";
    String history 
"in order:
Conv_ADCP_mooring (coverts to mat files)
Run_WHbeams_ALL.m (conv. to earth coord & avgs pressure)
Process mat data  to netCDF on 2024-Jan-03 16:50:44
2024-12-14T00:05:13Z (local files)
2024-12-14T00:05:13Z http://nwem.apl.washington.edu/griddap/nemo-ss_adcp.das";
    String infoUrl "???";
    String institution "NWEM Group";
    String intrument_model "TRDI Sentinel ADCP";
    String keywords "acoustic, adcp, average, circulation, current, currents, data, deployment, depth, doppler, earth, Earth Science > Oceans > Ocean Circulation > Ocean Currents, eastward, eastward_sea_water_velocity, echo, echo_intensity_average, facing, group, intensity, nemo, nemo-ss, nemo23a, northward, northward_sea_water_velocity, nwem, ocean, oceans, profiler, science, sea, seawater, statistics, time, upward, upward_sea_water_velocity, velocity, water";
    String keywords_vocabulary "GCMD Science Keywords";
    String latitude "47.9667N";
    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 longitude "-124.9433E";
    Byte magnetic_declination_applied 16;
    String mooring_id "NEMO_SS";
    Byte nominal_instrument_depth 93;
    String orientation "upfacing";
    String serial_number "SN10010";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "deployment_name, sn, target_depth";
    String summary "NEMO-SS Velocity Profiler - Upward facing Acoustic Doppler Current Profiler (ADCP) - 60-minute average";
    String time_coverage_end "2023-09-24T03:00:00Z";
    String time_coverage_start "2015-05-23T21:00:00Z";
    String timeOffset_applied "-22.84302581 seconds";
    String timeOffset_notes "applied. Seconds that ADCP was ahead of GMT--linearly applied over timeseries";
    String title "NEMO-SS Velocity Profiler - Upward facing Acoustic Doppler Current Profiler (ADCP) - 60-minute average (DEVELOPMENTAL)";
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form. It makes the URL for you.
(easy) You can make a graph or map by using the dataset's Make A Graph form. It makes the URL for you.
(not hard) You can bypass the forms and get the data or make a graph or map by generating the URL by hand or with a computer program or script.

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.