SAC files aren't recording location codes

[gthompson]

From @GoogleCodeExporter on August 1, 2015 21:51

What steps will reproduce the problem?
1. create a sac file for a SCNL that includes the location code (IU, for 
example uses 00 and 10 for location codes)
2. load the sac file into a waveform:    w= loadsac(waveform, mysacfilename)
3. look at the resulting waveform :  disp(w)

What is the expected output? What do you see instead?
There should be a location code.  Instead, there is a location code of --

Please use labels and text to provide additional information.

To fix, change getSCNL from within @waveform/private/sac2waveform.m  
include the location, which is stored in header.KHOLE.
I'm not fixing yet because I don't know what ramifications there might be.

Original issue reported on code.google.com by [email protected] on 22 Nov 2011 at 1:23

Copied from original issue: giseislab/gismotools#29

[gthompson]

From @GoogleCodeExporter on August 1, 2015 21:51

I asked around a bit. Sounds like KHOLE is frequently used to store location 
codes (I had never heard of the field). I am uneasy about it because it is 
technically a secondary use of this the field. Sounds extremely loose. But then 
location codes are also unusually loose.
     "KHOLE:  Nuclear: hole identifier; Other: location identifier."
Another way to pose the question is  "who the hell else is using the KHOLE 
field?"

I do not anticipate any problems arising from this change. 

Original comment by [email protected] on 22 Nov 2011 at 9:47