International Federation of Digital Seismograph Networks

FDSN Working Group II

Data Format, Data Centers and Software

fdsn-wg2-data@lists.fdsn.org

  • Your subscription must be approved by a moderator.
    Subscribe by email
  • You need to subscribe in order to post a message.
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 October 2016

Lion Krischer
Oct. 26, 2016, 12:38 p.m. - Oct. 27, 2016, 4:27 p.m.
Dear all, I propose a small change to be included in the next StationXML schema version that would force all datetimes to be explicitly marked as being in UTC. Technical details can be found here: https://github.com/FDSN/StationXML/pull/12 The proposed change forces all datetimes in a StationXML file to end with `Z`. This explicitly marks them as being in UTC which (according to the SEED standard) must be given in any case. # Motivation It is currently possible to have non-UTC datetimes... [more]
Replies
Reinoud Sleeman
Oct. 4, 2016, 11:02 a.m.
Dear WG2 members, during the last months numerous e-mails have been sent around in the discussion on the future of the mini-SEED (mseed) format as initialized by the strawman proposal by IRIS, both to the FDSN WG2 mailing list and also off-line. These e-mails have shown there is a lot of interest to think constructively about a modernized mseed format while at the same time there are severe concerns related to, in particular, backwards compatibility as the current format is strongly embedded... [more]
No replies