| orid |
| Base Entity | assocamo |
| Attribute Name | orid |
| Logical Rolename | orid |
| ColumnName | orid |
| RoleName | orid |
| 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 |
| ampid |
| Base Entity | assocamo |
| Attribute Name | ampid |
| Logical Rolename | ampid |
| ColumnName | ampid |
| RoleName | ampid |
| Definition | Amplitude identification. Each amplitude is assigned a unique positive integer identifying it. This number is used in the AssocAmO relation along with the origin identifier to link Amp and Origin. This number is used also in the AssocAmM relation along with the magnitude identifier to link Amp and Netmag |
| Note | Range: ampid > 0 |
| commid |
| Base Entity | assocamo |
| Attribute Name | commid |
| Logical Rolename | commid |
| ColumnName | commid |
| RoleName | commid |
| Definition | 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 |
| Note | Range: commid > 0 |
| auth |
| Base Entity | assocamo |
| Attribute Name | auth |
| Logical Rolename | auth |
| ColumnName | auth |
| RoleName | auth |
| Definition | 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 |
| Note | Range: Any free-format string up to 15 characters |
| subsource |
| Base Entity | assocamo |
| Attribute Name | subsource |
| Logical Rolename | subsource |
| ColumnName | subsource |
| RoleName | subsource |
| Definition | 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 |
| Note | Range: Any free-format string up to 8 characters |
| delta |
| Base Entity | assocamo |
| Attribute Name | delta |
| Logical Rolename | delta |
| ColumnName | delta |
| RoleName | delta |
| Definition | Source-receiver distance. This attribute is the arc length, over the earth’s surface, of the path the seismic phase follows from source to receiver. The location of the origin is specified in the origin record referenced by the attribute orid. The attribute arid points to the record in the Arrival relation that identifies the receiver. The value of the attribute can exceed 180 degrees, it can even exceed 360 degrees, the geographic distance between source and receiver is delta mod(180) |
| Note | Range: delta >= 0.0 Units: Degrees |
| seaz |
| Base Entity | assocamo |
| Attribute Name | seaz |
| Logical Rolename | seaz |
| ColumnName | seaz |
| RoleName | seaz |
| Definition | Station to event azimuth. This attribute is calculated from the station and event locations. It is measured clockwise from North |
| Note | Range: 0.0 <= seaz <= 360.0 Units: Degrees |
| rflag |
| Base Entity | assocamo |
| Attribute Name | rflag |
| Logical Rolename | rflag |
| ColumnName | rflag |
| RoleName | rflag |
| Definition | This flag describes whether an observation was generated automatically, by a human, or has been finalized |
| Note | Range: rflag = {A | H | F} A = automatic H = reviewed by human F = finalized |
| lddate |
| Base Entity | assocamo |
| Attribute Name | lddate |
| Logical Rolename | lddate |
| ColumnName | lddate |
| RoleName | lddate |
| Definition | Load date. Date and time that the record was created or last modified, 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 |