Reference · built on requestCommons signalEarth, seismic & volcanic

KNMI Earthquake Catalogue

Induced and tectonic earthquakes in and around the Netherlands from the KNMI catalogue, as JSON, CSV, KML, RSS, and an FDSN event service.

About

The Royal Netherlands Meteorological Institute keeps the earthquake catalogue of the Netherlands and publishes it as two lists: induced earthquakes, and tectonic earthquakes in and around the country. Each list comes as JSON, CSV, KML, and PDF from rdsa.knmi.nl, with an RSS feed of the latest 30 events of either kind. The same catalogue sits behind an FDSN event web service on a SeisComP back end, which returns QuakeML, text, CSV, or JSON and also carries sonic booms and quarry explosions. KNMI updates the files automatically when a new earthquake is published.

An operator on Fibric watches the feed for events near your Dutch sites and proposes an inspection, a welfare check, or an incident draft for your approval.

This is a reference listing. It documents what Fibric would read from KNMI Earthquake Catalogue and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Induced earthquakes from abcws/event/query?eventtype=induced as JSON, CSV, KML, or PDF, with date, time, place, lat, lon, depth, and mag
  • Tectonic earthquakes in and around the Netherlands from the same query with eventtype=tectonic
  • The latest 30 events of both kinds from the RSS feed, each with geo:lat, geo:lon, and a knmi event id as guid
  • Events from fdsnws/event/1/query filtered by time, box or radius, depth, magnitude, and eventtype, as xml, text, csv, or json
  • Whether an event was located automatically or reviewed by an analyst, from evaluationMode in the files and the Analyse column on the list
  • Municipality-based place names since 1 December 2016; the earlier catalogue used the nearest town, and KNMI publishes a list of revised names

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Inspect buildings near an induced event

    When a reviewed induced earthquake above your magnitude floor falls inside the radius you set around a property, the operator drafts an inspection with the knmi event id and place name for your approval.

    With Inspection Scheduling

  • Check on staff working alone nearby

    The operator lists lone workers on site within the radius at the event time and proposes a welfare check, quoting the magnitude and depth from the feed.

    With Lone Worker

  • Open an incident record for the site log

    For an event that trips your threshold, the operator drafts an incident entry with the catalogue fields and the automatic-or-reviewed status, ready for you to approve or discard.

    With Incident Draft

Requirements

  • Site coordinates for a radius or bounding-box filter on the FDSN service, or a client that filters the whole JSON file itself
  • A magnitude floor and a choice of event types; the feeds mix induced and tectonic earthquakes with sonic booms and explosions
  • Attribution to KNMI with the event service DOI 10.21944/ef5j-rz10, as the citation section asks
  • A place-name map that allows for the December 2016 switch from nearest town to municipality
Authentication
None. The catalogue files, the RSS feed, and the FDSN event service are open over HTTPS without a key or account.

Limits

  • The FDSN service does not implement updatedafter or catalog; contributor maps to the SeisComP agencyID
  • The catalogue files are whole-list downloads; the dataset page documents eventtype, format, and limit and no incremental parameter
  • The terms of use say data cannot be reused in unaltered form for commercial use; read that clause before republishing the list
  • Neither the dataset page nor the service states how soon after an event a record appears or moves from automatic to reviewed

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request KNMI Earthquake Catalogue ↗

Questions and answers

Which formats does the catalogue come in?
The dataset page links JSON, CSV, KML, and PDF files for induced and for tectonic events, plus an RSS feed of the latest 30 events. The FDSN event service adds xml (QuakeML), text, qml-rt, sc3ml, csv, and json through its format parameter.
Does the service support updatedafter?
No. The KNMI feature notes say updatedafter is not implemented because SeisComP tracks modification time per object and would have to evaluate all children recursively. The catalog parameter is also not implemented, and contributor maps to agencyID.
What licence applies?
The event service page states the data is Open Data under Creative Commons Attribution 4.0 International, with a request to cite KNMI and the DOI 10.21944/ef5j-rz10. Its terms of use also say the data cannot be reused in unaltered form for commercial use.
Ask about KNMI Earthquake Catalogue

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.