Dataset: Earthquake Seismogram Denoiser (EQS-Denoiser)

Open data API in a single place

Provided by Zenodo

Get early access to Dataset: Earthquake Seismogram Denoiser (EQS-Denoiser) API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.12.18 00:00
Created
2025.12.18
Available languages
English
Keywords
Quality scoring

Dataset description

This dataset contains preprocessed earthquake event and noise waveforms, supplementary to the publication: "Towards Operational Earthquake Seismogram Denoising"by Nikolaj Dahmen, John Clinton, Men-Andrin Meier, Luca ScarabelloBulletin of the Seismological Society of America Waveform data are provided in physical units [m/s],  Z12 components and with a sampling rate of 100 Hz. Event signals have been preprocessed according to the methods described in the publication to reduce background noise (see Figure 2). Event signals have 18k samples with P arrival aligned at sample 6000, noise signals have 8k samples. Dataset statistics for event and noise waveforms are summarized in Figures S1 and S2. The dataset is separated into training, validation, and testing dataset, and are here available for publicly accessible networks. Metadata includes information on recording station, earthquake, and identified phase arrivals. A subset of the test dataset with fixed event and noise waveform pairs is provided in the benchmark dataset.  Data are provided in HDF5 format with accompanying metadata, compatible with SeisBench.   Proposed dataset structure: Event waveforms: Event_data/waveforms.hdf5 Event_data/metadata.csv Noise waveforms: Noise_data/waveforms_noise.hdf5 Noise_data/metadata_noise.csv   Importing dataset with SeisBench: import seisbench.data as sbd # load noise dataset noise_ds = sbd.WaveformDataset("/Noise_data/", sampling_rate=100, component_order="Z12") # Training examples: 274,240 # Development examples: 81,416 # Test examples: 40,096 # load event dataset event_ds = sbd.WaveformDataset("/Event_data/", sampling_rate=100, component_order="Z12") # Training examples: 19,022 # Development examples: 5,385 # Test examples: 2,695 Data Sources: Network Source Year Link CH National Seismic Networks of Switzerland (SED, ETH Zurich) 1983 Link 9S Landslide deployments, Switzerland 2012 Link 8D Aftershock deployments, Switzerland 2025 Link G2 GEOBEST geothermal project networks 2006 Link S Seismology at School Program 2008 Link C4 CERN Seismic Network 2016 Link 1I Matterhorn Cryosphere Observatory 2015 Link Z3 AlpArray Temporary Network 2015 Link GU Regional Network NW Italy 1967 Link OX Northeast Italy OGS 2016 Link IV Rete Sismica Nazionale (INGV) 2005 Link 8C Mont-Blanc & Vallorcine Monitoring (RESIF-SISMOB) 2020 Link FR EPOS-France Broad-Band Network (RLBP) 1995 Link RA RESIF-RAP French Accelerometric Network 1995 Link BW BayernNetz, Germany 2001 Link GR German Regional Seismic Network (GRSN) 1976 Link LE Erdbebendienst SW Baden-Württemberg & RP 2009 Link OE Austrian Seismic Network (ZAMG) 1987 Link MN Mediterranean Very Broadband Seismographic Network (MedNet) 1990 Link   Dataset for benchmarking (Benchmark.zip), contains event and noise signals part of "test" partition in hdf5 files. Contains event and noise signal combinations as used in performance test in publication, with randomly sampled noise (TestDataSet.zip) and impulsive noise signals (TestDataSet_ImpulsiveNoise.zip). The ReadMe File documents test procedure.   Related code  
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks