Webservices Usage Examples

Webservices are the easiest way to download data from ORFEUS EIDA and requests are resolved from URLs that return data. They can be invoked by your browser, a command line tool, or automatically through software package like ObsPy and fdsnws_fetch. Data can be requested by querying the webservice with a standardized syntax. Each call consists of the webservice address followed by a service label and finalized by one or more option-value pairs that represent the request options that are initialized by a question mark.

https://webservice-address/label?option=value&option2=value2

FDSNWS-Dataselect must be used to download waveform data. This example requests raw waveform data between 2014-01-01T00:20:00 and 2014-01-01T00:50:00 for station FR.RENF from EIDA node RESIF. The response will be a single mSEED file that contains all streams that fit this request. The output streams are limited to the contacted nodes' data holdings.

Stations that belong to other networks may need to be downloaded from another data center (ref:Routing).

Alternatively, data can be downloaded using the EIDAWS-Federator web service. In this case user does not need to know which data center holds the desired waveforms.

Station metadata can be retrieved using FDSNWS-Station. This example requests station metadata from EIDA node NOA for stations within 0.7° arc-distance of 40°N, 23°E. The response will be a stationXML file with stations located in the selected area. Note that this request will only return stations within the data holdings of the respective node.

Alternatively, station metadata and instrument response can be requested for stations or networks.

Stations that belong to other networks may need to be downloaded from another data center (ref:Routing).

The EIDAWS-Federator web service can be used to browse entire EIDA metadata inventory in a single request. Following request will return metadata of stations located within arc-distance of 42.645°N, 18.016°E (Dubrovnik), hosted by INGV, NOA and NIEP.

Use FDSNWS-Availability to see data available at given datacenter. Following example requests data availability for network NA in January 2023 at node ODC. The query method provides list of all avaiable segments while extent groups them using mergegaps parameter (defaults to 0 seconds).

Use EIDAWS-Routing when unsure about what EIDA node holds the networks or stations you are interested in. Requesting dataselect (i.e. raw waveform data) routing information for network GE. The response is a JSON file that tells you this particular network belongs to GFZ and the waveform data can be retrieved from the returned webservice URL.

The EIDAWS-WFCatalog holds information on waveform metadata. This example requests waveform metadata from ODC between 2014-06-01 and 2014-06-03 for station NL.HGN excluding all streams with gaps. The response is a JSON file containing metadata documents for daily streams that pass the gapless criteria.

Alternatively, waveform metadata can be downloaded using the EIDAWS-Federator web service. In this case user does not need to know which data center holds the desired waveforms.


See the Advanced Workflow Examples page or the ORFEUS EIDA Webservices Notebook for a more extensive explanation on how to use the webservices.