International Federation of Digital Seismograph Networks
Sign in

FDSN Working Group III

FDSN Working Group III on Coordination of Products, Tools and Services

This group was established at the 2007 FDSN meeting in Perugia Italy.

FDSN WGIII will identify standard products that may be produced by FDSN data centers. It will advocate product uniformity and methods of production for FDSN products. It will advocate development and distribution of standard software tools that will support the production of FDSN products.

The goal of FDSN WGIII is to coordinate the creation of uniform products at participating FDSN data centers. It will also attempt to standardize services and share tools that produce FDSN approved products.

Email address
fdsn-wg3-products@lists.fdsn.org
Type
Discussion

Discussion lists are for back-and-forth exchanges among a smaller audience. Only subscribers can post (most of the time), and subscriptions have to be approved.

Subscribers
157
Moderated by
IRIS Webmaster, Chad Trabant, Marcelo Belentani de Bianchi
Login to manage your subscriptions
November
October
September
August
July
June
May
April
March
February
January (18)
December (3)
November
October (1)
September
August (1)
July (8)
June
May
April
March
February (1)
January (19)
December (5)
November
October
September
August
July
June
May
April (1)
March (4)
February
January
December
November
October
September (1)
August (2)
July (1)
June
May
April
March (1)
February
January
December
November
October
September
August
July (1)
June (1)
May
April (1)
March (1)
February (7)
January
December (5)
November (1)
October
September
August (3)
July (10)
June
May (3)
April (2)
March (5)
February (12)
January (12)
December (3)
November (9)
October
September (29)
August
July
June
May
April
March
February
January
December
November
October
September
August (6)
July (11)
June (14)
May
April (1)
March (15)
February
January
December
November (3)
October
September (1)
August (88)
July (15)
June (1)
May (7)
April (6)
March (4)
February (5)
January
December
November
October (3)
September (2)
August (1)
July (5)
June (5)
May (1)
April (1)
March
February
January (1)
December
November
October
September
August
July (1)
June (2)
May (2)
April
March (1)
February (6)
January (1)
December
November
October (11)
September (10)
August (2)
July
June
May
April
March
February (4)
January (5)
December
November
October
September
August (1)
July
June
May
April
March
February
January
December
November
October
September
August
July
June (2)
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January
December
November
October
September
August
July
June
May
April
March
February
January (1)
December
November
October
September
August
July
June (4)
May
April
March
February
January
December
November
October
September (1)
August (1)

Active Message Threads for August 2016

