FOR RESEARCHERS AND TEACHERS

What you can do with the data.

Every station on the network streams continuously. The waveforms, the metadata and the event catalogue are all open. This page is the honest version — what is available, how to reach it, and what it is not good for.

Live waveform stream (SeedLink)

Four channels per station, served by RingServer 4.5.4 (SeedLink 4.0, 3.1 compatible).

seedlink.geoshake.org:18000

A station appears here once it has been online long enough to fill its buffer.

Using GeoShake with jAmaSeis

jAmaSeis is free seismograph software from IRIS, widely used in classrooms. It has no GeoShake preset, but our stream is a standard SeedLink feed, so it connects through an existing source type.

1. Add a new station and choose the Raspberry Shake source type.
2. Enter the host and port above.
3. Pick a station from the list and start the stream.

Use the LNZ channel for classroom work — it runs continuously, so there is always a trace to look at. ENZ, EN1 and EN2 only carry data during a trigger.

Station metadata (FDSN)

Station, channel and response metadata in StationXML 1.1, through the standard FDSN web service. level=response returns a nominal, datasheet-derived sensitivity, not a per-unit calibration.

https://api.geoshake.org/fdsnws/station/1/

Event catalogue in QuakeML 1.2, through the same standard service. It is empty today (HTTP 204): an origin is published only once at least three stations associate the same event, and our station density does not yet support that.

https://api.geoshake.org/fdsnws/event/1/

Licence and citation

Seismic data is CC BY 4.0 — free to use, redistribute and build on, with attribution.

10.5281/zenodo.21313786 — GeoShake Community Seismic Event Catalog

Cite the concept DOI. It always resolves to the newest version of the catalogue, so a citation written today keeps working as the dataset grows. For a fixed snapshot, cite the version DOI instead.

The PCB design and the cloud backend are proprietary. We say so plainly, because "open source hardware" would not be true and the people who care about that distinction are exactly the people who would check.

Before you use this for research

Being straight about what this network is not is what makes the rest of it credible.

• Not an official warning system. GeoShake is a community network, not a civil-protection service. Do not rely on it for life-safety decisions.
• Sensors are uncalibrated MEMS accelerometers. The instrument response we publish is a nominal datasheet sensitivity (LSM6DSO, ±2 g, 16-bit), not a per-unit calibration: no shake-table calibration, no coupling correction, no poles/zeros. Amplitudes are indicative, not metrologically traceable.
• "Magnitude" in our QuakeML is a PGA-derived MMI intensity, labelled as such in the file. It is not a seismic magnitude, and there is no depth estimate.
• Channel and response metadata are published. level=channel and level=response are supported. Each channel carries a <Description> stating exactly what the samples are — read it before you process anything; LNZ in particular is a one-second peak of |vertical acceleration| — gravity-referenced and unsigned (no polarity), not a signed component; before 10 September 2026 it was a direction-less vector magnitude, and stations still on that definition carry a TRANSITIONAL comment in StationXML until they update.
• The horizontals have no azimuth. EN1/EN2 carry Dip 0 but no Azimuth: the devices have no magnetometer, so the horizontals are orthogonal but their bearing is unknown. Do not rotate them into north/east; that information does not exist in this dataset.
• Elevation is a DEM value, not a survey. Station elevations are sampled from a digital elevation model at the reported coordinates; where unknown, 0 is published and the station comment says so.
• Station codes are identical across services. StationXML, SAC and SeedLink all report the same code — BH2JN everywhere — since 28 August 2026. If you cached inventory before that date, re-fetch it: the inventory used a longer form (GEOBH2JN) and two stations were renumbered to satisfy the ISC letter-first rule (274YU → G274Y, 2TRS8 → G2TRS).
• Coordinates are chosen by station owners, who are asked to drop the pin near their home rather than at their exact address. Positions are approximate by design, for resident privacy.
• Some stations are community builds. Stations shown as Community build are self-assembled hardware in a self-printed enclosure, sometimes with fewer than four sensors. They join at full network weight, but their noise character can differ from the reference T1 — each such station's StationXML carries a comment saying so. This is context for a noisier trace, not a quality ranking.

Developer portal

REST API documentation with live responses, plus a free API key for the endpoints that need one.