# EIDA routing client

**URL:** <https://discourse.obspy.org/t/eida-routing-client/826>\
**Category:** Users Mailing List Archive\
**Tags:** archive\
**Created:** [March 18, 2019, 10:19am UTC](https://discourse.obspy.org/t/eida-routing-client/826 "2019-03-18T10:19:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Florian\_Fuchs](https://discourse.obspy.org/letter_avatar_proxy/v4/letter/f/858c86/32.png) [@Florian\_Fuchs](https://discourse.obspy.org/u/Florian_Fuchs)\
**Post date:** [March 18, 2019, 10:19am UTC](https://discourse.obspy.org/t/eida-routing-client/826/1 "2019-03-18T10:19:55Z")

</div>

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  
[https://www.obspy.org](https://www.obspy.org)  
Sending institution: ObsPy FDSN Routing 1.1.1  
Contains:  
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: 1.1.40.3  
[http://webservices.ingv.it/fdsnws/station/1/query?channel=HHZ&endti](http://webservices.ingv.it/fdsnws/station/1/query?channel=HHZ&endti)…  
Sending institution: SeisNet-mysql (INGV-CNT)  
Contains:  
Networks (1):  
IV  
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!

Best,  
Florian

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ 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](http://imgw.univie.ac.at) \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

---

<div class="post-metadata">

**Author:** ![Florian\_Fuchs](https://discourse.obspy.org/letter_avatar_proxy/v4/letter/f/858c86/32.png) [@Florian\_Fuchs](https://discourse.obspy.org/u/Florian_Fuchs)\
**Post date:** [March 19, 2019, 4:08pm UTC](https://discourse.obspy.org/t/eida-routing-client/826/2 "2019-03-19T16:08:08Z")

</div>

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?

Best,  
Florian

---

<div class="post-metadata">

**Author:** ![megies](https://discourse.obspy.org/user_avatar/discourse.obspy.org/megies/32/9_2.png) [@megies](https://discourse.obspy.org/u/megies)\
**Post date:** [March 19, 2019, 4:53pm UTC](https://discourse.obspy.org/t/eida-routing-client/826/3 "2019-03-19T16:53:04Z")

</div>

Hi Florian,

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

cheers,  
Tobias