Reference · built on requestCommons signalEarth, seismic & volcanic

ORFEUS EIDA

Seismic waveforms, station metadata, and data-quality metrics from the European Integrated Data Archive's FDSN web services.

Request accessPricing ↗

About

EIDA, the European Integrated Data Archive, is an initiative within ORFEUS: a distributed federation of data centres that archive seismic waveform data and metadata gathered by European research infrastructures. The web services page lists thirteen nodes: ODC, GFZ, EPOS-FR, INGV, ETHZ, BGR, NIEP, KOERI, LMU, NOA, UIB-NORSAR, ICGC, and BGS. Each node runs FDSN standard web services for waveforms, station metadata, and availability, plus EIDA services for routing, waveform metadata, and power spectral density. The Federator at federator.orfeus-eu.org answers one request across all holdings, whichever node curates the data.

Through Fibric, an operator reads station metadata and availability near your sites, pulls the waveform window around a felt event, and proposes the ticket or annotation for your approval.

This is a reference listing. It documents what Fibric would read from ORFEUS EIDA 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

  • Waveforms in mSEED from fdsnws/dataselect/1/query by network, station, location, channel, starttime, and endtime
  • Station and channel metadata as StationXML from fdsnws/station/1/query, at network, station, channel, or response level
  • Data availability from fdsnws/availability/1/query and /extent, as text, geocsv, or request format
  • Which node holds which network from eidaws/routing/1/query, returned as xml, json, get, or post
  • Waveform quality metrics from eidaws/wfcatalog/1/query: gaps, overlaps, availability, timing quality, and header flags, as JSON
  • One request across every node through the Federator: station, dataselect, availability, and wfcatalog
  • Network listings with FDSN code, restricted flag, node, and DOI on the EIDA networks page

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

  • Confirm ground motion before a vibration ticket

    When floor or machine vibration sensors trip together, the operator pulls the dataselect window from the nearest station and attaches it before proposing any maintenance ticket.

    With Sensor Health

  • Check data gaps before you trust a station

    The operator reads fdsnws/availability and the wfcatalog gap metrics for the stations you rely on and flags the ones with holes in the last window.

    With Data Freshness

  • Sort an alarm burst after a felt event

    After alarms flood in across a site, the operator checks station waveforms for shaking at that minute and proposes grouping the alarms under one event for your approval.

    With Alarm Triage

Requirements

  • The FDSN network and station codes, or coordinates with a radius, for the stations you care about
  • A token from the EIDA Authentication Service for any restricted network, valid for 1 day to 1 month as you choose
  • Citation of each network's DOI, with the network name or code, in anything you publish
  • A plan for large requests: a Federator call waits for the slowest contributing node
Authentication
No key for open networks. Restricted data need a token from the EIDA Authentication Service at geofon.gfz-potsdam.de/eas, issued after login with an institutional ID via eduGAIN or a B2ACCESS account.

Limits

  • The Federator serves only non-restricted waveform data and does not support authentication by tokens
  • HTTP response codes from the Federator may be misleading when one node's subtask fails
  • The dataselect spec lists starttime, endtime, network, station, location, channel, quality, format, and nodata; there is no event query
  • EIDA data are free of use but cannot be reused in unaltered form for commercial use

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 ORFEUS EIDA ↗

Questions and answers

Which EIDA service should you call when you do not know which node holds the data?
Use the Federator at federator.orfeus-eu.org, which returns all data using a single request independently of which data centre curates it, or call eidaws/routing/1/query, which returns the node that serves a given network and service.
How do you get restricted EIDA data?
Obtain a token from the EIDA Authentication Service. Log in with an institutional ID through eduGAIN or register a B2ACCESS account, choose a validity from 1 day to 1 month, and use the token with the node's web services. The Federator does not accept tokens.
How must EIDA data be cited?
Cite each network like a research article: a short reference in the text and a long reference in the reference list, using the network DOI where available. Acknowledgement of ORFEUS and EIDA is also appreciated.
Ask about ORFEUS EIDA

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by ORFEUS European Integrated Data Archive (orfeus-eu.org, federator.orfeus-eu.org). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy