| type |
| Base Table | eventprefor |
| Attribute Name | type |
| ColumnName | type |
| Logical Rolename | |
| RoleName | |
| Definition | Type of location |
| Note | Range: type = {H | C | A | D}
H = hypocenter
C = centroid
A = amplitude
D = double difference |
| evid |
| Base Table | eventprefor |
| Attribute Name | evid |
| ColumnName | evid |
| Logical Rolename | |
| RoleName | |
| Definition | Event identifier. Each event is assigned a unique integer which identifies it in a database. It is possible for several records in the Origin relation to have the same evid. This indicates there are several opinions about the location of the event. The evid does not have to be identical to the local network’s event identifier, which is stored in the Origin table. This allows merging data for a single event from multiple sources without insisting that database evid is identical to the source’s local event identifier |
| Note | Range: evid > 0 |
| orid |
| Base Table | eventprefor |
| Attribute Name | orid |
| ColumnName | orid |
| Logical Rolename | |
| RoleName | |
| Definition | Origin identification. Each origin is assigned a unique positive integer which identifies it in the database. The orid is used to identify one of the many hypotheses of the actual location of the event |
| Note | Range: orid > 0 |
| lddate |
| Base Table | eventprefor |
| Attribute Name | lddate |
| ColumnName | lddate |
| Logical Rolename | |
| RoleName | |
| Definition | Load date. Date and time that the record was created, in Oracle date datatype |
| Note | Range: Any valid date between January 01, 4712 BC and January 01, 4712 AD Units: YYYY/MM/DD HH24:MI:SS |