Joseph Steim
Open Letter on the future of miniSeed
2016-08-23 20:06:35 - 2016-08-30 18:30:17
Participants in the discussion on the future of miniSEED International data exchange in earthquake seismology has been effective over decades because, among other reasons, SEED format has been mostly static. There are places in SEED into which everything, albeit awkwardly in some cases, has to fit. This creates a format that everybody may grouse about equally, but lives within. As a result, there has been a remarkable level of data sharing across networks. We were one of the early partic… [more]
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 12 - Reduce record length field from 4 bytes to 2 bytes
2016-08-11 19:58:23 - 2016-08-25 01:48:01
Hi all, Change proposal #12 to the 2016-3-30 straw man (iteration 1) is attached: Reduce record length field from 4 bytes to 2 bytes. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 8 - Allow digitizer to set indicators in fixed section of header
2016-08-11 19:52:12 - 2016-08-23 20:47:05
Hi all, Change proposal #8 to the 2016-3-30 straw man (iteration 1) is attached: Allow digitizer to set indicators in fixed section of header. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 9 - Reserve space in header for post-realtime flags
2016-08-11 19:55:32 - 2016-08-23 20:46:57
Hi all, Change proposal #9 to the 2016-3-30 straw man (iteration 1) is attached: Reserve space in header for post-realtime (e.g. archive) flags. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 7 - Change start time to custom structure
2016-08-11 19:47:52 - 2016-08-23 20:42:27
Hi all, Change proposal #7 to the 2016-3-30 straw man (iteration 1) is attached: Change start time to custom structure. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 6 - Change CRC to represent encoded rather than decoded data
2016-08-11 19:46:39 - 2016-08-23 20:09:07
Hi all, Change proposal #6 to the 2016-3-30 straw man (iteration 1) is attached: Change CRC to represent encoded rather than decoded data. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 13 - Change name of location ID to group ID and expand to 4 characters
2016-08-11 19:59:09 - 2016-08-20 17:40:39
Hi all, Change proposal #13 to the 2016-3-30 straw man (iteration 1) is attached: Change name of location ID to group ID and expand to 4 characters. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 17 - General compression
2016-08-12 00:30:56 - 2016-08-20 03:47:27
Hi all, Change proposal #17 to the 2016-3-30 straw man (iteration 1) is attached: General compression. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 24 - Change variable record length field to 16 bits
2016-08-12 00:39:08 - 2016-08-19 23:02:03
Hi all, Change proposal #24 to the 2016-3-30 straw man (iteration 1) is attached: Change variable record length field to 16 bits. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 19 - Define fields/headers to details in blockettes
2016-08-12 00:34:04 - 2016-08-19 22:38:59
Hi all, Change proposal #19 to the 2016-3-30 straw man (iteration 1) is attached: Define fields/headers to details in blockettes. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 1 - Combine Location and Channel codes
2016-08-11 19:39:24 - 2016-08-19 19:47:21
Hi all, Change proposal #1 to the 2016-3-30 straw man (iteration 1) is attached: Combine location identifier with channel codes. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 2 - Add U to Quality Indicator for user modified data
2016-08-11 19:40:57 - 2016-08-19 19:41:30
Hi all, Change proposal #2 to the 2016-3-30 straw man (iteration 1) is attached: Add U to Quality Indicator for user modified data. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - Discussion archive in FDSN Message Center
2016-08-17 16:24:01
Hello all, In our effort to be as inclusive as possible the next generation miniSEED proposals were sent to a long list of recipients including two FDSN Working Groups. Unfortunately many of the replies to these messages are only going to the FDSN Working Group lists. If you are not already a member of one of these mailing lists you can follow the ongoing discussions in the FDSN Message Center here: http://www.fdsn.org/message-center/topic/fdsn-wg3-products/ http://www.fdsn.org/message-cen… [more]
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 16 - Retain and reorganize bit flags
2016-08-12 00:28:05 - 2016-08-12 23:37:26
Hi all, Change proposal #16 to the 2016-3-30 straw man (iteration 1) is attached: Retain and reorganize bit flags. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad P.S. The next 10 proposals/comments (#16 through #25) from KMI/Qaunterra are prefixed with the following general comment: Paraphrase: "Omit information that is in some cases vital or at least useful to detailed understanding of the data acquisition environment and quality o… [more]
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 11 - Define network code as 6 characters and convention for temporary deployments
2016-08-11 19:57:40 - 2016-08-12 04:32:49
Hi all, Change proposal #11 to the 2016-3-30 straw man (iteration 1) is attached: Define network code as 6 characters and convention for temporary deployments. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
Replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 25 - Support CRC, suggest Quanterra CRC
2016-08-12 00:40:30
Hi all, Change proposal #25 to the 2016-3-30 straw man (iteration 1) is attached: Support CRC, suggest Quanterra CRC. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 23 - Retain information in Event Detection Blockettes
2016-08-12 00:38:01
Hi all, Change proposal #23 to the 2016-3-30 straw man (iteration 1) is attached: Retain information in Event Detection Blockettes. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 22 - Retain information in Calibration Blockettes
2016-08-12 00:37:03
Hi all, Change proposal #22 to the 2016-3-30 straw man (iteration 1) is attached: Retain information in Calibration Blockettes. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 21 - Retain the information in Timing Bloockettes
2016-08-12 00:36:15
Hi all, Change proposal #21 to the 2016-3-30 straw man (iteration 1) is attached: Retain the information in Timing Bloockettes. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 20 - Retain a time quality value
2016-08-12 00:35:03
Hi all, Change proposal #20 to the 2016-3-30 straw man (iteration 1) is attached: Retain a time quality value. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 18 - Fixed point data sample encoding
2016-08-12 00:31:45
Hi all, Change proposal #18 to the 2016-3-30 straw man (iteration 1) is attached: Fixed point data sample encoding. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposals 4 and 10
2016-08-11 20:15:29
Hi all, Apologies for the flurry of emails about change proposals, but ideally we now will have somewhat organized feedback on each of them. I did not include the following two proposals: #4 was to fix a typo in the straw man, which will be fixed. #10 was to accommodate non-integer sample rates in the header. The 2016-3-30 straw man already accommodates this by denoting the sampling rate as an IEEE float. Please let me know if anything is unclear or if I have missed any proposals. We ar… [more]
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 15 - Change opaque headers to optional headers, some defined by FDSN
2016-08-11 20:03:19
Hi all, Change proposal #15 to the 2016-3-30 straw man (iteration 1) is attached: Change opaque headers to optional headers, some defined by FDSN. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 14 - Change field 17 from opaque header count to length of optional headers
2016-08-11 20:00:54
Hi all, Change proposal #14 to the 2016-3-30 straw man (iteration 1) is attached: Change field 17 from opaque header count to length of optional headers. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 5 - Add comment to warning about time ordering of records during leap second
2016-08-11 19:45:34
Hi all, Change proposal #5 to the 2016-3-30 straw man (iteration 1) is attached: Add comment to warning about time ordering of records during leap second Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Chad Trabant
Next generation miniSEED - 2016-3-30 straw man change proposal 3 - Move flags to byte 4
2016-08-11 19:41:34
Hi all, Change proposal #3 to the 2016-3-30 straw man (iteration 1) is attached: Move flags to byte 4. Please use this thread to provide your feedback on this proposal by Wednesday August 24th. thanks, Chad
No replies
Tim Ahern
The future of miniSeed
2016-03-31 15:44:07 - 2016-08-11 17:16:44
Hello everyone, You are receiving this email because either you were in the initial list I sent the announcement to, are a member of FDSN WGII or WGIII or have expressed an interest in attending these discussions at the EGU. This includes a good mix of FDSN Network and data center personnel as well as representatives from equipment manufacturers. I am attaching a draft agenda that identifies the topics of discussion as well as giving the time and meeting place. I am also attaching a straw man … [more]
Replies
Ellen Yu
FDSN web services for Southern California to be added to FDSN web services list
2016-08-02 23:38:18 - 2016-08-03 19:00:42
Hello, The Southern California Earthquake Data Center now has FDSN web services available for use: fdsn-station service: http://service.scedc.caltech.edu/fdsnws/station/1/ fdsnws-dataselect service: http://service.scedc.caltech.edu/fdsnws/dataselect/1/ fdsn-event service: http://service.scedc.caltech.edu/fdsnws/event/1/ Non fdsn service - event gathers: http://service.scedc.caltech.edu/webstp/ Please send any questions regarding these web services to scedc@gps.caltech.edu … [more]
Replies
Glenn Thompson
Re: fdsnws-event - add support for event type in query and text format
2016-07-22 05:52:15 - 2016-08-03 01:14:36
QuakeML, but it is a generic point too for any system or data format that aims to be useful for volcano-seismology. Much of my own work at different observatories has involved taking systems and database schema designed for regional earthquake monitoring and expanding them to support volcano-seismic monitoring needs. But maybe QuakeML isn't meant to support the exchange of volcano-seismic event metadata because many such events are small - which leads to other issues. On Jul 21, 2016, at 9:32 … [more]
Replies