-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add notification when element locations are all the same #13
Comments
Huh, that's new behavior. Agreed that we should check for this, but this is also definitely an issue with our AVO metadata — each element should have its own coordinates. Output of an FDSN query for DLL
shows identical coordinates
...weird that the elevations are still different! |
This is related to location codes and how AVO vs others choose to use them. It's a long story so easiest to explain in person. In short "AVO" has decided it wants infrasound array elements to all have the same station name and differentiate the channels via location code. WATC disagrees as large IMS arrays may be separated by km and should have difference station names, and prefers location codes be reserved for collocated sites with the same station and channel designation. Bottom-line, waveform_collection needs to be able to use location codes and provide unique coordinates and elevations. |
Just a note here that the problem here is really that each location code has the same lat/lon. We're working on fixing these metadata at IRIS. My response above was somewhat incorrect and misleading! |
DLL metadata now fixed on IRIS: |
@jwbishop can we close this? |
For example, the element locations are all the same for the following data:
SOURCE = 'IRIS'
NETWORK = 'AV'
STATION = 'DLL'
LOCATION = ''
CHANNEL = ''
STARTTIME = UTCDateTime('2019-07-15T16:50:00')
ENDTIME = STARTTIME + 10*60
It would be nice to know for beam forming when the user will need to import the element locations separately.
The text was updated successfully, but these errors were encountered: