Thread: Introducing PH5 Web Services: Three new FDSN Web Services for accessing PH5 datasets

Started: 2017-08-08 18:58:55
Last activity: 2017-08-08 22:47:10
Topics: Web Services
Hello web service users,

The IRIS DMC in collaboration with the IRIS PASSCAL Instrument Center is pleased to announce the addition of three new FDSN compliant web service interfaces. These services are designed to provide an interface to time series datasets, related station metadata, and active (controlled) source event (shot) information stored in the PH5 data archive.

Detailed descriptions of the service endpoints and example queries can be found in the following service documentation:

ph5ws-dataselect - http://service.iris.edu/ph5ws/dataselect/1/

The PH5 Dataselect Web Service can stream waveform data in both miniSEED or optionally as a compressed-zip of SAC formatted files. Users who require data in SEG-Y format will need to use a legacy PH5 Web Form <http://ds.iris.edu/pic-ph5/experiment_list.php?EXP, which will temporarily remain active for this purpose. For active source experiments, the PH5 Dataselect service also provides a new request type for requesting data immediately following the times that shots (events) occurred.

ph5ws-station - http://service.iris.edu/ph5ws/station/1/

The PH5 Station Web Service can output station metadata formatted as FDSN StationXML or in a text format.

ph5ws-event - http://service.iris.edu/ph5ws/event/1/
The PH5 Event Web Service can output active source event metadata formatted as QuakeML or in a text format.

The PH5 Dataselect and Station services are designed to work with existing FDSN clients, such as FetchData <https://seiscode.iris.washington.edu/projects/ws-fetch-scripts/wiki, FetchMetadata <https://seiscode.iris.washington.edu/projects/ws-fetch-scripts/wiki and ObsPy <https://github.com/obspy/obspy/wiki.

Among the handful of experiments currently available through the PH5 Web Services is the Community Wavefield Demonstration Experiment <https://www.iris.edu/hq/event/wavefields_community_demonstration_experiment. We anticipate the amount of data available through the PH5 Web Services to grow quickly as additional PH5 experiments are added. We encourage users to periodically revisit the services to discover newly added data.

Searching for and accessing data from both the PH5 and primary repository at the DMC can be accomplished using the IRIS Federator <http://service.iris.edu/irisws/fedcatalog/1/. For tools supporting the Federator, access to both of these repositories is seamless.

We welcome feedback and questions.

