You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: