Make A Graph

Dataset Title:	Active NRT Stations
Institution:	National Institute of Oceanography and Applied Geophysics - OGS, Division of Oceanography (Dataset ID: ACTIVE_STATIONS)
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

)

[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 {
  MAMBO1 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "MAMBO1 active";
    String standard_name "mambo1_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  MAMBO2 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "MAMBO2 active";
    String standard_name "mambo2_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  MAMBO3 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "MAMBO3 active";
    String standard_name "mambo3_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  MAMBO4 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "MAMBO4 active";
    String standard_name "mambo4_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  DWRG1 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "DWRG1 active";
    String standard_name "dwrg1_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  DWRG2 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "DWRG2 active";
    String standard_name "dwrg2_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  DWRG3 {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "DWRG3 active";
    String standard_name "dwrg3_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  E2M3A {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "E2M3A active";
    String standard_name "e2m3a_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  CURRISO {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "CURRISO active";
    String standard_name "curriso_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
  PIEZTAG {
    Byte _FillValue 127;
    String _Unsigned "false";
    Byte actual_range 0, 1;
    String flag_meanings "inactive, active";
    Byte flag_values 0, 1;
    String ioos_category "Other";
    String long_name "PIEZTAG active";
    String standard_name "pieztag_active";
    Byte valid_max 1;
    Byte valid_min 0;
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String creator_email "nodc@ogs.it";
    String creator_type "institution";
    String creator_url "https://nodc.ogs.it";
    String history 
"2025-05-13T03:28:04Z (source database)
2025-05-13T03:28:04Z https://nodc.ogs.it/tabledap/ACTIVE_STATIONS.das";
    String infoUrl "https://nodc.ogs.it";
    String institution "National Institute of Oceanography and Applied Geophysics - OGS, Division of Oceanography";
    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 Table v71";
    String summary "Active NRT Stations";
    String title "Active NRT Stations";
  }
}

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