significant_event

Logical Entity Name | significant_event
Default Table Name | significant_event
Definition | Summary information on a significant event

significant_event Attributes

Attribute/Logical Rolename | Domain | Datatype | NULL | Definition
evid |  | NUMERIC(15, 0) | NO | 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
evname |  | VARCHAR(80) | YES | Event name. This is a descriptive name for major events
remarks |  | VARCHAR(2) | YES | This attribute is used to give some information about the event, such as felt or damage
nfelt |  | NUMERIC(8, 0) | YES | Number of felt reports
mmi |  | NUMERIC(2, 0) | YES | Reported or inferred Mercali intensity for event
pga |  | NUMERIC(6, 4) | YES | Peak ground acceleration recorded by any station for the event. Represented in g, where 1.0 = 1g
lddate |  | DATE | YES | Load date. Date and time that the record was created or last modified, in Oracle date datatype

significant_event Relationships

Parent Entity | Child Entity | Type | Foreign Keys
event | significant_event | Identifying | evid

significant_event Check Constraints

Check Constraint Name | CheckConstraint
seg_event01 | mmi >= 1 and mmi <= 12
seg_event02 | nfelt > 0
seg_event03 | pga > 0.0
seg_event04 | remarks in ('f','d','fd','df')