International Federation of Digital Seismograph Networks

Thread: FDSN Availability Service

None
Started: Jan. 17, 2019, 10:40 a.m.
Last activity: Feb. 1, 2019, 3:09 p.m.
Tim Ahern
Jan. 17, 2019, 10:40 a.m.
Dear members of FDSN WG III

At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
Waveform data availability service

Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.

Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]

Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.

Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.

================================

In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

Thanks for your consideration
Tim Ahern

Chair
FDSN WG III


  • Stephane Zuzlewski
    Jan. 17, 2019, 9:04 a.m.
    Sounds good to the NCEDC.

    Cheers,
    Stephane

    On 1/17/19 8:41 AM, Tim Ahern wrote:
    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following
    about adding the Availability Service to SeisComp3. (Bold Italicized
    text is from the draft minutes)

    /*Waveform data availability service*/

    /*Chad Trabant hoped that the working group would adopt the “waveform
    data availability” webservice as an official service.*/

    /*Tim Ahern indicated that there may be a SeisComP3 solution. John
    Clinton suggested that it was more related to the EIDA data nodes than
    to SeisComP3 installations. He also mentioned that the metrics
    calculated should also be the same. [Note: the availability web
    service returns lists of start stop times of a timeseries. Metrics can
    be derived from this information (e.g. number of gaps, % available,
    etc) but it is not currently an agreed upon metric that is defined by
    any FDSN member. ]*/

    /*Florian Haslinger asked about what the service produces, Chad
    Trabant outlined that it was a raw list of time segments with start
    and end times at a fine grain level.*/

    /*Reinoud Sleeman suggested that this was related to the QC metrics
    service, Tim Ahern thought that they were related but slightly
    different in the information being*//*provided. Reinoud Sleeman also
    indicated that it would likely only be the EIDA nodes as it would not
    be so easy for base SeisComP3 installations. Ahern will investigate if
    the data availability service can be added to SeisComp3 to benefit a
    broader cross section of the FDSN community. */

    ================================

    In last year’s IRIS budget there was funding available that addressed
    this issue. IRIS contracted with gempa to implement this capability.
     The work has been completed and it  will be available as an extension
    in subsequent releases of SeisComP3.  The purpose for this email to
    WGIII is to see if WGIII will recommend the availability service
    becoming a standard FDSN service.  Details about the service as
    implemented by IRIS several years ago can be found at
    http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service
    just like dataselect, station, and event.  If approved, IRIS will
    begin using the fdsn-availability service and eliminate the IRIS
    service endpoint. If approved IRIS will undertake the documentation in
    the FDSN space but it will be based on the existing documentation for
    the current IRIS availability service. Obviously we will be happy to
    accommodate suggestions from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found
    at
    http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to
    adopt the availability service as an FDSN standard.  Please register
    your vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III


    ----------------------
    FDSN Working Group III
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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

    --
    ------------------------------------------------------------------
    Stephane Zuzlewski University of California, Berkeley
    stephane<at>seismo.berkeley.edu Berkeley Seismological Laboratory
    Office: 510-664-9029 (Thu) 215 McCone Hall # 4760
    Fax: 510-643-5811 Berkeley, CA 94720-4760
    Remote: 209-724-9540 (Mon,Tue,Wed,Fri)


  • Pete Davis
    Jan. 17, 2019, 9:46 a.m.
    IDA DCC supports this.

    Dr. Peter Davis
    Executive Director, Project IDA
    University of California, San Diego
    http://ida.ucsd.edu/
    (o) 858-534-2839
    (f) 858-534-6354



    On Jan 17, 2019, at 8:41 AM, Tim Ahern <tim<at>iris.washington.edu> wrote:

    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
    Waveform data availability service

    Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.

    Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]

    Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.

    Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.

    ================================

    In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III


    ----------------------
    FDSN Working Group III
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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


  • Philip Crotwell
    Jan. 17, 2019, 11:55 a.m.
    Hi

    South Carolina Seismic Network votes yes.

    Tim, thanks for funding this.

    Philip Crotwell

    On Thu, Jan 17, 2019 at 11:42 AM Tim Ahern <tim<at>iris.washington.edu> wrote:

    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)

    Waveform data availability service

    Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.

    Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]

    Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.

    Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.

    ================================

    In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III


    ----------------------
    FDSN Working Group III
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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

  • Jose Antonio Jara Salvador
    Jan. 22, 2019, 3:16 p.m.
    Dear all, the Catalan Seismic Network votes YES.

    Thanks to IRIS for promoting and funding this.

    Cheers,

    Jose


    De: fdsn-wg3-products-bounce<at>lists.fdsn.org [fdsn-wg3-products-bounce<at>lists.fdsn.org] En nombre de Tim Ahern
    Enviado el: jueves, 17 de enero de 2019 17:42
    Para: FDSN Working Group III
    Asunto: [fdsn-wg3-products] FDSN Availability Service

    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
    Waveform data availability service
    Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.
    Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]
    Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.
    Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.
    ================================

    In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III


    • Alexandros Savvaidis
      Jan. 22, 2019, 9:57 p.m.
      Dear all,

      TexNet supports the FDSN availability service.
      Many thanks to IRIS.

      Best Regards,
      Alexandros

      Alexandros Savvaidis, Ph.D., Research Scientist
      Manager of Texas Seismological Network (TexNet)
      PI in Seismology, Center of Integrated Seismicity Research (CISR)

      From: <fdsn-wg3-products-bounce<at>lists.fdsn.org> on behalf of Jose Antonio Jara Salvador <joseantonio.jara<at>icgc.cat>
      Date: Tuesday, January 22, 2019 at 9:16 AM
      To: FDSN Working Group III <fdsn-wg3-products<at>lists.fdsn.org>
      Subject: RE: [fdsn-wg3-products] FDSN Availability Service

      Dear all, the Catalan Seismic Network votes YES.

      Thanks to IRIS for promoting and funding this.

      Cheers,

      Jose


      De: fdsn-wg3-products-bounce<at>lists.fdsn.org [fdsn-wg3-products-bounce<at>lists.fdsn.org] En nombre de Tim Ahern
      Enviado el: jueves, 17 de enero de 2019 17:42
      Para: FDSN Working Group III
      Asunto: [fdsn-wg3-products] FDSN Availability Service

      Dear members of FDSN WG III

      At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
      Waveform data availability service
      Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.
      Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]
      Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.
      Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.
      ================================

      In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

      If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

      More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

      The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

      Thanks for your consideration
      Tim Ahern

      Chair
      FDSN WG III


  • Peter Voss
    Jan. 31, 2019, 12:34 p.m.
    Dear all,

    DK,GEUS,Denmark votes yes.

    Peter Voss

    Fra: fdsn-wg3-products-bounce<at>lists.fdsn.org <fdsn-wg3-products-bounce<at>lists.fdsn.org> På vegne af Tim Ahern
    Sendt: 17. januar 2019 17:42
    Til: FDSN Working Group III <fdsn-wg3-products<at>lists.fdsn.org>
    Emne: [fdsn-wg3-products] FDSN Availability Service

    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
    Waveform data availability service
    Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.
    Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]
    Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.
    Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.
    ================================

    In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III


  • Constantin Ionescu
    Jan. 31, 2019, 12:48 p.m.
    National Institute for Earth Physics (NIEP) supports the principle of availability as an FDSN service, according with EIDA specifications.
  • John Clinton
    Jan. 31, 2019, 12:59 p.m.
    Dear Tim,

    The Swiss Seismological Service supports the principle of availability as an FDSN service, but would like to see a process to endorse the specifications

    best regards,

    John


    • Robert Casey
      Jan. 31, 2019, 4:10 p.m.

      Just a comment to the FDSN Working Group.

      I am glad to see the approvals recommending the inclusion of the availability service as an FDSN standard. One thing we have observed here at IRIS is that having ready access to precise data discovery has greatly improved the efficiency and speed of our data access tools. I look forward to seeing a specification develop that is suitable for the entirety of our international colleagues.

      Regards,

      Robert Casey
      IRIS Data Services



  • Christos Evangelidis
    Jan. 31, 2019, 2:51 p.m.
    Dear all,

    NOA supports the principle of availability as an FDSN service, but would
    like a process to endorse the specifications.

    Best regards,
    Christos Evangelidis

    On Thu, Jan 17, 2019 at 6:42 PM Tim Ahern <tim<at>iris.washington.edu> wrote:

    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following about
    adding the Availability Service to SeisComp3. (Bold Italicized text is from
    the draft minutes)

    *Waveform data availability service*

    *Chad Trabant hoped that the working group would adopt the “waveform data
    availability” webservice as an official service.*

    *Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton
    suggested that it was more related to the EIDA data nodes than to SeisComP3
    installations. He also mentioned that the metrics calculated should also be
    the same. [Note: the availability web service returns lists of start stop
    times of a timeseries. Metrics can be derived from this information (e.g.
    number of gaps, % available, etc) but it is not currently an agreed upon
    metric that is defined by any FDSN member. ]*

    *Florian Haslinger asked about what the service produces, Chad Trabant
    outlined that it was a raw list of time segments with start and end times
    at a fine grain level.*

    *Reinoud Sleeman suggested that this was related to the QC metrics
    service, Tim Ahern thought that they were related but slightly different in
    the information being**provided. Reinoud Sleeman also indicated that it
    would likely only be the EIDA nodes as it would not be so easy for base
    SeisComP3 installations. Ahern will investigate if the data availability
    service can be added to SeisComp3 to benefit a broader cross section of the
    FDSN community. *
    ================================

    In last year’s IRIS budget there was funding available that addressed this
    issue. IRIS contracted with gempa to implement this capability. The work
    has been completed and it will be available as an extension in subsequent
    releases of SeisComP3. The purpose for this email to WGIII is to see if
    WGIII will recommend the availability service becoming a standard FDSN
    service. Details about the service as implemented by IRIS several years
    ago can be found at http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service just
    like dataselect, station, and event. If approved, IRIS will begin using
    the fdsn-availability service and eliminate the IRIS service endpoint. If
    approved IRIS will undertake the documentation in the FDSN space but it
    will be based on the existing documentation for the current IRIS
    availability service. Obviously we will be happy to accommodate suggestions
    from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found at
    http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to
    adopt the availability service as an FDSN standard. Please register your
    vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III


    ----------------------
    FDSN Working Group III
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ |
    Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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



    --
    ---------------------------------------------------------------
    Dr. Christos Evangelidis
    Associate Researcher - Seismologist
    Hellenic Broadband Seismic Network
    INSTITUTE OF GEODYNAMICS
    NATIONAL OBSERVATORY OF ATHENS
    Tel:+30 210 3490043
    Email: cevan<at>noa.gr
    Www: http://members.noa.gr/cevan/en/
    ---------------------------------------------------------------

  • Wen-Tzong Liang
    Jan. 31, 2019, 7:55 p.m.
    Dear all,

    The BATS/IES, Academia Sinica, Taiwan agrees to adopt this availability service as an FDSN standard.

    Thank you,
    Wen-Tzong

    -----Original message-----
    From:Tim Ahern<tim<at>iris.washington.edu>
    To:FDSN Working Group III<fdsn-wg3-products<at>lists.fdsn.org>
    Date: Fri, 18 Jan 2019 00:41:37
    Subject: [fdsn-wg3-products] FDSN Availability Service

    Dear members of FDSN WG III
    At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
    Waveform data availability service
    Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.
    Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]
    Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.
    Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.
    ================================
    In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.
    If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.
    More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/
    The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.
    Thanks for your consideration
    Tim AhernChairFDSN WG III

    ----------------------
    FDSN Working Group III
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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


    • Ali Pinar
      Jan. 31, 2019, 3:11 p.m.
      Dear All,

      KOERI-Turkey agrees to adopt the waveform data availability WS as an
      official service

      Best regards,

      Wen-Tzong Liang <wtl<at>earth.sinica.edu.tw>, 31 Oca 2019 Per, 14:56 tarihinde
      şunu yazdı:

      Dear all,

      The BATS/IES, Academia Sinica, Taiwan agrees to adopt this availability
      service as an FDSN standard.

      Thank you,
      Wen-Tzong

      -----Original message-----
      *From:*Tim Ahern<tim<at>iris.washington.edu>
      *To:*FDSN Working Group III<fdsn-wg3-products<at>lists.fdsn.org>
      *Date: * Fri, 18 Jan 2019 00:41:37
      *Subject:* [fdsn-wg3-products] FDSN Availability Service
      Dear members of FDSN WG III

      At the 2017 FDSN WGIII meetings the minutes reflect the following about
      adding the Availability Service to SeisComp3. (Bold Italicized text is from
      the draft minutes)

      *Waveform data availability service*

      *Chad Trabant hoped that the working group would adopt the “waveform data
      availability” webservice as an official service.*

      *Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton
      suggested that it was more related to the EIDA data nodes than to SeisComP3
      installations. He also mentioned that the metrics calculated should also be
      the same. [Note: the availability web service returns lists of start stop
      times of a timeseries. Metrics can be derived from this information (e.g.
      number of gaps, % available, etc) but it is not currently an agreed upon
      metric that is defined by any FDSN member. ]*

      *Florian Haslinger asked about what the service produces, Chad Trabant
      outlined that it was a raw list of time segments with start and end times
      at a fine grain level.*

      *Reinoud Sleeman suggested that this was related to the QC metrics
      service, Tim Ahern thought that they were related but slightly different in
      the information being**provided. Reinoud Sleeman also indicated that it
      would likely only be the EIDA nodes as it would not be so easy for base
      SeisComP3 installations. Ahern will investigate if the data availability
      service can be added to SeisComp3 to benefit a broader cross section of the
      FDSN community. *
      ================================

      In last year’s IRIS budget there was funding available that addressed this
      issue. IRIS contracted with gempa to implement this capability. The work
      has been completed and it will be available as an extension in subsequent
      releases of SeisComP3. The purpose for this email to WGIII is to see if
      WGIII will recommend the availability service becoming a standard FDSN
      service. Details about the service as implemented by IRIS several years
      ago can be found at http://service.iris.edu/irisws/availability/1/.

      If adopted by WGIII gempa will make it an FDSN standard web service just
      like dataselect, station, and event. If approved, IRIS will begin using
      the fdsn-availability service and eliminate the IRIS service endpoint. If
      approved IRIS will undertake the documentation in the FDSN space but it
      will be based on the existing documentation for the current IRIS
      availability service. Obviously we will be happy to accommodate suggestions
      from the FDSN when adopted by WG III.

      More information can be found at the recent IRIS DS Newsletter found at
      http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

      The technical work has been completed by gempa but I seek your vote to
      adopt the availability service as an FDSN standard. Please register your
      vote by January 31, 2019.

      Thanks for your consideration
      Tim Ahern

      Chair
      FDSN WG III


      ----------------------
      FDSN Working Group III
      Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ |
      Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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


      ----------------------
      FDSN Working Group III
      Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ |
      Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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


  • Claudio Satriano
    Feb. 1, 2019, 12:45 a.m.
    Dear all,

    RESIF supports the principle of adding "Availability" to the official FDSN web services.

    We think however that we need to go through the formal approval not only of the service, but also on its actual specifications, including for example details of output format or metrics.

    Best regards,
    Claudio Satriano
    • Brian Shiro
      Feb. 1, 2019, 9:10 a.m.
      Aloha, everyone.

      USGS-HVO supports the addition of the proposed web service, provided it
      doesn't compromise resources needed by the existing web services. Would
      the new web service only work in SeisComP3, or might it be compatible with
      other systems as well, such as AQMS? ANSS networks are increasingly using
      FDSN web services to query local AQMS repositories, so having the parallel
      ability as SeisComP3 would be most welcome.

      Thank you,
      Brian Shiro

      On Fri, Feb 1, 2019 at 6:24 AM Claudio Satriano <satriano<at>ipgp.fr> wrote:

      Dear all,

      RESIF supports the principle of adding "Availability" to the official FDSN
      web services.

      We think however that we need to go through the formal approval not only
      of the service, but also on its actual specifications, including for
      example details of output format or metrics.

      Best regards,
      Claudio Satriano

      ----------------------
      FDSN Working Group III
      Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ |
      Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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



      --
      *********************************************
      Brian Shiro
      Seismic Network Manager
      USGS Hawaiian Volcano Observatory
      1-808-265-1415 (UTC-10 HST)
      bshiro<at>usgs.gov
      orcid 0000-0001-8756-288X
      Mail: PO Box 1026, Hilo, HI 96721
      Shipping: 29 Kuhio Street, Hilo, HI 96720
      *********************************************

      • Tim Ahern
        Feb. 1, 2019, 11:16 a.m.
        Hi Brian

        The service could work with any system. IRIS has paid for this support in SeisComp3 but someone could add this capability to the AQMS system. IRIS runs our own internally developed system and does not rely on SeisComp3.

        As far as I know no other system is in place to do this at this time but it just takes someone to step up and pay for the development.


        Cheers
        Tim

        Director of IRIS Data Services
        IRIS DMC
        1408 NE 45th Street #201
        Seattle, WA 98105

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








        On Feb 1, 2019, at 11:11 AM, Brian Shiro <bshiro<at>usgs.gov> wrote:

        Aloha, everyone.

        USGS-HVO supports the addition of the proposed web service, provided it doesn't compromise resources needed by the existing web services. Would the new web service only work in SeisComP3, or might it be compatible with other systems as well, such as AQMS? ANSS networks are increasingly using FDSN web services to query local AQMS repositories, so having the parallel ability as SeisComP3 would be most welcome.

        Thank you,
        Brian Shiro

        On Fri, Feb 1, 2019 at 6:24 AM Claudio Satriano <satriano<at>ipgp.fr <satriano<at>ipgp.fr>> wrote:
        Dear all,

        RESIF supports the principle of adding "Availability" to the official FDSN web services.

        We think however that we need to go through the formal approval not only of the service, but also on its actual specifications, including for example details of output format or metrics.

        Best regards,
        Claudio Satriano

        ----------------------
        FDSN Working Group III
        Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org <fdsn-wg3-products-unsubscribe<at>lists.fdsn.org>

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


        --
        *********************************************
        Brian Shiro
        Seismic Network Manager
        USGS Hawaiian Volcano Observatory
        1-808-265-1415 (UTC-10 HST)
        bshiro<at>usgs.gov <bshiro<at>usgs.gov>
        orcid 0000-0001-8756-288X
        Mail: PO Box 1026, Hilo, HI 96721
        Shipping: 29 Kuhio Street, Hilo, HI 96720
        *********************************************



        ----------------------
        FDSN Working Group III
        Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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


        • Doug Neuhauser
          Feb. 1, 2019, 11:43 a.m.
          NCEDC had tools to provide precise waveform inventory info from AQMS Waveform tables.
          We plan to implement an appropriate FDSN waveform inventory service using these tools
          as the spec becomes finalized.

          Note that the problem may be a bit more time intensive if your archive has
          event waveform snippets rather than just continuous data. There will likely
          be overlapping waveforms for multiple events that will have to be merged into
          single timespans. The NCEDC, which houses both event and continuous waveforms,
          will have to address this issue.

          Tim, does IRIS precompute and store the continuous timespans for each
          channel from the archive info of each contiguous segment of data
          being archived (presumably on a daily basis), or does it perform this
          operation on-the-fly for each availability request?

          Inquiring minds want to know...

          - Doug N

          On 2/1/19 11:17 AM, Tim Ahern wrote:
          Hi Brian

          The service could work with any system.  IRIS has paid for this support in SeisComp3 but someone could add this capability to the AQMS system. IRIS runs our own internally developed system and does not rely on SeisComp3.

           As far as I know no other system is in place to do this at this time but it just takes someone to step up and pay for the development.


          Cheers
          Tim

          Director of IRIS Data Services
          IRIS DMC
          1408 NE 45th Street #201
          Seattle, WA  98105

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








          On Feb 1, 2019, at 11:11 AM, Brian Shiro <bshiro<at>usgs.gov <bshiro<at>usgs.gov>> wrote:

          Aloha, everyone.

          USGS-HVO supports the addition of the proposed web service, provided it doesn't compromise resources needed by the existing web services.  Would the new web service only work in SeisComP3, or might it be compatible with other systems as well, such as AQMS?  ANSS networks are increasingly using FDSN web services to query local AQMS repositories, so having the parallel ability as SeisComP3 would be most welcome.

          Thank you,
          Brian Shiro

          On Fri, Feb 1, 2019 at 6:24 AM Claudio Satriano <satriano<at>ipgp.fr <satriano<at>ipgp.fr>> wrote:

          Dear all,

          RESIF supports the principle of adding "Availability" to the official FDSN web services.

          We think however that we need to go through the formal approval not only of the service, but also on its actual specifications, including for example details of output format or metrics.

          Best regards,
          Claudio Satriano

          ----------------------
          FDSN Working Group III
          Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org <fdsn-wg3-products-unsubscribe<at>lists.fdsn.org>

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



          --
          *********************************************
          Brian Shiro
          Seismic Network Manager
          USGS Hawaiian Volcano Observatory
          1-808-265-1415 (UTC-10 HST)
          bshiro<at>usgs.gov <bshiro<at>usgs.gov>
          orcid 0000-0001-8756-288X
          Mail: PO Box 1026, Hilo, HI 96721
          Shipping: 29 Kuhio Street, Hilo, HI 96720
          *********************************************



          ----------------------
          FDSN Working Group III
          Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org <fdsn-wg3-products-unsubscribe<at>lists.fdsn.org>

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



          ----------------------
          FDSN Working Group III
          Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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


          --
          ------------------------------------------------------------------------
          Doug Neuhauser University of California, Berkeley
          doug<at>seismo.berkeley.edu Berkeley Seismological Laboratory
          Remote Office: 530-752-5615 Berkeley, CA 94720-4760

  • Alexei Malovichko
    Feb. 1, 2019, 9:23 a.m.
    Dear members of FDSN WG III,

    Geophysical Survey of RAS supports the FDSN availability service.
    Thanks to IRIS for promoting this.

    Best regards,
    Alexey Malovichko


    17.01.2019 19:41, Tim Ahern пишет:
    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
    Waveform data availability service

    Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.

    Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]

    Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.

    Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.

    ================================

    In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III




    ----------------------
    FDSN Working Group III
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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


  • Peter Danecek
    Feb. 1, 2019, 9:43 a.m.
    Dear WG III members,

    MedNet / Istituto Nazionale di Geofisica e Vulcanologia (Italy) supports the principle of waveform availability as an FDSN services.
    We understand this service would provide a list of time span information.

    Like other EIDA nodes we would like to see a process to endorse the specifications.
    We (INGV) anticipate that this process can be rather brief, would provide some necessary clarifications and ideally ensure maximum coherency/consistency with respect to existing services.

    Best Regards,
    Peter Danecek

    On 17 Jan 2019, at 17:41, Tim Ahern <tim<at>iris.washington.edu> wrote:

    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
    Waveform data availability service

    Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.

    Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]

    Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.

    Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.

    ================================

    In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III


    ----------------------
    FDSN Working Group III
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ | Unsubscribe: fdsn-wg3-products-unsubscribe<at>lists.fdsn.org

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


  • IASPEI
    Feb. 1, 2019, 3:09 p.m.
    Hi WG3 Community,

    I support the idea to install this FDSN web-service.

    Cheers and a nice weekend,

    Johannes


    Dr. Johannes Schweitzer
    Principal Research Geophysicist
    Assoc. Professor (CEED, University of Oslo)

    ________________________________
    [norsar]<http://www.norsar.no/

    NORSAR
    Gunnar Randers vei 15
    PO Box 53, N-2007 Kjeller
    Norway
    Mobile: +47 41614946
    Phone: +47 63 80 59 00

    From: fdsn-wg3-products-bounce<at>lists.fdsn.org <fdsn-wg3-products-bounce<at>lists.fdsn.org> On Behalf Of Tim Ahern
    Sent: Thursday, January 17, 2019 5:42 PM
    To: FDSN Working Group III <fdsn-wg3-products<at>lists.fdsn.org>
    Subject: [fdsn-wg3-products] FDSN Availability Service

    Dear members of FDSN WG III

    At the 2017 FDSN WGIII meetings the minutes reflect the following about adding the Availability Service to SeisComp3. (Bold Italicized text is from the draft minutes)
    Waveform data availability service
    Chad Trabant hoped that the working group would adopt the “waveform data availability” webservice as an official service.
    Tim Ahern indicated that there may be a SeisComP3 solution. John Clinton suggested that it was more related to the EIDA data nodes than to SeisComP3 installations. He also mentioned that the metrics calculated should also be the same. [Note: the availability web service returns lists of start stop times of a timeseries. Metrics can be derived from this information (e.g. number of gaps, % available, etc) but it is not currently an agreed upon metric that is defined by any FDSN member. ]
    Florian Haslinger asked about what the service produces, Chad Trabant outlined that it was a raw list of time segments with start and end times at a fine grain level.
    Reinoud Sleeman suggested that this was related to the QC metrics service, Tim Ahern thought that they were related but slightly different in the information beingprovided. Reinoud Sleeman also indicated that it would likely only be the EIDA nodes as it would not be so easy for base SeisComP3 installations. Ahern will investigate if the data availability service can be added to SeisComp3 to benefit a broader cross section of the FDSN community.
    ================================

    In last year’s IRIS budget there was funding available that addressed this issue. IRIS contracted with gempa to implement this capability. The work has been completed and it will be available as an extension in subsequent releases of SeisComP3. The purpose for this email to WGIII is to see if WGIII will recommend the availability service becoming a standard FDSN service. Details about the service as implemented by IRIS several years ago can be found at http://service.iris.edu/irisws/availability/1/.

    If adopted by WGIII gempa will make it an FDSN standard web service just like dataselect, station, and event. If approved, IRIS will begin using the fdsn-availability service and eliminate the IRIS service endpoint. If approved IRIS will undertake the documentation in the FDSN space but it will be based on the existing documentation for the current IRIS availability service. Obviously we will be happy to accommodate suggestions from the FDSN when adopted by WG III.

    More information can be found at the recent IRIS DS Newsletter found at http://ds.iris.edu/ds/newsletter/vol20/no3/504/the-new-seiscomp3-waveform-availability-service/

    The technical work has been completed by gempa but I seek your vote to adopt the availability service as an FDSN standard. Please register your vote by January 31, 2019.

    Thanks for your consideration
    Tim Ahern

    Chair
    FDSN WG III


    Attachments