International Federation of Digital Seismograph Networks

Thread: WG-II

None
Started: 2013-07-16 02:43:12
Last activity: 2013-07-20 12:14:24
Sleeman, Reinoud (KNMI)
2013-07-16 02:43:12
________________________________


Dear WG-II members,

please find the draft agenda for the upcoming meeting in Gothenburg,
scheduled Tuesday July 23, 12:00 – 13:30 (room F3).

1) Status of StationXML at different data centers
Please provide me with the status at your datacenter.
2) Proposal by IRIS-DMC for simple text output format to be an optional
output for FDSN web services (see below)
3) Suggestions by IRIS-DMC for StationXML changes, see list below.
4) Data centers interconnection: status in Europe

Please feel free to add relevant items to the list.

Cheers,
Reinoud

____________________________________ Proposed text output:

---- Network level output
#Network | Description | StartTime | EndTime | TotalStations
IU|Global Seismograph Network (GSN - IRIS/USGS)|1988-01-01T00:00:00|2500-12-12T23:59:59|254

---- Station level output
#Network | Station | Latitude | Longitude | Elevation | SiteName | StartTime | EndTime
IU|ANMO|34.94591|-106.4572|1820.0|Albuquerque, New Mexico, USA|2008-06-30T20:00:00|2599-12-31T23:59:59

---- Channel level output
#Network | Station | Location | Channel | Latitude | Longitude | Elevation | Depth | Azimuth | Dip | Instrument | Scale | ScaleFreq | ScaleUnits | SampleRate | StartTime | EndTime
IU|ANMO|00|LHZ|34.945981|-106.457133|1671.0|145.0|0.0|-90.0|Geotech KS-54000 Borehole Seismometer|3.27508E9|0.02|M/S|1.0|2012-03-12T20:28:00|2599-12-31T23:59:59




________________________________________________ StationXML suggested changes:

1) Station::CreationDate should be optional. This value denotes when a station/site was
originally installed and is distinct from the startDate attribute used to note the station
epoch start. There is no need for it to be required, it cannot be retained in conversions
and many data centers do not have this information forcing them to set it to, e.g., the startDate.

2) Use xs:double type instead of xs:decimal type for ApproximationLowerBound, ApproximationUpperBound
and MaximumError values (in PolynomialType::ApproximationType). For consistency, xs:double is used
for most other floating point values in the schema. Also xs:double allows values in scientific notation.

3) Change startDate attribute (for Network, Station and Channel) to be optional. The issue is that
startDate for Network is not commonly known or contained in SEED, forcing the insertion of potentially
bad dates.

4) Remove redundancy of FrequencyType and SampleRateType, they are effectively the same except units
described as HERTZ versus SAMPLES/S. SampleRateType can be replaced with FrequencyType. If that is
not desired the DecimationType::InputSampleRate should be changed to SampleRateType for consistency.

5) Include data availability elements described in the fdsn-station+availability-1.0.xsd extension schema
as optional elements of the main schema.

6) Add "updated" attribute to important response elements (PolesZeros, Coefficients, etc.) and other
important elements (Latitude, Longitude, Azimuth, etc.) to track when these details were last changed.
Required or optional? Required means no backwards compatibility.

