![]() |
EMODnet Physics ERDDAP
Easier access to scientific data |
log in|
Brought to you by EMODnet Physics |
| Dataset Title: | EMODnet Physics - European Impulsive Noise Events Registry
|
| Institution: | ICES (Dataset ID: EP_UWN_INER) |
| Information: | Summary
| License
| Metadata
| Background
| Make a graph
|
Attributes {
s {
pulsedays {
String long_name "Pulsedays";
}
subsquare {
String long_name "Subsquare";
}
year {
String long_name "Year";
}
classlegen {
String long_name "Classlegen";
}
sizeofclas {
String long_name "Sizeofclas";
}
wkb_geometry {
String long_name "Wkb Geometry";
}
source {
String long_name "Source";
}
}
NC_GLOBAL {
String cdm_data_type "Other";
String Conventions "COARDS, CF-1.10, ACDD-1.3";
String history
"2025-11-02T04:02:50Z (source database)
2025-11-02T04:02:50Z http://erddap.emodnet-physics.eu/erddap/tabledap/EP_UWN_INER.html";
String infoUrl "https://www.ices.dk/data/data-portals/Pages/impulsive-noise.aspx";
String institution "ICES";
String keywords "classlegen, data, fid, geometry, local, ogc, ogc_fid, pulsedays, sizeofclas, source, subsquare, wkb, wkb_geometry, year";
String license "Creative Commons Attribution Share-Alike http://www.opendefinition.org/licenses/cc-by-sa";
String sourceUrl "(source database)";
String standard_name_vocabulary "CF Standard Name Table v70";
String summary "EMODnet Physics - Impulsive noise events in Pulse Block Day unit. A PBDU is the number of days in a calendar year in which impulsive sound activity occurred within the cell-grid. The product applies a common grid (10' latitude x 20' longitude) to harmonize the Regional Conventions events DBs. These data are collected at national level and contribute to the Sea Regional Convention events registry. ICES (http://underwaternoise.ices.dk/map.aspx) is hosting OSPAR and HELCOM registries. Mediterranean data are integrated from CTN under the ACCOBAMS demonstrator (http://accobams.noiseregister.org/).";
String title "EMODnet Physics - European Impulsive Noise Events Registry";
}
}
Data Access Protocol (DAP)
and its
selection constraints
.
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.