Thread: New FDSN web services and retirement of deprecated services

Started: March 27, 2013, 1:43 p.m.
Last activity: Dec. 21, 2013, 12:47 p.m.
Topics: Web Services
Chad Trabant
March 27, 2013, 1:43 p.m.

Hello web services users,

We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


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/

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

Comments, feedback and questions are welcome.


== Transitioning clients to the FDSN services

The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

http://service.iris.edu/clients/

The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


== Deprecation of equivalent IRIS services

With the release of our FDSN services we are deprecating the equivalent services.

These services will be turned off in approximately 6 months:

ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
ws-dataselect (www.iris.edu/ws/dataselect)
ws-station (www.iris.edu/ws/bulkdataselect)
ws-event (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:
1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
4) 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:
1) the XML output is returned as FDSN StationXML, a different schema
2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
3) 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:
1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
2) the 'output' parameter name is changed to 'format'
3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
4) 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.

IRIS Web Services team






  • Chad,

    It's great to see that you have the new FDSN web services up and running and Russ is already using them in the new version of IEB that he is working on. I've been trying it out via IEB and also the URL builder, and I've got a couple of questions.

    1. The default NEIC PDE catalog only goes back to 1990, but on the USGS site, the PDE catalog goes back to 1973 ( http://earthquake.usgs.gov/research/data/pde.php or http://earthquake.usgs.gov/earthquakes/eqarchives/epic/ ). Is there any chance of adding the earlier years? This would make IEB much more useful.

    2. I understand you are aware that selecting another catalog slows the search down such that it can take minutes in some cases, which might be okay for some uses but it means the ISC catalog couldn't be selected for use in IEB, which was something David was hoping for (as long as it is the reviewed bulletin). Do you think it will be possible to speed up the use of other catalogs?

    Thanks for your help,

    John

    On Mar 27, 2013, at 4:43 PM, Chad Trabant wrote:


    Hello web services users,

    We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

    The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

    These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


    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/

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

    Comments, feedback and questions are welcome.


    == Transitioning clients to the FDSN services

    The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

    http://service.iris.edu/clients/

    The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


    == Deprecation of equivalent IRIS services

    With the release of our FDSN services we are deprecating the equivalent services.

    These services will be turned off in approximately 6 months:

    ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
    ws-dataselect (www.iris.edu/ws/dataselect)
    ws-station (www.iris.edu/ws/bulkdataselect)
    ws-event (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:
    1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
    2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
    3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
    4) 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:
    1) the XML output is returned as FDSN StationXML, a different schema
    2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
    3) 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:
    1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
    2) the 'output' parameter name is changed to 'format'
    3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
    4) 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.

    IRIS Web Services team





    _______________________________________________
    webservices mailing list
    webservices<at>iris.washington.edu
    http://www.iris.washington.edu/mailman/listinfo/webservices



    • Hi John,

      Regarding 1) if you follow the links on the first page you indicate you will find that the actual earliest data is more recent and dependent on the format (ehdf goes back to 1990, mchedr goes to 1981, ISF goes to 1990 and manuscript goes to 1994); what we loaded happens to only go back to 1990 unfortunately. This issue was moot when we were mixing the solutions from the ISC and PDE.

      We are considering an alternative approach of allowing the default catalog to change depending on the availability of catalog coverage. In particular, the default catalog for older events would be ISC and if it is not present the default would be NEIC PDE. This would be done without mixing information from different catalogs for any single event, but allow retrieval of information spanning the two catalogs and time ranges. Your thoughts on this idea would be appreciated.

      Regarding 2), yes we are aware that searching the ISC catalog using our service is now much slower. This is due to not being able to use the caching solution we had developed and been using for a long time as it was built around the concept of mixed catalogs. We are investigating other methods and I'm optimistic we can speed up access to all catalogs.

      Chad

      On Mar 28, 2013, at 3:13 PM, John Taber <taber<at>iris.edu> wrote:

      Chad,

      It's great to see that you have the new FDSN web services up and running and Russ is already using them in the new version of IEB that he is working on. I've been trying it out via IEB and also the URL builder, and I've got a couple of questions.

      1. The default NEIC PDE catalog only goes back to 1990, but on the USGS site, the PDE catalog goes back to 1973 ( http://earthquake.usgs.gov/research/data/pde.php or http://earthquake.usgs.gov/earthquakes/eqarchives/epic/ ). Is there any chance of adding the earlier years? This would make IEB much more useful.

      2. I understand you are aware that selecting another catalog slows the search down such that it can take minutes in some cases, which might be okay for some uses but it means the ISC catalog couldn't be selected for use in IEB, which was something David was hoping for (as long as it is the reviewed bulletin). Do you think it will be possible to speed up the use of other catalogs?

      Thanks for your help,

      John

      On Mar 27, 2013, at 4:43 PM, Chad Trabant wrote:


      Hello web services users,

      We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

      The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

      These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


      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/

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

      Comments, feedback and questions are welcome.


      == Transitioning clients to the FDSN services

      The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

      http://service.iris.edu/clients/

      The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


      == Deprecation of equivalent IRIS services

      With the release of our FDSN services we are deprecating the equivalent services.

      These services will be turned off in approximately 6 months:

      ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
      ws-dataselect (www.iris.edu/ws/dataselect)
      ws-station (www.iris.edu/ws/bulkdataselect)
      ws-event (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:
      1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
      2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
      3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
      4) 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:
      1) the XML output is returned as FDSN StationXML, a different schema
      2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
      3) 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:
      1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
      2) the 'output' parameter name is changed to 'format'
      3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
      4) 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.

      IRIS Web Services team





      _______________________________________________
      webservices mailing list
      webservices<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/webservices

      _______________________________________________
      webservices mailing list
      webservices<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/webservices


  • Philip Crotwell
    April 1, 2013, 11:42 a.m.
    Might be nice to put a "These services will be turned off in approximately
    6 months:" notice on the corresponding web services pages. Maybe in red or
    hot pink!

    Also link them to the new fsdn pages.

    Philip


    On Wed, Mar 27, 2013 at 4:43 PM, Chad Trabant <chad<at>iris.washington.edu>wrote:


    Hello web services users,

    We are pleased to announce that the IRIS DMC has implemented the
    International Federation of Digital Seismograph Networks (FDSN) versions of
    our 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 below.

    The FDSN service specification defines an internationally recognized,
    standard interface. Programs that access data via these FDSN web services
    should also be compatible with any other data center implementing FDSN
    interfaces. There are a few, clearly marked IRIS extensions to the
    functionality that may not be implemented elsewhere.

    These are an evolutionary step forward for DMC services and improve on
    what they are replacing in important ways. For example, the time series
    web service now supports wildcards, and much more flexibility in selection
    style (supporting both GET and POST submissions and comma separated lists
    for channel name fields).


    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/*

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

    Comments, feedback and questions are welcome.


    *== Transitioning clients to the FDSN services*
    *
    *
    The DMC has converted it's Perl-based Fetch scripts to use these new
    services, the latest version may be downloaded from here:

    http://service.iris.edu/clients/

    The transition of the IRIS Java Web Services library and the irisFetch.m
    for MATLAB are currently in progress.


    *== Deprecation of equivalent IRIS services*
    *
    *
    With the release of our FDSN services we are deprecating the equivalent
    services.

    *These services will be turned off in approximately 6 months:*
    *
    *
    ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
    ws-dataselect (www.iris.edu/ws/dataselect)
    ws-station (www.iris.edu/ws/bulkdataselect)
    ws-event (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:
    1) enhancement: the network, station, location and channel selections may
    be comma-separated lists (e.g. BHE,BHN)
    2) enhancement: the network, station, location and channel selections may
    contain * and ? wildcards
    3) should be a drop-in replacement for ws-bulkdataselect (accepts the
    same requests via POST).
    4) 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:
    1) the XML output is returned as FDSN StationXML, a different schema
    2) new 'matchtimeseries' parameter to limit results to channels with high
    probability of data at the DMC
    3) 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:
    1) the FDSN service returns event depths in meters to conform to QuakeML
    1.2 (the ws-event service used kilometers)
    2) the 'output' parameter name is changed to 'format'
    3) only a single catalog can be selected per-request, the default catalog
    is 'NEIC PDE'
    4) 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.

    IRIS Web Services team






    _______________________________________________
    webservices mailing list
    webservices<at>iris.washington.edu
    http://www.iris.washington.edu/mailman/listinfo/webservices



    • Hi Philip,
      Excellent suggestion, and prescient. I had just started to tackle that exact task moments before your email arrived.

      - Celso


      On Apr 1, 2013, at 8:42 AM, Philip Crotwell wrote:


      Might be nice to put a "These services will be turned off in approximately 6 months:" notice on the corresponding web services pages. Maybe in red or hot pink!

      Also link them to the new fsdn pages.

      Philip


      On Wed, Mar 27, 2013 at 4:43 PM, Chad Trabant <chad<at>iris.washington.edu> wrote:

      Hello web services users,

      We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

      The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

      These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


      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/

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

      Comments, feedback and questions are welcome.


      == Transitioning clients to the FDSN services

      The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

      http://service.iris.edu/clients/

      The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


      == Deprecation of equivalent IRIS services

      With the release of our FDSN services we are deprecating the equivalent services.

      These services will be turned off in approximately 6 months:

      ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
      ws-dataselect (www.iris.edu/ws/dataselect)
      ws-station (www.iris.edu/ws/bulkdataselect)
      ws-event (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:
      1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
      2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
      3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
      4) 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:
      1) the XML output is returned as FDSN StationXML, a different schema
      2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
      3) 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:
      1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
      2) the 'output' parameter name is changed to 'format'
      3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
      4) 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.

      IRIS Web Services team






      _______________________________________________
      webservices mailing list
      webservices<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/webservices


      _______________________________________________
      webservices mailing list
      webservices<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/webservices


  • Chad Trabant
    July 31, 2013, 3:20 p.m.

    Hello,

    This is a reminder of two important changes at the DMC effecting web service users.

    1) The DMC has deprecated 4 services in favor of new, FDSN standardized versions. These services will be shutdown in December of 2013:

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

    The replacement FDSN services are available at http://service.iris.edu/.

    2) All DMC services have been transitioned to a new location: http://service.iris.edu/. All services running under www.iris.edu/ws/ will be shutdown in December of 2013.

    Users and software developers should migrate to the new services and locations as soon as possible.

    For those of you using data access software written by the DMC, updating to the latest releases is all you need to do:
    http://service.iris.edu/clients/

    regards,
    IRIS DMC


    Begin forwarded message:

    From: Chad Trabant <chad<at>iris.washington.edu>
    Subject: New FDSN web services and retirement of deprecated services
    Date: March 27, 2013 1:43:01 PM PDT
    To: IRIS Web Services List <webservices<at>iris.washington.edu>


    Hello web services users,

    We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

    The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

    These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


    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/

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

    Comments, feedback and questions are welcome.


    == Transitioning clients to the FDSN services

    The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

    http://service.iris.edu/clients/

    The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


    == Deprecation of equivalent IRIS services

    With the release of our FDSN services we are deprecating the equivalent services.

    These services will be turned off in approximately 6 months:

    ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
    ws-dataselect (www.iris.edu/ws/dataselect)
    ws-station (www.iris.edu/ws/bulkdataselect)
    ws-event (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:
    1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
    2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
    3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
    4) 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:
    1) the XML output is returned as FDSN StationXML, a different schema
    2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
    3) 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:
    1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
    2) the 'output' parameter name is changed to 'format'
    3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
    4) 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.

    IRIS Web Services team







    • Hello,

      As we noted in an early post, the European High Schools are using
      directly the IRIS DMC Web Services for data hosted at IRIS and local
      implementations (Java / JAX-RS / NetBeans / Apache Tomcat) of a subset
      of these services for other data.

      Our local implementations of IRIS and FDSN web services are useful for
      our learning and for getting things running quickly, but in the longer
      term it is not practical for us and others to "chase" all the extensive
      and thorough ws developments at IRIS.

      So we wonder if there will be a distribution, workshops, support, etc.
      from IRIS so that the FDSN (and ultimately IRIS?) web-services can be
      easily implemented by other data providers?

      Thanks,

      Ciao,

      Anthony


      On 2013/08/01 00:20, Chad Trabant wrote:

      Hello,

      This is a reminder of two important changes at the DMC effecting web
      service users.

      1) The DMC has deprecated 4 services in favor of new, FDSN
      standardized versions. These services will be *shutdown in December
      of 2013:*

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

      The replacement FDSN services are available at http://service.iris.edu/.

      2) All DMC services have been transitioned to a new location:
      *http://service.iris.edu/*. All services running under
      www.iris.edu/ws/ <http://www.iris.edu/ws/ will be *shutdown
      in December of 2013*.

      Users and software developers should migrate to the new services and
      locations as soon as possible.

      For those of you using data access software written by the DMC,
      updating to the latest releases is all you need to do:
      http://service.iris.edu/clients/

      regards,
      IRIS DMC


      Begin forwarded message:

      *From: *Chad Trabant <chad<at>iris.washington.edu
      <chad<at>iris.washington.edu>>
      *Subject: **New FDSN web services and retirement of deprecated services*
      *Date: *March 27, 2013 1:43:01 PM PDT
      *To: *IRIS Web Services List <webservices<at>iris.washington.edu
      <webservices<at>iris.washington.edu>>


      Hello web services users,

      We are pleased to announce that the IRIS DMC has implemented the
      International Federation of Digital Seismograph Networks (FDSN)
      versions of our 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 below.

      The FDSN service specification defines an internationally recognized,
      standard interface. Programs that access data via these FDSN web
      services should also be compatible with any other data center
      implementing FDSN interfaces. There are a few, clearly marked IRIS
      extensions to the functionality that may not be implemented elsewhere.

      These are an evolutionary step forward for DMC services and improve
      on what they are replacing in important ways. For example, the time
      series web service now supports wildcards, and much more flexibility
      in selection style (supporting both GET and POST submissions and
      comma separated lists for channel name fields).


      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/*

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

      Comments, feedback and questions are welcome.


      *== Transitioning clients to the FDSN services*
      *
      *
      The DMC has converted it's Perl-based Fetch scripts to use these new
      services, the latest version may be downloaded from here:

      http://service.iris.edu/clients/

      The transition of the IRIS Java Web Services library and the
      irisFetch.m for MATLAB are currently in progress.


      *== Deprecation of equivalent IRIS services*
      *
      *
      With the release of our FDSN services we are deprecating the
      equivalent services.

      *These services will be turned off in approximately 6 months:*
      *
      *
      ws-bulkdataselect (www.iris.edu/ws/bulkdataselect
      <http://www.iris.edu/ws/bulkdataselect)
      ws-dataselect (www.iris.edu/ws/dataselect
      <http://www.iris.edu/ws/dataselect)
      ws-station (www.iris.edu/ws/bulkdataselect
      <http://www.iris.edu/ws/bulkdataselect)
      ws-event (www.iris.edu/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:
      1) enhancement: the network, station, location and channel
      selections may be comma-separated lists (e.g. BHE,BHN)
      2) enhancement: the network, station, location and channel
      selections may contain * and ? wildcards
      3) should be a drop-in replacement for ws-bulkdataselect (accepts
      the same requests via POST).
      4) 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:
      1) the XML output is returned as FDSN StationXML, a different schema
      2) new 'matchtimeseries' parameter to limit results to channels with
      high probability of data at the DMC
      3) 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:
      1) the FDSN service returns event depths in meters to conform to
      QuakeML 1.2 (the ws-event service used kilometers)
      2) the 'output' parameter name is changed to 'format'
      3) only a single catalog can be selected per-request, the default
      catalog is 'NEIC PDE'
      4) 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.

      IRIS Web Services team








      _______________________________________________
      webservices mailing list
      webservices<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/webservices

      --
      Sent from my iClayTablet

      ------------------------------------------------------------------------

      *Anthony Lomax*
      *161 Allée du Micocoulier, 06370 Mouans-Sartoux, France*
      *tel: +33 (0)4 93 75 25 02 e-mail: anthony<at>alomax.net
      <anthony<at>alomax.net> web: http://www.alomax.net
      <http://www.alomax.net/ *

      *Science & Special Topics: * *http://www.alomax.net/science*
      *Software: * *http://www.alomax.net/software* *- updates: *
      *https://twitter.com/ALomaxNet*
      ------------------------------------------------------------------------

      • Chad Trabant
        Sept. 14, 2013, 11:39 a.m.

        Hi Anthony,

        Yes, We have created a Web Service Shell (WSS) as a common component of REST-like service interfaces that deals with all of the HTTP aspects. At the DMC we use the WSS as the front end of each of our FDSN services running in Tomcat containers. This software is also being used by at least 3 other data centers in Europe and the US to implement FDSN services. The idea is that a data center only needs to develop the backend extraction routines specific to their repository/system to host services.

        You can find the WSS here:
        https://seiscode.iris.washington.edu/projects/webserviceshell

        The Wiki portion of the project page contains the documentation (still needs some cleanup). We are happy to share and will support this to the extent we have time.

        Of course, the WSS is not a complete solution for "chasing" the evolution of FDSN or other services. Changes to the services could easily require changes to the data center specific extraction routines that are not covered by the WSS.

        There are no plans to host workshops or support implementation at arbitrary data centers. The good news is that we are involved in a couple of projects that support development of web service components at targeted data centers, the WSS is the result of one of these. We will continue to evolve the WSS and perhaps other components, which everyone will benefit from.

        Chad

        On Sep 4, 2013, at 12:49 AM, Anthony Lomax <alomax<at>free.fr> wrote:

        Hello,

        As we noted in an early post, the European High Schools are using directly the IRIS DMC Web Services for data hosted at IRIS and local implementations (Java / JAX-RS / NetBeans / Apache Tomcat) of a subset of these services for other data.

        Our local implementations of IRIS and FDSN web services are useful for our learning and for getting things running quickly, but in the longer term it is not practical for us and others to "chase" all the extensive and thorough ws developments at IRIS.

        So we wonder if there will be a distribution, workshops, support, etc. from IRIS so that the FDSN (and ultimately IRIS?) web-services can be easily implemented by other data providers?

        Thanks,

        Ciao,

        Anthony


        On 2013/08/01 00:20, Chad Trabant wrote:

        Hello,

        This is a reminder of two important changes at the DMC effecting web service users.

        1) The DMC has deprecated 4 services in favor of new, FDSN standardized versions. These services will be shutdown in December of 2013:

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

        The replacement FDSN services are available at http://service.iris.edu/.

        2) All DMC services have been transitioned to a new location: http://service.iris.edu/. All services running under www.iris.edu/ws/ will be shutdown in December of 2013.

        Users and software developers should migrate to the new services and locations as soon as possible.

        For those of you using data access software written by the DMC, updating to the latest releases is all you need to do:
        http://service.iris.edu/clients/

        regards,
        IRIS DMC


        Begin forwarded message:

        From: Chad Trabant <chad<at>iris.washington.edu>
        Subject: New FDSN web services and retirement of deprecated services
        Date: March 27, 2013 1:43:01 PM PDT
        To: IRIS Web Services List <webservices<at>iris.washington.edu>


        Hello web services users,

        We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

        The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

        These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


        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/

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

        Comments, feedback and questions are welcome.


        == Transitioning clients to the FDSN services

        The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

        http://service.iris.edu/clients/

        The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


        == Deprecation of equivalent IRIS services

        With the release of our FDSN services we are deprecating the equivalent services.

        These services will be turned off in approximately 6 months:

        ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
        ws-dataselect (www.iris.edu/ws/dataselect)
        ws-station (www.iris.edu/ws/bulkdataselect)
        ws-event (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:
        1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
        2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
        3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
        4) 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:
        1) the XML output is returned as FDSN StationXML, a different schema
        2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
        3) 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:
        1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
        2) the 'output' parameter name is changed to 'format'
        3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
        4) 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.

        IRIS Web Services team








        _______________________________________________
        webservices mailing list
        webservices<at>iris.washington.edu
        http://www.iris.washington.edu/mailman/listinfo/webservices

        --
        Sent from my iClayTablet


        Anthony Lomax
        161 Allée du Micocoulier, 06370 Mouans-Sartoux, France
        tel: +33 (0)4 93 75 25 02 e-mail: anthony<at>alomax.net web: http://www.alomax.net

        Science & Special Topics: http://www.alomax.net/science
        Software: http://www.alomax.net/software - updates: https://twitter.com/ALomaxNet
        _______________________________________________
        webservices mailing list
        webservices<at>iris.washington.edu
        http://www.iris.washington.edu/mailman/listinfo/webservices



    • Hello web service users,

      Another reminder of important changes if you are using our web services. Some services will be shut down in December of 2013. To avoid an interruption in your data processing, please check that you are not using one of the deprecated services and are using the latest release of whatever software you are using to collect data.

      Please read the earlier previous announcements for details. If you have any questions regarding this transition please let us know.

      IRIS DMC

      On Jul 31, 2013, at 3:20 PM, Chad Trabant <chad<at>iris.washington.edu> wrote:

      Hello,

      This is a reminder of two important changes at the DMC effecting web service users.

      1) The DMC has deprecated 4 services in favor of new, FDSN standardized versions. These services will be shutdown in December of 2013:

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

      The replacement FDSN services are available at http://service.iris.edu/.

      2) All DMC services have been transitioned to a new location: http://service.iris.edu/. All services running under www.iris.edu/ws/ will be shutdown in December of 2013.

      Users and software developers should migrate to the new services and locations as soon as possible.

      For those of you using data access software written by the DMC, updating to the latest releases is all you need to do:
      http://service.iris.edu/clients/

      regards,
      IRIS DMC


      Begin forwarded message:

      From: Chad Trabant <chad<at>iris.washington.edu>
      Subject: New FDSN web services and retirement of deprecated services
      Date: March 27, 2013 1:43:01 PM PDT
      To: IRIS Web Services List <webservices<at>iris.washington.edu>


      Hello web services users,

      We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

      The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

      These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


      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/

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

      Comments, feedback and questions are welcome.


      == Transitioning clients to the FDSN services

      The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

      http://service.iris.edu/clients/

      The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


      == Deprecation of equivalent IRIS services

      With the release of our FDSN services we are deprecating the equivalent services.

      These services will be turned off in approximately 6 months:

      ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
      ws-dataselect (www.iris.edu/ws/dataselect)
      ws-station (www.iris.edu/ws/bulkdataselect)
      ws-event (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:
      1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
      2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
      3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
      4) 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:
      1) the XML output is returned as FDSN StationXML, a different schema
      2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
      3) 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:
      1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
      2) the 'output' parameter name is changed to 'format'
      3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
      4) 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.

      IRIS Web Services team









      • Hello web service users,

        Some deprecated web services at the IRIS DMC will be shut down in December of 2013. To avoid an interruption in your data processing, please check that you are not using one of the deprecated services and are using the latest release of whatever software you are using to collect data.

        The DMC’s command line Fetch scripts are here:
        https://seiscode.iris.washington.edu/projects/ws-fetch-scripts

        MATLAB users and those that need the Java IRIS-WS library should get the latest jar:
        http://www.iris.edu/dms/nodes/dmc/software/downloads/IRIS-WS/2-0-4/

        SOD users should be using version 3.2 or later and some modification of older recipes is needed:
        http://www.seis.sc.edu/sod/

        ObsPy (Python) users you will need to update to version 0.9 or later when it is released (hopefully soon!). ObsPy scripts will need to be converted from using the obspy.iris module to use the obspy.fdsn module for waveforms, station metadata and event information.
        https://github.com/obspy/obspy/wiki

        For users of other software please check that you are using the correct URLs, details below.

        regards,
        IRIS DMC

        On Oct 14, 2013, at 1:57 PM, Chad Trabant <chad<at>iris.washington.edu> wrote:

        Hello web service users,

        Another reminder of important changes if you are using our web services. Some services will be shut down in December of 2013. To avoid an interruption in your data processing, please check that you are not using one of the deprecated services and are using the latest release of whatever software you are using to collect data.

        Please read the earlier previous announcements for details. If you have any questions regarding this transition please let us know.

        IRIS DMC

        On Jul 31, 2013, at 3:20 PM, Chad Trabant <chad<at>iris.washington.edu> wrote:

        Hello,

        This is a reminder of two important changes at the DMC effecting web service users.

        1) The DMC has deprecated 4 services in favor of new, FDSN standardized versions. These services will be shutdown in December of 2013:

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

        The replacement FDSN services are available at http://service.iris.edu/.

        2) All DMC services have been transitioned to a new location: http://service.iris.edu/. All services running under www.iris.edu/ws/ will be shutdown in December of 2013.

        Users and software developers should migrate to the new services and locations as soon as possible.

        For those of you using data access software written by the DMC, updating to the latest releases is all you need to do:
        http://service.iris.edu/clients/

        regards,
        IRIS DMC


        Begin forwarded message:

        From: Chad Trabant <chad<at>iris.washington.edu>
        Subject: New FDSN web services and retirement of deprecated services
        Date: March 27, 2013 1:43:01 PM PDT
        To: IRIS Web Services List <webservices<at>iris.washington.edu>


        Hello web services users,

        We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

        The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

        These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


        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/

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

        Comments, feedback and questions are welcome.


        == Transitioning clients to the FDSN services

        The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

        http://service.iris.edu/clients/

        The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


        == Deprecation of equivalent IRIS services

        With the release of our FDSN services we are deprecating the equivalent services.

        These services will be turned off in approximately 6 months:

        ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
        ws-dataselect (www.iris.edu/ws/dataselect)
        ws-station (www.iris.edu/ws/bulkdataselect)
        ws-event (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:
        1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
        2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
        3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
        4) 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:
        1) the XML output is returned as FDSN StationXML, a different schema
        2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
        3) 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:
        1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
        2) the 'output' parameter name is changed to 'format'
        3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
        4) 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.

        IRIS Web Services team




        • Hi web service users,

          If you have not updated your data requests to use our new services instead of the deprecated services please do so immediately. We are only days away from shutting down the old service end-points.

          Java and MATLAB users:
          If you have used the DMC’s IRIS-WS library (or our irisFetch.m MATLAB interface) make sure you are using 2.0.4 (or later) to avoid problems with updates we plan on making in January.

          regards,
          IRIS DMC

          On Nov 22, 2013, at 9:41 AM, Chad Trabant <chad<at>iris.washington.edu> wrote:

          Hello web service users,

          Some deprecated web services at the IRIS DMC will be shut down in December of 2013. To avoid an interruption in your data processing, please check that you are not using one of the deprecated services and are using the latest release of whatever software you are using to collect data.

          The DMC’s command line Fetch scripts are here:
          https://seiscode.iris.washington.edu/projects/ws-fetch-scripts

          MATLAB users and those that need the Java IRIS-WS library should get the latest jar:
          http://www.iris.edu/dms/nodes/dmc/software/downloads/IRIS-WS/2-0-4/

          SOD users should be using version 3.2 or later and some modification of older recipes is needed:
          http://www.seis.sc.edu/sod/

          ObsPy (Python) users you will need to update to version 0.9 or later when it is released (hopefully soon!). ObsPy scripts will need to be converted from using the obspy.iris module to use the obspy.fdsn module for waveforms, station metadata and event information.
          https://github.com/obspy/obspy/wiki

          For users of other software please check that you are using the correct URLs, details below.

          regards,
          IRIS DMC

          On Oct 14, 2013, at 1:57 PM, Chad Trabant <chad<at>iris.washington.edu> wrote:

          Hello web service users,

          Another reminder of important changes if you are using our web services. Some services will be shut down in December of 2013. To avoid an interruption in your data processing, please check that you are not using one of the deprecated services and are using the latest release of whatever software you are using to collect data.

          Please read the earlier previous announcements for details. If you have any questions regarding this transition please let us know.

          IRIS DMC

          On Jul 31, 2013, at 3:20 PM, Chad Trabant <chad<at>iris.washington.edu> wrote:

          Hello,

          This is a reminder of two important changes at the DMC effecting web service users.

          1) The DMC has deprecated 4 services in favor of new, FDSN standardized versions. These services will be shutdown in December of 2013:

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

          The replacement FDSN services are available at http://service.iris.edu/.

          2) All DMC services have been transitioned to a new location: http://service.iris.edu/. All services running under www.iris.edu/ws/ will be shutdown in December of 2013.

          Users and software developers should migrate to the new services and locations as soon as possible.

          For those of you using data access software written by the DMC, updating to the latest releases is all you need to do:
          http://service.iris.edu/clients/

          regards,
          IRIS DMC


          Begin forwarded message:

          From: Chad Trabant <chad<at>iris.washington.edu>
          Subject: New FDSN web services and retirement of deprecated services
          Date: March 27, 2013 1:43:01 PM PDT
          To: IRIS Web Services List <webservices<at>iris.washington.edu>


          Hello web services users,

          We are pleased to announce that the IRIS DMC has implemented the International Federation of Digital Seismograph Networks (FDSN) versions of our 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 below.

          The FDSN service specification defines an internationally recognized, standard interface. Programs that access data via these FDSN web services should also be compatible with any other data center implementing FDSN interfaces. There are a few, clearly marked IRIS extensions to the functionality that may not be implemented elsewhere.

          These are an evolutionary step forward for DMC services and improve on what they are replacing in important ways. For example, the time series web service now supports wildcards, and much more flexibility in selection style (supporting both GET and POST submissions and comma separated lists for channel name fields).


          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/

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

          Comments, feedback and questions are welcome.


          == Transitioning clients to the FDSN services

          The DMC has converted it's Perl-based Fetch scripts to use these new services, the latest version may be downloaded from here:

          http://service.iris.edu/clients/

          The transition of the IRIS Java Web Services library and the irisFetch.m for MATLAB are currently in progress.


          == Deprecation of equivalent IRIS services

          With the release of our FDSN services we are deprecating the equivalent services.

          These services will be turned off in approximately 6 months:

          ws-bulkdataselect (www.iris.edu/ws/bulkdataselect)
          ws-dataselect (www.iris.edu/ws/dataselect)
          ws-station (www.iris.edu/ws/bulkdataselect)
          ws-event (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:
          1) enhancement: the network, station, location and channel selections may be comma-separated lists (e.g. BHE,BHN)
          2) enhancement: the network, station, location and channel selections may contain * and ? wildcards
          3) should be a drop-in replacement for ws-bulkdataselect (accepts the same requests via POST).
          4) 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:
          1) the XML output is returned as FDSN StationXML, a different schema
          2) new 'matchtimeseries' parameter to limit results to channels with high probability of data at the DMC
          3) 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:
          1) the FDSN service returns event depths in meters to conform to QuakeML 1.2 (the ws-event service used kilometers)
          2) the 'output' parameter name is changed to 'format'
          3) only a single catalog can be selected per-request, the default catalog is 'NEIC PDE'
          4) 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.

          IRIS Web Services team




Page built 14:07:31 | v.87755d31