EMODnet Physics ERDDAP Installation EMODnet Physics ERDDAP
Easier access to scientific data
log in    
Brought to you by EMODnet Physics    

ERDDAP > tabledap > Make A Graph ?

Dataset Title:  SPL values at OBSEA Subscribe RSS
Institution:  SARTI Research Group. Electronics Dept. Universitat Politecnica de Catalunya (UPC)   (Dataset ID: OBSEA_SPLs_NAXYS_hydrophone_at_OBSEA)
Range: time = 2017-09-08T09:11:41Z to 2020-04-29T10:07:23Z
Information:  Summary ? | License ? | Metadata | Background (external link) | Data Access Form
 
Graph Type:  ?
X Axis: 
Y Axis: 
Color: 
-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
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:

The Dataset Attribute Structure (.das) for this Dataset

Attributes {
 s {
  time {
    String _CoordinateAxisType "Time";
    Float64 actual_range 1.504861901e+9, 1.588154843e+9;
    String axis "T";
    String ioos_category "Time";
    String long_name "startTime";
    String source_name "startTime";
    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";
  }
  endTime {
    Float64 actual_range 1.504861921e+9, 1.588154863e+9;
    String ioos_category "Time";
    String long_name "endTime";
    String source_name "endTime";
    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";
  }
  SPL_full {
    Float32 actual_range 93.36, 164.19;
    String long_name "sound pressure level(full bandwidth)";
    String units "dB re 1 µPa";
  }
  SPL_63Hz {
    Float32 actual_range 70.71, 147.18;
    String long_name "sound pressure level at 63 Hz third-octave band";
    String units "dB re 1 µPa";
  }
  SPL_125Hz {
    Float32 actual_range 72.18, 150.52;
    String long_name "sound pressure level at 125 Hz third-octave band";
    String units "dB re 1 µPa";
  }
  SPL_2000Hz {
    Float32 actual_range 73.73, 139.02;
    String long_name "sound pressure level at 2000 Hz third-octave band";
    String units "dB re 1 µPa";
  }
 }
  NC_GLOBAL {
    String area "Mediterranean";
    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 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 
"2020-10-20T11:12:46Z (local files)
2020-10-20T11:12:46Z https://erddap.emodnet-physics.eu/tabledap/OBSEA_SPLs_NAXYS_hydrophone_at_OBSEA.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 "conductivity, Hydrophone, MSFD, OBSEA, pressure, salinity, sound_velocity, SPL, temperature, Underwater Noise, UPC";
    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 "Sound Pressure Level values at OBSEA calculated 63, 125 and 2000 Hz third-octave bands and full bandwidth";
    String time_coverage_end "2020-04-29T10:07:23Z";
    String time_coverage_start "2017-09-08T09:11:41Z";
    String title "SPL values at OBSEA";
  }
}

 

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