The EIDA routing service is the webservice that routes requests for different services between EIDA nodes. Different networks will be routed to different data centers depending on their respective data holdings.
Making a GET request
Routing information can be extracted from the routing webservices by contacting the webservice address with specific request options inside the URL query. Webservice requests are generally formatted as follows:
Copy the following URL
This request will return EIDA routing information for network GE from ORFEUS Data Center. The response indicates that the dataselect service for network GE is located at GFZ and waveform data can be retrieved at the returned URL.
Making a POST request
A plain-text file containing a selection list can be sent to the service. The contents of this message may contain multiple routes to be resolved. Option-value pairs are indicated once per request at the top of the message followed by a number of lines that contain SEED stream identifiers delimited by a space, followed by the trace starttime and endtime. Empty fields are marked by an asterisk.
NL * * * 2017-02-01T00:00:00 2017-02-01T00:01:00
GE * * * 2017-01-01T00:00:00 2017-01-01T00:01:00
Using wget to POST data
Save the example Request.txt file and use the wget command line tool to complete the request.
wget --post-file request.txt http://www.orfeus-eu.org/eidaws/routing/1/query
This request will return routes to the FDSNWS-Station webservice for networks NL and GE. The response indicates that the metadata for the networks need to be downloaded from different data centers.
A question mark represents a single character, while an asterisk represents zero or more characters. Multiple items may also be retrieved using a comma separated list. SEED identifiers support wildcards and lists.
Times must be specified in the ISO-8601 format (e.g. 2017-01-01T00:00:00 or 2017-01-01) and are assumed to be in UTC