7) Add an optional ChannelGroup element to explicitly define groups of channels that should be considered
a "set", i.e. from the same instrument. This would allowing explicit grouping of BHE, BHN & BHZ and other
combinations like BH1, BH2 & BHZ.




  • Catherine Pequegnat
    2013-07-19 22:50:24
    Dear Reinoud and all,
    FDSN WS station is implemented at RESIF datacentre, as reported in the
    slide joinded. We also plan to implement IRIS 'output=text' extension,
    as well IRIS 'dataAvailability' extension before the end of 2013.

    As part as our reflexion on station.xml within RESIF, we would like to
    propose some extensions linked to OBS needs, plus some addtionnal
    features for the level Network. We put a short summary of those possible
    extension in the joined document.

    Best reagrds,
    Catherine Péquegnat, for the RESIF 'station.xml' working group.



    On 07/15/2013 09:43 PM, Sleeman, Reinoud (KNMI) wrote:
    ________________________________


    Dear WG-II members,

    please find the draft agenda for the upcoming meeting in Gothenburg,
    scheduled Tuesday July 23, 12:00 – 13:30 (room F3).

    1) Status of StationXML at different data centers
    Please provide me with the status at your datacenter.
    2) Proposal by IRIS-DMC for simple text output format to be an optional
    output for FDSN web services (see below)
    3) Suggestions by IRIS-DMC for StationXML changes, see list below.
    4) Data centers interconnection: status in Europe

    Please feel free to add relevant items to the list.

    Cheers,
    Reinoud

    ____________________________________ Proposed text output:

    ---- Network level output
    #Network | Description | StartTime | EndTime | TotalStations
    IU|Global Seismograph Network (GSN - IRIS/USGS)|1988-01-01T00:00:00|2500-12-12T23:59:59|254

    ---- Station level output
    #Network | Station | Latitude | Longitude | Elevation | SiteName | StartTime | EndTime
    IU|ANMO|34.94591|-106.4572|1820.0|Albuquerque, New Mexico, USA|2008-06-30T20:00:00|2599-12-31T23:59:59

    ---- Channel level output
    #Network | Station | Location | Channel | Latitude | Longitude | Elevation | Depth | Azimuth | Dip | Instrument | Scale | ScaleFreq | ScaleUnits | SampleRate | StartTime | EndTime
    IU|ANMO|00|LHZ|34.945981|-106.457133|1671.0|145.0|0.0|-90.0|Geotech KS-54000 Borehole Seismometer|3.27508E9|0.02|M/S|1.0|2012-03-12T20:28:00|2599-12-31T23:59:59




    ________________________________________________ StationXML suggested changes:

    1) Station::CreationDate should be optional. This value denotes when a station/site was
    originally installed and is distinct from the startDate attribute used to note the station
    epoch start. There is no need for it to be required, it cannot be retained in conversions
    and many data centers do not have this information forcing them to set it to, e.g., the startDate.

    2) Use xs:double type instead of xs:decimal type for ApproximationLowerBound, ApproximationUpperBound
    and MaximumError values (in PolynomialType::ApproximationType). For consistency, xs:double is used
    for most other floating point values in the schema. Also xs:double allows values in scientific notation.

    3) Change startDate attribute (for Network, Station and Channel) to be optional. The issue is that
    startDate for Network is not commonly known or contained in SEED, forcing the insertion of potentially
    bad dates.

    4) Remove redundancy of FrequencyType and SampleRateType, they are effectively the same except units
    described as HERTZ versus SAMPLES/S. SampleRateType can be replaced with FrequencyType. If that is
    not desired the DecimationType::InputSampleRate should be changed to SampleRateType for consistency.

    5) Include data availability elements described in the fdsn-station+availability-1.0.xsd extension schema
    as optional elements of the main schema.

    6) Add "updated" attribute to important response elements (PolesZeros, Coefficients, etc.) and other
    important elements (Latitude, Longitude, Azimuth, etc.) to track when these details were last changed.
    Required or optional? Required means no backwards compatibility.

    7) Add an optional ChannelGroup element to explicitly define groups of channels that should be considered
    a "set", i.e. from the same instrument. This would allowing explicit grouping of BHE, BHN & BHZ and other
    combinations like BH1, BH2 & BHZ.



    _______________________________________________
    fdsn-wg2-data mailing list
    fdsn-wg2-data<at>iris.washington.edu
    http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data



    --
    Institut des Sciences de la Terre (ISTerre)

    Adresse postale: BP 53, 38041 Grenoble Cedex 9, France
    Adresse géographique: Maison de Géosciences, 1381 rue de la piscine,
    Domaine Universitaire, 38400 St Martin d'Hères

    Tél: +33 (0)4 76 63 52 48
    Fax: +33 (0)4 76 63 52 52



    • Sleeman, Reinoud (KNMI)
      2013-07-19 21:51:37
      Thank you, Catherine. I will put it on the agenda. Cheers, Reinoud
      ________________________________________
      From: fdsn-wg2-data-bounces<at>iris.washington.edu [fdsn-wg2-data-bounces<at>iris.washington.edu] on behalf of Catherine Pequegnat [Catherine.Pequegnat<at>ujf-grenoble.fr]
      Sent: 19 July 2013 15:50
      To: fdsn-wg2-data<at>iris.washington.edu; Helle Pedersen; Catherine Pequegnat
      Subject: Re: [fdsn-wg2-data] WG-II

      Dear Reinoud and all,
      FDSN WS station is implemented at RESIF datacentre, as reported in the
      slide joinded. We also plan to implement IRIS 'output=text' extension,
      as well IRIS 'dataAvailability' extension before the end of 2013.

      As part as our reflexion on station.xml within RESIF, we would like to
      propose some extensions linked to OBS needs, plus some addtionnal
      features for the level Network. We put a short summary of those possible
      extension in the joined document.

      Best reagrds,
      Catherine Péquegnat, for the RESIF 'station.xml' working group.



      On 07/15/2013 09:43 PM, Sleeman, Reinoud (KNMI) wrote:
      ________________________________


      Dear WG-II members,

      please find the draft agenda for the upcoming meeting in Gothenburg,
      scheduled Tuesday July 23, 12:00 – 13:30 (room F3).

      1) Status of StationXML at different data centers
      Please provide me with the status at your datacenter.
      2) Proposal by IRIS-DMC for simple text output format to be an optional
      output for FDSN web services (see below)
      3) Suggestions by IRIS-DMC for StationXML changes, see list below.
      4) Data centers interconnection: status in Europe

      Please feel free to add relevant items to the list.

      Cheers,
      Reinoud

      ____________________________________ Proposed text output:

      ---- Network level output
      #Network | Description | StartTime | EndTime | TotalStations
      IU|Global Seismograph Network (GSN - IRIS/USGS)|1988-01-01T00:00:00|2500-12-12T23:59:59|254

      ---- Station level output
      #Network | Station | Latitude | Longitude | Elevation | SiteName | StartTime | EndTime
      IU|ANMO|34.94591|-106.4572|1820.0|Albuquerque, New Mexico, USA|2008-06-30T20:00:00|2599-12-31T23:59:59

      ---- Channel level output
      #Network | Station | Location | Channel | Latitude | Longitude | Elevation | Depth | Azimuth | Dip | Instrument | Scale | ScaleFreq | ScaleUnits | SampleRate | StartTime | EndTime
      IU|ANMO|00|LHZ|34.945981|-106.457133|1671.0|145.0|0.0|-90.0|Geotech KS-54000 Borehole Seismometer|3.27508E9|0.02|M/S|1.0|2012-03-12T20:28:00|2599-12-31T23:59:59




      ________________________________________________ StationXML suggested changes:

      1) Station::CreationDate should be optional. This value denotes when a station/site was
      originally installed and is distinct from the startDate attribute used to note the station
      epoch start. There is no need for it to be required, it cannot be retained in conversions
      and many data centers do not have this information forcing them to set it to, e.g., the startDate.

      2) Use xs:double type instead of xs:decimal type for ApproximationLowerBound, ApproximationUpperBound
      and MaximumError values (in PolynomialType::ApproximationType). For consistency, xs:double is used
      for most other floating point values in the schema. Also xs:double allows values in scientific notation.

      3) Change startDate attribute (for Network, Station and Channel) to be optional. The issue is that
      startDate for Network is not commonly known or contained in SEED, forcing the insertion of potentially
      bad dates.

      4) Remove redundancy of FrequencyType and SampleRateType, they are effectively the same except units
      described as HERTZ versus SAMPLES/S. SampleRateType can be replaced with FrequencyType. If that is
      not desired the DecimationType::InputSampleRate should be changed to SampleRateType for consistency.

      5) Include data availability elements described in the fdsn-station+availability-1.0.xsd extension schema
      as optional elements of the main schema.

      6) Add "updated" attribute to important response elements (PolesZeros, Coefficients, etc.) and other
      important elements (Latitude, Longitude, Azimuth, etc.) to track when these details were last changed.
      Required or optional? Required means no backwards compatibility.

      7) Add an optional ChannelGroup element to explicitly define groups of channels that should be considered
      a "set", i.e. from the same instrument. This would allowing explicit grouping of BHE, BHN & BHZ and other
      combinations like BH1, BH2 & BHZ.



      _______________________________________________
      fdsn-wg2-data mailing list
      fdsn-wg2-data<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data



      --
      Institut des Sciences de la Terre (ISTerre)

      Adresse postale: BP 53, 38041 Grenoble Cedex 9, France
      Adresse géographique: Maison de Géosciences, 1381 rue de la piscine,
      Domaine Universitaire, 38400 St Martin d'Hères

      Tél: +33 (0)4 76 63 52 48
      Fax: +33 (0)4 76 63 52 52




      • Helle Pedersen
        2013-07-20 04:39:52
        Dear all,

        FYI I will be at the FDSN WG-II meeting in Göteborg, so I will be
        available for any further information on RESIF and RESIF data
        distribution. I will make sure that any technical questions make it back
        to the RESIF team and in particular Catherine who is coordinating the
        activities of the RESIF station.xml working group.

        We would be happy to receive any comments to the documents before the
        meeting (mail to Catherine and myself)

        See you in Göteborg,

        Helle Pedersen

        RESIF Executive Director


        Le 19/07/2013 16:51, Sleeman, Reinoud (KNMI) a écrit :
        Thank you, Catherine. I will put it on the agenda. Cheers, Reinoud
        ________________________________________
        From: fdsn-wg2-data-bounces<at>iris.washington.edu [fdsn-wg2-data-bounces<at>iris.washington.edu] on behalf of Catherine Pequegnat [Catherine.Pequegnat<at>ujf-grenoble.fr]
        Sent: 19 July 2013 15:50
        To: fdsn-wg2-data<at>iris.washington.edu; Helle Pedersen; Catherine Pequegnat
        Subject: Re: [fdsn-wg2-data] WG-II

        Dear Reinoud and all,
        FDSN WS station is implemented at RESIF datacentre, as reported in the
        slide joinded. We also plan to implement IRIS 'output=text' extension,
        as well IRIS 'dataAvailability' extension before the end of 2013.

        As part as our reflexion on station.xml within RESIF, we would like to
        propose some extensions linked to OBS needs, plus some addtionnal
        features for the level Network. We put a short summary of those possible
        extension in the joined document.

        Best reagrds,
        Catherine Péquegnat, for the RESIF 'station.xml' working group.



        On 07/15/2013 09:43 PM, Sleeman, Reinoud (KNMI) wrote:
        ________________________________


        Dear WG-II members,

        please find the draft agenda for the upcoming meeting in Gothenburg,
        scheduled Tuesday July 23, 12:00 – 13:30 (room F3).

        1) Status of StationXML at different data centers
        Please provide me with the status at your datacenter.
        2) Proposal by IRIS-DMC for simple text output format to be an optional
        output for FDSN web services (see below)
        3) Suggestions by IRIS-DMC for StationXML changes, see list below.
        4) Data centers interconnection: status in Europe

        Please feel free to add relevant items to the list.

        Cheers,
        Reinoud

        ____________________________________ Proposed text output:

        ---- Network level output
        #Network | Description | StartTime | EndTime | TotalStations
        IU|Global Seismograph Network (GSN - IRIS/USGS)|1988-01-01T00:00:00|2500-12-12T23:59:59|254

        ---- Station level output
        #Network | Station | Latitude | Longitude | Elevation | SiteName | StartTime | EndTime
        IU|ANMO|34.94591|-106.4572|1820.0|Albuquerque, New Mexico, USA|2008-06-30T20:00:00|2599-12-31T23:59:59

        ---- Channel level output
        #Network | Station | Location | Channel | Latitude | Longitude | Elevation | Depth | Azimuth | Dip | Instrument | Scale | ScaleFreq | ScaleUnits | SampleRate | StartTime | EndTime
        IU|ANMO|00|LHZ|34.945981|-106.457133|1671.0|145.0|0.0|-90.0|Geotech KS-54000 Borehole Seismometer|3.27508E9|0.02|M/S|1.0|2012-03-12T20:28:00|2599-12-31T23:59:59




        ________________________________________________ StationXML suggested changes:

        1) Station::CreationDate should be optional. This value denotes when a station/site was
        originally installed and is distinct from the startDate attribute used to note the station
        epoch start. There is no need for it to be required, it cannot be retained in conversions
        and many data centers do not have this information forcing them to set it to, e.g., the startDate.

        2) Use xs:double type instead of xs:decimal type for ApproximationLowerBound, ApproximationUpperBound
        and MaximumError values (in PolynomialType::ApproximationType). For consistency, xs:double is used
        for most other floating point values in the schema. Also xs:double allows values in scientific notation.

        3) Change startDate attribute (for Network, Station and Channel) to be optional. The issue is that
        startDate for Network is not commonly known or contained in SEED, forcing the insertion of potentially
        bad dates.

        4) Remove redundancy of FrequencyType and SampleRateType, they are effectively the same except units
        described as HERTZ versus SAMPLES/S. SampleRateType can be replaced with FrequencyType. If that is
        not desired the DecimationType::InputSampleRate should be changed to SampleRateType for consistency.

        5) Include data availability elements described in the fdsn-station+availability-1.0.xsd extension schema
        as optional elements of the main schema.

        6) Add "updated" attribute to important response elements (PolesZeros, Coefficients, etc.) and other
        important elements (Latitude, Longitude, Azimuth, etc.) to track when these details were last changed.
        Required or optional? Required means no backwards compatibility.

        7) Add an optional ChannelGroup element to explicitly define groups of channels that should be considered
        a "set", i.e. from the same instrument. This would allowing explicit grouping of BHE, BHN & BHZ and other
        combinations like BH1, BH2 & BHZ.



        _______________________________________________
        fdsn-wg2-data mailing list
        fdsn-wg2-data<at>iris.washington.edu
        http://www.iris.washington.edu/mailman/listinfo/fdsn-wg2-data


        --
        Institut des Sciences de la Terre (ISTerre)

        Adresse postale: BP 53, 38041 Grenoble Cedex 9, France
        Adresse géographique: Maison de Géosciences, 1381 rue de la piscine,
        Domaine Universitaire, 38400 St Martin d'Hères

        Tél: +33 (0)4 76 63 52 48
        Fax: +33 (0)4 76 63 52 52





        --
        Helle Pedersen

        Directrice de RESIF
        Déléguée Scientifique au CNRS-INSU

        ISTERRE
        Université Joseph Fourier, Grenoble
        BP 53
        F-38041 Grenoble Cedex
        FRANCE
        Tel +33 (0)4 76 63 52 59
        Fax +33 (0)4 76 63 52 01



        • Sleeman, Reinoud (KNMI)
          2013-07-20 12:14:24

          ________________________________________
          From: Helle Pedersen [Helle.Pedersen<at>ujf-grenoble.fr]
          Sent: 19 July 2013 21:39
          To: Sleeman, Reinoud (KNMI)
          Cc: Catherine.Pequegnat<at>ujf-grenoble.fr; fdsn-wg2-data<at>iris.washington.edu
          Subject: Re: [fdsn-wg2-data] WG-II

          Dear all,

          FYI I will be at the FDSN WG-II meeting in Göteborg, so I will be
          available for any further information on RESIF and RESIF data
          distribution. I will make sure that any technical questions make it back
          to the RESIF team and in particular Catherine who is coordinating the
          activities of the RESIF station.xml working group.

          We would be happy to receive any comments to the documents before the
          meeting (mail to Catherine and myself)

          See you in Göteborg,

          Helle Pedersen

          RESIF Executive Director




    • Sleeman, Reinoud (KNMI)
      2013-07-19 22:03:57
      Dear all,

      please find a request for additional elements in FDSN Station XML
      provided by RESIF. I will insert this item in the agenda

      As part as our reflexion on station.xml within RESIF, we would like to
      propose some extensions linked to OBS needs, plus some addtionnal
      features for the level Network. We put a short summary of those possible
      extension in the joined document.

      I expect those who have proposed changes or additions to the schema
      to motivate these during the meeting.

      Reinoud

      (sorry for multiple posting)
      Attachments