obspy.iris: Use new FDSN web services and retire deprecated services #537

megies · 2013-06-27T12:07:03Z

The IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of their core web services that support access to time series data, related metadata and event parameters. The equivalent DMC services are now deprecated and will be retired, read more on that at http://www.iris.washington.edu/pipermail/webservices/2013-March/000378.html.

The fdsnws-dataselect service returns selected time series in miniSEED format: http://service.iris.edu/fdsnws/dataselect/1/
The fdsnws-station service returns selected station metadata in FDSN StationXML and text formats: http://service.iris.edu/fdsnws/station/1/
The fdsnws-event service returns selected event parameters in QuakeML and text formats: http://service.iris.edu/fdsnws/event/1/

The FDSN web services are available from a dedicated host name with new web documentation: http://service.iris.edu/

Deprecation of equivalent IRIS services

With the release of the FDSN services they are deprecating the equivalent services.

These services will be turned off in approximately 6 months:

ws-bulkdataselect (http://www.iris.edu/ws/bulkdataselect)
ws-dataselect (http://www.iris.edu/ws/dataselect)
ws-station (http://www.iris.edu/ws/bulkdataselect)
ws-event (http://www.iris.edu/ws/event)

Differences between FDSN and the services they are replacing

The FDSN web services return HTTP status code 204 to indicate "No data" as opposed to status code 404 used by the services they are replacing. The behavior of returning a 404 can be restored by including the 'nodata=404' parameter and value in the request.

fdsnws-dataselect is a combination of the capabilities of ws-bulkdataselect and ws-dataselect:

enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
enhancement: the network, station, location and channel selections may contain * and ? wildcards
should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
a near complete replacement for ws-dataselect (accepts GET requests with parameters) except that it does not support the 'ref' parameter and does not support caching in the internal ICAB system.

fdsnws-station is equivalent to ws-station with these important changes:

the XML output is returned as FDSN StationXML, a different schema
new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
the 'output' parameter name is changed to 'format'

The FDSN StationXML schema (http://www.fdsn.org/xml/station/) is generally equivalent to the XML format previously used but it is a distinctly different schema that cannot be parsed with the same software parsing the XML from ws-station.

fdsnws-event is equivalent to ws-event with these differences:

the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
the 'output' parameter name is changed to 'format'
only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
in addition to the default order of descending results, the 'orderby' parameter can be 'time-asc' or 'magnitude-asc' to set the order to ascending.

barsch · 2013-03-28T12:32:01Z

just a rant: we should try to autogenerate our client by using the delivered WADL files (e.g. http://service.iris.edu/fdsnws/event/1/application.wadl ) to keep our clients up-to-date with IRIS - not dynamically on each client run, but once everytime we release a new version of ObsPy

krischer · 2013-04-03T09:13:03Z

+1 for the WADL autogeneration if it is possible. Not sure though. For some query options they only specify the default value and not the possible options. Furthermore they do not seem to use xs:boolean for their flags but a string with either "yes" or "no".

Also they now appear to be using a QuakeML version > 1.0. No version number is included for some reason, but the origin depth unit appears to be meter. Judging from their documentation is appears to be QuakeML 1.2RC3.

celso-iris · 2013-04-03T20:35:35Z

Before committing to using IRIS's WADL, you should know that the WADLs are in flux. More specifically, IRIS would love to hear recommendations for improving our WADLs and making them more useful. If we perfect the WADL that is used to describe our existing FDSN services, then hopefully future FDSN-based services will also provide better WADLs. Each service implementation may vary from each other in some minor way: some query parameters might not be relevant, or some may be augmented.

As a specific example, here the IRIS FDSN event service differs from the spec. in that IRIS offers a format parameter with two options, text and xml. However, the FDSN spec says nothing about format.

Another example might be if a data center doesn't store a particular type of metadata. Then the parameter used to filter upon that data will likely not be implemented. Hopefully a good WADL could be used to determine that ahead of time.

If you have any questions, feel free to contact us, as we would like to help make it easier for ObsPy to interface with the web services. Now that there are FDSN standardized versions of our core services, ObsPy should be able to nearly automatically / seamlessly interface with the equivalent services at other data centers.

Thanks,
Celso

krischer · 2013-04-05T14:34:32Z

Hi Celso,

what is the best way to contact you? It is ok, if we discuss it here?

We are of course interested in being able to automatically access data from centers implementing the FDSN specification. Also if anyone at IRIS is interested in changing parts of obspy.iris feel free to do it and send us a pull request.

I am no expert in WADL and do not know how feasible my suggestions are but they should be valid WADL. From our point of view the following changes would facilitate the autogeneration of code based on your WADLs. It is just a short snippets based on your event WADL.

<request>
  <!--Document the different fields, just done for one example here-->
  <param name="starttime" style="query" type="xs:date">
      <doc xml:lang="english" title="limit to events occurring on or after the specified start time.">
          Example: starttime=2012-11-29T00:00:00
      </doc>
  </param>

  <param name="endtime" style="query" type="xs:date"/>

  <!--Indicate the used default values. Only done for some examples here-->
  <param name="minlatitude" style="query" type="xs:double" default="-90.0"/>
  <param name="maxlatitude" style="query" type="xs:double" default="90.0"/>
  <param name="minlongitude" style="query" type="xs:double" default="-180.0"/>
  <param name="maxlongitude" style="query" type="xs:double" default="180.0"/>

  <param name="minmagnitude" style="query" type="xs:double"/>
  <param name="maxmagnitude" style="query" type="xs:double"/>

  <param name="magtype" style="query" type="xs:string"/>
  <param name="catalog" style="query" type="xs:string"/>
  <param name="contributor" style="query" type="xs:string"/>
  <param name="maxdepth" style="query" type="xs:double"/>
  <param name="mindepth" style="query" type="xs:double"/>
  <param name="latitude" style="query" type="xs:double"/>
  <param name="longitude" style="query" type="xs:double"/>
  <param name="maxradius" style="query" type="xs:double"/>
  <param name="minradius" style="query" type="xs:double"/>
  <param name="orderby" style="query" type="xs:string" default="time"/>
  <param name="updatedafter" style="query" type="xs:date"/>
  <param name="eventid" style="query" type="xs:long"/>
  <param name="originid" style="query" type="xs:long"/>

  <!--Use booleans variables for flags-->
  <param name="includearrivals" style="query" type="xs:boolean" default="false"/>
  <param name="includeallmagnitudes" style="query" type="xs:boolean" default="false"/>
  <param name="includeallorigins" style="query" type="xs:boolean" default="false"/>

  <param name="limit" style="query" type="xs:int" default="1"/>
  <param name="offset" style="query" type="xs:int" default="1"/>
  <param name="output" style="query" type="xs:string" default="xml"/>

  <!--Indicate the available options. Just done for one example here-->
  <param name="format" style="query" default="xml">
   <option value="xml"/>
   <option value="text"/>
  </param>

</request>

Best wishes,

Lion

celso-iris · 2013-04-09T18:13:12Z

Here's an example of a beefed up event wadl. It doesn't match the wadl we have on line yet, but we're working on getting everything synced. Nothing's written in stone yet (it can and probably will change), but how's this for wadl documentation of the FDSN event service?

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<application xmlns="http://wadl.dev.java.net/2009/02">
   <doc title="FDSN event web service 1.0"/>
   <resources base="http://service.iris.edu/fdsnws/event/1/">
      <resource path="/">
         <method id="index" name="GET">
            <response>
               <representation mediaType="text/plain"/>
               <representation mediaType="application/xml"/>
            </response>
         </method>
         <resource path="/counts">
            <method id="counts" name="GET">
               <request>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="starttime" style="query" type="xs:date">
                     <doc xml:lang="english" title="limit to events occurring on or after the specified start time">
                        Examples: starttime=2012-11-29 or 2012-11-29T00:00:00 or 2012-11-29T00:00:00.000
                     </doc>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="endtime" style="query" type="xs:date">
                     <doc xml:lang="english" title="limit to events occurring on or before the specified end time"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="minlatitude" style="query" type="xs:double" default="-90.0">
                     <doc xml:lang="english" title="southern boundary"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxlatitude" style="query" type="xs:double" default="90.0">
                     <doc xml:lang="english" title="northern boundary"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="minlongitude" style="query" type="xs:double" default="-180.0">
                     <doc xml:lang="english" title="western boundary"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxlongitude" style="query" type="xs:double" default="180.0">
                     <doc xml:lang="english" title="eastern boundary"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="minmagnitude" style="query" type="xs:double">
                     <doc xml:lang="english" title="Limit to events with a magnitude larger than or equal to the specified minimum"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxmagnitude" style="query" type="xs:double">
                     <doc xml:lang="english" title="Limit to events with a magnitude smaller than or equal to the specified maximum"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="magtype" style="query" type="xs:string">
                     <doc xml:lang="english" title="type of Magnitude used to test minimum and maximum limits (case insensitive)">
                     Examples: Ml,Ms,mb,Mw"</doc>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="catalog" style="query" type="xs:string" default="NEIC+PDE">
                     <doc xml:lang="english" title="Specify the catalog from which origins and magnitudes will be retrieved"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="contributor" style="query" type="xs:string">
                     <doc xml:lang="english" title="Limit to events contributed by a specified contributor"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxdepth" style="query" type="xs:double">
                     <doc xml:lang="english" title="Limit to events with depths equal to or less than the specified depth"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="mindepth" style="query" type="xs:double">
                     <doc xml:lang="english" title="Limit to events with depths equal to or greater than the specified depth"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="latitude" style="query" type="xs:double" default="0.0">
                     <doc xml:lang="english" title="Specify the central latitude point for a radial search"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="longitude" style="query" type="xs:double" default="0.0">
                     <doc xml:lang="english" title="Specify the central longitude point for a radial search"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxradius" style="query" type="xs:double" default="180.0">
                     <doc xml:lang="english" title="Specify maximum distance from the geographic point defined by latitude and longitude"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="minradius" style="query" type="xs:double" default="0.0">
                     <doc xml:lang="english" title="Specify minimum distance from the geographic point defined by latitude and longitude"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="updatedafter" style="query" type="xs:date">
                     <doc xml:lang="english" title="Limit to events updated after the specified time"/>
                  </param>
                  <!-- <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="output" style="query" type="xs:string" default="xml"/> -->
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="format" style="query" type="xs:string" default="xml">
                     <doc xml:lang="english" title=""/>
                     <option value="xml" mediaType="application/xml"/>
                     <option value="text" mediaType="text/plain"/>
                  </param>
               </request>
               <response>
                  <representation mediaType="text/plain"/>
                  <representation mediaType="application/xml"/>
               </response>
            </method>
         </resource>

         <resource path="/query">
            <method id="query" name="GET">
               <request>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="starttime" style="query" type="xs:date">
                     <doc xml:lang="english" title="limit to events occurring on or after the specified start time">
                        Examples: starttime=2012-11-29 or 2012-11-29T00:00:00 or 2012-11-29T00:00:00.000
                     </doc>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="endtime" style="query" type="xs:date">
                     <doc xml:lang="english" title="limit to events occurring on or before the specified end time"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="minlatitude" style="query" type="xs:double" default="-90.0">
                     <doc xml:lang="english" title="southern boundary"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxlatitude" style="query" type="xs:double" default="90.0">
                     <doc xml:lang="english" title="northern boundary"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="minlongitude" style="query" type="xs:double" default="-180.0">
                     <doc xml:lang="english" title="western boundary"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxlongitude" style="query" type="xs:double" default="180.0">
                     <doc xml:lang="english" title="eastern boundary"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="minmagnitude" style="query" type="xs:double">
                     <doc xml:lang="english" title="Limit to events with a magnitude larger than or equal to the specified minimum"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxmagnitude" style="query" type="xs:double">
                     <doc xml:lang="english" title="Limit to events with a magnitude smaller than or equal to the specified maximum"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="magtype" style="query" type="xs:string">
                     <doc xml:lang="english" title="type of Magnitude used to test minimum and maximum limits (case insensitive)">
                     Examples: Ml,Ms,mb,Mw"</doc>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="catalog" style="query" type="xs:string" default="NEIC+PDE">
                     <doc xml:lang="english" title="Specify the catalog from which origins and magnitudes will be retrieved"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="contributor" style="query" type="xs:string">
                     <doc xml:lang="english" title="Limit to events contributed by a specified contributor"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxdepth" style="query" type="xs:double">
                     <doc xml:lang="english" title="Limit to events with depths equal to or less than the specified depth"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="mindepth" style="query" type="xs:double">
                     <doc xml:lang="english" title="Limit to events with depths equal to or greater than the specified depth"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="latitude" style="query" type="xs:double" default="0.0">
                     <doc xml:lang="english" title="Specify the central latitude point for a radial search"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="longitude" style="query" type="xs:double" default="0.0">
                     <doc xml:lang="english" title="Specify the central longitude point for a radial search"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="maxradius" style="query" type="xs:double" default="180.0">
                     <doc xml:lang="english" title="Specify maximum distance from the geographic point defined by latitude and longitude"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="minradius" style="query" type="xs:double" default="0.0">
                     <doc xml:lang="english" title="Specify minimum distance from the geographic point defined by latitude and longitude"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="orderby" style="query" type="xs:string" default="time">
                     <doc xml:lang="english" title="Specify the ordering of the returned results"/>
                     <option value="time">
                        <doc xml:lang="english" title="Sort by time, descending"/>
                     </option>
                     <option value="magnitude">
                        <doc xml:lang="english" title="Sort by magnitude, descending"/>
                     </option>
                     <option value="time-asc">
                        <doc xml:lang="english" title="Sort by time, ascending"/>
                     </option>
                     <option value="magnitude-asc">
                        <doc xml:lang="english" title="Sort by magnitude, ascending"/>
                     </option>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="updatedafter" style="query" type="xs:date">
                     <doc xml:lang="english" title="Limit to events updated after the specified time"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="eventid" style="query" type="xs:long">
                     <doc xml:lang="english" title="Retrieve an event based on the unique ID numbers assigned by the IRIS DMC"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="originid" style="query" type="xs:long">
                     <doc xml:lang="english" title="Retrieve an event based on the unique origin ID numbers assigned by the IRIS DMC"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="includearrivals" style="query" type="xs:boolean" default="false">
                     <doc xml:lang="english" title="Specify if phase arrivals should be included"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="includeallmagnitudes" style="query" type="xs:sboolean" default="false">
                     <doc xml:lang="english" title="Retrieve all magnitudes for the event, or only the primary magnitude from within the catalog"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="includeallorigins" style="query" type="xs:boolean" default="false">
                     <doc xml:lang="english" title="Retrieve all origins or only the primary origin associated with each event in a catalog"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="limit" style="query" type="xs:int">
                     <doc xml:lang="english" title="Limit the results to the specified number of events"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="offset" style="query" type="xs:int" default="1">
                     <doc xml:lang="english" title="Return results starting at the event count specified"/>
                  </param>
                  <!-- <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="output" style="query" type="xs:string" default="xml"/> -->
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="format" style="query" type="xs:string" default="xml">
                     <doc xml:lang="english" title="Specify output format. This is an IRIS extension to the FDSN specification"/>
                     <option value="xml" mediaType="application/xml"/>
                     <option value="text" mediaType="text/plain"/>
                  </param>
                  <param xmlns:xs="http://www.w3.org/2001/XMLSchema" name="nodata" style="query" type="xs:int" default="204">
                     <doc xml:lang="english" title="Specify which HTML Status code is returned when no data is found. This is an IRIS extension to the FDSN specification"/>
                     <option value="204"/>
                     <option value="404"/>
                  </param>
               </request>
               <response>
                  <representation mediaType="text/plain"/>
                  <representation mediaType="application/xml"/>
               </response>
            </method>
         </resource>
         <resource path="/version">
            <method id="version" name="GET">
               <response>
                  <representation mediaType="text/plain"/>
               </response>
            </method>
         </resource>
         <resource path="/catalogs">
            <method id="catalogs" name="GET">
               <response>
                  <representation mediaType="application/xml"/>
               </response>
            </method>
         </resource>
         <resource path="/contributors">
            <method id="contributors" name="GET">
               <response>
                  <representation mediaType="application/xml"/>
               </response>
            </method>
         </resource>
      </resource>
   </resources>
</application>

krischer · 2013-04-16T13:42:29Z

Hi Celso,

this look very good in my opinion and should enable us to query the webservice without specifying every option by hand. We might encounter more subtle problems as soon as we start working on an implementation.

@barsch: Right now I would actually prefer to create a generic FDSN webservice that is able to query all datacenters providing one. The corresponding WADL can be downloaded on-the-fly during client initialization.

@celso-iris: I am currently working on StationXML support for ObsPy and noticed that the returned StationXML files do not validate against the schema. This should require only some very minor changes. Examples:

The QuakeML files are fine :)

barsch · 2013-04-16T13:46:56Z

@krischer: obspy.fdsn is definitively the way to go - I wanted to propose that anyway ;)

krischer · 2013-04-16T13:48:54Z

+1

Orfeus is AFAIK currently also working on an implementation.

megies · 2013-04-17T20:59:06Z

@krischer: did you validate requested QuakeML files against the official schemas/relaxNG? So far, those accepted a lot that was not conform with the UML/pdf documentation, from my experience...

megies · 2013-06-23T11:59:09Z

Was thinking about starting work on this at some point. Just to make sure, this is supposed to go into a new module obspy.fdsn and the client should basically take an url at initialization which will default to the IRIS ws for now. Did I get this right?

celso-iris · 2013-06-25T02:25:21Z

@megies : That sounds correct to me.
You might like to know that the USGS has their version of the FDSN event webservice up and running now.

http://comcat.cr.usgs.gov/fdsnws/event/1/
http://comcat.cr.usgs.gov/fdsnws/event/1/application.wadl

and RESIF has data and metadata services up and running:

http://ws.resif.fr/

These might be a good places to try alternate URLs. The USGS happens to have many extensions to the FDSN spec. I don't know how you might handle it. In the IRIS-WS java library, we added an "add" routine to the EventCriteria object that takes an arbitrary string pair, and adds the results to the query url.

krischer · 2013-06-25T07:43:46Z

I would suggest that we directly parse the WADL files upon client instantiation. We could also provide some kind of mapping for known services.

Something like this might work:

WADL_MAPPINGS = {
    "IRIS": "url to iris wadl",
    "USGS": "url to usgs wadl",
    "RESIF": "url to resif wadl",
    ...
}


class Client(object):
    def __init__(self, WADL):
        if WADL in WADL_MAPPINGS:
            self._parse_wadl(WADL_MAPPINGS[WADL])
        else:
            self._parse_wadl(WADL)


# Usage
from obspy.fdsn import Client
c = Client("IRIS")
...

megies · 2013-06-25T08:10:03Z

I thought we consented to not using WADL in the initial implementation?

edit: talked with @krischer, should probably parse the wadls right from the start..

Now maps the short names of the parameters to their proper long names when necessary. Furthermore a dynamic help function for the different services is now available.

Added a sensible exception in case no services are being discovered at the chosen endpoint.

be removed again, when IRIS updates the event WADL (and after updating data/event.wadl)

tests were running fine when executing the corresponding test. tests were only failing with `obspy-runtests fdsn` because of prior warnings.

@deprecated

also fixed @deprecated's kwarg see http://stackoverflow.com/questions/5929107/python-decorators-with-parameters

megies · 2013-10-04T11:28:23Z

I'm OK with merging this. Open points are tracked in #646.

krischer · 2013-10-04T12:25:18Z

@celso-iris I found a small bug: The event HTML page does not describe the originid parameter, but the WADL does.

Now only print derivations from the standard. Also some minor other changes.

ObsPy now has support for the FDSN webservices.

megies mentioned this pull request Mar 28, 2013

iris.client.getWaveform: use station WS + location code wildcard handling #486

Closed

megies and others added 16 commits June 27, 2013 14:04

fdsn: setting up new submodule basic structure

1355390

fdsn: add key for new FSDN webservice at NCEDC

51fcd7b

fdsn: docstring for previous commit

30add1f

Merge remote branch 'upstream/obspy.fdsn' into obspy.fdsn

0a0c9f2

URL building for the FDSN submodule.

2f72963

Added WADL file downloading.

b216978

Added WADL parser including tests.

27e0be7

Merge remote-tracking branch 'upstream/master' into obspy.fdsn

03049dd

Done with WADL parsing.

dbf02ce

Now maps the short names of the parameters to their proper long names when necessary. Furthermore a dynamic help function for the different services is now available.

Two more WADL files with no given types.

0f627cc

WADL parser can now deal with parameters without types.

4594d7e

Special handling for the USGS event WADL.

e919eb9

Improved error handling.

3696988

Added a sensible exception in case no services are being discovered at the chosen endpoint.

WADL parser now warns if some parameters are missing.

3f7ace4

Updated license notes.

0aaef2d

Finished service specific help string.

e9c9dac

megies and others added 9 commits October 4, 2013 09:41

fdsn: fix a test that fails due to an issue with IRIS event WADL, should

ef4b5a3

be removed again, when IRIS updates the event WADL (and after updating data/event.wadl)

fdsn: fix failing tests

5e4fde2

tests were running fine when executing the corresponding test. tests were only failing with `obspy-runtests fdsn` because of prior warnings.

fdsn: change args order to match all other clients in get_waveform()

c36316d

fdsn: get_waveform tests

d58a562

fdsn: docstrings/examples/frontpage

658fec1

fdsn: deprecation warnings in obspy.iris

e54bf7b

also fixed @deprecated's kwarg see http://stackoverflow.com/questions/5929107/python-decorators-with-parameters

Updating the IRIS event WADL.

733f54c

IRIS fixed the bug. Remove workaround.

2b0d9ce

Merge remote-tracking branch 'upstream/obspy.fdsn' into obspy.fdsn

5afd537

megies mentioned this pull request Oct 4, 2013

obspy.fdsn TODO list #646

Closed

7 tasks

pep8

2ffe4d6

megies and others added 14 commits October 4, 2013 14:34

fdsn: test that conflicts in parameters raise

4e32a8d

fdsn: raise on conflicting parameters in queries

cecb7dd

minor refactoring

39a7517

gaah, pep8 for previous commit

e836a36

fdsn: IRIS service discovery test.

b225d7f

Added tests for contributor and catalog availability

d9b4545

Manual merging

b5b39a0

Fix the tests

2826071

Automatic downloading of catalogs and contribs

2dc841c

Adjusting test to changes

a1835f1

Better exception handling

7219732

Adding both to the help() method

a1d22ec

Modified help method.

b0d8d2c

Now only print derivations from the standard. Also some minor other changes.

Added test for the help() method

71e5efd

krischer added a commit that referenced this pull request Oct 4, 2013

Merge pull request #537 from obspy/obspy.fdsn

ff05839

ObsPy now has support for the FDSN webservices.

krischer merged commit ff05839 into master Oct 4, 2013

mbyt deleted the obspy.fdsn branch February 16, 2014 12:34

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

obspy.iris: Use new FDSN web services and retire deprecated services #537

obspy.iris: Use new FDSN web services and retire deprecated services #537

megies commented Jun 27, 2013

barsch commented Mar 28, 2013

krischer commented Apr 3, 2013

celso-iris commented Apr 3, 2013

krischer commented Apr 5, 2013

celso-iris commented Apr 9, 2013

krischer commented Apr 16, 2013

barsch commented Apr 16, 2013

krischer commented Apr 16, 2013

megies commented Apr 17, 2013

megies commented Jun 23, 2013

celso-iris commented Jun 25, 2013

krischer commented Jun 25, 2013

megies commented Jun 25, 2013

megies commented Oct 4, 2013

krischer commented Oct 4, 2013

obspy.iris: Use new FDSN web services and retire deprecated services #537

obspy.iris: Use new FDSN web services and retire deprecated services #537

Conversation

megies commented Jun 27, 2013

Deprecation of equivalent IRIS services

Differences between FDSN and the services they are replacing

barsch commented Mar 28, 2013

krischer commented Apr 3, 2013

celso-iris commented Apr 3, 2013

krischer commented Apr 5, 2013

celso-iris commented Apr 9, 2013

krischer commented Apr 16, 2013

barsch commented Apr 16, 2013

krischer commented Apr 16, 2013

megies commented Apr 17, 2013

megies commented Jun 23, 2013

celso-iris commented Jun 25, 2013

krischer commented Jun 25, 2013

megies commented Jun 25, 2013

megies commented Oct 4, 2013

krischer commented Oct 4, 2013