Nautilos    ERDDAP NAUTILOS
Easier access to scientific data
   
Brought to you by Nautilos    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  NAUTILOS - Passive Acoustic Sensor - Aquatec - Test Subscribe RSS
Institution:  Aquatec   (Dataset ID: passive_acoustic_sensor_aquatec_test)
Range: longitude = -8.7045 to 25.090708°E, latitude = 0.0 to 59.908817°N, time = 2023-09-06T12:48:00Z to 2024-05-22T00:00:00Z
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
Graph Type:  ?
X Axis: 
Y Axis: 
-1+1
 
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.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.Hover here to see a list of options. Click on an option to select it.")
 
Graph Settings
Color: 
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 ? )
   
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  Sample_ID {
    String long_name "Sample ID";
  }
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.69400448e+9, 1.716336e+9;
    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 time_precision "1970-01-01T00:00:00Z";
    String units "seconds since 1970-01-01T00:00:00Z";
  }
  elapsedTime {
    Float64 actual_range 0.0, 10.026645833333333;
    String long_name "Elapsed Time";
    String units "s";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 0.0, 59.908817;
    String axis "Y";
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String ioos_category "Location";
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  longitude {
    String _CoordinateAxisType "Lon";
    Float64 actual_range -8.7045, 25.090708;
    String axis "X";
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String ioos_category "Location";
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
  channel_1 {
    Int16 actual_range -32768, 32760;
    Float64 colorBarMaximum 33000.0;
    Float64 colorBarMinimum -33000.0;
    String long_name "Channel 1 384kHz";
  }
  file_name {
    String long_name "Audio file name";
  }
 }
  NC_GLOBAL {
    String audioBigEndian "false";
    Int32 audioChannels 1;
    String audioEncoding "PCM_SIGNED";
    Float32 audioFrameRate 384000.0;
    Int32 audioFrameSize 2;
    Float32 audioSampleRate 384000.0;
    Int32 audioSampleSizeInBits 16;
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    String defaultGraphQuery "elapsedTime,channel_1&elapsedTime>=0&elapsedTime<=1&.draw=lines";
    Float64 Easternmost_Easting 25.090708;
    Float64 geospatial_lat_max 59.908817;
    Float64 geospatial_lat_min 0.0;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 25.090708;
    Float64 geospatial_lon_min -8.7045;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-11-23T13:50:46Z (local files)
2024-11-23T13:50:46Z http://data-nautilos-h2020.eu/tabledap/passive_acoustic_sensor_aquatec_test.das";
    String infoUrl "https://nautilos-h2020.eu/";
    String institution "Aquatec";
    String keywords "Passive Acoustic Sensor";
    String license "CC-BY 4.0";
    String naming_authority "NAUTILOS";
    Float64 Northernmost_Northing 59.908817;
    String project_code "NAUTILOS";
    String Project_DOI "https://doi.org/10.3030/101000825";
    String project_edmerp "13720";
    String project_id "101000825";
    String project_name "New Approach to Underwater Technologies for Innovative, Low-cost Ocean obServation";
    String project_statement "This project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 101000825 (NAUTILOS). This output reflects only the author's view and the European Union cannot be held responsible for any use that may be made of the information contained therein";
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 0.0;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "Sample_ID";
    String summary "NAUTILOS - Passive Acoustic Sensor - Aquatec - Test";
    String time_coverage_end "2024-05-22T00:00:00Z";
    String time_coverage_start "2023-09-06T12:48:00Z";
    String title "NAUTILOS - Passive Acoustic Sensor - Aquatec - Test";
    Float64 Westernmost_Easting -8.7045;
  }
}

 

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.

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