International Federation of Digital Seismograph Networks

FDSN Working Group II

Data Format, Data Centers and Software

Email address
fdsn-wg2-data@lists.fdsn.org
Type
Subscribers
165
Moderated by
Philip Crotwell, Javier Quinteros, IRIS Webmaster
Login to manage your subscriptions
October
September
August
July
June
May
April
March
February
January
December
November
October (1)
September
August (1)
July (3)
June
May
April (25)
March (1)
February
January
December
November
October
September (1)
August (8)
July (1)
June
May
April
March
February
January
December (2)
November (23)
October
September (1)
August
July
June
May (1)
April
March (4)
February
January
December
November
October
September
August
July (2)
June
May (1)
April (2)
March
February
January
December
November
October
September
August
July
June (1)
May
April (1)
March
February (2)
January (5)
December (1)
November (10)
October
September
August (2)
July (7)
June
May
April
March
February (1)
January
December
November
October
September (3)
August
July (3)
June (1)
May (5)
April
March (1)
February
January
December
November
October
September
August
July (10)
June
May
April (1)
March
February
January
December (1)
November (9)
October
September
August
July
June
May (2)
April
March
February
January
December
November
October
September
August
July
June (4)
May
April
March
February
January (6)
December (1)
November
October
September
August
July
June
May (1)
April (5)
March (5)
February
January
December
November
October
September
August
July
June
May
April
March
February
January (6)
December
November
October
September
August
July
June
May
April
March
February
January
December
November (2)
October (2)
September
August
July
June (1)

Active Message Threads for August 2016

Joseph Steim
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
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
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
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
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
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
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
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
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
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
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
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]
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
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
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
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
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
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
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
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
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
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
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
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
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
Goran Ekstrom
2016-08-04 22:59:04
Dear Colleagues and Members of Working Group II: I have been observing some of the discussions and exchanges in WGII concerning the efforts of developing a standard for a new/updated miniSEED format. It is clear from these discussions, as well as from input from users, data managers, and equipment manufacturers, that the time is right for FDSN to address -- with a new standard -- the shortcomings of the current miniSEED format. The development, adoption, and promotion of standards throu… [more]
No replies