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:  Registry of continuous noise monitoring sites Subscribe RSS
Institution:  EMODnet Physics   (Dataset ID: registry_noise_fixed_platforms)
Range: longitude = -3.536 to 30.6°E, latitude = 35.1978 to 68.91°N
Information:  Summary ? | License ? | FGDC | ISO 19115 | Metadata | Background (external link) | Subset | Data Access Form | Files
 
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: 
Draw land mask: 
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 ? )
    Click on the map to specify a new center point. ?
Zoom: 
[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 {
  country {
    String long_name "Country";
  }
  institution {
    String long_name "Institution";
  }
  institution_url {
    String long_name "Institution Url";
  }
  EDMO_code {
    Int16 _FillValue 32767;
    Int16 actual_range 28, 5439;
    String long_name "EDMO Code";
  }
  reference_url {
    String long_name "Reference Url";
  }
  data_source {
    String long_name "Data Source";
  }
  station_code_surce {
    String long_name "Station Code Surce";
  }
  latitude {
    String _CoordinateAxisType "Lat";
    Float64 actual_range 35.1978, 68.91;
    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 -3.536, 30.6;
    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";
  }
  lat_b {
    Float32 _FillValue NaN;
    Float32 actual_range 36.11, 45.315;
    Float64 colorBarMaximum 90.0;
    Float64 colorBarMinimum -90.0;
    String long_name "Latitude";
    String standard_name "latitude";
    String units "degrees_north";
  }
  lon_b {
    Float32 _FillValue NaN;
    Float32 actual_range 1.65, 28.77;
    Float64 colorBarMaximum 180.0;
    Float64 colorBarMinimum -180.0;
    String long_name "Longitude";
    String standard_name "longitude";
    String units "degrees_east";
  }
 }
  NC_GLOBAL {
    String cdm_data_type "Other";
    String Conventions "COARDS, CF-1.6, ACDD-1.3";
    Float64 Easternmost_Easting 30.6;
    Float64 geospatial_lat_max 68.91;
    Float64 geospatial_lat_min 35.1978;
    String geospatial_lat_units "degrees_north";
    Float64 geospatial_lon_max 30.6;
    Float64 geospatial_lon_min -3.536;
    String geospatial_lon_units "degrees_east";
    String history 
"2024-04-28T05:27:03Z (local files)
2024-04-28T05:27:03Z https://erddap.emodnet-physics.eu/tabledap/registry_noise_fixed_platforms.das";
    String infoUrl "https://prod-geonetwork.emodnet-physics.eu/geonetwork/srv/eng/catalog.search#/metadata/5a0ba2e8-38ce-44df-b9a8-c0aa120fcb33";
    String institution "EMODnet Physics";
    String keywords "code, country, data, data_source, edmo, EDMO_code, institution, institution_url, lat_b, latitude, local, lon_b, longitude, reference, reference_url, source, station, station_code_surce, surce";
    String license "CC-BY 4.0";
    Float64 Northernmost_Northing 68.91;
    String sourceUrl "(local files)";
    Float64 Southernmost_Northing 35.1978;
    String standard_name_vocabulary "CF Standard Name Table v70";
    String subsetVariables "country, institution";
    String summary "This product displays the fixed stations and transects to assess continuous noise. Data are collected from ICES DB (https://www.ices.dk/data/data-portals/Pages/Continuous-Noise.aspx), the JOMOPANS (https://jomopansgestool.au.dk/en/about) project and QUIETSEA (https://quietseas.eu/).";
    String title "Registry of continuous noise monitoring sites";
    Float64 Westernmost_Easting -3.536;
  }
}

 

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