Sincerely,
IRIS Web Services Team
  • Hi

    The FDSN web services spec says that:

    The following base URI pattern is to be used at each data center
    implementing FDSN services:
    <site>/fdsnws/<service>/<majorversion>/

    so having these services under /ph5ws instead of /fdsnws makes them
    not quite compliant with the FDSN spec.

    Having the fixed URL pattern makes it easy for clients to simply
    change the host and know that everything else is the same. As I spend
    a lot of time writing clients and want them to be able to access all
    fdsn web services, this change is a concern. Is this intended to
    signal a change to the fdsn web service spec, or is compliance with
    that part of the spec not longer considered important for these
    particular services?

    thanks
    Philip




    On Tue, Aug 8, 2017 at 2:59 PM, Nick Falco <nick<at>iris.washington.edu> wrote:
    Hello web service users,

    The IRIS DMC in collaboration with the IRIS PASSCAL Instrument Center is
    pleased to announce the addition of three new FDSN compliant web service
    interfaces. These services are designed to provide an interface to time
    series datasets, related station metadata, and active (controlled) source
    event (shot) information stored in the PH5 data archive.

    Detailed descriptions of the service endpoints and example queries can be
    found in the following service documentation:

    ph5ws-dataselect - http://service.iris.edu/ph5ws/dataselect/1/

    The PH5 Dataselect Web Service can stream waveform data in both miniSEED or
    optionally as a compressed-zip of SAC formatted files. Users who require
    data in SEG-Y format will need to use a legacy PH5 Web Form, which will
    temporarily remain active for this purpose. For active source experiments,
    the PH5 Dataselect service also provides a new request type for requesting
    data immediately following the times that shots (events) occurred.

    ph5ws-station - http://service.iris.edu/ph5ws/station/1/

    The PH5 Station Web Service can output station metadata formatted as FDSN
    StationXML or in a text format.

    ph5ws-event - http://service.iris.edu/ph5ws/event/1/

    The PH5 Event Web Service can output active source event metadata formatted
    as QuakeML or in a text format.

    The PH5 Dataselect and Station services are designed to work with existing
    FDSN clients, such as FetchData, FetchMetadata and ObsPy.

    Among the handful of experiments currently available through the PH5 Web
    Services is the Community Wavefield Demonstration Experiment. We anticipate
    the amount of data available through the PH5 Web Services to grow quickly as
    additional PH5 experiments are added. We encourage users to periodically
    revisit the services to discover newly added data.

    Searching for and accessing data from both the PH5 and primary repository at
    the DMC can be accomplished using the IRIS Federator. For tools supporting
    the Federator, access to both of these repositories is seamless.

    We welcome feedback and questions.

    Sincerely,
    IRIS Web Services Team


    ----------------------
    Web Services | http://ds.iris.edu/message-center/topic/webservices/ |
    Unsubscribe: webservices-unsubscribe<at>lists.ds.iris.edu

    Sent from the IRIS Message Center (http://ds.iris.edu/message-center/)
    Update subscription preferences at http://ds.iris.edu/account/profile/



    • Hi Philip-

      I may have to leave the particulars to Chad or other FDSN members on this question, but you make an interesting point.

      For example, we have endeavored to make MUSTANG 'FDSN-compliant' through familiar path and parameter behaviors, but there is still much that is distinctively MUSTANG.

      http://service.iris.edu/mustang/<service>/<version>/

      I wonder if there needs to be the distinction between a 'certified' FDSN service and a 'compliant' FDSN service. Or maybe the terms 'compliant' and 'friendly' or something to that effect.

      We currently have the PH5 family of services as an adjunct from our main archival service end point so it is clear that this is a different archive. Perhaps this raises the issue of how FDSN services will grow to support heterogeneous datasets.

      I think I shouldn't comment more on the matter as this really should reside with the appropriate FDSN working group.

      -Rob


      On Aug 8, 2017, at 12:48 PM, Philip Crotwell <crotwell<at>seis.sc.edu> wrote:

      Hi

      The FDSN web services spec says that:

      The following base URI pattern is to be used at each data center
      implementing FDSN services:
      <site>/fdsnws/<service>/<majorversion>/

      so having these services under /ph5ws instead of /fdsnws makes them
      not quite compliant with the FDSN spec.

      Having the fixed URL pattern makes it easy for clients to simply
      change the host and know that everything else is the same. As I spend
      a lot of time writing clients and want them to be able to access all
      fdsn web services, this change is a concern. Is this intended to
      signal a change to the fdsn web service spec, or is compliance with
      that part of the spec not longer considered important for these
      particular services?

      thanks
      Philip




      On Tue, Aug 8, 2017 at 2:59 PM, Nick Falco <nick<at>iris.washington.edu> wrote:
      Hello web service users,

      The IRIS DMC in collaboration with the IRIS PASSCAL Instrument Center is
      pleased to announce the addition of three new FDSN compliant web service
      interfaces. These services are designed to provide an interface to time
      series datasets, related station metadata, and active (controlled) source
      event (shot) information stored in the PH5 data archive.

      Detailed descriptions of the service endpoints and example queries can be
      found in the following service documentation:

      ph5ws-dataselect - http://service.iris.edu/ph5ws/dataselect/1/

      The PH5 Dataselect Web Service can stream waveform data in both miniSEED or
      optionally as a compressed-zip of SAC formatted files. Users who require
      data in SEG-Y format will need to use a legacy PH5 Web Form, which will
      temporarily remain active for this purpose. For active source experiments,
      the PH5 Dataselect service also provides a new request type for requesting
      data immediately following the times that shots (events) occurred.

      ph5ws-station - http://service.iris.edu/ph5ws/station/1/

      The PH5 Station Web Service can output station metadata formatted as FDSN
      StationXML or in a text format.

      ph5ws-event - http://service.iris.edu/ph5ws/event/1/

      The PH5 Event Web Service can output active source event metadata formatted
      as QuakeML or in a text format.

      The PH5 Dataselect and Station services are designed to work with existing
      FDSN clients, such as FetchData, FetchMetadata and ObsPy.

      Among the handful of experiments currently available through the PH5 Web
      Services is the Community Wavefield Demonstration Experiment. We anticipate
      the amount of data available through the PH5 Web Services to grow quickly as
      additional PH5 experiments are added. We encourage users to periodically
      revisit the services to discover newly added data.

      Searching for and accessing data from both the PH5 and primary repository at
      the DMC can be accomplished using the IRIS Federator. For tools supporting
      the Federator, access to both of these repositories is seamless.

      We welcome feedback and questions.

      Sincerely,
      IRIS Web Services Team


      ----------------------
      Web Services | http://ds.iris.edu/message-center/topic/webservices/ |
      Unsubscribe: webservices-unsubscribe<at>lists.ds.iris.edu

      Sent from the IRIS Message Center (http://ds.iris.edu/message-center/)
      Update subscription preferences at http://ds.iris.edu/account/profile/


      ----------------------
      Web Services | http://ds.iris.edu/message-center/topic/webservices/ | Unsubscribe: webservices-unsubscribe<at>lists.ds.iris.edu

      Sent from the IRIS Message Center (http://ds.iris.edu/message-center/)
      Update subscription preferences at http://ds.iris.edu/account/profile/


Page built 22:37:49 | v.090361a2