Understanding background seismic noise levels is crucial for assessing the suitability of a site for seismic monitoring and instrumentation. Background noise analysis helps identify optimal locations for seismic sensors and ensures accurate detection of seismic events. This blog explores how to calculate background noise levels based on methodologies from Ramirez et al. (2019), using power spectral density (PSD) techniques.
Why Measure Seismic Noise Levels?
Seismic stations continuously record ambient noise from both natural and anthropogenic sources. High noise levels can mask low-magnitude earthquakes and reduce the effectiveness of seismic monitoring networks. The analysis of background noise levels provides insights into:
- The impact of environmental conditions on sensor performance.
- The influence of geological settings on noise characteristics.
- The optimal placement of seismic sensors for improved data quality.
Step 1: Data Collection
To measure background seismic noise, long-term continuous seismic data from a given site must be collected. Typically, broadband seismometers and accelerometers are used to capture signals across a wide range of frequencies. These data are stored in a digital format, such as miniSEED, which allows for efficient processing.
Step 2: Preprocessing the Seismic Data
Before analyzing noise levels, raw seismic data must be preprocessed to remove unwanted signals. This includes:
- Segmenting Data: Breaking continuous records into smaller time windows (e.g., hourly segments) to analyze temporal variations.
- Applying Windowing Functions: Using techniques like cosine tapers to reduce spectral leakage.
- Fourier Transform: Converting time-domain data into the frequency domain for spectral analysis.
- Acceleration Conversion: Deriving acceleration spectra from velocity or displacement records.
Step 3: Power Spectral Density (PSD) Calculation
The Power Spectral Density (PSD) method is widely used to quantify ambient seismic noise levels. This technique measures the energy distribution of seismic signals across different frequencies. The steps include:
- Computing the Fast Fourier Transform (FFT): This transforms seismic data from the time domain to the frequency domain.
- Averaging Spectra: To improve statistical reliability, multiple PSD estimates are averaged over time.
- Expressing Noise Levels in Decibels (dB): PSD values are converted to decibels relative to a reference power level (e.g., 1 μm²/s⁴/Hz).
- Generating PSD Probability Density Functions (PDFs): A statistical representation of noise levels over time to assess variations.
Step 4: Analyzing Noise Level Trends
Once PSDs are computed, trends in noise levels can be analyzed:
- Comparing Different Geological Settings: Sites on sedimentary deposits often exhibit higher noise levels than those on bedrock.
- Assessing Diurnal Variations: Noise levels tend to be higher during the day due to human activities.
- Impact of Environmental Factors: Atmospheric pressure and temperature fluctuations can influence background noise levels.
Step 5: Comparing with Standard Noise Models
To interpret seismic noise levels, results are compared with global noise models:
- New High-Noise Model (NHNM): Represents the highest observed noise levels at global seismic stations.
- New Low-Noise Model (NLNM): Represents the lowest possible ambient noise levels.
Step 6: Identifying and Mitigating Noise Sources
If noise levels are excessive, it is essential to identify and mitigate noise sources:
- Relocating Sensors: Moving stations away from urban areas or installing them in underground vaults can reduce anthropogenic noise.
- Improving Insulation: Using thermal and acoustic insulation can minimize environmental noise interference.
- Using Different Sensor Types: Some sensors may exhibit different sensitivity to background noise, requiring careful selection based on site conditions.
Complete Python Code for Computing Background Seismic Noise Levels
Below is a full Python script that includes preprocessing, PSD computation, and noise model comparison.
import numpy as np
import obspy
import matplotlib.pyplot as plt
from obspy.signal.spectral_estimation import PSD, get_nlnm, get_nhnm
def preprocess_seismic_data(trace):
"""Preprocess seismic data: detrend, taper, and remove response."""
trace.detrend("linear")
trace.taper(max_percentage=0.05, type="hann")
return trace
def compute_psd(trace, nfft=1024, overlap=0.5):
"""Compute Power Spectral Density (PSD) for a given seismic trace."""
psd, freq = PSD(trace.data, nfft=nfft, overlap=overlap, fs=trace.stats.sampling_rate)
psd_db = 10 * np.log10(psd)
return freq, psd_db
def plot_noise_models(freq, psd_db):
"""Plot the computed PSD against global noise models."""
nlnm_freq, nlnm_psd = get_nlnm()
nhnm_freq, nhnm_psd = get_nhnm()
plt.figure(figsize=(8,6))
plt.plot(nlnm_freq, nlnm_psd, label="NLNM", linestyle="dashed")
plt.plot(nhnm_freq, nhnm_psd, label="NHNM", linestyle="dashed")
plt.plot(freq, psd_db, label="Computed PSD", color='red')
plt.xlabel("Frequency (Hz)")
plt.ylabel("Power Spectral Density (dB)")
plt.legend()
plt.title("Comparison of Seismic Noise Levels with Global Models")
plt.grid()
plt.show()
# Example usage
st = obspy.read("example.mseed")
st = st.select(component="Z")
for tr in st:
tr = preprocess_seismic_data(tr)
freq, psd_db = compute_psd(tr)
plot_noise_models(freq, psd_db)
Conclusion
Calculating background seismic noise levels using the PSD method provides a robust approach to evaluating site suitability for seismic monitoring. By following these steps, researchers and engineers can optimize sensor placement, minimize noise interference, and enhance the reliability of seismic data. Understanding noise trends and environmental influences allows for better decision-making in seismic instrumentation and hazard assessment.ntal influences allows for better decision-making in seismic instrumentation and hazard assessment.
Reference
Ramírez, E. E., Vidal-Villegas, J. A., Nuñez-Leal, M. A., Ramírez-Hernández, J., Mejía-Trejo, A., & Rosas-Verdug, E. (2019). Seismic noise levels in northern Baja California, Mexico. Bulletin of the Seismological Society of America, 109(2), 610–620. https://doi.org/10.1785/0120180155
Last reviewed: 2026-07-04
Executive Summary
Seismic sensors convert ground motion into measured signals for event detection, site characterization, structural monitoring, and engineering analysis. This article has been expanded as an engineering resource for readers evaluating seismic sensors concepts, instrumentation choices, and monitoring workflows. The discussion is educational and should be paired with project-specific review by qualified engineers, applicable codes, owner requirements, and equipment documentation.
Key Takeaways
- Define the engineering objective before selecting sensors, test equipment, trigger thresholds, or reporting workflows.
- Use calibrated instrumentation, documented installation practices, time synchronization, and traceable data handling where measurement quality matters.
- Interpret measured data in context: site conditions, structure type, noise environment, sampling rate, bandwidth, and boundary conditions all affect conclusions.
- Use authoritative references and project-specific criteria rather than relying on generic thresholds or unsupported performance claims.
Technical Explanation
In practical seismic sensors work, the engineering system is more than a sensor or a test platform. A credible workflow includes the measurement objective, instrument selection, mounting or boundary conditions, sampling and timing strategy, data validation, event or response detection, engineering review, and reporting. Weakness in any part of that chain can reduce confidence in the final interpretation.
For monitoring applications, engineers should document sensor orientation, coupling, environmental exposure, dynamic range, frequency bandwidth, data logger configuration, clock synchronization, communications, and maintenance procedures. For testing applications, engineers should document input motion, fixture design, payload properties, control limits, safety interlocks, acceptance criteria, and post-test data review.
Engineering Applications
| Application | Engineering Question | Typical Evidence Needed |
|---|---|---|
| Research and education | How does a structure, component, or sensor respond under controlled conditions? | Test plan, calibrated data, input motion, boundary conditions, and repeatable observations. |
| Critical infrastructure | Is the asset response normal, changing, or potentially unsafe after an event? | Baseline data, event records, thresholds, inspection workflow, and engineering sign-off. |
| Industrial facilities | Can monitoring support operational continuity and response decisions? | Site-specific criteria, reliable telemetry, alarm logic, maintenance records, and documented procedures. |
People Also Ask
What should be specified before buying equipment?
Specify the measurement objective, frequency range, amplitude range, environment, data format, timing needs, installation constraints, reporting requirements, and applicable standards or owner criteria.
Why do references and standards matter?
They provide terminology, acceptance criteria, test methods, and documentation expectations. They do not replace engineering judgment, but they reduce ambiguity and make results easier to review.
How should data quality be checked?
Review calibration status, timing, clipping, sensor orientation, signal-to-noise ratio, environmental artifacts, data completeness, and whether the record supports the engineering decision being made.
Related QuakeLogic Resources
- Should You Use Acceleration or Velocity Data for Earthquake Monitoring?
- Understanding OCTAVE Analysis and Vibration Data Analysis
- A Guide to MASW and ESPAC Surveys: Techniques, Equipment, and Software Solutions
- Galperin vs Orthogonal Seismometer Configurations: What’s the Difference and Why It Matters?
- Related QuakeLogic products and technologies
- QuakeLogic Engineering Blog topic resources
References
Recommended Diagram or Download
Media placeholder: Add an original diagram showing the measurement chain from sensor or test platform to data acquisition, analysis, engineering interpretation, and reporting. Where this article becomes a buyer guide or application note, create a downloadable PDF version after engineering review.
Discuss a Monitoring or Testing Application
QuakeLogic supports seismic monitoring, earthquake early warning, structural health monitoring, infrasound monitoring, vibration monitoring, data acquisition, and shake table testing applications. For project-specific guidance, contact QuakeLogic with the asset type, measurement objective, site constraints, and required deliverables.


