EIDA routing client

Dear ObsPy team,

there seems to be some issue with the EIDA fdsn routing client. Using the routing client I cannot access any metadata that is hosted at INGV. Using the normal/direct fdsn client and specifying ‘INGV’ it works, though.

from obspy.clients.fdsn import RoutingClient
from obspy.clients.fdsn import Client

from obspy import UTCDateTime

routed = RoutingClient(‘eida-routing’)
direct = Client(‘INGV’)

start = UTCDateTime(‘2016-01-01T00:00:00’)
end = UTCDateTime(‘2018-12-31T00:00:00’)

routed.get_stations(network='IV, starttime=start, endtime=end)

Inventory created at 2019-03-18T10:16:53.943659Z
Created by: ObsPy 1.1.1
Sending institution: ObsPy FDSN Routing 1.1.1
Networks (0):

Stations (0):

Channels (0):

direct.get_stations(network=‘IV’, starttime=start, endtime=end)

Inventory created at 2019-03-18T10:18:04.000000Z
Created by: INGV-CNT WEB SERVICE: fdsnws-station | version:
Sending institution: SeisNet-mysql (INGV-CNT)
Networks (1):
Stations (267):
IV.ACER (Acerenza)
IV.AGLI (Aglientu)
IV.AIO (Antillo, Italy)
IV.ALJA (Alia)

… …

Specifying more/less station/channel/location info does not change the behaviour.

Can you have a look into this? Thanks!


_____________________________________ Dr. Florian Fuchs Department of Meteorology and Geophysics University of Vienna UZA II, 2D508 Althanstraße 14 1090 Vienna Austria Phone: +43 1 4277 53726 Mobile: +43 664 60277 53726 www: http://imgw.univie.ac.at _____________________________________

Hi again,

meanwhile I was able to narrow it down: When specifying the level of the request (e.g. level=‘channel’), everything works. Without specifying the level the routing client does not work. Not sure if this behaviour is wanted … maybe some default behaviour should be set when no level is specified?


Hi Florian,

this indeed seems to be a bug, can you open a ticket on github for it? Thanks!