Make A Graph

Dataset Title:	ADV data from Jamaica bay mooring JB02
Institution:	Rutgers University (Dataset ID: Jamaica_Bay_ADV_Burst)
Range:	time = 2015-07-09T15:00:00Z to 2015-07-28T05:34:59Z
Information:	Summary \| License \| Metadata \| Background \| Data Access Form

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:

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.

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:

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 {
 s {
  sample {
    Int32 actual_range 0, 6704999;
    String ioos_category "Unknown";
    String long_name "Sample";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.436454e+9, 1.43806169996e+9;
    String axis "T";
    String comment "time of the first sample of the burst.";
    String ioos_category "Time";
    String long_name "survey time";
    String standard_name "time";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  amp1 {
    Float64 actual_range 9.03, 101.48;
    String ioos_category "Statistics";
    String long_name "Burst Mean Beam 1 amplitude";
    String units "dB";
  }
  amp2 {
    Float64 actual_range 9.459999999999999, 102.34;
    String ioos_category "Statistics";
    String long_name "Burst Mean Beam 2 amplitude";
    String units "dB";
  }
  amp3 {
    Float64 actual_range 8.6, 101.91;
    String ioos_category "Statistics";
    String long_name "Burst Mean Beam 3 amplitude";
    String units "dB";
  }
  corr1 {
    Float64 actual_range 0.0, 111.0;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Burst Mean Beam 1 correlation";
    String units "percent";
  }
  corr2 {
    Float64 actual_range 0.0, 112.0;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Burst Mean Beam 2 correlation";
    String units "percent";
  }
  corr3 {
    Float64 actual_range 0.0, 144.0;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Burst Mean Beam 3 correlation";
    String units "percent";
  }
  u {
    Float64 actual_range -308.17, 283.83;
    String ioos_category "Currents";
    String long_name "Eastward velocity";
    String units "cm/s";
  }
  v {
    Float64 actual_range -289.29, 283.12;
    String ioos_category "Currents";
    String long_name "Northward velocity";
    String units "cm/s";
  }
  w {
    Float64 actual_range -60.38, 60.48;
    String ioos_category "Currents";
    String long_name "Vertical velocity";
    String units "cm/s";
  }
  pressure {
    Float64 actual_range 15.039, 17.182;
    String ioos_category "Pressure";
    String long_name "Presure";
    String units "decibars";
  }
  burstnumber {
    Float64 actual_range 1.0, 894.0;
    Float64 colorBarMaximum 100.0;
    Float64 colorBarMinimum 0.0;
    String ioos_category "Statistics";
    String long_name "Burst Number";
  }
 }
  NC_GLOBAL {
    Float64 Burst_sammple_rate 25.0;
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String History "File created on 23-Jan-2020 09:36:33 using convert_adv by EJH";
    String history 
"File created on 23-Jan-2020 09:36:33 using convert_adv by EJH
2024-04-18T20:51:01Z (local files)
2024-04-18T20:51:01Z https://tds.marine.rutgers.edu/tabledap/Jamaica_Bay_ADV_Burst.das";
    String infoUrl "Marine.Rutgers.edu";
    String institution "Rutgers University";
    String keywords "adv, amp1, amp2, amp3, amplitude, bay, beam, burst, burstnumber, corr1, corr2, corr3, correlation, currents, data, eastward, jamaica, jb02, mean, mooring, northward, number, pressure, presure, sample, statistics, survey, time, u, v, velocity, vertical, w";
    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 "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String Summary "Acoustic doppler velocimeter burst data from Jamica Bay mooring JB02. July, 2015";
    String summary "Acoustic doppler velocimeter burst data from Jamica Bay mooring JB02. July, 2015";
    String time_coverage_end "2015-07-28T05:34:59Z";
    String time_coverage_start "2015-07-09T15:00:00Z";
    String Title "ADV data from Jamaica bay mooring JB02";
    String title "ADV data from Jamaica bay mooring JB02";
  }
}

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.

(easy) You can get data by using the dataset's Data Access Form or Subset form. They make 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.

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