Expansion of the station code

[krischer]

Assuming the FDSN identifiers will be used in the new data format (please discuss this in #4) how should the station code be expanded (or not)?

[chad-earthscope]

As one idea described in an draft of new identifiers, posted to #4, the station code could be enhanced in the following ways:

• Allow up to 8 characters
• Allow a dash "-" character, in addition to the traditional Uppercase [A-Z] and Numeric [0-9] characters.

[jmsaurel]

I think FDSN should state that for permanent stations from global broadband networks (typically stations which enter tsunami warning systems or EEW) should continue to follow miniSEED rules :

• no more than 5 characters;
• only uppercase [A-Z] and [0-9] characters.

More generally, I think the new station codes (extended for example at 8 characters, as @chad-iris proposes), should retain the following two rules:

• first character should be a letter [A-Z];
• at least 3 characters.

[crotwell]

Is there an existing SEED requirement that station codes be 3+ chars?

[jmsaurel]

Is there an existing SEED requirement that station codes be 3+ chars?

Maybe not in SEED, but at least in ISC station registration form See this link

[kaestli]

Besides length restriction of the station name (not so relevant in the light of the new stream identification proposals), we may also consider good practices on the level of uniqueness station names should provide. Should it be globally unique in naming an instrumented site (as the ISC station registry implies), is it enough to be unique within a network (as stationXML and seed imply), or is it, also for the FDSN accepted that it is purely descriptive or can be missing (as the stream identification schemes proposed by this format imply)

[crotwell]

I assume by station names you mean station codes?

As a practical matter, the network code provides namespace, so I see no reason for station codes to be globally unique. The do need to be unique within the network.

The proposal from @chad-iris says the network, station and channel codes are required to be non-empty and the location code may be empty, so the station code can't be missing.

One nice extension might be to allow FDSN:<network>_<station> to identify a station, and perhaps FDSN:<network> to identify a network.

[kaestli]

@crotwell station names => yes, i meant station codes.

identifying a network or a station as a whole? fine, but do you see any use of this here / in purely stream oriented format?

[crotwell]

@kaestli may not be used in NGF directly, I was more thinking of external use cases like getting stationxml for a station from a fdsn web service. This makes it so that I can specify a single station with one parameter instead of 2.