Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Larger network codes, e.g. 10 characters #1

Open
chad-earthscope opened this issue Mar 19, 2020 · 4 comments
Open

Larger network codes, e.g. 10 characters #1

chad-earthscope opened this issue Mar 19, 2020 · 4 comments

Comments

@chad-earthscope
Copy link
Member

A suggestion to allow larger network codes beyond 8 characters has been posed, such as 10 characters, was posed at the 2019 FDSN meetings. This would allow a full 4-digit year in temporary network codes and more space for description of the deployment.

@crotwell
Copy link

I don't have strong feelings on 8 vs 10 chars, but I do think the network code should always be a 'code' or abbreviation, not a name. Too much length adds a burden on implementations and should be supported by a reason. Was any concrete reason given?

8 chars seems sufficient, allowing 4 chars for the code even when the full 4 digit year is included.

If there is a specific use case where 10 would make usage easier or better, then 10 is fine, but otherwise I feel 8 is enough.

@chad-earthscope
Copy link
Member Author

The reasons for 10 characters, as I remember it, were:

  • for temporary codes, if 4 are used for a year, only 4 are left to identify the experiment, e.g. SEIS1998

and

  • if we are going through expansion why not add more and avoid regret latter when we want more, the classic go-big-while-changing argument

I agree that we don't want something too big. I could go either way.

@crotwell
Copy link

crotwell commented Jul 1, 2020

My feel for how this will go is that for the forseeible future (years to a decade), all new temporary networks will want to be identified by a 2 char plus year identifier to allow interoperability with existing systems, so the SEISEX experiment in 2025 will probably want XQ2025 to be the network code instead of SEISEX2025.

At some later point, if/when systems that depend on 2 char network codes have been upgraded, then distinction between temp and permanent networks will just go away and the SEISEX2 experiment in 2035 may not even care about the start year part and will request the network code of just SEISEX2.

I kind of feel that 10 chars is kind of entering vanity license plate territory, and probably doesn't serve a real need. I do not see a huge benefit of 10, but don't see a huge downside either to be honest.

@WayneCrawford
Copy link

No strong feeling either, I would stick with 8 if there isn't a compelling reason for 10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants