Web Services

Station Map (stationView)

URL: stationView


See here for a desription of the “Quality parameters” in the stationView web application.


Please note that your Raspberry Shake’s geolocation information will only be used by the automatic earthquake processing system and will not be exposed to the broader community. On the StationView map, for example, we have implemented an algorithm for security that takes your Shake’s location and randomizes it to another location within 1 mile of its actual location.

Earthquake Map (EQView)

URL: eqView


EQView is a map of global earthquake solutions generated using the Raspberry Shake network.

This means that YOU are now your own source of earthquake solutions.

The denser the network, the faster and more accurate the earthquake solutions. So please help us spread the word.

Mobile App: EQInfo

Visualize your Raspberry Shake’s data on gempa GmbH’s EQInfo mobile app!:


Download EQInfo from Google Play


Currently only available for Android users.


Released: March, 2018 (beta)

URL: sound.raspberryshake.net

Earthquake example: As recorded by Raspberry Shake

Rocket launch example: Feb, 2018 SpaceX Falcon Heavy from 10 km away, as recorded by the Raspberry Boom

What it does:

raspishake2sound generates a video showing the waveform and spectrum together and converts the waveform to the audible frequency range of the human ear.

Note that the audible frequency range of the human ear is 20 - 20,000 Hz and most earthquake energy is in the roughly 0.8 to 5 Hz range, or well below what is audible.

Output format: MP4

How is an earthquake/ waveform converted to sound?:

What you hear is the normalized samples of the input trace, fed to the sound card with a higher sampling rate. In a way, you indeed listen to the earthquake.

Technical details: Samples of the input trace are 1) normalized (max.value becomes 1, other samples scaled accordingly); 2) written to a MP4 file with a new sampling rate (more on this below); and 3) this MP4 file is amplified by 10 dB and re-sampled to some standard audio sampling rate like 44100Hz. The new sampling rate from step 2) is determined as follows: input sampling rate is just multiplied by 140. This makes a trace recorded at 50 Hz (SHZ channels) become a sound sampled at 7000 Hz (quite audible), and a trace recorded at 100 Hz (EH?/EN? channels) become a sound with a 14000 Hz sampling rate. Because the number of samples remain the same, the MP4 file becomes 140 times shorter than the input trace. For example, 900s of input trace becomes ~6.4s of audio.

Re-sampling summary:

  • Normal: 50 Hz becomes sound sampled at 7000 Hz
  • Twice as slow: 50 Hz >> 3500 Hz
  • Four times as slow: 50 Hz >> 1750 Hz

How is event list populated?:

global events fetched: M6.5+ in last month

regional events fetched: M4.5+ in last month within 5 degrees of station, where 1 degree = ~112.5 km

local events fetched: any event within 1 degree of station, last month

The same events are returned as are available at EQInfo and EQView.

This is not configurable, but you can always enter the event time below if you want to look at an event that does not appear in the list.

Table Of Contents