Make A Graph

Dataset Title:	SOCHIC-SOSCEx_STORM2_Glider_Data/EPSFINAL_soscex_storm2
Institution:	University of Gothenburg (Dataset ID: SOCHIC_SOSCEx_STORM2_Glider_Data_EPSFINAL_soscex_storm2)
Range:	depth = 1.0 to 200.0m, time = 2018-12-19T19:44:54Z to 2019-03-08T10:08:05Z
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:

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 {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.545248694578e+9, 1.5520396856132002e+9;
    String axis "T";
    String calendar "proleptic_gregorian";
    String ioos_category "Time";
    String long_name "TIME EPSFINAL";
    String source_name "TIME_EPSFINAL";
    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";
    Int16 actual_range 1, 200;
    String axis "Z";
    Float64 colorBarMaximum 8000.0;
    Float64 colorBarMinimum -8000.0;
    String colorBarPalette "TopographyDepth";
    String ioos_category "Location";
    String long_name "Depth";
    Int16 missing_value 127;
    String positive "down";
    String standard_name "depth";
    String units "m";
  }
  EPS_FINAL {
    Float64 _FillValue NaN;
    Float64 actual_range 1.9821472842571312e-11, 7.348132402427374e-5;
    String long_name "EPS FINAL";
    Float64 missing_value NaN;
  }
  EPS_THEORY {
    Float64 _FillValue NaN;
    Float64 actual_range 1.7348984476243517e-4, 9355.57722671611;
    String long_name "EPS THEORY";
    Float64 missing_value NaN;
  }
 }
  NC_GLOBAL {
    String _NCProperties "version=2,netcdf=4.6.3,hdf5=1.10.4";
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String EDMO_code "3984";
    Float64 geospatial_vertical_max 200.0;
    Float64 geospatial_vertical_min 1.0;
    String geospatial_vertical_positive "down";
    String geospatial_vertical_units "m";
    String history 
"2024-05-20T12:01:29Z (local files)
2024-05-20T12:01:29Z https://erddap.sochic-h2020.eu/tabledap/SOCHIC_SOSCEx_STORM2_Glider_Data_EPSFINAL_soscex_storm2.das";
    String infoUrl "https://doi.org/10.1029/2021JC017760";
    String institution "University of Gothenburg";
    String keywords "data, depth, eps, EPS_FINAL, EPS_THEORY, epsfinal, final, local, source, theory, time";
    String license "CC BY-NC 4.0 https://creativecommons.org/licenses/by-nc/4.0/";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "SOCHIC-SOSCEx_STORM2_Glider_Data/EPSFINAL_soscex_storm2";
    String time_coverage_end "2019-03-08T10:08:05Z";
    String time_coverage_start "2018-12-19T19:44:54Z";
    String title "SOCHIC-SOSCEx_STORM2_Glider_Data/EPSFINAL_soscex_storm2";
  }
}

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