Voice of the Ocean ERDDAP™
Easier access to scientific data

Make A Graph

Dataset Title:	Data from a local source.
Institution:	??? (Dataset ID: meta_ballast)
Information:	Summary \| License \| Metadata \| Background \| Subset \| 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:

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

)

[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 {
  deployment_id {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 8, 98;
    String long_name "Deployment Id";
  }
  glider_serial {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 44, 79;
    String long_name "Glider Serial";
  }
  total_dives {
    Int16 _FillValue 32767;
    Int16 actual_range 9, 1968;
    String long_name "Total Dives";
  }
  max_depth {
    Int16 _FillValue 32767;
    Int16 actual_range 59, 1034;
    String long_name "Max Depth (m)";
  }
  max_ballast {
    Int16 _FillValue 32767;
    Int16 actual_range 495, 615;
    String long_name "Max Ballast (ml)";
  }
  min_ballast {
    Int16 _FillValue 32767;
    Int16 actual_range -546, -259;
    String long_name "Min Ballast (ml)";
  }
  avg_max_pumping_value {
    Int16 _FillValue 32767;
    Int16 actual_range -266, 501;
    String long_name "Avg Max Pumping Value (ml)";
  }
  std_max {
    Int16 _FillValue 32767;
    Int16 actual_range 5, 278;
    String long_name "Std Max";
  }
  std_min {
    Int16 _FillValue 32767;
    Int16 actual_range 0, 365;
    String long_name "Std Min";
  }
  avg_min_pumping_value {
    Int16 _FillValue 32767;
    Int16 actual_range -509, 318;
    String long_name "Avg Min Pumping Value (ml)";
  }
  avg_pumping_range {
    Int16 _FillValue 32767;
    Int16 actual_range 133, 996;
    String long_name "Avg Pumping Range (ml)";
  }
  total_active_pumping {
    Int32 _FillValue 2147483647;
    Int32 actual_range 2298, 1294664;
    String long_name "Total Active Pumping (ml)";
  }
  times_crossing_over_420_ml {
    Int16 _FillValue 32767;
    Int16 actual_range 1, 1290;
    String long_name "Times Crossing Over 420 Ml";
  }
  basin {
    String long_name "Basin";
  }
  threshold {
    Int16 _FillValue 32767;
    Int16 actual_range 420, 420;
    String long_name "Threshold";
  }
  datasetID {
    String long_name "Dataset ID";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.10, ACDD-1.3";
    String history 
"2024-11-21T10:33:06Z (local files)
2024-11-21T10:33:06Z https://erddap.observations.voiceoftheocean.org/tabledap/meta_ballast.das";
    String infoUrl "???";
    String institution "???";
    String keywords "active, average, avg_max_pumping_value, avg_min_pumping_value, avg_pumping_range, ballast, basin, crossing, data, dataset, datasetID, deployment, deployment_id, depth, dives, glider, glider_serial, local, max, max_ballast, max_depth, min, min_ballast, over, profiler, pumping, range, salinity, salinity-temperature-depth, serial, source, std, std_max, std_min, temperature, threshold, times, times_crossing_over_420_ml, total, total_active_pumping, total_dives, value";
    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 v70";
    String subsetVariables "threshold";
    String summary "Data from a local source.";
    String title "Data from a local source.";
  }
}

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