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