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

Add notification when element locations are all the same #13

Open
jwbishop opened this issue Dec 16, 2019 · 5 comments
Open

Add notification when element locations are all the same #13

jwbishop opened this issue Dec 16, 2019 · 5 comments
Labels
enhancement New feature or request

Comments

@jwbishop
Copy link
Collaborator

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.

@jwbishop jwbishop added the enhancement New feature or request label Dec 16, 2019
@liamtoney
Copy link
Member

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

http://service.iris.edu/irisws/fedcatalog/1/query?net=AV&format=text&includeoverlaps=true&nodata=404&station=DLL

shows identical coordinates

#Network | Station | Location | Channel | Latitude | Longitude | Elevation | Depth | Azimuth | Dip | SensorDescription | Scale | ScaleFreq | ScaleUnits | SampleRate | StartTime | EndTime

#DATACENTER=IRISDMC,http://ds.iris.edu
AV|DLL|01|HDF|59.136028|-158.614243|57.1|0|0|0|50A,Chaparral at DLL H1,Infrasound|244566.0|1|PA|100|2010-10-12T00:00:00|2599-12-31T23:59:59
AV|DLL|02|HDF|59.136028|-158.614243|43.3|0|0|0|50A,Chaparral at DLL H2,Infrasound|244566.0|1|PA|100|2010-10-12T00:00:00|2599-12-31T23:59:59
AV|DLL|03|HDF|59.136028|-158.614243|53.8|0|0|0|50A,Chaparral at DLL H3,Infrasound|244566.0|1|PA|100|2010-10-12T00:00:00|2599-12-31T23:59:59
AV|DLL|04|HDF|59.136028|-158.614243|58.5|0|0|0|50A,Chaparral at DLL H4,Infrasound|244566.0|1|PA|100|2010-10-12T00:00:00|2599-12-31T23:59:59
AV|DLL|05|HDF|59.136028|-158.614243|68.7|0|0|0|50A,Chaparral at DLL H5,Infrasound|244566.0|1|PA|100|2010-10-12T00:00:00|2599-12-31T23:59:59
AV|DLL|06|HDF|59.136028|-158.614243|58.5|0|0|0|50A,Chaparral at DLL H6,Infrasound|244566.0|1|PA|100|2010-10-12T00:00:00|2599-12-31T23:59:59

...weird that the elevations are still different!

@davidfee5
Copy link
Member

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.

@davidfee5
Copy link
Member

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!

@liamtoney
Copy link
Member

DLL metadata now fixed on IRIS:

http://service.iris.edu/irisws/fedcatalog/1/query?net=AV&format=text&includeoverlaps=true&nodata=404&station=DLL

@liamtoney
Copy link
Member

@jwbishop can we close this?

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

No branches or pull requests

3 participants