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

Channel naming 1,2,3 for seismometers #15

Closed
flofux opened this issue Jul 16, 2020 · 13 comments
Closed

Channel naming 1,2,3 for seismometers #15

flofux opened this issue Jul 16, 2020 · 13 comments

Comments

@flofux
Copy link

flofux commented Jul 16, 2020

As this documentation will be the new main guideline for channel naming, I'd suggest to expand the explanation for seismometer channels that are not Z,N,E or should not be Z,N,E because this sometimes creates confusion/mess. We state that channels should be named Z,N,E when within 5 degrees of true N/E, but maybe we should add what to do if it's not. Let's be clear about whether the naming scheme should be 1,2,3 or Z,1,2 or Z,2,3. I vote for Z,2,3 as I think 1 should be reserved for a somewhat vertical component. Both Z,1,2 and Z,2,3 are currently in use, so either way we will break consistency in some cases.

I'd suggest to expand the description of 1,2,3 channels like this (or similar):

Orthogonal components but non traditional orientations. If the orientation of the horizontal components is known to deviate more than 5 degrees from true North/East, the respective channels should be named 2,3 instead of N,E (N->2, E->3).

In the field for Z,N,E channels it could be (or similar):

Traditional (Vertical, North-South, East-West), when WITHIN 5 degrees of true directions. Do not use N or E labels if the orientation of the horizontal components is known to deviate more than 5 degrees from true North/East.

@chad-earthscope
Copy link
Member

I agree, stronger wording in for this issue would be much better and documenting a common pattern very useful.

I would lean towards Z,1,2 due popularity (in the IRIS holdings) over Z,2,3. The counts of combinations at IRIS:

{1,2,Z} = 15461 <- the highest channel set count for number and Z combinations
{2,3,Z} = 617

Interestingly also high:
{1,2,3} = 4394

@crotwell
Copy link

Might also be helpful to give names in terms of a right handed xyz coordinate system relative to the seismometer. For some reason I get confused on that easily.

I think Z12 means 1 is in the seismometer's "y" direction and 2 is in the seismometer's "x" direction, which ends up being a left handed coordinate system, but...

@WayneCrawford
Copy link

For OBSs we have been using "Z12", based on IRIS precedent. Then, when we figured out that many of our short period OBS (geophone) vertical components were inverted, we went to "312" (can also be read as '123', but the important thing is that the "3" channel is the vertical). Don't know of a better solution, if you have one I'm game. It's good to have a convention to simplify processing but, in any case, once we're off of "ZNE" the the metadata should include the dip and azimuth, which is the true reference.

@WayneCrawford
Copy link

WayneCrawford commented Jul 16, 2020 via email

@crotwell
Copy link

Yikes, I thought that xyz was universal! :( But I guess names are always subject to local language and custom.

+1 for your version.
Maybe change "when the seismometer is properly oriented" to "when the seismometer is oriented to align with the traditional vertical-north-east coordinate system", just to be really clear?

I agree the metadata should be the real authority, but at least nice to have a naming convention that has some logic to it.

@crotwell
Copy link

This might not be a sentence. Was that meant to be a subheading?

Orthogonal components but non traditional orientations.

Also, just question, should 1 and 2 imply horizontal in general? Or is the implication only the other way?

Is it worth adding at end something about orthogonal but not vertical-horizontal orientations? Maybe like:

Orthogonal components that are not vertical and horizontal, e.g. along the edges of a cube turned up on a corner, should use A,B,C or U,V,W. Components with other orientations may use any remaining valid subsource codes.

@chad-earthscope
Copy link
Member

Also, just question, should 1 and 2 imply horizontal in general? Or is the implication only the other way?

I would think we should go for as much consistency as possible. I changed the table for seismometers (http://docs.fdsn.org/projects/source-identifiers/en/draft/channel-codes.html#seismometer) to have them in a 3,1,2 order FWIW.

@chad-earthscope
Copy link
Member

Is it worth adding at end something about orthogonal but not vertical-horizontal orientations? Maybe like:

That is touched on in the seismometer specific details.

@chad-earthscope
Copy link
Member

This might not be a sentence. Was that meant to be a subheading?

Orthogonal components but non traditional orientations.

I've fixed that grammar I believe.

If we want to specifically mention a mapping for "Z" let me know.

@crotwell
Copy link

Looks good to me.

@chad-earthscope
Copy link
Member

Are we done with this one?

@crotwell
Copy link

crotwell commented Sep 2, 2020

Can we add a line for Z12, like in the J source section? As that is very common and is not in the table. Like:

Z, 1, 2 | Orthogonal components, but non traditional horizontal orientations

@chad-earthscope
Copy link
Member

Done in e1743f2

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

4 participants