Make A Graph

Dataset Title:	RV Sikuliaq : MBES 710_224 : Longitude
Institution:	UAF (Dataset ID: longitude_degrees_multib710224_fullres)
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 {
  time_raw {
    String ioos_category "Time";
    String long_name "Time Raw";
    String time_origin "01-JAN-1970 00:00:00";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  time {
    String _CoordinateAxisType "Time";
    String axis "T";
    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";
  }
  value {
    String colorBarMaximum "180.0";
    String colorBarMinimum "-180.0";
    String ioos_category "Location";
    String long_name "Longitude";
    String parameter_description "Longitude obtained from a separate GPS source. The time of the GPS latitude/longitude is closest to the LDS timestamp (not the datagram XYZ88 header timestamp).";
    String short_name "longitude";
    String standard_name "longitude";
    String units "degrees";
  }
  flag_summary {
    String colorBarMaximum "9";
    String colorBarMinimum "0";
    String flag_meanings "QC test not applicable, passed the QC test, quality was not evaluated or is unknown, quality is questionable/suspect, failed the QC test, data are missing";
    String flag_values "0, 1, 2, 3, 4, 9";
    String ioos_category "Quality";
    String long_name "Longitude QC Summary Flag";
    String short_name "longitude_qc_flag";
    String standard_name "longitude_qc_flag";
    String units "unitless";
  }
  flag_string {
    String flag_meanings "QC test not applicable, passed the QC test, quality was not evaluated or is unknown, quality is questionable/suspect, failed the QC test, data are missing";
    String flag_values "0, 1, 2, 3, 4, 9";
    String ioos_category "Quality";
    String long_name "Longitude QC Flags";
    String qc_test_indices "0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29";
    String qc_test_names "Gap Test, Syntax Test, Gross Range Test, Global Range Test, Recommended Range Test, Sensor Status Test, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused, Unused";
    String short_name "longitude_qc_flag_string";
    String standard_name "longitude_qc_flag_string";
    String units "unitless";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String contributor_name "RV Sikuliaq";
    String contributor_role "Data collector";
    String creator_name "CORIOLIX, RDESC, RCRV Project, Oregon State University";
    String creator_url "http://ceoas.oregonstate.edu";
    String history 
"2026-05-02T14:11:51Z (source database)
2026-05-02T14:11:51Z https://coriolix.sikuliaq.alaska.edu/tabledap/longitude_degrees_multib710224_fullres.das";
    String infoUrl "https://www.uaf.edu/cfos/sikuliaq/";
    String institution "UAF";
    String keywords "atmosphere, data, observations, ocean";
    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";
    String summary 
"Longitude time series data.
Platform: RV Sikuliaq
Sensor Model: Kongsberg EM 710 multibeam echosounder
Sensor S/N: 224
Sensor Location Onboard: Hull
Sensor Description: Shallow Water Multibeam Echo Sounder. 70 to 100 kHz operating frequencies.
Parameter Description: Longitude obtained from a separate GPS source. The time of the GPS latitude/longitude is closest to the LDS timestamp (not the datagram XYZ88 header timestamp).";
    String title "RV Sikuliaq : MBES 710_224 : Longitude";
  }
}

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