Skip to content

Commit

Permalink
Obspy versions previous to 1.1.1 could include a bug
Browse files Browse the repository at this point in the history
  • Loading branch information
javiquinte committed Apr 29, 2019
1 parent 9fd8c94 commit a383d10
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Expand Up @@ -24,6 +24,8 @@ In the following example the RoutingClient from Obspy is used to access data fro

It is highly recommended to use **always** the token with the client. Even if you are requesting open data. That prevents errors like not providing a token due to a misunderstanding about the data being open/restricted. And on the other hand it helps data centres to understand better user needs by means of more detailed statistics.

`Warning: Some issues have been detected with Obspy version 1.1.0 and previous`

>>> from obspy.clients.fdsn import RoutingClient
>>> from obspy import UTCDateTime

Expand All @@ -39,8 +41,6 @@ It is highly recommended to use **always** the token with the client. Even if yo

Z3.A216A.00.HHZ | 2016-03-01 - 2016-03-01T00:02:00.000000Z | 100.0 Hz, 12001 samples

..warning:: Some issues have been detected with Obspy version 1.1.0 and previous.

In the case that this does not work you can always turn on the debugging at the moment of the client creation

>>> rsClient = RoutingClient("eida-routing", debug=True, credentials= ...)
Expand Down

0 comments on commit a383d10

Please sign in to comment.