International Federation of Digital Seismograph Networks

Thread: Proposal for extended FDSN Source Identifier scheme

None
Started: 2020-03-20 08:32:53
Last activity: 2020-05-20 06:33:48
Chad Trabant
2020-03-20 08:32:53
Dear Javier and WG II members,

As presented at the 2019 FDSN meeting in Montreal, IRIS has prepared a proposed an extended FDSN Source Identifier scheme for consideration by the FDSN.

This specification incorporates the SEED network, station, location and channel codes into a single URI-like string in a way that each code can be extended for future use. This identifier scheme is expected to be used in future data formats, can be included in current StationXML, and other places where identification of data sources is needed.

The proposed specification may be found here:

https://iris-edu.github.io/xFDSN-source-identifiers/

Currently, the specification documentation source material is in an IRIS repository in GitHub:

https://github.com/iris-edu/xFDSN-source-identifiers/

We expect this will be transferred to the FDSN organization in GitHub upon approval (or earlier). We also recommend using the repository issues and pull request mechanism for review discussion and refinement of the specification.

We look forward to the discussion, refinement and eventual acceptance of a new identifier scheme for the FDSN.

regards,
Chad


  • Javier Quinteros
    2020-03-21 18:30:34
    Dear WG2 members,

    first of all, thanks Chad for sending this proposal.
    We will take the opportunity to use for the first time the "Framework
    for adoption" approved in Montreal (last July).
    http://fdsn.org/wg/framework/

    Let me remind you that we had an initial discussion on the proposal Chad
    is submitting some months ago (almost one year?) with a quite positive
    feedback from the community.
    So please, take a look again to the information sent, as well as the
    discussion in 2019, and let me know via email if you would like to take
    part of the "Proposal Review Team".

    We know that this a complicated moment, so we will try to use our common
    sense regarding deadlines.

    Stay health!

    Javier



    On 20.03.20 12:33, Chad Trabant wrote:
    Dear Javier and WG II members,

    As presented at the 2019 FDSN meeting in Montreal, IRIS has prepared a
    proposed an extended FDSN Source Identifier scheme for consideration by
    the FDSN.

    This specification incorporates the SEED network, station, location and
    channel codes into a single URI-like string in a way that each code can
    be extended for future use.  This identifier scheme is expected to be
    used in future data formats, can be included in current StationXML, and
    other places where identification of data sources is needed.

    The proposed specification may be found here:

    https://iris-edu.github.io/xFDSN-source-identifiers/

    Currently, the specification documentation source material is in an IRIS
    repository in GitHub:

    https://github.com/iris-edu/xFDSN-source-identifiers/

    We expect this will be transferred to the FDSN organization in GitHub
    upon approval (or earlier).  We also recommend using the repository
    issues and pull request mechanism for review discussion and refinement
    of the specification.

    We look forward to the discussion, refinement and eventual acceptance of
    a new identifier scheme for the FDSN.

    regards,
    Chad



    ----------------------
    FDSN Working Group II
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg2-data/ | Unsubscribe: fdsn-wg2-data-unsubscribe<at>lists.fdsn.org

    Sent from the FDSN Message Center (http://www.fdsn.org/message-center/)
    Update subscription preferences at http://www.fdsn.org/account/profile/


    --
    Javier Quinteros
    -------------------------------------------
    2.4/Seismologie
    Tel.: +49 (0)331/288-1931
    Fax: +49 (0)331/288-1277
    Email: javier<at>gfz-potsdam.de
    ___________________________________

    Helmholtz-Zentrum Potsdam
    Deutsches GeoForschungsZentrum GFZ
    Stiftung des öff. Rechts Land Brandenburg
    Telegrafenberg, 14473 Potsdam


  • Wayne Crawford
    2020-03-22 16:20:38
    Dear Chad and working group

    The proposal looks great and most ideas/expansions very welcome.  My only concern is about the transitional mapping of previously allocated temporary network codes:

    Transitional mapping of previously allocated temporary network codes
    Historical temporary network codes were allocated as two-character codes, with the first character being a digit or the letters X, Y or Z. Many of these codes have been reused for different deployments in different years and are therefore not globally unique. A data owner or delegate data center may wish to convert, or provide an alias, for data using the older, 2-character codes. The mapping from the 2-character codes is strongly recommended to follow this pattern:

    <2-character code><4-digit start year>
    For example, a network deployment allocated a network code of XA operating in the years 2002 and 2003 could be mapped to XA2002.

    Some temporary codes end with a number, which could result in "confusing" codes such as Z12010.   That wouldn't confuse anyone if 6-character codes always end with the 4-character year, the specification just needs to be very clear about this.

    Regards
    Wayne

    _______________________________
    Wayne Crawford
    CNRS Researcher
    Institut de Physique du Globe de Paris
    1, rue Jussieu
    75238 Paris Cedex 05
    +33 6 5151 1054

    On 20 March 2020 at 16:34:30, Chad Trabant (chad<at>iris.washington.edu) wrote:

    Dear Javier and WG II members,

    As presented at the 2019 FDSN meeting in Montreal, IRIS has prepared a proposed an extended FDSN Source Identifier scheme for consideration by the FDSN.

    This specification incorporates the SEED network, station, location and channel codes into a single URI-like string in a way that each code can be extended for future use.  This identifier scheme is expected to be used in future data formats, can be included in current StationXML, and other places where identification of data sources is needed.

    The proposed specification may be found here:

    https://iris-edu.github.io/xFDSN-source-identifiers/

    Currently, the specification documentation source material is in an IRIS repository in GitHub:

    https://github.com/iris-edu/xFDSN-source-identifiers/

    We expect this will be transferred to the FDSN organization in GitHub upon approval (or earlier).  We also recommend using the repository issues and pull request mechanism for review discussion and refinement of the specification.

    We look forward to the discussion, refinement and eventual acceptance of a new identifier scheme for the FDSN.

    regards,
    Chad


    ----------------------
    FDSN Working Group II
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg2-data/ | Unsubscribe: fdsn-wg2-data-unsubscribe<at>lists.fdsn.org

    Sent from the FDSN Message Center (http://www.fdsn.org/message-center/)
    Update subscription preferences at http://www.fdsn.org/account/profile/

    • Dear Wayne,

      Thank you for your input. I've entered this issue on the project site <https://github.com/iris-edu/xFDSN-source-identifiers/issues/8 as for the Proposal Review Team to consider.

      regards,
      Chad

      On Mar 22, 2020, at 8:20 AM, Wayne Crawford <crawford<at>ipgp.fr> wrote:

      Dear Chad and working group

      The proposal looks great and most ideas/expansions very welcome. My only concern is about the transitional mapping of previously allocated temporary network codes:

      Transitional mapping of previously allocated temporary network codes
      Historical temporary network codes were allocated as two-character codes, with the first character being a digit or the letters X, Y or Z. Many of these codes have been reused for different deployments in different years and are therefore not globally unique. A data owner or delegate data center may wish to convert, or provide an alias, for data using the older, 2-character codes. The mapping from the 2-character codes is strongly recommended to follow this pattern:

      <2-character code><4-digit start year>
      For example, a network deployment allocated a network code of XA operating in the years 2002 and 2003 could be mapped to XA2002.

      Some temporary codes end with a number, which could result in "confusing" codes such as Z12010. That wouldn't confuse anyone if 6-character codes always end with the 4-character year, the specification just needs to be very clear about this.

      Regards
      Wayne

      _______________________________
      Wayne Crawford
      CNRS Researcher
      Institut de Physique du Globe de Paris
      1, rue Jussieu
      75238 Paris Cedex 05
      +33 6 5151 1054

      On 20 March 2020 at 16:34:30, Chad Trabant (chad<at>iris.washington.edu <chad<at>iris.washington.edu>) wrote:

      Dear Javier and WG II members,

      As presented at the 2019 FDSN meeting in Montreal, IRIS has prepared a proposed an extended FDSN Source Identifier scheme for consideration by the FDSN.

      This specification incorporates the SEED network, station, location and channel codes into a single URI-like string in a way that each code can be extended for future use. This identifier scheme is expected to be used in future data formats, can be included in current StationXML, and other places where identification of data sources is needed.

      The proposed specification may be found here:

      https://iris-edu.github.io/xFDSN-source-identifiers/

      Currently, the specification documentation source material is in an IRIS repository in GitHub:

      https://github.com/iris-edu/xFDSN-source-identifiers/

      We expect this will be transferred to the FDSN organization in GitHub upon approval (or earlier). We also recommend using the repository issues and pull request mechanism for review discussion and refinement of the specification.

      We look forward to the discussion, refinement and eventual acceptance of a new identifier scheme for the FDSN.

      regards,
      Chad


      ----------------------
      FDSN Working Group II
      Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg2-data/ | Unsubscribe: fdsn-wg2-data-unsubscribe<at>lists.fdsn.org

      Sent from the FDSN Message Center (http://www.fdsn.org/message-center/)
      Update subscription preferences at http://www.fdsn.org/account/profile/


  • Javier Quinteros
    2020-05-20 06:33:48
    Dear WG II members,

    I hope you are all healthy and safe.

    Regarding the proposal sent some weeks ago by Chad (see below), we
    finally have a Review Team.
    They are Wayne Crawford, Philip Crotwell and Florian Fuchs. The three
    members, in close cooperation with Chad, will take the next 2 months to
    evaluate the proposal and present their recommendations.

    AFAIK, this is the first time that the new framework approved in
    Montreal is applied, so we will try to make the best to keep the spirit
    of the discussions on the framework.

    http://fdsn.org/wg/framework/

    Best,

    Javier Quinteros



    On 20.03.20 16:33, Chad Trabant wrote:
    Dear Javier and WG II members,

    As presented at the 2019 FDSN meeting in Montreal, IRIS has prepared a
    proposed an extended FDSN Source Identifier scheme for consideration by
    the FDSN.

    This specification incorporates the SEED network, station, location and
    channel codes into a single URI-like string in a way that each code can
    be extended for future use.  This identifier scheme is expected to be
    used in future data formats, can be included in current StationXML, and
    other places where identification of data sources is needed.

    The proposed specification may be found here:

    https://iris-edu.github.io/xFDSN-source-identifiers/

    Currently, the specification documentation source material is in an IRIS
    repository in GitHub:

    https://github.com/iris-edu/xFDSN-source-identifiers/

    We expect this will be transferred to the FDSN organization in GitHub
    upon approval (or earlier).  We also recommend using the repository
    issues and pull request mechanism for review discussion and refinement
    of the specification.

    We look forward to the discussion, refinement and eventual acceptance of
    a new identifier scheme for the FDSN.

    regards,
    Chad



    ----------------------
    FDSN Working Group II
    Topic home: http://www.fdsn.org/message-center/topic/fdsn-wg2-data/ | Unsubscribe: fdsn-wg2-data-unsubscribe<at>lists.fdsn.org

    Sent from the FDSN Message Center (http://www.fdsn.org/message-center/)
    Update subscription preferences at http://www.fdsn.org/account/profile/


    --
    Javier Quinteros
    -------------------------------------------
    2.4/Seismologie
    Tel.: +49 (0)331/288-1931
    Fax: +49 (0)331/288-1277
    Email: javier<at>gfz-potsdam.de
    ___________________________________

    Helmholtz-Zentrum Potsdam
    Deutsches GeoForschungsZentrum GFZ
    Stiftung des öff. Rechts Land Brandenburg
    Telegrafenberg, 14473 Potsdam