EMODnet Physics ERDDAP
Easier access to scientific data

Make A Graph

Dataset Title:	Hydrophone Recordings at OBSEA (audio data)
Institution:	SARTI Research Group. Electronics Dept. Universitat Politecnica de Catalunya (UPC) (Dataset ID: OBSEA_NAXYS_hydrophone_audio_data)
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:

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.

(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

)

X 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 {
  elapsedTime {
    Float64 actual_range 0.0, 59.99998958333333;
    String ioos_category "Time";
    String long_name "Elapsed Time";
    String units "seconds";
  }
  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";
  }
  channel_1 {
    Float64 colorBarMaximum 33000.0;
    Float64 colorBarMinimum -33000.0;
    String ioos_category "Other";
    String long_name "Channel 1";
  }
 }
  NC_GLOBAL {
    String area "Mediterranean";
    String audioBigEndian "false";
    Int32 audioChannels 1;
    String audioEncoding "PCM_SIGNED";
    Float32 audioFrameRate 96000.0;
    Int32 audioFrameSize 2;
    Float32 audioSampleRate 96000.0;
    Int32 audioSampleSizeInBits 16;
    String author "Universitat Politecnica de Catalunya (UPC)";
    String cdm_data_type "Other";
    String contact "enoc.martinez@upc.edu";
    String Conventions "COARDS, CF-1.6, ACDD-1.3, NCCSV-1.0";
    String defaultGraphQuery "elapsedTime,channel_1&elapsedTime>=0&elapsedTime<=1&.draw=lines";
    String geospatial_lat_max "41.18212";
    String geospatial_lat_min "41.18212";
    String geospatial_lon_max "1.75257";
    String geospatial_lon_min "1.75257";
    String history 
"2021-07-31T20:51:57Z (local files)
2021-07-31T20:51:57Z https://erddap.emodnet-physics.eu/tabledap/OBSEA_NAXYS_hydrophone_audio_data.das";
    String infoUrl "http://www.obsea.es";
    String institution "SARTI Research Group. Electronics Dept. Universitat Politecnica de Catalunya (UPC)";
    String institution_edmo_code "2150";
    String institution_references "http://www.obsea.es/, http://cdsarti.org/";
    String keywords "audio, hydrophone, OBSEA, recordings, UPC, wav";
    String license "Creative Commons Attribution 4.0 International (CC-BY-4.0)";
    String pi_name "Joaquin del Rio, joaquin.del.rio@upc.edu";
    String platform_code "OBSEA";
    String site_code "OBSEA";
    String sourceUrl "(local files)";
    String standard_name_vocabulary "CF Standard Name Table v55";
    String summary "Recordings from a Bjorge NAXYS Ethernet Hydrophone at OBSEA (as ERDDAP audio data)";
    String title "Hydrophone Recordings at OBSEA (audio data)";
  }
}

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