Attribute/Logical Rolename |
Domain |
Datatype |
NULL |
Definition |
coid |
|
NUMERIC(15, 0) |
NO |
Coda identification. Each coda is assigned a unique positive integer which identifies it in the database |
commid |
|
NUMERIC(15, 0) |
YES |
Comment identification. This is a key used to point to free-form comments entered in the Remark relation. These comments store additional information about a tuple in another relation. Within the Remark relation, there may be many tuples with the same commid and different lineno, but the same commid will appear in only one other tuple among the rest of the relations in the database |
sta |
|
VARCHAR(6) |
NO |
Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used |
net |
|
VARCHAR(8) |
YES |
Unique network identifier. This character string is the name of a seismic network |
auth |
|
VARCHAR(15) |
NO |
The auth field specifies the source of the information. This may be a network identifier (FDSN or otherwise), or any other string indicating the source of the information in the record |
subsource |
|
VARCHAR(8) |
YES |
A second identifier to specify the system or process that derived the data. e.g., the origin's AUTH is CI, but the subsource (the solution) was computed by JIGGLE |
channel |
|
VARCHAR(8) |
YES |
Channel name |
channelsrc |
|
VARCHAR(8) |
YES |
Domain for channel. This specifies what naming convention is used for the channel name (i.e. SEED, USGS, etc.) |
seedchan |
|
VARCHAR(3) |
YES |
SEED channel name. The first character denotes the band code, the second for the instrument code and the third represents the component code |
location |
|
VARCHAR(2) |
YES |
Describes the individual sites on an array station, operated by the same network operator |
codatype |
|
VARCHAR(3) |
YES |
Coda type |
afix |
|
NUMERIC(7, 4) |
YES |
Nominal coda amplitude |
afree |
|
NUMERIC(7, 4) |
YES |
Free amplitude |
qfix |
|
NUMERIC(7, 4) |
YES |
Fixed coda decay constant |
qfree |
|
NUMERIC(7, 4) |
YES |
Free decay |
tau |
|
NUMERIC(7, 4) |
YES |
Coda duration (F-P time) |
nsample |
|
NUMERIC(6, 0) |
YES |
Number of coda sample windows |
rms |
|
NUMERIC(5, 3) |
YES |
Square root of the sum of the squares of the coda residuals, divided by the number of observations |
durtype |
|
VARCHAR(3) |
YES |
Duration type |
iphase |
|
VARCHAR(8) |
YES |
Reported phase. This eight-character field holds the name initially given to a seismic phase. Standard seismological labels for the types of signals (or phases) are used (e.g., P, PKP, PcP, pP). Both upper and lower case letters are available and should be used when appropriate, for example, pP or PcP.
(CNSS Table 15: P -> P-wave S -> S-wave) |
eramp |
|
NUMERIC(5, 3) |
YES |
Uncertainty in amplitude measurement |
units |
|
VARCHAR(4) |
NO |
Units of amplitude |
time1 |
|
NUMERIC(10, 0) |
YES |
Time for pairs |
amp1 |
|
NUMERIC(10, 0) |
YES |
Amplitude for pairs |
time2 |
|
NUMERIC(10, 0) |
YES |
Time for pairs |
amp2 |
|
NUMERIC(10, 0) |
YES |
Amplitude for pairs |
time3 |
|
NUMERIC(10, 0) |
YES |
Time for pairs |
amp3 |
|
NUMERIC(10, 0) |
YES |
Amplitude for pairs |
time4 |
|
NUMERIC(10, 0) |
YES |
Time for pairs |
amp4 |
|
NUMERIC(10, 0) |
YES |
Amplitude for pairs |
time5 |
|
NUMERIC(10, 0) |
YES |
Time for pairs |
amp5 |
|
NUMERIC(10, 0) |
YES |
Amplitude for pairs |
time6 |
|
NUMERIC(10, 0) |
YES |
Time for pairs |
amp6 |
|
NUMERIC(10, 0) |
YES |
Amplitude for pairs |
quality |
|
NUMERIC(3, 2) |
YES |
This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad.
Hypoinverse station archive card column 83:
0, 5 --> 1.00
1, 6 --> 0.75
2, 7 --> 0.50
3, 8 --> 0.25 |
datetime |
|
NUMERIC(25, 10) |
NO |
The UTC epoch "start time" from which the relative seconds time values stored in the time1 ... time6 columns are measured |
algorithm |
|
VARCHAR(15) |
YES |
Algorithm used. This is a brief textual description of the algorithm used to derive coda data |
winsize |
|
NUMERIC(7, 4) |
YES |
Window over which waveform absolute amplitudes averaged |
rflag |
|
VARCHAR(2) |
YES |
This flag describes whether an observation was generated automatically, by a human, or has been finalized |
lddate |
|
DATE |
YES |
Load date. Date and time that the record was created, in Oracle date datatype |