International Federation of Digital Seismograph Networks
Sign in
Posted:

System Upgrade 2026-07-02

The fdsn.org website will undergo a scheduled upgrade on 2026-07-02. Some operations may be paused during the process, and live data such as user sessions may be reset.

This message will be updated with details as the update time approaches.

Thread: FDSN Working Group V meeting @ IUGG, Montreal, 16 July 2019

Started: 2019-05-20 13:39:20
Last activity: 2019-07-01 11:18:40
Topics: FDSN Working Group V

This thread is from a mailing list that has moved to Google Groups. Use the following links to browse the updated archives.
Bruce Beaudoin
FDSN Working Group V meeting @ IUGG, Montreal, 16 July 2019
2019-05-20 13:39:20
Dear FDSN WG-V,

Below is a tentative agenda in preparation for our upcoming FSDN WG-V meeting in July during the IUGG meeting in Montreal, Canada July 11-17, 2019. If you have additional topics you would like WG-V to discuss, please send me your suggestions.

The FDSN WG-V meeting is scheduled for Tuesday 16 July from 12:00-13:30 in MCC room 513D

Tentative Agenda:
1. Proposal for standardize data logger state of health reporting (see attached pdf).

Sincerely, Bruce

===============
Bruce Beaudoin
Chair FDSN WG-V
IRIS PASSCAL Instrument Center
100 East Rd., New Mexico Tech
Socorro, NM 87801 USA
(575) 835-5071





View this message in Google Groups at https://groups.google.com/a/fdsn.org/d/msgid/fdsn-wg5-portable/7EDF557E-F4D8-4793-9F2F-A851089672D2%40passcal.nmt.edu.
Attachments
  • John Clinton
    Re: FDSN Working Group V meeting @ IUGG, Montreal, 16 July 2019
    2019-07-01 11:18:40
    Hi Bruce,

    thanks for this very nice and concise document on SoH. Attached are a few comments and suggestions from ETH. I hope this can be approved by FDSN in a relatively short time!

    John


    Add channel codes: the proposed time series channels also include guidelines for SEED channel code names so there is consistency across different manufacturers implementations.

    Sampling rate: GPS channels are specified to be at 0.00005sps - equal to about four samples per day. This is very low sampling compared to the data actually measured. Also, it's not a fraction of 86400, meaning that daily files will not always have the same amount of samples. That's an unnecessary complication.

    Sampling rate: instead of specifying an exact sampling rate value, rather specify a reasonable range for each type of data, which should include 1 per minute, so that what the manufacturers already have built would be within specification.

    View this message in Google Groups at https://groups.google.com/a/fdsn.org/d/msgid/fdsn-wg5-portable/20190701111840.30294.5857%40fdsn1.fdsn.org.