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

instrument identifier clarification for 2 char case #32

Open
crotwell opened this issue Jul 28, 2017 · 1 comment
Open

instrument identifier clarification for 2 char case #32

crotwell opened this issue Jul 28, 2017 · 1 comment

Comments

@crotwell
Copy link
Collaborator

See also #2 (comment)

The example in the instrument identifier section gives a 2 char code that is a "sub-instrument-type" of an existing 1 char type, ie WU in LWUS is a subtype of a W instrument. We do have this:

Extended instrument codes are not necessarily limited to extending sensor families defined using a single instrument code.

but I feel this is still confusing. The primary example should be of a totally new 2 char instrument code that has no relation to a preexisting 1 char instrument code. Say a "foobarmeter" with instrument code FB. If needed, we can also say that they FDSN may wish to define some 2 char instrument codes that are sub-types of existing 1 char codes,. But this is not the default or even primary reason for the expansion.

@chad-earthscope
Copy link

OK, I'll put in something else and change the emphasis to being new instruments with only a mentioned that they may be extensions as you suggest.

As noted in the 20170718 Identifiers document:

this example should be replaced with real codes once the first is defined

but good to change the emphasis.

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

2 participants