| Attribute/Logical Rolename |
Domain |
Datatype |
NULL |
Definition |
magid |
|
NUMERIC(15, 0) |
NO |
Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude |
| 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 |
| 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 |
| weight |
|
NUMERIC(4, 3) |
YES |
Magnitude weight |
| in_wgt |
|
NUMERIC(4, 3) |
YES |
Input weight.
Hypoinverse station archive card column 83:
0, 1, 2, 3 --> 1.00
4, 5, 6, 7, 8, 9 --> 0.00 |
| mag |
|
NUMERIC(7, 4) |
YES |
Magnitude for this station reading |
| magres |
|
NUMERIC(7, 4) |
YES |
Magnitude residual |
| magcorr |
|
NUMERIC(7, 4) |
YES |
Magnitude correction for this channel |
| 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 |