International Federation of Digital Seismograph Networks

Thread: Draft Agenda

None
Started: July 21, 2017, 12:29 p.m.
Last activity: July 28, 2017, 3:49 p.m.
Tim Ahern
July 21, 2017, 12:29 p.m.
Greetings members of FDSN WG III on Products, Tools, and Services.

In preparation for the WG III meeting I am attaching the draft agenda and a few documents. If there are other issues to be discussed they can be considered at the meeting. Time will be short as this meeting is only 90 minutes long.

There are three attachments

1) the draft agenda with the all the topics recommended by various parties, and the time and place of our meeting in Kobe



This attachment that covers Phillips Crotwell’s wish to make times specified in the services ISO compliant


And finally a document to be referred to for the change recommended by John Clinton regarding the event_type for fads-event service

I hope I got this correct John, please let us know if I didn’t. I think it is straightforwardo



I hope to see many of you in Kobe.

Until then


Tim Ahern

Director of Data Services
IRIS

IRIS DMC
1408 NE 45th Street #201
Seattle, WA 98105

(206)547-0393 x118
(206) 547-1093 FAX


  • Jean-Marie Saurel
    July 22, 2017, 4:18 a.m.
    Hello Tim,

    Thanks for the documents.

    I will unfortunately not be there in Kobé.
    However, I have just a little question on the third document from John.

    Does this option will allow to select several event types in the same
    request ?

    Like, for example "eventtype=landslide,rockslide,collapse".

    Regards.
    Have a nice week-end.

    Jean-Marie SAUREL.

    Le 21.07.2017 19:29, Tim Ahern a écrit :
    Greetings members of FDSN WG III on Products, Tools, and Services.

    In preparation for the WG III meeting I am attaching the draft agenda
    and a few documents. If there are other issues to be discussed they
    can be considered at the meeting. Time will be short as this meeting
    is only 90 minutes long.

    There are three attachments

    1) the draft agenda with the all the topics recommended by various
    parties, and the time and place of our meeting in Kobe

    This attachment that covers Phillips Crotwell’s wish to make times
    specified in the services ISO compliant

    And finally a document to be referred to for the change recommended
    by John Clinton regarding the event_type for fads-event service

    I hope I got this correct John, please let us know if I didn’t.
    I think it is straightforwardo


    I hope to see many of you in Kobe.

    Until then


    Tim Ahern

    --------------------------------------
    Institut de Physique du Globe de Paris
    Observatoires Volcanologiques et Sismologiques
    +33 1 83 95 74 37
    1 rue Jussieu
    75238 Paris cédex 5

    • John Clinton
      July 28, 2017, 11:20 a.m.
      sorry for the late reaction on this due taking vacation right before the Kobe meeting:

      @ Tim, thanks for creating the template document for the changes to the event service. I review the proposed changes, and would like to add changes / actions. The first is to do with the standard used for Event Type descriptions. quakeMl2.0 is still at RFC stage, so we should refer to quakeMl1.2, the currently agreed standard.

      @ Jean-Marie, thank you for your comment. Of course there should be an option to allow selection of multiple event types.

      to be consistent with the conventions in the specifications document (if I understand them correctly), I have amended the file send by Tim, with new changes in green. I hope we can agree these at the meeting in Kobe, I will present these briefly at the WGIII meeting.

      John




      On 22 Jul 2017, at 05:25, Jean-Marie Saurel <saurel<at>ipgp.fr> wrote:

      Hello Tim,

      Thanks for the documents.

      I will unfortunately not be there in Kobé.
      However, I have just a little question on the third document from John.

      Does this option will allow to select several event types in the same
      request ?

      Like, for example "eventtype=landslide,rockslide,collapse".

      Regards.
      Have a nice week-end.

      Jean-Marie SAUREL.

      Le 21.07.2017 19:29, Tim Ahern a écrit :
      Greetings members of FDSN WG III on Products, Tools, and Services.

      In preparation for the WG III meeting I am attaching the draft agenda
      and a few documents. If there are other issues to be discussed they
      can be considered at the meeting. Time will be short as this meeting
      is only 90 minutes long.

      There are three attachments

      1) the draft agenda with the all the topics recommended by various
      parties, and the time and place of our meeting in Kobe

      This attachment that covers Phillips Crotwell’s wish to make times
      specified in the services ISO compliant

      And finally a document to be referred to for the change recommended
      by John Clinton regarding the event_type for fads-event service

      I hope I got this correct John, please let us know if I didn’t.
      I think it is straightforwardo


      I hope to see many of you in Kobe.

      Until then


      Tim Ahern

      --------------------------------------
      Institut de Physique du Globe de Paris
      Observatoires Volcanologiques et Sismologiques
      +33 1 83 95 74 37
      1 rue Jussieu
      75238 Paris cédex 5

      ----------------------
      FDSN Working Group III (http://www.fdsn.org/message-center/topic/fdsn-wg3-products/)

      Sent from the FDSN Message Center (http://www.fdsn.org/message-center/)
      Update subscription preferences at http://www.fdsn.org/account/profile/

      • Joachim Saul
        July 28, 2017, 3:31 p.m.
        John Clinton wrote on 07/28/2017 01:21 PM:
        quakeMl2.0 is still at RFC stage, so we should refer to quakeMl1.2, the currently agreed standard.

        Hi John,

        it shouldn't even refer to QuakeML at all as QuakeML adopted its event
        type list from a list compiled by the ISC [1], which I would regard as
        more "authoritative" instance on this matter than any QuakeML
        specification adopting it. Perhaps the ISC can elaborate on the status
        of this event type list and whether a revision / addition is planned.
        IIRC there were comments about some kinds of volcanic events missing on
        that list (and consequently the QuakeML list, too).

        Another potential source for confusion may be the spelling even if said
        QuakeML event type list shall be used. The default value of the event
        type is "Earthquake". In the QuakeML list, however, we have either
        "EARTHQUAKE" or "earthquake". This may be solved by specifying that the
        event type must be case insensitive but that still wouldn't resolve
        "NuclearExplosion" vs. "nuclear explosion" vs. "NUCLEAR_EXPLOSION".

        IMHO these issues should be resolved before the adoption as a standard
        feature.

        Regards
        Joachim


        [1] http://www.isc.ac.uk/standards/event_types/event_types.pdf

        • Fabian Euchner
          July 28, 2017, 3:49 p.m.
          Hi Joachim, hi all,

          the QuakeML standard document http://quakeml.org/docs/REC?
          action=AttachFile&do=view&target=QuakeML-BED-20130214a.pdf (pages 27/28/29)
          contains a reference to the Storchak et al. whitepaper (without the URL, since
          it was not known/available when the standard was written).

          The standard document lists the "correct" spelling of the EventTypes: all
          lowercase, separated with one blank space. I would suggest that in the event
          web service, we make the match case insensitive and allow also word separation
          by underscores:

          'induced event' matches 'induced_event' matches 'INDUCED_EVENT' matches
          'INDUCED event'

          I would not allow camel case, since it is typically used for element/attribute
          names, and not the values.

          Cheers,
          Fabian


          it shouldn't even refer to QuakeML at all as QuakeML adopted its event
          type list from a list compiled by the ISC [1], which I would regard as
          more "authoritative" instance on this matter than any QuakeML
          specification adopting it. Perhaps the ISC can elaborate on the status
          of this event type list and whether a revision / addition is planned.
          IIRC there were comments about some kinds of volcanic events missing on
          that list (and consequently the QuakeML list, too).

          Another potential source for confusion may be the spelling even if said
          QuakeML event type list shall be used. The default value of the event
          type is "Earthquake". In the QuakeML list, however, we have either
          "EARTHQUAKE" or "earthquake". This may be solved by specifying that the
          event type must be case insensitive but that still wouldn't resolve
          "NuclearExplosion" vs. "nuclear explosion" vs. "NUCLEAR_EXPLOSION".

          IMHO these issues should be resolved before the adoption as a standard
          feature.

          Regards
          Joachim


          [1] http://www.isc.ac.uk/standards/event_types/event_types.pdf

          ----------------------
          FDSN Working Group III
          (http://www.fdsn.org/message-center/topic/fdsn-wg3-products/)

          Sent from the FDSN Message Center (http://www.fdsn.org/message-center/)
          Update subscription preferences at http://www.fdsn.org/account/profile/


          --
          -----------------------------------------------------------------------------
          Fabian Euchner phone +41 44 633 7178
          Institute of Geophysics fax +41 44 633 1065
          ETH Zurich, NO F5 e-mail fabian<at>sed.ethz.ch
          Sonneggstrasse 5 orcid.org/0000-0001-6340-7439
          8092 Zurich (Switzerland)
          -----------------------------------------------------------------------------
          QuakeML http://quakeml.org QuakePy http://quakepy.org
          CSEP http://www.cseptesting.org/centers/eth
          -----------------------------------------------------------------------------