AVO station coordinates are incomplete in IRIS FDSN

[liamtoney]

Original report by me.

---

The IRIS FDSN data source has most AVO station coordinates, but not all. Some examples of stations with missing coordinates are SSLN and OK01–OK04. gather_waveforms() does a good job of reporting such stations, but currently does not add in their coordinates. This would have to be a hard-coded sort of implementation — kind of unavoidable. But since I’m already hard-coding some stuff for the AVO Winston data source, perhaps having a few more conditional statements in there wouldn’t make much of a difference.

[liamtoney]

For storing these coordinates, one option would be to use a JSON file with key-value pairs for station code and lat/lon. This would be like my current JSON implementation for calib values. The JSON syntax would look something like

{
"SSLN" : [54.8118, -163.9959]
}

and the file would be kept under version control like the calib JSON file. I could start by using the coordinates provided in the AVO infrasound station Google Sheet.

[liamtoney]

Original comment by David Fee (Bitbucket: 557058:f36e7514-bbba-431e-8df0-3e3ac9a3395b, GitHub: davidfee5).

---

The JSON file could be an ok work-around, but we really should just get them correct on IRIS. OK0* should actually be OKIF 01,02,etc, so that may help a little.

[liamtoney]

Today I actually went through the process of finding all AVO infrasound stations which exist on AVO Winston but not on IRIS. The list is:

ADAK, AUE, CLCO1, CLCO2, CLCO3, CLCO4, CLCO5, CLES, DFR, FONW, FOSS, ISNN, OK01, OK02, OK03, OK04, OK05, OK06, SSLN

I’m aware that some of these stations were renamed and do exist in IRIS (under slightly different names) with coordinates. For the time being, though, I will still construct a JSON file with coordinates from these derived from the AVO Infrasound Station Google Sheet.

[liamtoney]

A work-around which addresses this (not the larger issue of AVO coords not being in IRIS, though!) via a JSON file is implemented in df8ab61