Diagram Report

 CISN/ANSS Parametric Information
Version 1.6.3

Berkeley Seismological Laboratory
Stephane Zuzlewski
Last Modified 4/13/2020
Copyright 2020 CISN/ANSS
 
Table of Contents

            Table of Contents	          
            Model Summary Report	          
            Model Detail Reports	          
            Entity Summary Report	          
            Entity Detail Reports	          
            Model Detail Reports	          
            Table Summary Report	          
            Table Detail Reports	          
            Oracle Sequence Summary Report	          
            Oracle Sequence Detail Report	          

Model Summary Report

Name	DatabasePlatform	 
Logical	Logical	
NCEDC	Oracle 12c	

Model Detail Reports

Logical

Model Name	Logical	
Database Platform	Logical	

Entity Summary Report

Entity Name	Entity Type	Primary Keys	 # Attr	
amp	Independent	ampid	27	
ampset	Dependent	ampsetid,ampid	2	
ampsettypes	Independent	ampsettype	2	
arrival	Independent	arid	28	
assocamm	Dependent	magid,ampid	13	
assocamo	Dependent	orid,ampid	9	
assocaro	Dependent	orid,arid	20	
assoccom	Dependent	magid,coid	12	
assoccoo	Dependent	orid,coid	9	
assocevampset	Dependent	ampsetid,ampsettype	6	
assoctypecat	Independent	etype,catid	2	
coda	Independent	coid	40	
event	Independent	evid	11	
eventcategory	Independent	catid	3	
eventprefmag	Independent	magtype,evid	4	
eventprefmec	Independent	mechtype,evid	4	
eventprefor	Independent	type,evid	4	
eventtype	Independent	etype	3	
mec	Independent	mecid	56	
mecchannel	Dependent	mecdataid,net,sta,seedchan,location	5	
mecdata	Independent	mecdataid	17	
mecfreq	Independent	mecfreqid	3	
mecfreqdata	Dependent	mecfreqid,type	3	
mecobject	Independent	dataid,mecid	5	
netmag	Independent	magid	16	
origin	Independent	orid	43	
origin_error	Dependent	orid	21	
remark	Independent	commid,lineno	4	

Entity Detail Reports

amp

Entity Name	amp	
Owner Name		
Primary Keys	ampid	
Definition	Summary information on an amplitude reading	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
ampid		NUMERIC(15, 0)	N	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	 
commid		NUMERIC(15, 0)	Y	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	 
datetime		NUMERIC(25, 10)	Y	The date of associated with information in the record, in true epoch format

* In the current real time system, we know the exact amplitude time as well as the window.
  Therefore, we can set values for the datetime, wstart & duration fields.

* In the case where we know only the time of the amplitude but not the window, we set:
        datetime = [AMPLITUDE TIME]
        wstart = [AMPLITUDE TIME]
        duration = 0

* In the case where we do not know the amplitude time nor the window, we set:
        datetime = NULL
        wstart = [ORIGIN TIME]
        duration = NULL
	 
sta		VARCHAR(6)	N	Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used	 
net		VARCHAR(8)	Y	Unique network identifier. This character string is the name of a seismic network	 
auth		VARCHAR(15)	N	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)	Y	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)	Y	Channel name	 
channelsrc		VARCHAR(8)	Y	Domain for channel. This specifies what naming convention is used for the channel name (i.e. SEED, USGS, etc.)	 
seedchan		VARCHAR(3)	Y	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)	Y	Describes the individual sites on an array station, operated by the same network operator	 
iphase		VARCHAR(8)	Y	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	 
amplitude		DOUBLE PRECISION	N	Amplitude in appropriate units for type	 
amptype		VARCHAR(8)	Y	Amplitude type	 
units		VARCHAR(4)	N	Units of amplitude	 
ampmeas		VARCHAR(1)	Y	Amplitude measure	 
eramp		NUMERIC(5, 3)	Y	Uncertainty in amplitude measurement	 
flagamp		VARCHAR(4)	Y	This attribute is a flag to indicate whether amplitude is over P packet, S packet, entire waveform, etc	 
per		NUMERIC(10, 4)	Y	Signal period. This attribute is the period of the signal described by the amplitude record	 
snr		DOUBLE PRECISION	Y	Signal-to-noise ratio. This is an estimate of the signal relative to that of the noise immediately preceding it	 
tau		NUMERIC(9, 4)	Y	Coda duration (F-P time)	 
quality		NUMERIC(2, 1)	Y	This attribute describes the completeness of the time window of data. A complete time window is 1.0, an incomplete time window is 0.0. If an incomplete time window has been human-reviewed and the analyst is confident that the peak amplitude was recorded and properly computed despite the presence of data gaps, the value is set to 0.5 to indicate the window contains data gaps, but is usable	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
cflag		VARCHAR(2)	Y	This flag indicates whether the amplitude value is below noise, on scale or clipped	 
wstart		DOUBLE PRECISION	N	Start of time window of amplitude measurement

* In the current real time system, we know the exact amplitude time as well as the window.
  Therefore, we can set values for the datetime, wstart & duration fields.

* In the case where we know only the time of the amplitude but not the window, we set:
        datetime = [AMPLITUDE TIME]
        wstart = [AMPLITUDE TIME]
        duration = 0

* In the case where we do not know the amplitude time nor the window, we set:
        datetime = NULL
        wstart = [ORIGIN TIME]
        duration = NULL
	 
duration		DOUBLE PRECISION	Y	Duration of amplitude reading

* In the current real time system, we know the exact amplitude time as well as the window.
  Therefore, we can set values for the datetime, wstart & duration fields.

* In the case where we know only the time of the amplitude but not the window, we set:
        datetime = [AMPLITUDE TIME]
        wstart = [AMPLITUDE TIME]
        duration = 0

* In the case where we do not know the amplitude time nor the window, we set:
        datetime = NULL
        wstart = [ORIGIN TIME]
        duration = NULL
	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	amp01	ampid > 0	 
	Check	amp02	amplitude > 0	 
	Check	amp03	ampmeas in ('0','1')	 
	Check	amp04	amptype in ('C','WA','WAS','WASF','PGA','PGV','PGD','WAC','WAU','IV2','SP.3','SP1.0','SP3.0','ML100','ME100','EGY','M0')	 
	Check	amp06	eramp >= 0.0	 
	Check	amp07	flagamp in ('P','S','R','PP','ALL','SUR')	 
	Check	amp08	per > 0.0	 
	Check	amp09	tau > 0.0	 
	Check	amp10	units in ('c','s','mm','cm','m','ms','mss','cms','cmss','mms','mmss','mc','nm','e','cmcms','none','dycm')	 
	Check	amp11	quality >= 0.0 and quality <= 1.0	 
	Check	amp12	rflag in ('a','h','f','A','H','F')	 
	Check	amp13	cflag in ('bn', 'os','cl','BN','OS','CL')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
ampset	Identifying	One To Zero or More					NO	 
assocamm	Identifying	One To Zero or More					NO	 
assocamo	Identifying	One To Zero or More					NO	 

ampset

Entity Name	ampset	
Owner Name		
Primary Keys	ampsetid,ampid	
Definition	This table associates amplitudes with a set	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
ampsetid		NUMERIC(0, 0)	N	Amplitude set identifier	 
ampid		NUMERIC(15, 0)	N	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	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
assocevampset	Non-Specific						NO	 
amp	Identifying	One To Zero or More				ampid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

ampsettypes

Entity Name	ampsettypes	
Owner Name		
Primary Keys	ampsettype	
Definition	This table describes the list of valid amplitudes set types	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
ampsettype		VARCHAR(20)	N	Amplitude set type	 
description		VARCHAR(80)	Y	The long description of an amplitude set type	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
assocevampset	Identifying	One To Zero or More					NO	 

arrival

Entity Name	arrival	
Owner Name		
Primary Keys	arid	
Definition	Summary information on a seismic arrival	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
arid		NUMERIC(15, 0)	N	Arrival identifier. Each arrival is assigned a unique positive integer identifying it. This number is used in the AssocArO relation along with the origin identifier to link Arrival and Origin	 
commid		NUMERIC(15, 0)	Y	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	 
datetime		NUMERIC(25, 10)	N	The date of associated with information in the record, in true epoch format	 
sta		VARCHAR(6)	N	Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used	 
net		VARCHAR(8)	Y	Unique network identifier. This character string is the name of a seismic network	 
auth		VARCHAR(15)	N	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)	Y	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.
Contains hypoinverse station card column 109 for historic catalogs	 
channel		VARCHAR(8)	Y	Channel name	 
channelsrc		VARCHAR(8)	Y	Domain for channel. This specifies what naming convention is used for the channel name (i.e. SEED, USGS, etc.)	 
seedchan		VARCHAR(3)	Y	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)	Y	Describes the individual sites on an array station, operated by the same network operator	 
iphase		VARCHAR(8)	Y	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	 
qual		VARCHAR(1)	Y	Onset quality. This single-character flag is used to denote the sharpness of the onset of a seismic phase. This attribute does not denote the timing accuracy	 
clockqual		VARCHAR(1)	Y	This field describes whether the clock quality associated with a particular arrival is known, and if so, is good or bad	 
clockcorr		NUMERIC(15, 0)	Y	This field indicates the amount of time to add to the arrival time if clock correction is known	 
ccset		VARCHAR(1)	Y	This field describes whether the clock correction has been added or applied to the arrivals in computing a hypocenter solution	 
fm		VARCHAR(2)	Y	First motion. This is a two-character indication of first motion. The first character describes first motion seen on short-period channels and the second holds for long-period instruments. Compression (dilation) on a short-period sensor is denoted by c(d) and compression (dilation) on a long-period sensor is denoted by u(r). Empty character positions will be indicated by dots (e.g., ".r"). Lower quality first motions can be described by +(-)	 
ema		NUMERIC(5, 2)	Y	Emergence angle. This attribute is the emergence angle of an arrival, as observed at a three-component station or array. The value increases from the vertical direction towards the horizontal	 
azimuth		NUMERIC(4, 1)	Y	Station to event azimuth measured clockwise from true north. Identified from waveform analysis	 
slow		NUMERIC(8, 4)	Y	Observed slowness. This is the observed slowness of a wave as it sweeps across an array	 
deltim		NUMERIC(5, 2)	Y	Arrival time uncertainty. This attribute gives the standard deviation of a detection time	 
delinc		NUMERIC(4, 2)	Y	Uncertainty in the angle. This attribute gives the standard deviation of the angle of emergence	 
delaz		NUMERIC(5, 2)	Y	Uncertainty in the azimuth. This attribute gives the standard deviation of the azimuth of a signal	 
delslo		NUMERIC(8, 4)	Y	Uncertainty in slowness. This attribute gives the standard deviation of the slowness of a signal	 
quality		NUMERIC(3, 2)	Y	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad.
Hypoinverse station archive card columns 17 & 50:
0, 5 --> 1.00
1, 6 --> 0.75
2, 7 --> 0.50
3, 8 --> 0.25
4, 9 --> 0.00	 
snr		DOUBLE PRECISION	Y	Signal-to-noise ratio. This is an estimate of the signal relative to that of the noise immediately preceding it	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	arrival01	arid > 0	 
	Check	arrival02	azimuth >= 0.0 and azimuth <= 360.0	 
	Check	arrival03	delaz > 0.0	 
	Check	arrival04	delinc >= 0.0	 
	Check	arrival05	delslo > 0.0	 
	Check	arrival06	deltim >= 0.0	 
	Check	arrival07	ema >= 0.0 and ema <= 90.0	 
	Check	arrival08	fm in ('cu','cr','c.','du','dr','d.','.u','.r','..','+u','+r','+.','-u','-r','-.')	 
	Check	arrival09	qual in ('i','e','w','I','E','W')	 
	Check	arrival10	slow >= 0.0	 
	Check	arrival11	snr > 0.0	 
	Check	arrival12	quality >= 0.0 and quality <= 1.0	 
	Check	arrival13	ccset < 1	 
	Check	arrival14	rflag in ('a','h','f','A','H','F')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
assocaro	Identifying	One To Zero or More					NO	 

assocamm

Entity Name	assocamm	
Owner Name		
Primary Keys	magid,ampid	
Definition	Data associating amplitudes with magnitudes	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
magid		NUMERIC(15, 0)	N	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
ampid		NUMERIC(15, 0)	N	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	 
commid		NUMERIC(15, 0)	Y	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)	N	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)	Y	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)	Y	Magnitude weight	 
in_wgt		NUMERIC(4, 3)	Y	Input weight	 
mag		NUMERIC(5, 2)	Y	Magnitude for this station reading	 
magres		NUMERIC(5, 2)	Y	Magnitude residual	 
magcorr		NUMERIC(5, 2)	Y	Magnitude correction for this channel	 
importance		NUMERIC(4, 3)	Y	This attribute denotes the importance of a phase/amplitude reading towards an origin/magnitude. 0.0 means no importance, 1.0 implies extremely important	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	assocamm01	mag >= -10.0 and mag <= 10.0	 
	Check	assocamm02	magcorr >= -10.0 and magcorr <= 10.0	 
	Check	assocamm03	magid > 0	 
	Check	assocamm05	weight >= 0.0 and weight <= 1.0	 
	Check	assocamm06	in_wgt >= 0.0 and in_wgt <= 1.0	 
	Check	assocamm07	importance > 0.0 and importance <= 1.0	 
	Check	assocamm08	rflag in ('a','h','f','A','H','F')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
amp	Identifying	One To Zero or More				ampid	NO	 
netmag	Identifying	One To Zero or More				magid	NO	 
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

assocamo

Entity Name	assocamo	
Owner Name		
Primary Keys	orid,ampid	
Definition	Data associating amplitudes with origins	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
orid		NUMERIC(15, 0)	N	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	 
ampid		NUMERIC(15, 0)	N	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	 
commid		NUMERIC(15, 0)	Y	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)	N	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)	Y	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	 
delta		NUMERIC(9, 4)	Y	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.	 
seaz		NUMERIC(4, 1)	Y	Station to event azimuth. This attribute is calculated from the station and event locations. It is measured clockwise from North	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	assocamo01	seaz >= 0.0 and seaz <= 360.0	 
	Check	assocamo02	delta >= 0.0	 
	Check	assocamo03	rflag in ('a','h','f','A','H','F')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
amp	Identifying	One To Zero or More				ampid	NO	 
origin	Identifying	One To Zero or More				orid	NO	 
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

assocaro

Entity Name	assocaro	
Owner Name		
Primary Keys	orid,arid	
Definition	Data associating arrivals with origins	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
orid		NUMERIC(15, 0)	N	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	 
arid		NUMERIC(15, 0)	N	Arrival identifier. Each arrival is assigned a unique positive integer identifying it. This number is used in the AssocArO relation along with the origin identifier to link Arrival and Origin	 
commid		NUMERIC(15, 0)	Y	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)	N	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)	Y	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	 
iphase		VARCHAR(8)	Y	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	 
importance		NUMERIC(4, 3)	Y	This attribute denotes the importance of a phase/amplitude reading towards an origin/magnitude. 0.0 means no importance, 1.0 implies extremely important	 
delta		NUMERIC(9, 4)	Y	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.	 
seaz		NUMERIC(4, 1)	Y	Event to station azimuth. This attribute is calculated from the event and station locations. It is measured clockwise from North	 
in_wgt		NUMERIC(4, 3)	Y	Input weight.
Hypoinverse station archive card columns 17 & 50:
0, 1, 2, 3 --> 1.00
4, 5, 6, 7, 8, 9 --> 0.00	 
wgt		NUMERIC(4, 3)	Y	Location weight. This attribute gives the final weight assigned to the allied arrival by the location program. It is used primarily for location programs that adaptively weight data by their residuals. Raw values from hypoinverse columns 39 & 64	 
timeres		NUMERIC(5, 2)	Y	Time residual. This attribute is a travel time residual, measured in seconds. The residual is found by taking the observed arrival time (saved in the Arrival relation) of a seismic phase and substracting the expected arrival time. The expected arrival time is calculated by a formula based on earth velocity model, an event location and origin time, the distance to the station, and the particular seismic phase	 
ema		NUMERIC(5, 2)	Y	The takeoff angle at the source, measured in degrees, with vertical down. ema=0 leaves the source straight down, while ema=180 leaves the source straight up; calculated in hypoinverse using the velocity model	 
slow		NUMERIC(8, 4)	Y	Slowness residual. This attribute gives the difference between an observed slowness (saved in the Arrival relation) and a theorical prediction. The prediction is calculated for the related phase and event origin described in the record	 
vmodelid		NUMERIC(3, 0)	Y	Velocity model identification	 
scorr		NUMERIC(6, 4)	Y	Station correction	 
sdelay		NUMERIC(7, 4)	Y	Station delay	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
ccset		VARCHAR(1)	Y	This field describes whether the clock correction has been added or applied to the arrivals in computing a hypocenter solution	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	assocaro02	delta >= 0.0	 
	Check	assocaro03	ema >= 0 and ema <= 180	 
	Check	assocaro04	importance >= 0.0 and importance < 1.0	 
	Check	assocaro05	seaz >= 0.0 and seaz <= 360.0	 
	Check	assocaro06	slow >= 0.0	 
	Check	assocaro07	timeres >= 0.0	 
	Check	assocaro09	ccset < 1	 
	Check	assocaro10	rflag in ('a','h','f','A','H','F')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
arrival	Identifying	One To Zero or More				arid	NO	 
origin	Identifying	One To Zero or More				orid	NO	 
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

assoccom

Entity Name	assoccom	
Owner Name		
Primary Keys	magid,coid	
Definition	Data associating codas with magnitudes	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
magid		NUMERIC(15, 0)	N	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
coid		NUMERIC(15, 0)	N	Coda identification. Each coda is assigned a unique positive integer which identifies it in the database	 
commid		NUMERIC(15, 0)	Y	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)	N	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)	Y	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)	Y	Magnitude weight	 
in_wgt		NUMERIC(4, 3)	Y	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)	Y	Magnitude for this station reading	 
magres		NUMERIC(7, 4)	Y	Magnitude residual	 
magcorr		NUMERIC(7, 4)	Y	Magnitude correction for this channel	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	assoccomkey04	weight >= 0.0 and weight <= 1.0	 
	Check	assoccomkey05	in_wgt >= 0.0 and in_wgt <= 1.0	 
	Check	assoccomkey06	rflag in ('a','h','f','A','H','F')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
coda	Identifying	One To Zero or More				coid	NO	 
netmag	Identifying	One To Zero or More				magid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
remark	Non-Specific						NO	 

assoccoo

Entity Name	assoccoo	
Owner Name		
Primary Keys	orid,coid	
Definition	Data associating codas with origins	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
orid		NUMERIC(15, 0)	N	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	 
coid		NUMERIC(15, 0)	N	Coda identification. Each coda is assigned a unique positive integer which identifies it in the database	 
commid		NUMERIC(15, 0)	Y	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)	N	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)	Y	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	 
delta		NUMERIC(9, 4)	Y	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.	 
seaz		NUMERIC(7, 4)	Y	Station to event azimuth. This attribute is calculated from the station and event locations. It is measured clockwise from North	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	assoccookey04	rflag in ('a','h','f','A','H','F')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
coda	Identifying	One To Zero or More				coid	NO	 
origin	Identifying	One To Zero or More				orid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
remark	Non-Specific						NO	 

assocevampset

Entity Name	assocevampset	
Owner Name		
Primary Keys	ampsetid,ampsettype	
Definition	This table associates amplitude sets with an event	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
ampsetid		NUMERIC(0, 0)	N	Amplitude set identifier	 
ampsettype		VARCHAR(20)	N	Amplitude set type	 
evid		NUMERIC(15, 0)	N	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	 
subsource		VARCHAR(8)	N	Name tag of the application creating the set (e.g. AmpGen AmpGenPp Gmp2Db)	 
isvalid		NUMERIC(0, 0)	N	Has value 1 if preferred set, 0 otherwise 	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		(cast(sys_extract_utc(systimestamp)asdate))	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
event	Non-Identifying	One To Zero or More				evid	NO	 
ampsettypes	Identifying	One To Zero or More				ampsettype	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
ampset	Non-Specific						NO	 

assoctypecat

Entity Name	assoctypecat	
Owner Name		
Primary Keys	etype,catid	
Definition	Data associating event types with categories	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
etype		VARCHAR(2)	N	This attribute is used to identify the type of seismic event	 
catid		NUMERIC(0, 0)	N	Category identifier	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
eventtype	Non-Identifying	One To Zero or More				etype	NO	 
eventcategory	Non-Identifying	One To Zero or More				catid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

coda

Entity Name	coda	
Owner Name		
Primary Keys	coid	
Definition	Summary information on a coda	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
coid		NUMERIC(15, 0)	N	Coda identification. Each coda is assigned a unique positive integer which identifies it in the database	 
commid		NUMERIC(15, 0)	Y	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)	N	Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used	 
net		VARCHAR(8)	Y	Unique network identifier. This character string is the name of a seismic network	 
auth		VARCHAR(15)	N	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)	Y	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)	Y	Channel name	 
channelsrc		VARCHAR(8)	Y	Domain for channel. This specifies what naming convention is used for the channel name (i.e. SEED, USGS, etc.)	 
seedchan		VARCHAR(3)	Y	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)	Y	Describes the individual sites on an array station, operated by the same network operator	 
codatype		VARCHAR(3)	Y	Coda type	 
afix		NUMERIC(7, 4)	Y	Nominal coda amplitude	 
afree		NUMERIC(7, 4)	Y	Free amplitude	 
qfix		NUMERIC(7, 4)	Y	Fixed coda decay constant	 
qfree		NUMERIC(7, 4)	Y	Free decay	 
tau		NUMERIC(7, 4)	Y	Coda duration (F-P time)	 
nsample		NUMERIC(6, 0)	Y	Number of coda sample windows	 
rms		NUMERIC(5, 3)	Y	Square root of the sum of the squares of the coda residuals, divided by the number of observations	 
durtype		VARCHAR(3)	Y	Duration type	 
iphase		VARCHAR(8)	Y	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)	Y	Uncertainty in amplitude measurement	 
units		VARCHAR(4)	N	Units of amplitude	 
time1		NUMERIC(10, 0)	Y	Time for pairs	 
amp1		NUMERIC(10, 0)	Y	Amplitude for pairs	 
time2		NUMERIC(10, 0)	Y	Time for pairs	 
amp2		NUMERIC(10, 0)	Y	Amplitude for pairs	 
time3		NUMERIC(10, 0)	Y	Time for pairs	 
amp3		NUMERIC(10, 0)	Y	Amplitude for pairs	 
time4		NUMERIC(10, 0)	Y	Time for pairs	 
amp4		NUMERIC(10, 0)	Y	Amplitude for pairs	 
time5		NUMERIC(10, 0)	Y	Time for pairs	 
amp5		NUMERIC(10, 0)	Y	Amplitude for pairs	 
time6		NUMERIC(10, 0)	Y	Time for pairs	 
amp6		NUMERIC(10, 0)	Y	Amplitude for pairs	 
quality		NUMERIC(3, 2)	Y	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)	N	The UTC epoch "start time" from which the relative seconds time values stored in the time1 ... time6 columns are measured	 
algorithm		VARCHAR(15)	Y	Algorithm used. This is a brief textual description of the algorithm used to derive coda data	 
winsize		NUMERIC(7, 4)	Y	Window over which waveform absolute amplitudes averaged	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	coda01	afix >= 0.0	 
	Check	coda03	amp1 > 0	 
	Check	coda04	amp2 > 0	 
	Check	coda05	amp3 > 0	 
	Check	coda06	amp4 > 0	 
	Check	coda07	amp5 > 0	 
	Check	coda08	amp6 > 0	 
	Check	coda09	codatype in ('P','S')	 
	Check	coda10	coid > 0	 
	Check	coda11	nsample >= 0	 
	Check	coda12	rms >= 0.0	 
	Check	coda13	time1 > 0	 
	Check	coda14	time2 > 0	 
	Check	coda15	time3 > 0	 
	Check	coda16	time4 > 0	 
	Check	coda17	time5 > 0	 
	Check	coda18	time6 > 0	 
	Check	coda19	rflag in ('a','h','f','A','H','F')	 
	Check	coda20	quality >= 0.0 and quality <= 1.0	 
	Check	coda21	durtype in ('a','d','h')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
assoccoo	Identifying	One To Zero or More					NO	 
assoccom	Identifying	One To Zero or More					NO	 

event

Entity Name	event	
Owner Name		
Primary Keys	evid	
Definition	Summary information on an event	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
evid		NUMERIC(15, 0)	N	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	 
prefor		NUMERIC(15, 0)	Y	Preferred origin. This attribute holds the origin identifier, orid, that points to the preferred origin for a seismic event	 
prefmag		NUMERIC(15, 0)	Y	Preferred magnitude. This attribute holds the magnitude identifier, magid, that points to the preferred magnitude for a seismic event or an origin	 
prefmec		NUMERIC(15, 0)	Y	Preferred mechanism. This attribute holds the mechanism identifier, mecid, that points to the preferred mechanism for a seismic event or an origin	 
commid		NUMERIC(15, 0)	Y	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)	N	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)	Y	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	 
etype		VARCHAR(2)	N	This attribute is used to identify the type of seismic event, when known	 
selectflag		NUMERIC(1, 0)	Y	This flag describes the “definitive” definition of an event. Helps to differentiate which event to use from two different real-time systems	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
version		NUMERIC(3, 0)	N	Event version number. This attribute is incremented each time the preferred origin, magnitude or mechanism of the event is updated	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
version	Default		(0)	 
	Check	event02	evid > 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
eventtype	Non-Identifying	One To Zero or More				etype	NO	 
mec	Non-Identifying	Zero or One to Zero or More				prefmec	NO	 
netmag	Non-Identifying	Zero or One to Zero or More				prefmag	NO	 
origin	Non-Identifying	Zero or One to Zero or More				prefor	NO	 
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
eventprefmec	Non-Identifying	One To Zero or More					NO	 
assocevampset	Non-Identifying	One To Zero or More					NO	 
eventprefor	Non-Identifying	Zero or One to Zero or More					NO	 
eventprefmag	Non-Identifying	One To Zero or More					NO	 
origin	Non-Identifying	One To Zero or More					NO	 

eventcategory

Entity Name	eventcategory	
Owner Name		
Primary Keys	catid	
Definition	Summary information on event categories	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
catid		NUMERIC(0, 0)	N	Category identifier	 
category		VARCHAR(25)	N	Name associated with an event category	 
description		VARCHAR(80)	Y	Event category description	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
	Check	EvCat01	catid > 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
assoctypecat	Non-Identifying	One To Zero or More					NO	 

eventprefmag

Entity Name	eventprefmag	
Owner Name		
Primary Keys	magtype,evid	
Definition	Summary information on preferred magnitudes for an event	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
magtype		VARCHAR(6)	N	Magnitude type. This character string is used to specify the type of the magnitude measure	 
evid		NUMERIC(15, 0)	N	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	 
magid		NUMERIC(15, 0)	N	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	EventPrefMag_CHKTYP	magtype in ('p','a','b','e','l','l1','l2','lg','c','s','w','z','B', 'un','d','h','n','dl','lr')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
event	Non-Identifying	One To Zero or More				evid	NO	 
netmag	Non-Identifying	One To Zero or More				magid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

eventprefmec

Entity Name	eventprefmec	
Owner Name		
Primary Keys	mechtype,evid	
Definition	Summary information on preferred mechanisms for an event	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
mechtype		VARCHAR(2)	N	Mechanism type	 
evid		NUMERIC(15, 0)	N	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	 
mecid		NUMERIC(15, 0)	Y	Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	EvPMec01	evid > 0	 
	Check	EvPMec02	mecid > 0	 
	Check	EvPMec03	mechtype IN ('FP','MT')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
mec	Non-Identifying	Zero or One to Zero or More				mecid	NO	 
event	Non-Identifying	Zero or One to Zero or More				evid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

eventprefor

Entity Name	eventprefor	
Owner Name		
Primary Keys	type,evid	
Definition	Summary information on preferred origins for an event	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
type		VARCHAR(2)	N	Type of location	 
evid		NUMERIC(15, 0)	N	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	 
orid		NUMERIC(15, 0)	N	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	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	EventPrefOr_CHKTYP	type in ('h','H','c','C','a','A','d','D','u','U')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
origin	Non-Identifying	One To Zero or More				orid	NO	 
event	Non-Identifying	One To Zero or More				evid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

eventtype

Entity Name	eventtype	
Owner Name		
Primary Keys	etype	
Definition	Summary information on event types	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
etype		VARCHAR(2)	N	This attribute is used to identify the type of seismic event	 
name		VARCHAR(16)	N	Name associated with an event type	 
description		VARCHAR(80)	Y	Event type description	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
	Check	EVENTTYPE02	etype IN ('eq','lp','se','to','tr','vt','nt','qb','ce','ex','sh','sn','th','av','co','df','ls','rb','rs','ve','bc','mi','pc','ot','st','uk','lf','su','px')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
assoctypecat	Non-Identifying	One To Zero or More					NO	 
event	Non-Identifying	One To Zero or More					NO	 

mec

Entity Name	mec	
Owner Name		
Primary Keys	mecid	
Definition	Summary information on a moment tensor	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
mecid		NUMERIC(15, 0)	N	Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database	 
oridin		NUMERIC(15, 0)	Y	Input origin. This attribute holds the origin identifier, orid, that points to the origin from which the mechanism was computed	 
oridout		NUMERIC(15, 0)	Y	Output origin. This attribute holds the origin identifier, orid, that points to the origin computed from the mechanism	 
magid		NUMERIC(15, 0)	Y	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
commid		NUMERIC(15, 0)	Y	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	 
mechtype		VARCHAR(2)	Y	Mechanism type	 
mecalgo		VARCHAR(15)	Y	This attribute represents the algorithm used to compute the mechanism (TDMT,TMTS=Dreger's code; FPFIT=fpfit; SMTINV=Pasyanos code)	 
scalar		DOUBLE PRECISION	Y	Seismic scalar moment (no value stored for fpfit)	 
erscalar		DOUBLE PRECISION	Y	Error in scalar moment. This is the standard deviation of the scalar moment	 
tft		VARCHAR(8)	Y	Type of source time function. Used to specify if time function and source half-duration are assumed, derived, or determined	 
tfd		DOUBLE PRECISION	Y	Duration of the source time function	 
mxx		DOUBLE PRECISION	Y	Moment tensor elements. Given in Aki convention	 
myy		DOUBLE PRECISION	Y	Moment tensor elements. Given in Aki convention	 
mzz		DOUBLE PRECISION	Y	Moment tensor elements. Given in Aki convention	 
mxy		DOUBLE PRECISION	Y	Moment tensor elements. Given in Aki convention	 
mxz		DOUBLE PRECISION	Y	Moment tensor elements. Given in Aki convention	 
myz		DOUBLE PRECISION	Y	Moment tensor elements. Given in Aki convention	 
smxx		DOUBLE PRECISION	Y	Uncertainties in moment tensor elements	 
smyy		DOUBLE PRECISION	Y	Uncertainties in moment tensor elements	 
smzz		DOUBLE PRECISION	Y	Uncertainties in moment tensor elements	 
smxy		DOUBLE PRECISION	Y	Uncertainties in moment tensor elements	 
smxz		DOUBLE PRECISION	Y	Uncertainties in moment tensor elements	 
smyz		DOUBLE PRECISION	Y	Uncertainties in moment tensor elements	 
srcduration		NUMERIC(6, 3)	Y	Source half-duration	 
auth		VARCHAR(15)	N	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)	Y	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	 
strike1		NUMERIC(3, 0)	Y	Strike of fault plane 1 from the best double couple	 
dip1		NUMERIC(3, 0)	Y	Dip of fault plane 1 from the best double couple	 
rake1		NUMERIC(4, 0)	Y	Rake of fault plane 1 from the best double couple solution	 
strike2		NUMERIC(3, 0)	Y	Strike of fault plane 2 from the best double couple	 
dip2		NUMERIC(2, 0)	Y	Dip of fault plane 2 from the best double couple	 
rake2		NUMERIC(4, 0)	Y	Rake of fault plane 2 from the best double couple solution	 
unstrike1		NUMERIC(6, 3)	Y	Uncertainty in strike 1	 
undip1		NUMERIC(5, 3)	Y	Uncertainty in dip 1	 
unrake1		NUMERIC(6, 3)	Y	Uncertainty in rake 1	 
unstrike2		NUMERIC(6, 3)	Y	Uncertainty in strike 2	 
undip2		NUMERIC(5, 3)	Y	Uncertainty in dip 2	 
unrake2		NUMERIC(6, 3)	Y	Uncertainty in rake 2	 
eigenp		DOUBLE PRECISION	Y	Eigen value of compressional axis in the principal axes representation of the best double couple	 
plungep		NUMERIC(2, 0)	Y	Plunge of the compressional axis in the principal axes representation of the best double couple	 
strikep		NUMERIC(3, 0)	Y	Strike of compressional axis in the principal axes representation of the best double couple	 
eigenn		DOUBLE PRECISION	Y	Eigen value of null axis in the principal axes representation of the best double couple	 
plungen		NUMERIC(2, 0)	Y	Plunge of the null axis in the principal axes representation of the best double couple	 
striken		NUMERIC(3, 0)	Y	Strike of null axis in the principal axes representation of the best double couple	 
eigent		DOUBLE PRECISION	Y	Eigen value of tension axis in the principal axes representation of the best double couple	 
plunget		NUMERIC(2, 0)	Y	Plunge of the tension axis in the principal axes representation of the best double couple	 
striket		NUMERIC(3, 0)	Y	Strike of tension axis in the principal axes representation of the best double couple	 
nsta		NUMERIC(5, 0)	Y	This quantity is the number of observations with non-zero input weights used to compute the mechanism. For CW=nsta, for FPFIT=nPobs, for HASH=nobs	 
pvr		NUMERIC(5, 0)	Y	Goodness of fit. For TDMT this is percent variance reduction; for FPFIT this is (1-misfit)*100	 
quality		NUMERIC(2, 1)	Y	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad	 
pdc		NUMERIC(3, 0)	Y	Percent double couple of the seismic moment tensor	 
pclvd		NUMERIC(3, 0)	Y	Percent compensated linear vector dipole of the seismic moment tensor	 
piso		NUMERIC(3, 0)	Y	Percent isotropic of the seismic moment tensor. If the solution is constrained to have zero trace (no "ISO"), then "ISO" should be NULL, as opposed to a case where the full moment tensor was used, and the ISO component ended up being very small ("0")	 
datetime		NUMERIC(25, 10)	N	The date of associated with information in the record, in true epoch format	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	mec13	plungen >= 0 and plungen <= 90	 
	Check	mec14	plungep >= 0 and plungep <= 90	 
	Check	mec15	plunget >= 0 and plunget <= 90	 
	Check	mec16	pclvd >= 0 and pclvd <= 100	 
	Check	mec17	pdc >= 0 and pdc <= 100	 
	Check	mec18	piso >= 0 and piso <= 100	 
	Check	mec19	pvr >= 0 and pvr <= 100	 
	Check	mec20	rake1 >= -180 and rake1 <= 180	 
	Check	mec21	rake2 >= -180 and rake2 <= 180	 
	Check	mec23	srcduration >= 0.0 and srcduration <= 100.0	 
	Check	mec24	striken >= 0 and striken <= 360	 
	Check	mec25	strikep >= 0 and strikep <= 360	 
	Check	mec26	striket >= 0 and striket <= 360	 
	Check	mec27	strike1 >= 0 and strike1 <= 360	 
	Check	mec28	strike2 >= 0 and strike2 <= 360	 
	Check	mec29	tfd > 0	 
	Check	mec30	undip1 >= -180 and undip1 <= 180	 
	Check	mec31	undip2 >= -180 and undip2 <= 180	 
	Check	mec38	unrake1 >= -180.0 and unrake1 <= 180.0	 
	Check	mec39	unrake2 >= -180.0 and unrake2 <= 180.0	 
	Check	mec40	unstrike1 >= -180.0 and unstrike1 <= 180.0	 
	Check	mec41	unstrike2 >= -180.0 and unstrike2 <= 180.0	 
	Check	mec01	dip1 >= -90 and dip1 <= 90	 
	Check	mec02	dip2 >= -90 and dip2 <= 90	 
	Check	mec03	erscalar >= 0.0	 
	Check	mec05	mecid > 0	 
	Check	mec06	mechtype in ('FP','MT')	 
	Check	mec42	quality >= 0.0 and quality <= 1.0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
netmag	Non-Identifying	Zero or One to Zero or More				magid	NO	 
origin	Non-Identifying	Zero or One to Zero or More				oridin	NO	 
origin	Non-Identifying	Zero or One to Zero or More				oridout	NO	 
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
mecobject	Non-Identifying	One To Zero or More					NO	 
mecdata	Non-Identifying	One To Zero or More					NO	 
eventprefmec	Non-Identifying	One To Zero or More					NO	 
event	Non-Identifying	One To Zero or More					NO	 
origin	Non-Identifying	One To Zero or More					NO	 

mecchannel

Entity Name	mecchannel	
Owner Name		
Primary Keys	mecdataid,net,sta,seedchan,location	
Definition	Summary information on channels associated with a mechanism	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
mecdataid		NUMERIC(15, 0)	N	Mechanisn data identifier	 
net		VARCHAR(8)	N	Unique network identifier. This character string is the name of a seismic network	 
sta		VARCHAR(6)	N	Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used	 
seedchan		VARCHAR(3)	N	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)	N	Describes the individual sites on an array station, operated by the same network operator	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
	Check	MecD01	mecdataid > 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
mecdata	Identifying	One To Zero or More				mecdataid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

mecdata

Entity Name	mecdata	
Owner Name		
Primary Keys	mecdataid	
Definition	Summary information on data associated with a mechanism	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
mecdataid		NUMERIC(15, 0)	N	Mechanism data identifier	 
mecid		NUMERIC(15, 0)	Y	Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database	 
mecfreqid		NUMERIC(15, 0)	Y	Frequency information identifier	 
polarity		VARCHAR(2)	Y	Polarity of pick. This is the polarity as used by fpfit, corrected for dip, gain and reversals. Format like arrival.fm	 
discrepancy		VARCHAR(1)	Y	Mainly used for fpfit. Does the polarity of the data match the quadrant of the mechanism	 
orientation		VARCHAR(1)	Y	How are the components listed in the mecchannel table used (rotation, transformation). If channel has a polarity reversal, i.e. polarity is inverted from the raw polarity read from the waveforms, this should be indicated by a 'I' for inverted in this field. If data have not been inverted, enter " " (blank)	 
quality		NUMERIC(3, 2)	Y	Quality. Fpfit uses quality 0-9	 
amplitude		REAL/SMALLFLOAT	Y	SMTINV: spectral amplitude at the frequency given by mecfreqid	 
phase		REAL/SMALLFLOAT	Y	SMTINV: spectral phase at the frequency given by mecfreqid	 
time1		NUMERIC(25, 10)	Y	Start time of:
	TDMT: complete waveform window
	SMTINV: window for spectrum
	FPFIT: pick time	 
time2		NUMERIC(25, 10)	Y	End of window, if window used (CW, SW)	 
model		VARCHAR(10)	Y	Model used for greens functions; velocity model for other methods	 
zcor		NUMERIC(5, 0)	Y	TDMT: value of cross correlation shift in samples for best solution	 
corlen		NUMERIC(5, 0)	Y	TDMT: length of cross correlation window used in samples	 
dt		NUMERIC(11, 5)	Y	Sampling interval of data used in inversion (could be resampled from original data); sampling interval valid for GF and data	 
varred		NUMERIC(4, 1)	Y	Fit for tis station	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	MecData01	discrepancy IN ('T','F')	 
	Check	MecData02	orientation IN ('C','R','T','H','3','L','E','N','Z','A','I',' ')	 
	Check	MecData03	quality BETWEEN 0 AND 1	 
	Check	MecData04	model IN ('mend1_','socal','gil7_')	 
	Check	MecData05	mecid > 0	 
	Check	MecData06	mecdataid > 0	 
	Check	MecData07	mecfreqid > 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
mec	Non-Identifying	Zero or One to Zero or More				mecid	NO	 
mecfreq	Non-Identifying	Zero or One to Zero or More				mecfreqid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
mecchannel	Identifying	One To Zero or More					NO	 

mecfreq

Entity Name	mecfreq	
Owner Name		
Primary Keys	mecfreqid	
Definition	Summary information on frequency data	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
mecfreqid		NUMERIC(15, 0)	N	Frequency information identifier	 
mecalgo		VARCHAR(15)	Y	This attribute represents the algorithm used to compute the mechanism	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	MecF01	mecfreqid > 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
mecdata	Non-Identifying	One To Zero or More					NO	 
mecfreqdata	Identifying	One To Zero or More					NO	 

mecfreqdata

Entity Name	mecfreqdata	
Owner Name		
Primary Keys	mecfreqid,type	
Definition	Summary information on frequency data	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
mecfreqid		NUMERIC(15, 0)	N	Frequency information identifier	 
type		VARCHAR(15)	N	What this frequency is (frequency for fit)	 
freq		NUMERIC(15, 6)	N	Frequency value	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
	Check	MecFreqData01	type IN ('LP','HP','SF')	 
	Check	MecFreqData02	mecfreqid > 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
mecfreq	Identifying	One To Zero or More				mecfreqid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

mecobject

Entity Name	mecobject	
Owner Name		
Primary Keys	dataid,mecid	
Definition	Summary information on objects associated with a mechanism	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
dataid		NUMERIC(15, 0)	N	Object type	 
mecid		NUMERIC(15, 0)	N	Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database	 
mimetype		VARCHAR(20)	Y	Image type	 
data		PICTURE	Y	Object described by dataid/mimetype	 
meta		VARCHAR(128)	Y	Metadata for object, i.e. filename=email.txt	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
	Check	MecObj01	mecid > 0	 
	Check	MecObj02	dataid >= 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
mec	Non-Identifying	Zero or One to Zero or More				mecid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

netmag

Entity Name	netmag	
Owner Name		
Primary Keys	magid	
Definition	Summary information on a magnitude	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
magid		NUMERIC(15, 0)	N	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
orid		NUMERIC(15, 0)	N	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	 
commid		NUMERIC(15, 0)	Y	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	 
magnitude		NUMERIC(5, 2)	N	Magnitude. This gives the magnitude value of the type indicated by magtype	 
magtype		VARCHAR(6)	N	Magnitude type. This character string is used to specify the type of the magnitude measure	 
auth		VARCHAR(15)	N	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)	Y	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	 
magalgo		VARCHAR(15)	Y	This attribute represents the algorithm used to compute the magnitude	 
nsta		NUMERIC(5, 0)	Y	This quantity is the number of stations with non-zero input weights used to compute the magnitude	 
nobs		NUMERIC(5, 0)	Y	This quantity is the number of observations with non-zero input weights used to compute the magnitude	 
uncertainty		NUMERIC(5, 3)	Y	Magnitude uncertainty. Median of the absolute values of the channel magnitude residual deviations from the channel magnitude's median, the summary magnitude.	 
gap		NUMERIC(4, 1)	Y	Gap in azimuthal coverage	 
distance		NUMERIC(7, 3)	Y	Distance from the origin to the nearest station	 
quality		NUMERIC(2, 1)	Y	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	netmag01	magnitude >= -10.0 and magnitude <= 10.0	 
	Check	netmag02	magtype in ('p', 'a','b','e','l','l1','l2','lg','c','s','w','z','B','un','d','h','n','dl')	 
	Check	netmag03	nsta >= 0	 
	Check	netmag04	uncertainty >= 0.0	 
	Check	netmag05	quality >= 0.0 and quality <= 1.0	 
	Check	netmag06	magid > 0	 
	Check	netmag07	rflag in ('a','h','f','A','H','F')	 
	Check	netmag08	nobs >= 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
origin	Non-Identifying	One To Zero or More				orid	NO	 
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
assocamm	Identifying	One To Zero or More					NO	 
assoccom	Identifying	One To Zero or More					NO	 
eventprefmag	Non-Identifying	One To Zero or More					NO	 
event	Non-Identifying	One To Zero or More					NO	 
mec	Non-Identifying	One To Zero or More					NO	 
origin	Non-Identifying	One To Zero or More					NO	 

origin

Entity Name	origin	
Owner Name		
Primary Keys	orid	
Definition	Data on event location	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
orid		NUMERIC(15, 0)	N	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	 
evid		NUMERIC(15, 0)	N	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	 
prefmag		NUMERIC(15, 0)	Y	Preferred magnitude. This attribute holds the magnitude identifier, magid, that points to the preferred magnitude for a seismic event or an origin	 
prefmec		NUMERIC(15, 0)	Y	Preferred mechanism. This attribute holds the mechanism identifier, mecid, that points to the preferred mechanism for a seismic event or an origin	 
commid		NUMERIC(15, 0)	Y	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	 
bogusflag		NUMERIC(1, 0)	N	This field describes whether an origin is bogus or not	 
datetime		NUMERIC(25, 10)	N	The date of associated with information in the record, in true epoch format	 
lat		NUMERIC(9, 7)	N	Latitude. This attribute is the geographic latitude. Locations north of the equator have positive latitudes	 
lon		NUMERIC(10, 7)	N	Longitude. This attribute is the geographic longitude. Longitudes are measured positive east of the Greenwich meridian	 
depth		NUMERIC(7, 3)	Y	Distance in KM of the earthquake source below the geoid. Hypoinverse model types E, L or V are always geoid depths	 
mdepth		NUMERIC(7, 3)	Y	Distance in KM of the earthquake source below the model surface. For model depths, all the recording stations are located at the top of the model and their elevations are not used. Model types T or H if uncorrected by depth datum are always model depths	 
type		VARCHAR(2)	Y	Type of location	 
algorithm		VARCHAR(15)	Y	Algorithm used. This is a brief textual description of the algorithm used to compute a seismic origin	 
algo_assoc		VARCHAR(80)	Y	Association algorithm used. This is a textual description of the algorithm used for associating the data	 
auth		VARCHAR(15)	N	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)	Y	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	 
datumhor		VARCHAR(8)	Y	Datum type for horizontal (latitude and longitude) coordinates	 
datumver		VARCHAR(8)	Y	Datum type for depth or elevation	 
gap		NUMERIC(4, 1)	Y	Gap in azimuthal coverage	 
distance		NUMERIC(7, 3)	Y	Distance from the origin to the nearest station	 
wrms		NUMERIC(5, 3)	Y	This attribute denotes the weighted RMS	 
stime		NUMERIC(6, 3)	Y	Origin time error. This attribute denotes the standard deviation of the origin time	 
erhor		NUMERIC(7, 3)	Y	Horizontal error. This attribute denotes the location uncertainty that accompanies the location	 
sdep		NUMERIC(7, 3)	Y	Depth error. This is the standard deviation of the depth estimate	 
erlat		NUMERIC(7, 3)	Y	Error in latitude. This is the standard deviation of the latitude estimate	 
erlon		NUMERIC(7, 3)	Y	Error in longitude. This is the standard deviation of the longitude estimate	 
totalarr		NUMERIC(5, 0)	Y	Total number of phases in the database for the specified orid. This field signifies the number of P and S arrivals with non-zero input weights	 
totalamp		NUMERIC(6, 0)	Y	Total number of amplitudes in the database for the specified orid. Not all amplitudes have to associated with all magnitudes or origins	 
ndef		NUMERIC(5, 0)	Y	This attribute denotes the number of phases with non-zero output weights used in hypocenter calculation	 
nbs		NUMERIC(4, 0)	Y	Number of S phase readings with non-zero output weights	 
nbfm		NUMERIC(4, 0)	Y	Number of P first motions with non-zero input weights	 
locevid		VARCHAR(12)	Y	Local event identifier. This attribute describes the original event identifier of the event. In combination with auth and subsource, it can be used to uniquely identify the original event identifier from that source. For example, waveforms from the original source may be associated with this identifier	 
quality		NUMERIC(2, 1)	Y	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad	 
fdepth		VARCHAR(1)	Y	This attribute indicates if the depth was fixed or not to compute the solution	 
fepi		VARCHAR(1)	Y	This attribute indicates if the epicenter was fixed or not to compute the solution	 
ftime		VARCHAR(1)	Y	This attribute indicates if the origin time was fixed or not to compute the solution	 
vmodelid		VARCHAR(2)	Y	Velocity model identification. This string identifies a version (instance) of the velocity model for the specified domain and algorithm. This version should be changed whenever the velocity model is changed. It is recommended that values 00 - 99 be used for this field	 
cmodelid		VARCHAR(2)	Y	Velocity model domain. This string identifies the organization responsible for the velocity model. Recommendations for this field are the SEED network name, or a unique abbreviation of the processing center when using data from multiple networks	 
rflag		VARCHAR(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been saved,  finalized or canceled	 
crust_type		VARCHAR(1)	Y	The type of crust model used for travel time calculations. Each type has its own geometry of velocity layers or gradients within layers, tied to the options of the location program	 
crust_model		VARCHAR(3)	Y	The code for the regional (geographic) crust model that is dominant in the travel time calculations. The crust model depends on the location of the earthquake origin and not on the recording station. The code is for the highest weighted model if more than one is used	 
gtype		VARCHAR(1)	Y	Geographic type. Describes the location of the event relative to the network. If the event occurred within the network's boundaries the geographic type is 'local'. If it occurs within delta < xxxx it is regional. Events outside this distance are teleseisms	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
bogusflag	Default		(0)	 
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	origin02	datumhor in ('NAD27','WGS84')	 
	Check	origin03	datumver in ('NAD27','WGS84','AVERAGE')	 
	Check	origin04	depth >= -10.0 and depth <= 1000.0	 
	Check	origin05	distance >= 0.0	 
	Check	origin06	erhor >= 0.0	 
	Check	origin07	erlat >= 0.0	 
	Check	origin08	erlon >= 0.0	 
	Check	origin09	fdepth in ('y','n')	 
	Check	origin10	fepi in ('y','n')	 
	Check	origin11	ftime in ('y','n')	 
	Check	origin12	gap >= 0.0 and gap <= 360.0	 
	Check	origin15	nbfm >= 0	 
	Check	origin16	nbs >= 0	 
	Check	origin17	ndef >= 0	 
	Check	origin18	orid > 0	 
	Check	origin19	quality >= 0.0 and quality <= 1.0	 
	Check	origin20	type in ('H','h','C','c','A','a','D','d','u','U')	 
	Check	origin21	stime >= 0.0	 
	Check	origin23	wrms >= 0.0	 
	Check	origin24	sdep >=0.0	 
	Check	origin25	totalarr >=0	 
	Check	origin26	totalamp >= 0	 
	Check	origin28	rflag in ('a','h','f','A','H','F','i','I','c','C')	 
	Check	origin30	crust_type in ('H','T','E','L','V')	 
	Check	origin31	gtype in ('L','R','T')	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
event	Non-Identifying	One To Zero or More				evid	NO	 
mec	Non-Identifying	Zero or One to Zero or More				prefmec	NO	 
netmag	Non-Identifying	Zero or One to Zero or More				prefmag	NO	 
remark	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
eventprefor	Non-Identifying	One To Zero or More					NO	 
assocaro	Identifying	One To Zero or More					NO	 
assoccoo	Identifying	One To Zero or More					NO	 
assocamo	Identifying	One To Zero or More					NO	 
event	Non-Identifying	One To Zero or More					NO	 
mec	Non-Identifying	One To Zero or More					NO	 
mec	Non-Identifying	One To Zero or More					NO	 
netmag	Non-Identifying	One To Zero or More					NO	 
origin_error	Identifying	One To Zero or More					NO	 

origin_error

Entity Name	origin_error	
Owner Name		
Primary Keys	orid	
Definition	Error data on event location	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
orid		NUMERIC(15, 0)	N	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	 
sxx		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
syy		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
szz		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
stt		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
sxy		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
sxz		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
syz		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
stx		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
sty		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
stz		NUMERIC(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
azismall		NUMERIC(5, 2)	Y	Azimuth of smallest principal error	 
dipsmall		NUMERIC(4, 2)	Y	Dip of smallest principal error	 
magsmall		NUMERIC(7, 5)	Y	Magnitude of smallest principal error	 
aziinter		NUMERIC(5, 2)	Y	Azimuth of intermediate principal error	 
dipinter		NUMERIC(4, 2)	Y	Dip of intermediate principal error	 
maginter		NUMERIC(7, 5)	Y	Magnitude of intermediate principal error	 
azilarge		NUMERIC(5, 2)	Y	Azimuth of largest principal error	 
diplarge		NUMERIC(4, 2)	Y	Dip of largest principal error	 
maglarge		NUMERIC(7, 5)	Y	Magnitude of largest principal error	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	orig_error01	aziinter >= 0.0 and aziinter <= 360.0	 
	Check	orig_error02	azilarge >= 0.0 and azilarge <= 360.0	 
	Check	orig_error03	azismall >= 0.0 and azismall <= 360.0	 
	Check	orig_error04	dipinter >= -90.0 and dipinter <= 90.0	 
	Check	orig_error05	diplarge >= -90.0 and diplarge <= 90.0	 
	Check	orig_error06	dipsmall >= -90.0 and dipsmall <= 90.0	 
	Check	orig_error07	maginter >= 0.0	 
	Check	orig_error08	maglarge >= 0.0	 
	Check	orig_error09	magsmall >= 0.0	 
	Check	orig_error10	stx > 0.0	 
	Check	orig_error11	sty > 0.0	 
	Check	orig_error12	stz > 0.0	 
	Check	orig_error13	sxx > 0.0	 
	Check	orig_error14	sxy > 0.0	 
	Check	orig_error15	sxz > 0.0	 
	Check	orig_error16	syy > 0.0	 
	Check	orig_error17	syz > 0.0	 
	Check	orig_error18	stt > 0.0	 
	Check	orig_error19	szz > 0.0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
origin	Identifying	One To Zero or More				orid	NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	

remark

Entity Name	remark	
Owner Name		
Primary Keys	commid,lineno	
Definition	Comments	
Attributes 

Attribute/Logical Rolename	Domain	Datatype	Null	Definition	
commid		NUMERIC(15, 0)	N	Comment Identifier	 
lineno		NUMERIC(15, 0)	N	Comment line number. This integer attribute is assigned as a sequence number for multiple line comments. The combination of commid and lineno is unique	 
remark		VARCHAR(80)	Y	Descriptive text. This single line of text is an arbitrary comment about a record in the database. The comment is linked to its parent relation only by forward reference from commid in the tuple of the relation of interest	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Attribute	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP) 	 
	Check	remark01	commid > 0	 
	Check	remark02	lineno > 0	 
Relationships 

 Parent Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	
assoccom	Non-Specific						NO	 
assoccoo	Non-Specific						NO	 
 Child Relationships: 

Entity Name	Type	Cardinality	Business Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	
assocamm	Non-Specific						NO	 
assocaro	Non-Specific						NO	 
assocamo	Non-Specific						NO	 
amp	Non-Specific						NO	 
arrival	Non-Specific						NO	 
coda	Non-Specific						NO	 
event	Non-Specific						NO	 
mec	Non-Specific						NO	 
netmag	Non-Specific						NO	 
origin	Non-Specific						NO	 

Model Detail Reports

NCEDC

Model Name	NCEDC	
Database Platform	Oracle 12c	

Table Summary Report

Table Name	Table Type	Primary Keys	# Col	
amp	Independent	ampid	27	
ampset	Dependent	ampsetid, ampid	2	
ampsettypes	Independent	ampsettype	2	
arrival	Independent	arid	28	
assocamm	Dependent	magid, ampid	13	
assocamo	Dependent	orid, ampid	9	
assocaro	Dependent	orid, arid	20	
assoccom	Dependent	magid, coid	12	
assoccoo	Dependent	orid, coid	9	
assocevampset	Dependent	ampsetid, ampsettype	6	
assoctypecat	Independent	etype, catid	2	
coda	Independent	coid	40	
event	Independent	evid	11	
eventcategory	Independent	catid	3	
eventprefmag	Independent	magtype, evid	4	
eventprefmec	Independent	mechtype, evid	4	
eventprefor	Independent	type, evid	4	
eventtype	Independent	etype	3	
mec	Independent	mecid	56	
mecchannel	Dependent	mecdataid, net, sta, seedchan, location	5	
mecdata	Independent	mecdataid	17	
mecfreq	Independent	mecfreqid	3	
mecfreqdata	Dependent	mecfreqid, type	3	
mecobject	Independent	dataid, mecid	5	
netmag	Independent	magid	16	
origin	Independent	orid	43	
origin_error	Dependent	orid	21	
remark	Independent	commid, lineno	4	
remark origin	Dependent	lineno, commid, orid	3	

Table Detail Reports

amp

Table Name	amp	
Owner Name		
Primary Keys	ampid	
Definition	Summary information on an amplitude reading	
Columns 

Column Name	Domain	Datatype	Null	Definition	
ampid		NUMBER(15, 0)	N	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	 
commid		NUMBER(15, 0)	Y	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	 
datetime		NUMBER(25, 10)	Y	The date of associated with information in the record, in true epoch format

* In the current real time system, we know the exact amplitude time as well as the window.
  Therefore, we can set values for the datetime, wstart & duration fields.

* In the case where we know only the time of the amplitude but not the window, we set:
        datetime = [AMPLITUDE TIME]
        wstart = [AMPLITUDE TIME]
        duration = 0

* In the case where we do not know the amplitude time nor the window, we set:
        datetime = NULL
        wstart = [ORIGIN TIME]
        duration = NULL
	 
sta		VARCHAR2(6)	N	Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used	 
net		VARCHAR2(8)	Y	Unique network identifier. This character string is the name of a seismic network	 
auth		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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		VARCHAR2(8)	Y	Channel name	 
channelsrc		VARCHAR2(8)	Y	Domain for channel. This specifies what naming convention is used for the channel name (i.e. SEED, USGS, etc.)	 
seedchan		VARCHAR2(3)	Y	SEED channel name. The first character denotes the band code, the second for the instrument code and the third represents the component code	 
location		VARCHAR2(2)	Y	Describes the individual sites on an array station, operated by the same network operator	 
iphase		VARCHAR2(8)	Y	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	 
amplitude		BINARY_DOUBLE	N	Amplitude in appropriate units for type	 
amptype		VARCHAR2(8)	Y	Amplitude type	 
units		VARCHAR2(4)	N	Units of amplitude	 
ampmeas		VARCHAR2(1)	Y	Amplitude measure	 
eramp		NUMBER(5, 3)	Y	Uncertainty in amplitude measurement	 
flagamp		VARCHAR2(4)	Y	This attribute is a flag to indicate whether amplitude is over P packet, S packet, entire waveform, etc	 
per		NUMBER(10, 4)	Y	Signal period. This attribute is the period of the signal described by the amplitude record	 
snr		BINARY_DOUBLE	Y	Signal-to-noise ratio. This is an estimate of the signal relative to that of the noise immediately preceding it	 
tau		NUMBER(9, 4)	Y	Coda duration (F-P time)	 
quality		NUMBER(2, 1)	Y	This attribute describes the completeness of the time window of data. A complete time window is 1.0, an incomplete time window is 0.0. If an incomplete time window has been human-reviewed and the analyst is confident that the peak amplitude was recorded and properly computed despite the presence of data gaps, the value is set to 0.5 to indicate the window contains data gaps, but is usable	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
cflag		VARCHAR2(2)	Y	This flag indicates whether the amplitude value is below noise, on scale or clipped	 
wstart		BINARY_DOUBLE	N	Start of time window of amplitude measurement

* In the current real time system, we know the exact amplitude time as well as the window.
  Therefore, we can set values for the datetime, wstart & duration fields.

* In the case where we know only the time of the amplitude but not the window, we set:
        datetime = [AMPLITUDE TIME]
        wstart = [AMPLITUDE TIME]
        duration = 0

* In the case where we do not know the amplitude time nor the window, we set:
        datetime = NULL
        wstart = [ORIGIN TIME]
        duration = NULL
	 
duration		BINARY_DOUBLE	Y	Duration of amplitude reading

* In the current real time system, we know the exact amplitude time as well as the window.
  Therefore, we can set values for the datetime, wstart & duration fields.

* In the case where we know only the time of the amplitude but not the window, we set:
        datetime = [AMPLITUDE TIME]
        wstart = [AMPLITUDE TIME]
        duration = 0

* In the case where we do not know the amplitude time nor the window, we set:
        datetime = NULL
        wstart = [ORIGIN TIME]
        duration = NULL
	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	amp01	ampid > 0	 
	Check	amp02	amplitude > 0	 
	Check	amp03	ampmeas in ('0','1')	 
	Check	amp04	amptype in ('C','WA','WAS','WASF','PGA','PGV','PGD','WAC','WAU','IV2','SP.3','SP1.0','SP3.0','ML100','ME100','EGY','M0')	 
	Check	amp06	eramp >= 0.0	 
	Check	amp07	flagamp in ('P','S','R','PP','ALL','SUR')	 
	Check	amp08	per > 0.0	 
	Check	amp09	tau > 0.0	 
	Check	amp10	units in ('c','s','mm','cm','m','ms','mss','cms','cmss','mms','mmss','mc','nm','e','cmcms','none','dycm')	 
	Check	amp11	quality >= 0.0 and quality <= 1.0	 
	Check	amp12	rflag in ('a','h','f','A','H','F')	 
	Check	amp13	cflag in ('bn', 'os','cl','BN','OS','CL')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
ampset	Identifying	One To Zero or More					NO	NO	 
assocamm	Identifying	One To Zero or More	Aam_Amp				NO	NO	 
assocamo	Identifying	One To Zero or More	Amo_Amp				NO	NO	 
DDL Code 

CREATE TABLE amp(
    ampid         NUMBER(15, 0)     NOT NULL,
    commid        NUMBER(15, 0),
    datetime      NUMBER(25, 10),
    sta           VARCHAR2(6)       NOT NULL,
    net           VARCHAR2(8),
    auth          VARCHAR2(15)      NOT NULL,
    subsource     VARCHAR2(8),
    channel       VARCHAR2(8),
    channelsrc    VARCHAR2(8),
    seedchan      VARCHAR2(3),
    location      VARCHAR2(2),
    iphase        VARCHAR2(8),
    amplitude     BINARY_DOUBLE     NOT NULL,
    amptype       VARCHAR2(8),
    units         VARCHAR2(4)       NOT NULL,
    ampmeas       VARCHAR2(1),
    eramp         NUMBER(5, 3),
    flagamp       VARCHAR2(4),
    per           NUMBER(10, 4),
    snr           BINARY_DOUBLE,
    tau           NUMBER(9, 4),
    quality       NUMBER(2, 1),
    rflag         VARCHAR2(2),
    cflag         VARCHAR2(2),
    wstart        BINARY_DOUBLE     NOT NULL,
    duration      BINARY_DOUBLE,
    lddate        DATE              DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT amp01 CHECK (ampid > 0),
    CONSTRAINT amp02 CHECK (amplitude > 0),
    CONSTRAINT amp03 CHECK (ampmeas in ('0','1')),
    CONSTRAINT amp04 CHECK (amptype in ('C','WA','WAS','WASF','PGA','PGV','PGD','WAC','WAU','IV2','SP.3','SP1.0','SP3.0','ML100','ME100','EGY','M0')),
    CONSTRAINT amp06 CHECK (eramp >= 0.0),
    CONSTRAINT amp07 CHECK (flagamp in ('P','S','R','PP','ALL','SUR')),
    CONSTRAINT amp08 CHECK (per > 0.0),
    CONSTRAINT amp09 CHECK (tau > 0.0),
    CONSTRAINT amp10 CHECK (units in ('c','s','mm','cm','m','ms','mss','cms','cmss','mms','mmss','mc','nm','e','cmcms','none','dycm')),
    CONSTRAINT amp11 CHECK (quality >= 0.0 and quality <= 1.0),
    CONSTRAINT amp12 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT amp13 CHECK (cflag in ('bn', 'os','cl','BN','OS','CL')),
    CONSTRAINT ampkey01 PRIMARY KEY (ampid)
    USING INDEX
        LOGGING
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

ampset

Table Name	ampset	
Owner Name		
Primary Keys	ampsetid,ampid	
Definition	This table associates amplitudes with a set	
Columns 

Column Name	Domain	Datatype	Null	Definition	
ampsetid		NUMBER	N	Amplitude set identifier	 
ampid		NUMBER(15, 0)	N	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	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
amp	Identifying	One To Zero or More				ampid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE ampset(
    ampsetid    NUMBER           NOT NULL,
    ampid       NUMBER(15, 0)    NOT NULL,
    CONSTRAINT ampsetkey01 PRIMARY KEY (ampsetid, ampid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Refamp98 FOREIGN KEY (ampid)
    REFERENCES amp(ampid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

ampsettypes

Table Name	ampsettypes	
Owner Name		
Primary Keys	ampsettype	
Definition	This table describes the list of valid amplitudes set types	
Columns 

Column Name	Domain	Datatype	Null	Definition	
ampsettype		VARCHAR2(20)	N	Amplitude set type	 
description		VARCHAR2(80)	Y	The long description of an amplitude set type	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
assocevampset	Identifying	One To Zero or More	assocevampsetkey02				NO	NO	 
DDL Code 

CREATE TABLE ampsettypes(
    ampsettype     VARCHAR2(20)    NOT NULL,
    description    VARCHAR2(80),
    CONSTRAINT ampsettypeskey01 PRIMARY KEY (ampsettype)
    USING INDEX
        LOGGING
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

arrival

Table Name	arrival	
Owner Name		
Primary Keys	arid	
Definition	Summary information on a seismic arrival	
Columns 

Column Name	Domain	Datatype	Null	Definition	
arid		NUMBER(15, 0)	N	Arrival identifier. Each arrival is assigned a unique positive integer identifying it. This number is used in the AssocArO relation along with the origin identifier to link Arrival and Origin	 
commid		NUMBER(15, 0)	Y	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	 
datetime		NUMBER(25, 10)	N	The date of associated with information in the record, in true epoch format	 
sta		VARCHAR2(6)	N	Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used	 
net		VARCHAR2(8)	Y	Unique network identifier. This character string is the name of a seismic network	 
auth		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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.
Contains hypoinverse station card column 109 for historic catalogs	 
channel		VARCHAR2(8)	Y	Channel name	 
channelsrc		VARCHAR2(8)	Y	Domain for channel. This specifies what naming convention is used for the channel name (i.e. SEED, USGS, etc.)	 
seedchan		VARCHAR2(3)	Y	SEED channel name. The first character denotes the band code, the second for the instrument code and the third represents the component code	 
location		VARCHAR2(2)	Y	Describes the individual sites on an array station, operated by the same network operator	 
iphase		VARCHAR2(8)	Y	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	 
qual		VARCHAR2(1)	Y	Onset quality. This single-character flag is used to denote the sharpness of the onset of a seismic phase. This attribute does not denote the timing accuracy	 
clockqual		VARCHAR2(1)	Y	This field describes whether the clock quality associated with a particular arrival is known, and if so, is good or bad	 
clockcorr		NUMBER(15, 0)	Y	This field indicates the amount of time to add to the arrival time if clock correction is known	 
ccset		VARCHAR2(1)	Y	This field describes whether the clock correction has been added or applied to the arrivals in computing a hypocenter solution	 
fm		VARCHAR2(2)	Y	First motion. This is a two-character indication of first motion. The first character describes first motion seen on short-period channels and the second holds for long-period instruments. Compression (dilation) on a short-period sensor is denoted by c(d) and compression (dilation) on a long-period sensor is denoted by u(r). Empty character positions will be indicated by dots (e.g., ".r"). Lower quality first motions can be described by +(-)	 
ema		NUMBER(5, 2)	Y	Emergence angle. This attribute is the emergence angle of an arrival, as observed at a three-component station or array. The value increases from the vertical direction towards the horizontal	 
azimuth		NUMBER(4, 1)	Y	Station to event azimuth measured clockwise from true north. Identified from waveform analysis	 
slow		NUMBER(8, 4)	Y	Observed slowness. This is the observed slowness of a wave as it sweeps across an array	 
deltim		NUMBER(5, 2)	Y	Arrival time uncertainty. This attribute gives the standard deviation of a detection time	 
delinc		NUMBER(4, 2)	Y	Uncertainty in the angle. This attribute gives the standard deviation of the angle of emergence	 
delaz		NUMBER(5, 2)	Y	Uncertainty in the azimuth. This attribute gives the standard deviation of the azimuth of a signal	 
delslo		NUMBER(8, 4)	Y	Uncertainty in slowness. This attribute gives the standard deviation of the slowness of a signal	 
quality		NUMBER(3, 2)	Y	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad.
Hypoinverse station archive card columns 17 & 50:
0, 5 --> 1.00
1, 6 --> 0.75
2, 7 --> 0.50
3, 8 --> 0.25
4, 9 --> 0.00	 
snr		BINARY_DOUBLE	Y	Signal-to-noise ratio. This is an estimate of the signal relative to that of the noise immediately preceding it	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	arrival01	arid > 0	 
	Check	arrival02	azimuth >= 0.0 and azimuth <= 360.0	 
	Check	arrival03	delaz > 0.0	 
	Check	arrival04	delinc >= 0.0	 
	Check	arrival05	delslo > 0.0	 
	Check	arrival06	deltim >= 0.0	 
	Check	arrival07	ema >= 0.0 and ema <= 90.0	 
	Check	arrival08	fm in ('cu','cr','c.','du','dr','d.','.u','.r','..','+u','+r','+.','-u','-r','-.')	 
	Check	arrival09	qual in ('i','e','w','I','E','W')	 
	Check	arrival10	slow >= 0.0	 
	Check	arrival11	snr > 0.0	 
	Check	arrival12	quality >= 0.0 and quality <= 1.0	 
	Check	arrival13	ccset < 1	 
	Check	arrival14	rflag in ('a','h','f','A','H','F')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
assocaro	Identifying	One To Zero or More	Aao_Arr				NO	NO	 
DDL Code 

CREATE TABLE arrival(
    arid          NUMBER(15, 0)     NOT NULL,
    commid        NUMBER(15, 0),
    datetime      NUMBER(25, 10)    NOT NULL,
    sta           VARCHAR2(6)       NOT NULL,
    net           VARCHAR2(8),
    auth          VARCHAR2(15)      NOT NULL,
    subsource     VARCHAR2(8),
    channel       VARCHAR2(8),
    channelsrc    VARCHAR2(8),
    seedchan      VARCHAR2(3),
    location      VARCHAR2(2),
    iphase        VARCHAR2(8),
    qual          VARCHAR2(1),
    clockqual     VARCHAR2(1),
    clockcorr     NUMBER(15, 0),
    ccset         VARCHAR2(1),
    fm            VARCHAR2(2),
    ema           NUMBER(5, 2),
    azimuth       NUMBER(4, 1),
    slow          NUMBER(8, 4),
    deltim        NUMBER(5, 2),
    delinc        NUMBER(4, 2),
    delaz         NUMBER(5, 2),
    delslo        NUMBER(8, 4),
    quality       NUMBER(3, 2),
    snr           BINARY_DOUBLE,
    rflag         VARCHAR2(2),
    lddate        DATE              DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT arrival01 CHECK (arid > 0),
    CONSTRAINT arrival02 CHECK (azimuth >= 0.0 and azimuth <= 360.0),
    CONSTRAINT arrival03 CHECK (delaz > 0.0),
    CONSTRAINT arrival04 CHECK (delinc >= 0.0),
    CONSTRAINT arrival05 CHECK (delslo > 0.0),
    CONSTRAINT arrival06 CHECK (deltim >= 0.0),
    CONSTRAINT arrival07 CHECK (ema >= 0.0 and ema <= 90.0),
    CONSTRAINT arrival08 CHECK (fm in ('cu','cr','c.','du','dr','d.','.u','.r','..','+u','+r','+.','-u','-r','-.')),
    CONSTRAINT arrival09 CHECK (qual in ('i','e','w','I','E','W')),
    CONSTRAINT arrival10 CHECK (slow >= 0.0),
    CONSTRAINT arrival11 CHECK (snr > 0.0),
    CONSTRAINT arrival12 CHECK (quality >= 0.0 and quality <= 1.0),
    CONSTRAINT arrival13 CHECK (ccset < 1),
    CONSTRAINT arrival14 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT arkey01 PRIMARY KEY (arid)
    USING INDEX
        LOGGING
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

assocamm

Table Name	assocamm	
Owner Name		
Primary Keys	magid,ampid	
Definition	Data associating amplitudes with magnitudes	
Columns 

Column Name	Domain	Datatype	Null	Definition	
magid		NUMBER(15, 0)	N	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
ampid		NUMBER(15, 0)	N	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	 
commid		NUMBER(15, 0)	Y	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		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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		NUMBER(4, 3)	Y	Magnitude weight	 
in_wgt		NUMBER(4, 3)	Y	Input weight	 
mag		NUMBER(5, 2)	Y	Magnitude for this station reading	 
magres		NUMBER(5, 2)	Y	Magnitude residual	 
magcorr		NUMBER(5, 2)	Y	Magnitude correction for this channel	 
importance		NUMBER(4, 3)	Y	This attribute denotes the importance of a phase/amplitude reading towards an origin/magnitude. 0.0 means no importance, 1.0 implies extremely important	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	assocamm01	mag >= -10.0 and mag <= 10.0	 
	Check	assocamm02	magcorr >= -10.0 and magcorr <= 10.0	 
	Check	assocamm03	magid > 0	 
	Check	assocamm05	weight >= 0.0 and weight <= 1.0	 
	Check	assocamm06	in_wgt >= 0.0 and in_wgt <= 1.0	 
	Check	assocamm07	importance > 0.0 and importance <= 1.0	 
	Check	assocamm08	rflag in ('a','h','f','A','H','F')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
amp	Identifying	One To Zero or More	Aam_Amp			ampid	NO	NO	 
netmag	Identifying	One To Zero or More	Aam_Net			magid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE assocamm(
    magid         NUMBER(15, 0)    NOT NULL,
    ampid         NUMBER(15, 0)    NOT NULL,
    commid        NUMBER(15, 0),
    auth          VARCHAR2(15)     NOT NULL,
    subsource     VARCHAR2(8),
    weight        NUMBER(4, 3),
    in_wgt        NUMBER(4, 3),
    mag           NUMBER(5, 2),
    magres        NUMBER(5, 2),
    magcorr       NUMBER(5, 2),
    importance    NUMBER(4, 3),
    rflag         VARCHAR2(2),
    lddate        DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT assocamm01 CHECK (mag >= -10.0 and mag <= 10.0),
    CONSTRAINT assocamm02 CHECK (magcorr >= -10.0 and magcorr <= 10.0),
    CONSTRAINT assocamm03 CHECK (magid > 0),
    CONSTRAINT assocamm05 CHECK (weight >= 0.0 and weight <= 1.0),
    CONSTRAINT assocamm06 CHECK (in_wgt >= 0.0 and in_wgt <= 1.0),
    CONSTRAINT assocamm07 CHECK (importance > 0.0 and importance <= 1.0),
    CONSTRAINT assocamm08 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT assocammkey01 PRIMARY KEY (magid, ampid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Aam_Net FOREIGN KEY (magid)
    REFERENCES netmag(magid),
    CONSTRAINT Aam_Amp FOREIGN KEY (ampid)
    REFERENCES amp(ampid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

assocamo

Table Name	assocamo	
Owner Name		
Primary Keys	orid,ampid	
Definition	Data associating amplitudes with origins	
Columns 

Column Name	Domain	Datatype	Null	Definition	
orid		NUMBER(15, 0)	N	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	 
ampid		NUMBER(15, 0)	N	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	 
commid		NUMBER(15, 0)	Y	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		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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	 
delta		NUMBER(9, 4)	Y	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.	 
seaz		NUMBER(4, 1)	Y	Station to event azimuth. This attribute is calculated from the station and event locations. It is measured clockwise from North	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	assocamo01	seaz >= 0.0 and seaz <= 360.0	 
	Check	assocamo02	delta >= 0.0	 
	Check	assocamo03	rflag in ('a','h','f','A','H','F')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
amp	Identifying	One To Zero or More	Amo_Amp			ampid	NO	NO	 
origin	Identifying	One To Zero or More	Amo_Ori			orid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE assocamo(
    orid         NUMBER(15, 0)    NOT NULL,
    ampid        NUMBER(15, 0)    NOT NULL,
    commid       NUMBER(15, 0),
    auth         VARCHAR2(15)     NOT NULL,
    subsource    VARCHAR2(8),
    delta        NUMBER(9, 4),
    seaz         NUMBER(4, 1),
    rflag        VARCHAR2(2),
    lddate       DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT assocamo01 CHECK (seaz >= 0.0 and seaz <= 360.0),
    CONSTRAINT assocamo02 CHECK (delta >= 0.0),
    CONSTRAINT assocamo03 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT assocamokey01 PRIMARY KEY (orid, ampid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Amo_Ori FOREIGN KEY (orid)
    REFERENCES origin(orid),
    CONSTRAINT Amo_Amp FOREIGN KEY (ampid)
    REFERENCES amp(ampid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

assocaro

Table Name	assocaro	
Owner Name		
Primary Keys	orid,arid	
Definition	Data associating arrivals with origins	
Columns 

Column Name	Domain	Datatype	Null	Definition	
orid		NUMBER(15, 0)	N	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	 
arid		NUMBER(15, 0)	N	Arrival identifier. Each arrival is assigned a unique positive integer identifying it. This number is used in the AssocArO relation along with the origin identifier to link Arrival and Origin	 
commid		NUMBER(15, 0)	Y	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		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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	 
iphase		VARCHAR2(8)	Y	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	 
importance		NUMBER(4, 3)	Y	This attribute denotes the importance of a phase/amplitude reading towards an origin/magnitude. 0.0 means no importance, 1.0 implies extremely important	 
delta		NUMBER(9, 4)	Y	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.	 
seaz		NUMBER(4, 1)	Y	Event to station azimuth. This attribute is calculated from the event and station locations. It is measured clockwise from North	 
in_wgt		NUMBER(4, 3)	Y	Input weight.
Hypoinverse station archive card columns 17 & 50:
0, 1, 2, 3 --> 1.00
4, 5, 6, 7, 8, 9 --> 0.00	 
wgt		NUMBER(4, 3)	Y	Location weight. This attribute gives the final weight assigned to the allied arrival by the location program. It is used primarily for location programs that adaptively weight data by their residuals. Raw values from hypoinverse columns 39 & 64	 
timeres		NUMBER(5, 2)	Y	Time residual. This attribute is a travel time residual, measured in seconds. The residual is found by taking the observed arrival time (saved in the Arrival relation) of a seismic phase and substracting the expected arrival time. The expected arrival time is calculated by a formula based on earth velocity model, an event location and origin time, the distance to the station, and the particular seismic phase	 
ema		NUMBER(5, 2)	Y	The takeoff angle at the source, measured in degrees, with vertical down. ema=0 leaves the source straight down, while ema=180 leaves the source straight up; calculated in hypoinverse using the velocity model	 
slow		NUMBER(8, 4)	Y	Slowness residual. This attribute gives the difference between an observed slowness (saved in the Arrival relation) and a theorical prediction. The prediction is calculated for the related phase and event origin described in the record	 
vmodelid		NUMBER(3, 0)	Y	Velocity model identification	 
scorr		NUMBER(6, 4)	Y	Station correction	 
sdelay		NUMBER(7, 4)	Y	Station delay	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
ccset		VARCHAR2(1)	Y	This field describes whether the clock correction has been added or applied to the arrivals in computing a hypocenter solution	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	assocaro02	delta >= 0.0	 
	Check	assocaro03	ema >= 0 and ema <= 180	 
	Check	assocaro04	importance >= 0.0 and importance < 1.0	 
	Check	assocaro05	seaz >= 0.0 and seaz <= 360.0	 
	Check	assocaro06	slow >= 0.0	 
	Check	assocaro07	timeres >= 0.0	 
	Check	assocaro09	ccset < 1	 
	Check	assocaro10	rflag in ('a','h','f','A','H','F')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
arrival	Identifying	One To Zero or More	Aao_Arr			arid	NO	NO	 
origin	Identifying	One To Zero or More	Aao_Ori			orid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE assocaro(
    orid          NUMBER(15, 0)    NOT NULL,
    arid          NUMBER(15, 0)    NOT NULL,
    commid        NUMBER(15, 0),
    auth          VARCHAR2(15)     NOT NULL,
    subsource     VARCHAR2(8),
    iphase        VARCHAR2(8),
    importance    NUMBER(4, 3),
    delta         NUMBER(9, 4),
    seaz          NUMBER(4, 1),
    in_wgt        NUMBER(4, 3),
    wgt           NUMBER(4, 3),
    timeres       NUMBER(5, 2),
    ema           NUMBER(5, 2),
    slow          NUMBER(8, 4),
    vmodelid      NUMBER(3, 0),
    scorr         NUMBER(6, 4),
    sdelay        NUMBER(7, 4),
    rflag         VARCHAR2(2),
    ccset         VARCHAR2(1),
    lddate        DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT assocaro02 CHECK (delta >= 0.0),
    CONSTRAINT assocaro03 CHECK (ema >= 0 and ema <= 180),
    CONSTRAINT assocaro04 CHECK (importance >= 0.0 and importance < 1.0),
    CONSTRAINT assocaro05 CHECK (seaz >= 0.0 and seaz <= 360.0),
    CONSTRAINT assocaro06 CHECK (slow >= 0.0),
    CONSTRAINT assocaro07 CHECK (timeres >= 0.0),
    CONSTRAINT assocaro09 CHECK (ccset < 1),
    CONSTRAINT assocaro10 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT assocarokey01 PRIMARY KEY (orid, arid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Aao_Ori FOREIGN KEY (orid)
    REFERENCES origin(orid),
    CONSTRAINT Aao_Arr FOREIGN KEY (arid)
    REFERENCES arrival(arid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

assoccom

Table Name	assoccom	
Owner Name		
Primary Keys	magid,coid	
Definition	Data associating codas with magnitudes	
Columns 

Column Name	Domain	Datatype	Null	Definition	
magid		NUMBER(15, 0)	N	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
coid		NUMBER(15, 0)	N	Coda identification. Each coda is assigned a unique positive integer which identifies it in the database	 
commid		NUMBER(15, 0)	Y	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		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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		NUMBER(4, 3)	Y	Magnitude weight	 
in_wgt		NUMBER(4, 3)	Y	Input weight.
Hypoinverse station archive card column 83:
0, 1, 2, 3 --> 1.00
4, 5, 6, 7, 8, 9 --> 0.00	 
mag		NUMBER(7, 4)	Y	Magnitude for this station reading	 
magres		NUMBER(7, 4)	Y	Magnitude residual	 
magcorr		NUMBER(7, 4)	Y	Magnitude correction for this channel	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	assoccomkey04	weight >= 0.0 and weight <= 1.0	 
	Check	assoccomkey05	in_wgt >= 0.0 and in_wgt <= 1.0	 
	Check	assoccomkey06	rflag in ('a','h','f','A','H','F')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
coda	Identifying	One To Zero or More	Aom_Cod			coid	NO	NO	 
netmag	Identifying	One To Zero or More	Aom_Net			magid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE assoccom(
    magid        NUMBER(15, 0)    NOT NULL,
    coid         NUMBER(15, 0)    NOT NULL,
    commid       NUMBER(15, 0),
    auth         VARCHAR2(15)     NOT NULL,
    subsource    VARCHAR2(8),
    weight       NUMBER(4, 3),
    in_wgt       NUMBER(4, 3),
    mag          NUMBER(7, 4),
    magres       NUMBER(7, 4),
    magcorr      NUMBER(7, 4),
    rflag        VARCHAR2(2),
    lddate       DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT assoccomkey04 CHECK (weight >= 0.0 and weight <= 1.0),
    CONSTRAINT assoccomkey05 CHECK (in_wgt >= 0.0 and in_wgt <= 1.0),
    CONSTRAINT assoccomkey06 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT assoccomkey01 PRIMARY KEY (magid, coid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Aom_Net FOREIGN KEY (magid)
    REFERENCES netmag(magid),
    CONSTRAINT Aom_Cod FOREIGN KEY (coid)
    REFERENCES coda(coid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

assoccoo

Table Name	assoccoo	
Owner Name		
Primary Keys	orid,coid	
Definition	Data associating codas with origins	
Columns 

Column Name	Domain	Datatype	Null	Definition	
orid		NUMBER(15, 0)	N	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	 
coid		NUMBER(15, 0)	N	Coda identification. Each coda is assigned a unique positive integer which identifies it in the database	 
commid		NUMBER(15, 0)	Y	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		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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	 
delta		NUMBER(9, 4)	Y	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.	 
seaz		NUMBER(7, 4)	Y	Station to event azimuth. This attribute is calculated from the station and event locations. It is measured clockwise from North	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	assoccookey04	rflag in ('a','h','f','A','H','F')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
coda	Identifying	One To Zero or More	Aco_Cod			coid	NO	NO	 
origin	Identifying	One To Zero or More	Aco_Ori			orid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE assoccoo(
    orid         NUMBER(15, 0)    NOT NULL,
    coid         NUMBER(15, 0)    NOT NULL,
    commid       NUMBER(15, 0),
    auth         VARCHAR2(15)     NOT NULL,
    subsource    VARCHAR2(8),
    delta        NUMBER(9, 4),
    seaz         NUMBER(7, 4),
    rflag        VARCHAR2(2),
    lddate       DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT assoccookey04 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT assoccookey01 PRIMARY KEY (orid, coid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Aco_Ori FOREIGN KEY (orid)
    REFERENCES origin(orid),
    CONSTRAINT Aco_Cod FOREIGN KEY (coid)
    REFERENCES coda(coid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

assocevampset

Table Name	assocevampset	
Owner Name		
Primary Keys	ampsetid,ampsettype	
Definition	This table associates amplitude sets with an event	
Columns 

Column Name	Domain	Datatype	Null	Definition	
ampsetid		NUMBER	N	Amplitude set identifier	 
ampsettype		VARCHAR2(20)	N	Amplitude set type	 
evid		NUMBER(15, 0)	N	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	 
subsource		VARCHAR2(8)	N	Name tag of the application creating the set (e.g. AmpGen AmpGenPp Gmp2Db)	 
isvalid		NUMBER	N	Has value 1 if preferred set, 0 otherwise 	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		(cast(sys_extract_utc(systimestamp)asdate))	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
event	Non-Identifying	One To Zero or More				evid	NO	NO	 
ampsettypes	Identifying	One To Zero or More	assocevampsetkey02			ampsettype	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE assocevampset(
    ampsetid      NUMBER           NOT NULL,
    ampsettype    VARCHAR2(20)     NOT NULL,
    evid          NUMBER(15, 0)    NOT NULL,
    subsource     VARCHAR2(8)      NOT NULL,
    isvalid       NUMBER           NOT NULL,
    lddate        DATE             DEFAULT (cast(sys_extract_utc(systimestamp)asdate)),
    CONSTRAINT assocevampsetkey01 PRIMARY KEY (ampsetid, ampsettype)
    USING INDEX
        LOGGING, 
    CONSTRAINT Refevent102 FOREIGN KEY (evid)
    REFERENCES event(evid),
    CONSTRAINT assocevampsetkey02 FOREIGN KEY (ampsettype)
    REFERENCES ampsettypes(ampsettype)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

assoctypecat

Table Name	assoctypecat	
Owner Name		
Primary Keys	etype,catid	
Definition	Data associating event types with categories	
Columns 

Column Name	Domain	Datatype	Null	Definition	
etype		VARCHAR2(2)	N	This attribute is used to identify the type of seismic event	 
catid		NUMBER	N	Category identifier	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
eventcategory	Non-Identifying	One To Zero or More				catid	NO	NO	 
eventtype	Non-Identifying	One To Zero or More				etype	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE assoctypecat(
    etype    VARCHAR2(2)    NOT NULL,
    catid    NUMBER         NOT NULL,
    CONSTRAINT AssocTypeCatKey01 PRIMARY KEY (etype, catid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Refeventcategory83 FOREIGN KEY (catid)
    REFERENCES eventcategory(catid),
    CONSTRAINT Refeventtype84 FOREIGN KEY (etype)
    REFERENCES eventtype(etype)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

coda

Table Name	coda	
Owner Name		
Primary Keys	coid	
Definition	Summary information on a coda	
Columns 

Column Name	Domain	Datatype	Null	Definition	
coid		NUMBER(15, 0)	N	Coda identification. Each coda is assigned a unique positive integer which identifies it in the database	 
commid		NUMBER(15, 0)	Y	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		VARCHAR2(6)	N	Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used	 
net		VARCHAR2(8)	Y	Unique network identifier. This character string is the name of a seismic network	 
auth		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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		VARCHAR2(8)	Y	Channel name	 
channelsrc		VARCHAR2(8)	Y	Domain for channel. This specifies what naming convention is used for the channel name (i.e. SEED, USGS, etc.)	 
seedchan		VARCHAR2(3)	Y	SEED channel name. The first character denotes the band code, the second for the instrument code and the third represents the component code	 
location		VARCHAR2(2)	Y	Describes the individual sites on an array station, operated by the same network operator	 
codatype		VARCHAR2(3)	Y	Coda type	 
afix		NUMBER(7, 4)	Y	Nominal coda amplitude	 
afree		NUMBER(7, 4)	Y	Free amplitude	 
qfix		NUMBER(7, 4)	Y	Fixed coda decay constant	 
qfree		NUMBER(7, 4)	Y	Free decay	 
tau		NUMBER(7, 4)	Y	Coda duration (F-P time)	 
nsample		NUMBER(6, 0)	Y	Number of coda sample windows	 
rms		NUMBER(5, 3)	Y	Square root of the sum of the squares of the coda residuals, divided by the number of observations	 
durtype		VARCHAR2(3)	Y	Duration type	 
iphase		VARCHAR2(8)	Y	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		NUMBER(5, 3)	Y	Uncertainty in amplitude measurement	 
units		VARCHAR2(4)	N	Units of amplitude	 
time1		NUMBER(10, 0)	Y	Time for pairs	 
amp1		NUMBER(10, 0)	Y	Amplitude for pairs	 
time2		NUMBER(10, 0)	Y	Time for pairs	 
amp2		NUMBER(10, 0)	Y	Amplitude for pairs	 
time3		NUMBER(10, 0)	Y	Time for pairs	 
amp3		NUMBER(10, 0)	Y	Amplitude for pairs	 
time4		NUMBER(10, 0)	Y	Time for pairs	 
amp4		NUMBER(10, 0)	Y	Amplitude for pairs	 
time5		NUMBER(10, 0)	Y	Time for pairs	 
amp5		NUMBER(10, 0)	Y	Amplitude for pairs	 
time6		NUMBER(10, 0)	Y	Time for pairs	 
amp6		NUMBER(10, 0)	Y	Amplitude for pairs	 
quality		NUMBER(3, 2)	Y	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		NUMBER(25, 10)	N	The UTC epoch "start time" from which the relative seconds time values stored in the time1 ... time6 columns are measured	 
algorithm		VARCHAR2(15)	Y	Algorithm used. This is a brief textual description of the algorithm used to derive coda data	 
winsize		NUMBER(7, 4)	Y	Window over which waveform absolute amplitudes averaged	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	coda01	afix >= 0.0	 
	Check	coda03	amp1 > 0	 
	Check	coda04	amp2 > 0	 
	Check	coda05	amp3 > 0	 
	Check	coda06	amp4 > 0	 
	Check	coda07	amp5 > 0	 
	Check	coda08	amp6 > 0	 
	Check	coda09	codatype in ('P','S')	 
	Check	coda10	coid > 0	 
	Check	coda11	nsample >= 0	 
	Check	coda12	rms >= 0.0	 
	Check	coda13	time1 > 0	 
	Check	coda14	time2 > 0	 
	Check	coda15	time3 > 0	 
	Check	coda16	time4 > 0	 
	Check	coda17	time5 > 0	 
	Check	coda18	time6 > 0	 
	Check	coda19	rflag in ('a','h','f','A','H','F')	 
	Check	coda20	quality >= 0.0 and quality <= 1.0	 
	Check	coda21	durtype in ('a','d','h')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
assoccoo	Identifying	One To Zero or More	Aco_Cod				NO	NO	 
assoccom	Identifying	One To Zero or More	Aom_Cod				NO	NO	 
DDL Code 

CREATE TABLE coda(
    coid          NUMBER(15, 0)     NOT NULL,
    commid        NUMBER(15, 0),
    sta           VARCHAR2(6)       NOT NULL,
    net           VARCHAR2(8),
    auth          VARCHAR2(15)      NOT NULL,
    subsource     VARCHAR2(8),
    channel       VARCHAR2(8),
    channelsrc    VARCHAR2(8),
    seedchan      VARCHAR2(3),
    location      VARCHAR2(2),
    codatype      VARCHAR2(3),
    afix          NUMBER(7, 4),
    afree         NUMBER(7, 4),
    qfix          NUMBER(7, 4),
    qfree         NUMBER(7, 4),
    tau           NUMBER(7, 4),
    nsample       NUMBER(6, 0),
    rms           NUMBER(5, 3),
    durtype       VARCHAR2(3),
    iphase        VARCHAR2(8),
    eramp         NUMBER(5, 3),
    units         VARCHAR2(4)       NOT NULL,
    time1         NUMBER(10, 0),
    amp1          NUMBER(10, 0),
    time2         NUMBER(10, 0),
    amp2          NUMBER(10, 0),
    time3         NUMBER(10, 0),
    amp3          NUMBER(10, 0),
    time4         NUMBER(10, 0),
    amp4          NUMBER(10, 0),
    time5         NUMBER(10, 0),
    amp5          NUMBER(10, 0),
    time6         NUMBER(10, 0),
    amp6          NUMBER(10, 0),
    quality       NUMBER(3, 2),
    datetime      NUMBER(25, 10)    NOT NULL,
    algorithm     VARCHAR2(15),
    winsize       NUMBER(7, 4),
    rflag         VARCHAR2(2),
    lddate        DATE              DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT coda01 CHECK (afix >= 0.0),
    CONSTRAINT coda03 CHECK (amp1 > 0),
    CONSTRAINT coda04 CHECK (amp2 > 0),
    CONSTRAINT coda05 CHECK (amp3 > 0),
    CONSTRAINT coda06 CHECK (amp4 > 0),
    CONSTRAINT coda07 CHECK (amp5 > 0),
    CONSTRAINT coda08 CHECK (amp6 > 0),
    CONSTRAINT coda09 CHECK (codatype in ('P','S')),
    CONSTRAINT coda10 CHECK (coid > 0),
    CONSTRAINT coda11 CHECK (nsample >= 0),
    CONSTRAINT coda12 CHECK (rms >= 0.0),
    CONSTRAINT coda13 CHECK (time1 > 0),
    CONSTRAINT coda14 CHECK (time2 > 0),
    CONSTRAINT coda15 CHECK (time3 > 0),
    CONSTRAINT coda16 CHECK (time4 > 0),
    CONSTRAINT coda17 CHECK (time5 > 0),
    CONSTRAINT coda18 CHECK (time6 > 0),
    CONSTRAINT coda19 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT coda20 CHECK (quality >= 0.0 and quality <= 1.0),
    CONSTRAINT coda21 CHECK (durtype in ('a','d','h')),
    CONSTRAINT codakey01 PRIMARY KEY (coid)
    USING INDEX
        LOGGING
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

event

Table Name	event	
Owner Name		
Primary Keys	evid	
Definition	Summary information on an event	
Columns 

Column Name	Domain	Datatype	Null	Definition	
evid		NUMBER(15, 0)	N	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	 
prefor		NUMBER(15, 0)	Y	Preferred origin. This attribute holds the origin identifier, orid, that points to the preferred origin for a seismic event	 
prefmag		NUMBER(15, 0)	Y	Preferred magnitude. This attribute holds the magnitude identifier, magid, that points to the preferred magnitude for a seismic event or an origin	 
prefmec		NUMBER(15, 0)	Y	Preferred mechanism. This attribute holds the mechanism identifier, mecid, that points to the preferred mechanism for a seismic event or an origin	 
commid		NUMBER(15, 0)	Y	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		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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	 
etype		VARCHAR2(2)	N	This attribute is used to identify the type of seismic event, when known	 
selectflag		NUMBER(1, 0)	Y	This flag describes the “definitive” definition of an event. Helps to differentiate which event to use from two different real-time systems	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
version		NUMBER(3, 0)	N	Event version number. This attribute is incremented each time the preferred origin, magnitude or mechanism of the event is updated	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
version	Default		(0)	 
	Check	event02	evid > 0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
eventtype	Non-Identifying	One To Zero or More				etype	NO	NO	 
mec	Non-Identifying	Zero or One to Zero or More	Eve_Mec			prefmec	NO	NO	 
netmag	Non-Identifying	Zero or One to Zero or More	Eve_Net			prefmag	NO	NO	 
origin	Non-Identifying	Zero or One to Zero or More	Eve_Ori			prefor	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
assocevampset	Non-Identifying	Zero or One to Zero or More					NO	NO	 
eventprefor	Non-Identifying	One To Zero or More					NO	NO	 
eventprefmec	Non-Identifying	One To Zero or More					NO	NO	 
eventprefmag	Non-Identifying	One To Zero or More	Epm_Eve				NO	NO	 
origin	Non-Identifying	One To Zero or More	Ori_Eve				NO	NO	 
DDL Code 

CREATE TABLE event(
    evid          NUMBER(15, 0)    NOT NULL,
    prefor        NUMBER(15, 0),
    prefmag       NUMBER(15, 0),
    prefmec       NUMBER(15, 0),
    commid        NUMBER(15, 0),
    auth          VARCHAR2(15)     NOT NULL,
    subsource     VARCHAR2(8),
    etype         VARCHAR2(2)      NOT NULL,
    selectflag    NUMBER(1, 0),
    lddate        DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    version       NUMBER(3, 0)     DEFAULT 0 NOT NULL,
    CONSTRAINT event02 CHECK (evid > 0),
    CONSTRAINT evkey01 PRIMARY KEY (evid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Eve_Ori FOREIGN KEY (prefor)
    REFERENCES origin(orid),
    CONSTRAINT Eve_Net FOREIGN KEY (prefmag)
    REFERENCES netmag(magid),
    CONSTRAINT Eve_Mec FOREIGN KEY (prefmec)
    REFERENCES mec(mecid),
    CONSTRAINT Refeventtype85 FOREIGN KEY (etype)
    REFERENCES eventtype(etype)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

eventcategory

Table Name	eventcategory	
Owner Name		
Primary Keys	catid	
Definition	Summary information on event categories	
Columns 

Column Name	Domain	Datatype	Null	Definition	
catid		NUMBER	N	Category identifier	 
category		VARCHAR2(25)	N	Name associated with an event category	 
description		VARCHAR2(80)	Y	Event category description	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
	Check	EvCat01	catid > 0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
assoctypecat	Non-Identifying	One To Zero or More					NO	NO	 
DDL Code 

CREATE TABLE eventcategory(
    catid          NUMBER          NOT NULL,
    category       VARCHAR2(25)    NOT NULL,
    description    VARCHAR2(80),
    CONSTRAINT EvCat01 CHECK (catid > 0),
    CONSTRAINT EvCatKey01 PRIMARY KEY (catid)
    USING INDEX
        LOGGING
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

CREATE UNIQUE INDEX EvCat01 ON eventcategory(category)
    LOGGING
;

eventprefmag

Table Name	eventprefmag	
Owner Name		
Primary Keys	magtype,evid	
Definition	Summary information on preferred magnitudes for an event	
Columns 

Column Name	Domain	Datatype	Null	Definition	
magtype		VARCHAR2(6)	N	Magnitude type. This character string is used to specify the type of the magnitude measure	 
evid		NUMBER(15, 0)	N	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	 
magid		NUMBER(15, 0)	N	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	EventPrefMag_CHKTYP	magtype in ('p','a','b','e','l','l1','l2','lg','c','s','w','z','B', 'un','d','h','n','dl','lr')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
event	Non-Identifying	One To Zero or More	Epm_Eve			evid	NO	NO	 
netmag	Non-Identifying	One To Zero or More	Epm_Net			magid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE eventprefmag(
    magtype    VARCHAR2(6)      NOT NULL,
    evid       NUMBER(15, 0)    NOT NULL,
    magid      NUMBER(15, 0)    NOT NULL,
    lddate     DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT EventPrefMag_CHKTYP CHECK (magtype in ('p','a','b','e','l','l1','l2','lg','c','s','w','z','B', 'un','d','h','n','dl','lr')),
    CONSTRAINT EventPrefMag_PK PRIMARY KEY (magtype, evid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Epm_Net FOREIGN KEY (magid)
    REFERENCES netmag(magid),
    CONSTRAINT Epm_Eve FOREIGN KEY (evid)
    REFERENCES event(evid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

eventprefmec

Table Name	eventprefmec	
Owner Name		
Primary Keys	mechtype,evid	
Definition	Summary information on preferred mechanisms for an event	
Columns 

Column Name	Domain	Datatype	Null	Definition	
mechtype		VARCHAR2(2)	N	Mechanism type	 
evid		NUMBER(15, 0)	N	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	 
mecid		NUMBER(15, 0)	Y	Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	EvPMec02	mecid > 0	 
	Check	EvPMec03	mechtype IN ('FP','MT')	 
	Check	EvPMec01	evid > 0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
event	Non-Identifying	Zero or One to Zero or More				evid	NO	NO	 
mec	Non-Identifying	Zero or One to Zero or More				mecid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE eventprefmec(
    mechtype    VARCHAR2(2)      NOT NULL,
    evid        NUMBER(15, 0)    NOT NULL,
    mecid       NUMBER(15, 0),
    lddate      DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT EvPMec02 CHECK (mecid > 0),
    CONSTRAINT EvPMec03 CHECK (mechtype IN ('FP','MT')),
    CONSTRAINT EvPMec01 CHECK (evid > 0),
    CONSTRAINT EventPrefMec_PK PRIMARY KEY (mechtype, evid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Refevent70 FOREIGN KEY (evid)
    REFERENCES event(evid),
    CONSTRAINT Refmec71 FOREIGN KEY (mecid)
    REFERENCES mec(mecid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

eventprefor

Table Name	eventprefor	
Owner Name		
Primary Keys	type,evid	
Definition	Summary information on preferred origins for an event	
Columns 

Column Name	Domain	Datatype	Null	Definition	
type		VARCHAR2(2)	N	Type of location	 
evid		NUMBER(15, 0)	N	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	 
orid		NUMBER(15, 0)	N	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	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	EventPrefOr_CHKTYP	type in ('h','H','c','C','a','A','d','D','u','U')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
event	Non-Identifying	One To Zero or More				evid	NO	NO	 
origin	Non-Identifying	One To Zero or More				orid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE eventprefor(
    type      VARCHAR2(2)      NOT NULL,
    evid      NUMBER(15, 0)    NOT NULL,
    orid      NUMBER(15, 0)    NOT NULL,
    lddate    DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT EventPrefOr_CHKTYP CHECK (type in ('h','H','c','C','a','A','d','D','u','U')),
    CONSTRAINT EventPrefOr_PK PRIMARY KEY (type, evid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Refevent108 FOREIGN KEY (evid)
    REFERENCES event(evid),
    CONSTRAINT Reforigin109 FOREIGN KEY (orid)
    REFERENCES origin(orid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

eventtype

Table Name	eventtype	
Owner Name		
Primary Keys	etype	
Definition	Summary information on event types	
Columns 

Column Name	Domain	Datatype	Null	Definition	
etype		VARCHAR2(2)	N	This attribute is used to identify the type of seismic event	 
name		VARCHAR2(16)	N	Name associated with an event type	 
description		VARCHAR2(80)	Y	Event type description	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
	Check	EVENTTYPE02	etype IN ('eq','lp','se','to','tr','vt','nt','qb','ce','ex','sh','sn','th','av','co','df','ls','rb','rs','ve','bc','mi','pc','ot','st','uk','lf','su','px')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
assoctypecat	Non-Identifying	Zero or One to Zero or More					NO	NO	 
event	Non-Identifying	One To Zero or More					NO	NO	 
DDL Code 

CREATE TABLE eventtype(
    etype          VARCHAR2(2)     NOT NULL,
    name           VARCHAR2(16)    NOT NULL,
    description    VARCHAR2(80),
    CONSTRAINT EVENTTYPE02 CHECK (etype IN ('eq','lp','se','to','tr','vt','nt','qb','ce','ex','sh','sn','th','av','co','df','ls','rb','rs','ve','bc','mi','pc','ot','st','uk','lf','su','px')),
    CONSTRAINT EVENTTYPEKEY01 PRIMARY KEY (etype)
    USING INDEX
        LOGGING
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

CREATE UNIQUE INDEX EVENTTYPE01 ON eventtype(name)
    LOGGING
;

mec

Table Name	mec	
Owner Name		
Primary Keys	mecid	
Definition	Summary information on a moment tensor	
Columns 

Column Name	Domain	Datatype	Null	Definition	
mecid		NUMBER(15, 0)	N	Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database	 
oridin		NUMBER(15, 0)	Y	Input origin. This attribute holds the origin identifier, orid, that points to the origin from which the mechanism was computed	 
oridout		NUMBER(15, 0)	Y	Output origin. This attribute holds the origin identifier, orid, that points to the origin computed from the mechanism	 
magid		NUMBER(15, 0)	Y	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
commid		NUMBER(15, 0)	Y	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	 
mechtype		VARCHAR2(2)	Y	Mechanism type	 
mecalgo		VARCHAR2(15)	Y	This attribute represents the algorithm used to compute the mechanism (TDMT,TMTS=Dreger's code; FPFIT=fpfit; SMTINV=Pasyanos code)	 
scalar		BINARY_DOUBLE	Y	Seismic scalar moment (no value stored for fpfit)	 
erscalar		BINARY_DOUBLE	Y	Error in scalar moment. This is the standard deviation of the scalar moment	 
tft		VARCHAR2(8)	Y	Type of source time function. Used to specify if time function and source half-duration are assumed, derived, or determined	 
tfd		BINARY_DOUBLE	Y	Duration of the source time function	 
mxx		BINARY_DOUBLE	Y	Moment tensor elements. Given in Aki convention	 
myy		BINARY_DOUBLE	Y	Moment tensor elements. Given in Aki convention	 
mzz		BINARY_DOUBLE	Y	Moment tensor elements. Given in Aki convention	 
mxy		BINARY_DOUBLE	Y	Moment tensor elements. Given in Aki convention	 
mxz		BINARY_DOUBLE	Y	Moment tensor elements. Given in Aki convention	 
myz		BINARY_DOUBLE	Y	Moment tensor elements. Given in Aki convention	 
smxx		BINARY_DOUBLE	Y	Uncertainties in moment tensor elements	 
smyy		BINARY_DOUBLE	Y	Uncertainties in moment tensor elements	 
smzz		BINARY_DOUBLE	Y	Uncertainties in moment tensor elements	 
smxy		BINARY_DOUBLE	Y	Uncertainties in moment tensor elements	 
smxz		BINARY_DOUBLE	Y	Uncertainties in moment tensor elements	 
smyz		BINARY_DOUBLE	Y	Uncertainties in moment tensor elements	 
srcduration		NUMBER(6, 3)	Y	Source half-duration	 
auth		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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	 
strike1		NUMBER(3, 0)	Y	Strike of fault plane 1 from the best double couple	 
dip1		NUMBER(3, 0)	Y	Dip of fault plane 1 from the best double couple	 
rake1		NUMBER(4, 0)	Y	Rake of fault plane 1 from the best double couple solution	 
strike2		NUMBER(3, 0)	Y	Strike of fault plane 2 from the best double couple	 
dip2		NUMBER(2, 0)	Y	Dip of fault plane 2 from the best double couple	 
rake2		NUMBER(4, 0)	Y	Rake of fault plane 2 from the best double couple solution	 
unstrike1		NUMBER(6, 3)	Y	Uncertainty in strike 1	 
undip1		NUMBER(5, 3)	Y	Uncertainty in dip 1	 
unrake1		NUMBER(6, 3)	Y	Uncertainty in rake 1	 
unstrike2		NUMBER(6, 3)	Y	Uncertainty in strike 2	 
undip2		NUMBER(5, 3)	Y	Uncertainty in dip 2	 
unrake2		NUMBER(6, 3)	Y	Uncertainty in rake 2	 
eigenp		BINARY_DOUBLE	Y	Eigen value of compressional axis in the principal axes representation of the best double couple	 
plungep		NUMBER(2, 0)	Y	Plunge of the compressional axis in the principal axes representation of the best double couple	 
strikep		NUMBER(3, 0)	Y	Strike of compressional axis in the principal axes representation of the best double couple	 
eigenn		BINARY_DOUBLE	Y	Eigen value of null axis in the principal axes representation of the best double couple	 
plungen		NUMBER(2, 0)	Y	Plunge of the null axis in the principal axes representation of the best double couple	 
striken		NUMBER(3, 0)	Y	Strike of null axis in the principal axes representation of the best double couple	 
eigent		BINARY_DOUBLE	Y	Eigen value of tension axis in the principal axes representation of the best double couple	 
plunget		NUMBER(2, 0)	Y	Plunge of the tension axis in the principal axes representation of the best double couple	 
striket		NUMBER(3, 0)	Y	Strike of tension axis in the principal axes representation of the best double couple	 
nsta		NUMBER(5, 0)	Y	This quantity is the number of observations with non-zero input weights used to compute the mechanism. For CW=nsta, for FPFIT=nPobs, for HASH=nobs	 
pvr		NUMBER(5, 0)	Y	Goodness of fit. For TDMT this is percent variance reduction; for FPFIT this is (1-misfit)*100	 
quality		NUMBER(2, 1)	Y	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad	 
pdc		NUMBER(3, 0)	Y	Percent double couple of the seismic moment tensor	 
pclvd		NUMBER(3, 0)	Y	Percent compensated linear vector dipole of the seismic moment tensor	 
piso		NUMBER(3, 0)	Y	Percent isotropic of the seismic moment tensor. If the solution is constrained to have zero trace (no "ISO"), then "ISO" should be NULL, as opposed to a case where the full moment tensor was used, and the ISO component ended up being very small ("0")	 
datetime		NUMBER(25, 10)	N	The date of associated with information in the record, in true epoch format	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	mec13	plungen >= 0 and plungen <= 90	 
	Check	mec14	plungep >= 0 and plungep <= 90	 
	Check	mec15	plunget >= 0 and plunget <= 90	 
	Check	mec16	pclvd >= 0 and pclvd <= 100	 
	Check	mec17	pdc >= 0 and pdc <= 100	 
	Check	mec18	piso >= 0 and piso <= 100	 
	Check	mec19	pvr >= 0 and pvr <= 100	 
	Check	mec20	rake1 >= -180 and rake1 <= 180	 
	Check	mec21	rake2 >= -180 and rake2 <= 180	 
	Check	mec23	srcduration >= 0.0 and srcduration <= 100.0	 
	Check	mec24	striken >= 0 and striken <= 360	 
	Check	mec25	strikep >= 0 and strikep <= 360	 
	Check	mec26	striket >= 0 and striket <= 360	 
	Check	mec27	strike1 >= 0 and strike1 <= 360	 
	Check	mec28	strike2 >= 0 and strike2 <= 360	 
	Check	mec29	tfd > 0	 
	Check	mec30	undip1 >= -180 and undip1 <= 180	 
	Check	mec31	undip2 >= -180 and undip2 <= 180	 
	Check	mec38	unrake1 >= -180.0 and unrake1 <= 180.0	 
	Check	mec39	unrake2 >= -180.0 and unrake2 <= 180.0	 
	Check	mec40	unstrike1 >= -180.0 and unstrike1 <= 180.0	 
	Check	mec41	unstrike2 >= -180.0 and unstrike2 <= 180.0	 
	Check	mec42	quality >= 0.0 and quality <= 1.0	 
	Check	mec01	dip1 >= -90 and dip1 <= 90	 
	Check	mec02	dip2 >= -90 and dip2 <= 90	 
	Check	mec03	erscalar >= 0.0	 
	Check	mec05	mecid > 0	 
	Check	mec06	mechtype in ('FP','MT')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
netmag	Non-Identifying	Zero or One to Zero or More	Mec_Net			magid	NO	NO	 
origin	Non-Identifying	Zero or One to Zero or More	Mec_Ori			oridin	NO	NO	 
origin	Non-Identifying	Zero or One to Zero or More	Mec_Ori2			oridout	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
eventprefmec	Non-Identifying	Zero or One to Zero or More					NO	NO	 
mecdata	Non-Identifying	One To Zero or More					NO	NO	 
mecobject	Non-Identifying	One To Zero or More					NO	NO	 
event	Non-Identifying	One To Zero or More	Eve_Mec				NO	NO	 
origin	Non-Identifying	One To Zero or More	Ori_Mec				NO	NO	 
DDL Code 

CREATE TABLE mec(
    mecid          NUMBER(15, 0)     NOT NULL,
    oridin         NUMBER(15, 0),
    oridout        NUMBER(15, 0),
    magid          NUMBER(15, 0),
    commid         NUMBER(15, 0),
    mechtype       VARCHAR2(2),
    mecalgo        VARCHAR2(15),
    scalar         BINARY_DOUBLE,
    erscalar       BINARY_DOUBLE,
    tft            VARCHAR2(8),
    tfd            BINARY_DOUBLE,
    mxx            BINARY_DOUBLE,
    myy            BINARY_DOUBLE,
    mzz            BINARY_DOUBLE,
    mxy            BINARY_DOUBLE,
    mxz            BINARY_DOUBLE,
    myz            BINARY_DOUBLE,
    smxx           BINARY_DOUBLE,
    smyy           BINARY_DOUBLE,
    smzz           BINARY_DOUBLE,
    smxy           BINARY_DOUBLE,
    smxz           BINARY_DOUBLE,
    smyz           BINARY_DOUBLE,
    srcduration    NUMBER(6, 3),
    auth           VARCHAR2(15)      NOT NULL,
    subsource      VARCHAR2(8),
    strike1        NUMBER(3, 0),
    dip1           NUMBER(3, 0),
    rake1          NUMBER(4, 0),
    strike2        NUMBER(3, 0),
    dip2           NUMBER(2, 0),
    rake2          NUMBER(4, 0),
    unstrike1      NUMBER(6, 3),
    undip1         NUMBER(5, 3),
    unrake1        NUMBER(6, 3),
    unstrike2      NUMBER(6, 3),
    undip2         NUMBER(5, 3),
    unrake2        NUMBER(6, 3),
    eigenp         BINARY_DOUBLE,
    plungep        NUMBER(2, 0),
    strikep        NUMBER(3, 0),
    eigenn         BINARY_DOUBLE,
    plungen        NUMBER(2, 0),
    striken        NUMBER(3, 0),
    eigent         BINARY_DOUBLE,
    plunget        NUMBER(2, 0),
    striket        NUMBER(3, 0),
    nsta           NUMBER(5, 0),
    pvr            NUMBER(5, 0),
    quality        NUMBER(2, 1),
    pdc            NUMBER(3, 0),
    pclvd          NUMBER(3, 0),
    piso           NUMBER(3, 0),
    datetime       NUMBER(25, 10)    NOT NULL,
    rflag          VARCHAR2(2),
    lddate         DATE              DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT mec13 CHECK (plungen >= 0 and plungen <= 90),
    CONSTRAINT mec14 CHECK (plungep >= 0 and plungep <= 90),
    CONSTRAINT mec15 CHECK (plunget >= 0 and plunget <= 90),
    CONSTRAINT mec16 CHECK (pclvd >= 0 and pclvd <= 100),
    CONSTRAINT mec17 CHECK (pdc >= 0 and pdc <= 100),
    CONSTRAINT mec18 CHECK (piso >= 0 and piso <= 100),
    CONSTRAINT mec19 CHECK (pvr >= 0 and pvr <= 100),
    CONSTRAINT mec20 CHECK (rake1 >= -180 and rake1 <= 180),
    CONSTRAINT mec21 CHECK (rake2 >= -180 and rake2 <= 180),
    CONSTRAINT mec23 CHECK (srcduration >= 0.0 and srcduration <= 100.0),
    CONSTRAINT mec24 CHECK (striken >= 0 and striken <= 360),
    CONSTRAINT mec25 CHECK (strikep >= 0 and strikep <= 360),
    CONSTRAINT mec26 CHECK (striket >= 0 and striket <= 360),
    CONSTRAINT mec27 CHECK (strike1 >= 0 and strike1 <= 360),
    CONSTRAINT mec28 CHECK (strike2 >= 0 and strike2 <= 360),
    CONSTRAINT mec29 CHECK (tfd > 0),
    CONSTRAINT mec30 CHECK (undip1 >= -180 and undip1 <= 180),
    CONSTRAINT mec31 CHECK (undip2 >= -180 and undip2 <= 180),
    CONSTRAINT mec38 CHECK (unrake1 >= -180.0 and unrake1 <= 180.0),
    CONSTRAINT mec39 CHECK (unrake2 >= -180.0 and unrake2 <= 180.0),
    CONSTRAINT mec40 CHECK (unstrike1 >= -180.0 and unstrike1 <= 180.0),
    CONSTRAINT mec41 CHECK (unstrike2 >= -180.0 and unstrike2 <= 180.0),
    CONSTRAINT mec42 CHECK (quality >= 0.0 and quality <= 1.0),
    CONSTRAINT mec01 CHECK (dip1 >= -90 and dip1 <= 90),
    CONSTRAINT mec02 CHECK (dip2 >= -90 and dip2 <= 90),
    CONSTRAINT mec03 CHECK (erscalar >= 0.0),
    CONSTRAINT mec05 CHECK (mecid > 0),
    CONSTRAINT mec06 CHECK (mechtype in ('FP','MT')),
    CONSTRAINT meckey01 PRIMARY KEY (mecid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Mec_Ori FOREIGN KEY (oridin)
    REFERENCES origin(orid),
    CONSTRAINT Mec_Ori2 FOREIGN KEY (oridout)
    REFERENCES origin(orid),
    CONSTRAINT Mec_Net FOREIGN KEY (magid)
    REFERENCES netmag(magid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

mecchannel

Table Name	mecchannel	
Owner Name		
Primary Keys	mecdataid,net,sta,seedchan,location	
Definition	Summary information on channels associated with a mechanism	
Columns 

Column Name	Domain	Datatype	Null	Definition	
mecdataid		NUMBER(15, 0)	N	Mechanisn data identifier	 
net		VARCHAR2(8)	N	Unique network identifier. This character string is the name of a seismic network	 
sta		VARCHAR2(6)	N	Station code. This is the common code-name of a seismic observatory. Generally only three or four characters are used	 
seedchan		VARCHAR2(3)	N	SEED channel name. The first character denotes the band code, the second for the instrument code and the third represents the component code	 
location		VARCHAR2(2)	N	Describes the individual sites on an array station, operated by the same network operator	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
	Check	MecD01	mecdataid > 0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
mecdata	Identifying	One To Zero or More	MecChannel_FK01			mecdataid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE mecchannel(
    mecdataid    NUMBER(15, 0)    NOT NULL,
    net          VARCHAR2(8)      NOT NULL,
    sta          VARCHAR2(6)      NOT NULL,
    seedchan     VARCHAR2(3)      NOT NULL,
    location     VARCHAR2(2)      NOT NULL,
    CONSTRAINT MecD01 CHECK (mecdataid > 0),
    CONSTRAINT MecChannel_PK PRIMARY KEY (mecdataid, net, sta, seedchan, location)
    USING INDEX
        LOGGING, 
    CONSTRAINT MecChannel_FK01 FOREIGN KEY (mecdataid)
    REFERENCES mecdata(mecdataid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

mecdata

Table Name	mecdata	
Owner Name		
Primary Keys	mecdataid	
Definition	Summary information on data associated with a mechanism	
Columns 

Column Name	Domain	Datatype	Null	Definition	
mecdataid		NUMBER(15, 0)	N	Mechanism data identifier	 
mecid		NUMBER(15, 0)	Y	Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database	 
mecfreqid		NUMBER(15, 0)	Y	Frequency information identifier	 
polarity		VARCHAR2(2)	Y	Polarity of pick. This is the polarity as used by fpfit, corrected for dip, gain and reversals. Format like arrival.fm	 
discrepancy		VARCHAR2(1)	Y	Mainly used for fpfit. Does the polarity of the data match the quadrant of the mechanism	 
orientation		VARCHAR2(1)	Y	How are the components listed in the mecchannel table used (rotation, transformation). If channel has a polarity reversal, i.e. polarity is inverted from the raw polarity read from the waveforms, this should be indicated by a 'I' for inverted in this field. If data have not been inverted, enter " " (blank)	 
quality		NUMBER(3, 2)	Y	Quality. Fpfit uses quality 0-9	 
amplitude		FLOAT(126)	Y	SMTINV: spectral amplitude at the frequency given by mecfreqid	 
phase		FLOAT(126)	Y	SMTINV: spectral phase at the frequency given by mecfreqid	 
time1		NUMBER(25, 10)	Y	Start time of:
	TDMT: complete waveform window
	SMTINV: window for spectrum
	FPFIT: pick time	 
time2		NUMBER(25, 10)	Y	End of window, if window used (CW, SW)	 
model		VARCHAR2(10)	Y	Model used for greens functions; velocity model for other methods	 
zcor		NUMBER(5, 0)	Y	TDMT: value of cross correlation shift in samples for best solution	 
corlen		NUMBER(5, 0)	Y	TDMT: length of cross correlation window used in samples	 
dt		NUMBER(11, 5)	Y	Sampling interval of data used in inversion (could be resampled from original data); sampling interval valid for GF and data	 
varred		NUMBER(4, 1)	Y	Fit for tis station	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	MecData02	orientation IN ('C','R','T','H','3','L','E','N','Z','A','I',' ')	 
	Check	MecData03	quality BETWEEN 0 AND 1	 
	Check	MecData04	model IN ('mend1_','socal','gil7_')	 
	Check	MecData05	mecid > 0	 
	Check	MecData06	mecdataid > 0	 
	Check	MecData07	mecfreqid > 0	 
	Check	MecData01	discrepancy IN ('T','F')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
mec	Non-Identifying	Zero or One to Zero or More				mecid	NO	NO	 
mecfreq	Non-Identifying	Zero or One to Zero or More	MecData_FK02			mecfreqid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
mecchannel	Identifying	One To Zero or More	MecChannel_FK01				NO	NO	 
DDL Code 

CREATE TABLE mecdata(
    mecdataid      NUMBER(15, 0)     NOT NULL,
    mecid          NUMBER(15, 0),
    mecfreqid      NUMBER(15, 0),
    polarity       VARCHAR2(2),
    discrepancy    VARCHAR2(1),
    orientation    VARCHAR2(1),
    quality        NUMBER(3, 2),
    amplitude      FLOAT(126),
    phase          FLOAT(126),
    time1          NUMBER(25, 10),
    time2          NUMBER(25, 10),
    model          VARCHAR2(10),
    zcor           NUMBER(5, 0),
    corlen         NUMBER(5, 0),
    dt             NUMBER(11, 5),
    varred         NUMBER(4, 1),
    lddate         DATE              DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT MecData02 CHECK (orientation IN ('C','R','T','H','3','L','E','N','Z','A','I',' ')),
    CONSTRAINT MecData03 CHECK (quality BETWEEN 0 AND 1),
    CONSTRAINT MecData04 CHECK (model IN ('mend1_','socal','gil7_')),
    CONSTRAINT MecData05 CHECK (mecid > 0),
    CONSTRAINT MecData06 CHECK (mecdataid > 0),
    CONSTRAINT MecData07 CHECK (mecfreqid > 0),
    CONSTRAINT MecData01 CHECK (discrepancy IN ('T','F')),
    CONSTRAINT MecData_PK PRIMARY KEY (mecdataid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Refmec73 FOREIGN KEY (mecid)
    REFERENCES mec(mecid),
    CONSTRAINT MecData_FK02 FOREIGN KEY (mecfreqid)
    REFERENCES mecfreq(mecfreqid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

mecfreq

Table Name	mecfreq	
Owner Name		
Primary Keys	mecfreqid	
Definition	Summary information on frequency data	
Columns 

Column Name	Domain	Datatype	Null	Definition	
mecfreqid		NUMBER(15, 0)	N	Frequency information identifier	 
mecalgo		VARCHAR2(15)	Y	This attribute represents the algorithm used to compute the mechanism	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	MecF01	mecfreqid > 0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
mecdata	Non-Identifying	One To Zero or More	MecData_FK02				NO	NO	 
mecfreqdata	Identifying	One To Zero or More	MecFreqData_FK01				NO	NO	 
DDL Code 

CREATE TABLE mecfreq(
    mecfreqid    NUMBER(15, 0)    NOT NULL,
    mecalgo      VARCHAR2(15),
    lddate       DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT MecF01 CHECK (mecfreqid > 0),
    CONSTRAINT MecFreq_PK PRIMARY KEY (mecfreqid)
    USING INDEX
        LOGGING
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

mecfreqdata

Table Name	mecfreqdata	
Owner Name		
Primary Keys	mecfreqid,type	
Definition	Summary information on frequency data	
Columns 

Column Name	Domain	Datatype	Null	Definition	
mecfreqid		NUMBER(15, 0)	N	Frequency information identifier	 
type		VARCHAR2(15)	N	What this frequency is (frequency for fit)	 
freq		NUMBER(15, 6)	N	Frequency value	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
	Check	MecFreqData02	mecfreqid > 0	 
	Check	MecFreqData01	type IN ('LP','HP','SF')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
mecfreq	Identifying	One To Zero or More	MecFreqData_FK01			mecfreqid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE mecfreqdata(
    mecfreqid    NUMBER(15, 0)    NOT NULL,
    type         VARCHAR2(15)     NOT NULL,
    freq         NUMBER(15, 6)    NOT NULL,
    CONSTRAINT MecFreqData02 CHECK (mecfreqid > 0),
    CONSTRAINT MecFreqData01 CHECK (type IN ('LP','HP','SF')),
    CONSTRAINT MecFreqData_PK PRIMARY KEY (mecfreqid, type)
    USING INDEX
        LOGGING, 
    CONSTRAINT MecFreqData_FK01 FOREIGN KEY (mecfreqid)
    REFERENCES mecfreq(mecfreqid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

mecobject

Table Name	mecobject	
Owner Name		
Primary Keys	dataid,mecid	
Definition	Summary information on objects associated with a mechanism	
Columns 

Column Name	Domain	Datatype	Null	Definition	
dataid		NUMBER(15, 0)	N	Object type	 
mecid		NUMBER(15, 0)	N	Mechanism identification. Each mechanism is assigned a unique positive integer which identifies it in the database	 
mimetype		VARCHAR2(20)	Y	Image type	 
data		BLOB	Y	Object described by dataid/mimetype	 
meta		VARCHAR2(128)	Y	Metadata for object, i.e. filename=email.txt	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
	Check	MecObj02	dataid >= 0	 
	Check	MecObj01	mecid > 0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
mec	Non-Identifying	Zero or One to Zero or More				mecid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE mecobject(
    dataid      NUMBER(15, 0)    NOT NULL,
    mecid       NUMBER(15, 0)    NOT NULL,
    mimetype    VARCHAR2(20),
    data        BLOB,
    meta        VARCHAR2(128),
    CONSTRAINT MecObj02 CHECK (dataid >= 0),
    CONSTRAINT MecObj01 CHECK (mecid > 0),
    CONSTRAINT MecObject_PK PRIMARY KEY (dataid, mecid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Refmec76 FOREIGN KEY (mecid)
    REFERENCES mec(mecid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

netmag

Table Name	netmag	
Owner Name		
Primary Keys	magid	
Definition	Summary information on a magnitude	
Columns 

Column Name	Domain	Datatype	Null	Definition	
magid		NUMBER(15, 0)	N	Magnitude identifier. This key is used to identify a magnitude in the Netmag relation. It is required for every magnitude	 
orid		NUMBER(15, 0)	N	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	 
commid		NUMBER(15, 0)	Y	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	 
magnitude		NUMBER(5, 2)	N	Magnitude. This gives the magnitude value of the type indicated by magtype	 
magtype		VARCHAR2(6)	N	Magnitude type. This character string is used to specify the type of the magnitude measure	 
auth		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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	 
magalgo		VARCHAR2(15)	Y	This attribute represents the algorithm used to compute the magnitude	 
nsta		NUMBER(5, 0)	Y	This quantity is the number of stations with non-zero input weights used to compute the magnitude	 
nobs		NUMBER(5, 0)	Y	This quantity is the number of observations with non-zero input weights used to compute the magnitude	 
uncertainty		NUMBER(5, 3)	Y	Magnitude uncertainty. Median of the absolute values of the channel magnitude residual deviations from the channel magnitude's median, the summary magnitude.	 
gap		NUMBER(4, 1)	Y	Gap in azimuthal coverage	 
distance		NUMBER(7, 3)	Y	Distance from the origin to the nearest station	 
quality		NUMBER(2, 1)	Y	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been finalized	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	netmag01	magnitude >= -10.0 and magnitude <= 10.0	 
	Check	netmag02	magtype in ('p', 'a','b','e','l','l1','l2','lg','c','s','w','z','B','un','d','h','n','dl')	 
	Check	netmag03	nsta >= 0	 
	Check	netmag04	uncertainty >= 0.0	 
	Check	netmag05	quality >= 0.0 and quality <= 1.0	 
	Check	netmag06	magid > 0	 
	Check	netmag07	rflag in ('a','h','f','A','H','F')	 
	Check	netmag08	nobs >= 0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
origin	Non-Identifying	One To Zero or More	Net_Ori			orid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
assocamm	Identifying	One To Zero or More	Aam_Net				NO	NO	 
assoccom	Identifying	One To Zero or More	Aom_Net				NO	NO	 
eventprefmag	Non-Identifying	One To Zero or More	Epm_Net				NO	NO	 
event	Non-Identifying	One To Zero or More	Eve_Net				NO	NO	 
mec	Non-Identifying	Zero or One to Zero or More	Mec_Net				NO	NO	 
origin	Non-Identifying	One To Zero or More	Ori_Net				NO	NO	 
DDL Code 

CREATE TABLE netmag(
    magid          NUMBER(15, 0)    NOT NULL,
    orid           NUMBER(15, 0)    NOT NULL,
    commid         NUMBER(15, 0),
    magnitude      NUMBER(5, 2)     NOT NULL,
    magtype        VARCHAR2(6)      NOT NULL,
    auth           VARCHAR2(15)     NOT NULL,
    subsource      VARCHAR2(8),
    magalgo        VARCHAR2(15),
    nsta           NUMBER(5, 0),
    nobs           NUMBER(5, 0),
    uncertainty    NUMBER(5, 3),
    gap            NUMBER(4, 1),
    distance       NUMBER(7, 3),
    quality        NUMBER(2, 1),
    rflag          VARCHAR2(2),
    lddate         DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT netmag01 CHECK (magnitude >= -10.0 and magnitude <= 10.0),
    CONSTRAINT netmag02 CHECK (magtype in ('p', 'a','b','e','l','l1','l2','lg','c','s','w','z','B','un','d','h','n','dl')),
    CONSTRAINT netmag03 CHECK (nsta >= 0),
    CONSTRAINT netmag04 CHECK (uncertainty >= 0.0),
    CONSTRAINT netmag05 CHECK (quality >= 0.0 and quality <= 1.0),
    CONSTRAINT netmag06 CHECK (magid > 0),
    CONSTRAINT netmag07 CHECK (rflag in ('a','h','f','A','H','F')),
    CONSTRAINT netmag08 CHECK (nobs >= 0),
    CONSTRAINT magkey01 PRIMARY KEY (magid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Net_Ori FOREIGN KEY (orid)
    REFERENCES origin(orid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

origin

Table Name	origin	
Owner Name		
Primary Keys	orid	
Definition	Data on event location	
Columns 

Column Name	Domain	Datatype	Null	Definition	
orid		NUMBER(15, 0)	N	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	 
evid		NUMBER(15, 0)	N	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	 
prefmag		NUMBER(15, 0)	Y	Preferred magnitude. This attribute holds the magnitude identifier, magid, that points to the preferred magnitude for a seismic event or an origin	 
prefmec		NUMBER(15, 0)	Y	Preferred mechanism. This attribute holds the mechanism identifier, mecid, that points to the preferred mechanism for a seismic event or an origin	 
commid		NUMBER(15, 0)	Y	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	 
bogusflag		NUMBER(1, 0)	N	This field describes whether an origin is bogus or not	 
datetime		NUMBER(25, 10)	N	The date of associated with information in the record, in true epoch format	 
lat		NUMBER(9, 7)	N	Latitude. This attribute is the geographic latitude. Locations north of the equator have positive latitudes	 
lon		NUMBER(10, 7)	N	Longitude. This attribute is the geographic longitude. Longitudes are measured positive east of the Greenwich meridian	 
depth		NUMBER(7, 3)	Y	Distance in KM of the earthquake source below the geoid. Hypoinverse model types E, L or V are always geoid depths	 
mdepth		NUMBER(7, 3)	Y	Distance in KM of the earthquake source below the model surface. For model depths, all the recording stations are located at the top of the model and their elevations are not used. Model types T or H if uncorrected by depth datum are always model depths	 
type		VARCHAR2(2)	Y	Type of location	 
algorithm		VARCHAR2(15)	Y	Algorithm used. This is a brief textual description of the algorithm used to compute a seismic origin	 
algo_assoc		VARCHAR2(80)	Y	Association algorithm used. This is a textual description of the algorithm used for associating the data	 
auth		VARCHAR2(15)	N	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		VARCHAR2(8)	Y	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	 
datumhor		VARCHAR2(8)	Y	Datum type for horizontal (latitude and longitude) coordinates	 
datumver		VARCHAR2(8)	Y	Datum type for depth or elevation	 
gap		NUMBER(4, 1)	Y	Gap in azimuthal coverage	 
distance		NUMBER(7, 3)	Y	Distance from the origin to the nearest station	 
wrms		NUMBER(5, 3)	Y	This attribute denotes the weighted RMS	 
stime		NUMBER(6, 3)	Y	Origin time error. This attribute denotes the standard deviation of the origin time	 
erhor		NUMBER(7, 3)	Y	Horizontal error. This attribute denotes the location uncertainty that accompanies the location	 
sdep		NUMBER(7, 3)	Y	Depth error. This is the standard deviation of the depth estimate	 
erlat		NUMBER(7, 3)	Y	Error in latitude. This is the standard deviation of the latitude estimate	 
erlon		NUMBER(7, 3)	Y	Error in longitude. This is the standard deviation of the longitude estimate	 
totalarr		NUMBER(5, 0)	Y	Total number of phases in the database for the specified orid. This field signifies the number of P and S arrivals with non-zero input weights	 
totalamp		NUMBER(6, 0)	Y	Total number of amplitudes in the database for the specified orid. Not all amplitudes have to associated with all magnitudes or origins	 
ndef		NUMBER(5, 0)	Y	This attribute denotes the number of phases with non-zero output weights used in hypocenter calculation	 
nbs		NUMBER(4, 0)	Y	Number of S phase readings with non-zero output weights	 
nbfm		NUMBER(4, 0)	Y	Number of P first motions with non-zero input weights	 
locevid		VARCHAR2(12)	Y	Local event identifier. This attribute describes the original event identifier of the event. In combination with auth and subsource, it can be used to uniquely identify the original event identifier from that source. For example, waveforms from the original source may be associated with this identifier	 
quality		NUMBER(2, 1)	Y	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad	 
fdepth		VARCHAR2(1)	Y	This attribute indicates if the depth was fixed or not to compute the solution	 
fepi		VARCHAR2(1)	Y	This attribute indicates if the epicenter was fixed or not to compute the solution	 
ftime		VARCHAR2(1)	Y	This attribute indicates if the origin time was fixed or not to compute the solution	 
vmodelid		VARCHAR2(2)	Y	Velocity model identification. This string identifies a version (instance) of the velocity model for the specified domain and algorithm. This version should be changed whenever the velocity model is changed. It is recommended that values 00 - 99 be used for this field	 
cmodelid		VARCHAR2(2)	Y	Velocity model domain. This string identifies the organization responsible for the velocity model. Recommendations for this field are the SEED network name, or a unique abbreviation of the processing center when using data from multiple networks	 
rflag		VARCHAR2(2)	Y	This flag describes whether an observation was generated automatically, by a human, or has been saved,  finalized or canceled	 
crust_type		VARCHAR2(1)	Y	The type of crust model used for travel time calculations. Each type has its own geometry of velocity layers or gradients within layers, tied to the options of the location program	 
crust_model		VARCHAR2(3)	Y	The code for the regional (geographic) crust model that is dominant in the travel time calculations. The crust model depends on the location of the earthquake origin and not on the recording station. The code is for the highest weighted model if more than one is used	 
gtype		VARCHAR2(1)	Y	Geographic type. Describes the location of the event relative to the network. If the event occurred within the network's boundaries the geographic type is 'local'. If it occurs within delta < xxxx it is regional. Events outside this distance are teleseisms	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
bogusflag	Default		(0)	 
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	origin02	datumhor in ('NAD27','WGS84')	 
	Check	origin03	datumver in ('NAD27','WGS84','AVERAGE')	 
	Check	origin04	depth >= -10.0 and depth <= 1000.0	 
	Check	origin05	distance >= 0.0	 
	Check	origin06	erhor >= 0.0	 
	Check	origin07	erlat >= 0.0	 
	Check	origin08	erlon >= 0.0	 
	Check	origin09	fdepth in ('y','n')	 
	Check	origin10	fepi in ('y','n')	 
	Check	origin11	ftime in ('y','n')	 
	Check	origin12	gap >= 0.0 and gap <= 360.0	 
	Check	origin15	nbfm >= 0	 
	Check	origin16	nbs >= 0	 
	Check	origin17	ndef >= 0	 
	Check	origin18	orid > 0	 
	Check	origin19	quality >= 0.0 and quality <= 1.0	 
	Check	origin20	type in ('H','h','C','c','A','a','D','d','u','U')	 
	Check	origin21	stime >= 0.0	 
	Check	origin23	wrms >= 0.0	 
	Check	origin24	sdep >=0.0	 
	Check	origin25	totalarr >=0	 
	Check	origin26	totalamp >= 0	 
	Check	origin28	rflag in ('a','h','f','A','H','F','i','I','c','C')	 
	Check	origin30	crust_type in ('H','T','E','L','V')	 
	Check	origin31	gtype in ('L','R','T')	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
event	Non-Identifying	One To Zero or More	Ori_Eve			evid	NO	NO	 
mec	Non-Identifying	Zero or One to Zero or More	Ori_Mec			prefmec	NO	NO	 
netmag	Non-Identifying	Zero or One to Zero or More	Ori_Net			prefmag	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
eventprefor	Non-Identifying	One To Zero or More					NO	NO	 
remark origin	Identifying	One To Zero or More					NO	NO	 
assocaro	Identifying	One To Zero or More	Aao_Ori				NO	NO	 
assoccoo	Identifying	One To Zero or More	Aco_Ori				NO	NO	 
assocamo	Identifying	One To Zero or More	Amo_Ori				NO	NO	 
event	Non-Identifying	One To Zero or More	Eve_Ori				NO	NO	 
mec	Non-Identifying	One To Zero or More	Mec_Ori				NO	NO	 
mec	Non-Identifying	One To Zero or More	Mec_Ori2				NO	NO	 
netmag	Non-Identifying	One To Zero or More	Net_Ori				NO	NO	 
origin_error	Identifying	One To Zero or More	Ori__Err_Ori				NO	NO	 
DDL Code 

CREATE TABLE origin(
    orid           NUMBER(15, 0)     NOT NULL,
    evid           NUMBER(15, 0)     NOT NULL,
    prefmag        NUMBER(15, 0),
    prefmec        NUMBER(15, 0),
    commid         NUMBER(15, 0),
    bogusflag      NUMBER(1, 0)      DEFAULT 0 NOT NULL,
    datetime       NUMBER(25, 10)    NOT NULL,
    lat            NUMBER(9, 7)      NOT NULL,
    lon            NUMBER(10, 7)     NOT NULL,
    depth          NUMBER(7, 3),
    mdepth         NUMBER(7, 3),
    type           VARCHAR2(2),
    algorithm      VARCHAR2(15),
    algo_assoc     VARCHAR2(80),
    auth           VARCHAR2(15)      NOT NULL,
    subsource      VARCHAR2(8),
    datumhor       VARCHAR2(8),
    datumver       VARCHAR2(8),
    gap            NUMBER(4, 1),
    distance       NUMBER(7, 3),
    wrms           NUMBER(5, 3),
    stime          NUMBER(6, 3),
    erhor          NUMBER(7, 3),
    sdep           NUMBER(7, 3),
    erlat          NUMBER(7, 3),
    erlon          NUMBER(7, 3),
    totalarr       NUMBER(5, 0),
    totalamp       NUMBER(6, 0),
    ndef           NUMBER(5, 0),
    nbs            NUMBER(4, 0),
    nbfm           NUMBER(4, 0),
    locevid        VARCHAR2(12),
    quality        NUMBER(2, 1),
    fdepth         VARCHAR2(1),
    fepi           VARCHAR2(1),
    ftime          VARCHAR2(1),
    vmodelid       VARCHAR2(2),
    cmodelid       VARCHAR2(2),
    rflag          VARCHAR2(2),
    crust_type     VARCHAR2(1),
    crust_model    VARCHAR2(3),
    gtype          VARCHAR2(1),
    lddate         DATE              DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT origin02 CHECK (datumhor in ('NAD27','WGS84')),
    CONSTRAINT origin03 CHECK (datumver in ('NAD27','WGS84','AVERAGE')),
    CONSTRAINT origin04 CHECK (depth >= -10.0 and depth <= 1000.0),
    CONSTRAINT origin05 CHECK (distance >= 0.0),
    CONSTRAINT origin06 CHECK (erhor >= 0.0),
    CONSTRAINT origin07 CHECK (erlat >= 0.0),
    CONSTRAINT origin08 CHECK (erlon >= 0.0),
    CONSTRAINT origin09 CHECK (fdepth in ('y','n')),
    CONSTRAINT origin10 CHECK (fepi in ('y','n')),
    CONSTRAINT origin11 CHECK (ftime in ('y','n')),
    CONSTRAINT origin12 CHECK (gap >= 0.0 and gap <= 360.0),
    CONSTRAINT origin15 CHECK (nbfm >= 0),
    CONSTRAINT origin16 CHECK (nbs >= 0),
    CONSTRAINT origin17 CHECK (ndef >= 0),
    CONSTRAINT origin18 CHECK (orid > 0),
    CONSTRAINT origin19 CHECK (quality >= 0.0 and quality <= 1.0),
    CONSTRAINT origin20 CHECK (type in ('H','h','C','c','A','a','D','d','u','U')),
    CONSTRAINT origin21 CHECK (stime >= 0.0),
    CONSTRAINT origin23 CHECK (wrms >= 0.0),
    CONSTRAINT origin24 CHECK (sdep >=0.0),
    CONSTRAINT origin25 CHECK (totalarr >=0),
    CONSTRAINT origin26 CHECK (totalamp >= 0),
    CONSTRAINT origin28 CHECK (rflag in ('a','h','f','A','H','F','i','I','c','C')),
    CONSTRAINT origin30 CHECK (crust_type in ('H','T','E','L','V')),
    CONSTRAINT origin31 CHECK (gtype in ('L','R','T')),
    CONSTRAINT orkey01 PRIMARY KEY (orid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Ori_Eve FOREIGN KEY (evid)
    REFERENCES event(evid),
    CONSTRAINT Ori_Net FOREIGN KEY (prefmag)
    REFERENCES netmag(magid),
    CONSTRAINT Ori_Mec FOREIGN KEY (prefmec)
    REFERENCES mec(mecid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

origin_error

Table Name	origin_error	
Owner Name		
Primary Keys	orid	
Definition	Error data on event location	
Columns 

Column Name	Domain	Datatype	Null	Definition	
orid		NUMBER(15, 0)	N	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	 
sxx		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
syy		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
szz		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
stt		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
sxy		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
sxz		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
syz		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
stx		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
sty		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
stz		NUMBER(7, 3)	Y	Elements of the covariance matrix for the location defined by orid. The covariance matrix is symmetric (and positive definite) so that sxy = syx, etc., (x, y, z, t) refer to latitude, longitude, depth and origin time, respectively. These attributes (together with sdobs, ndef and dattype) provide all the information necessary to construct the K-dimensional (K=2, 3, 4) confidence ellipse or ellipsoids at any confidence limit desired	 
azismall		NUMBER(5, 2)	Y	Azimuth of smallest principal error	 
dipsmall		NUMBER(4, 2)	Y	Dip of smallest principal error	 
magsmall		NUMBER(7, 5)	Y	Magnitude of smallest principal error	 
aziinter		NUMBER(5, 2)	Y	Azimuth of intermediate principal error	 
dipinter		NUMBER(4, 2)	Y	Dip of intermediate principal error	 
maginter		NUMBER(7, 5)	Y	Magnitude of intermediate principal error	 
azilarge		NUMBER(5, 2)	Y	Azimuth of largest principal error	 
diplarge		NUMBER(4, 2)	Y	Dip of largest principal error	 
maglarge		NUMBER(7, 5)	Y	Magnitude of largest principal error	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	orig_error01	aziinter >= 0.0 and aziinter <= 360.0	 
	Check	orig_error02	azilarge >= 0.0 and azilarge <= 360.0	 
	Check	orig_error03	azismall >= 0.0 and azismall <= 360.0	 
	Check	orig_error04	dipinter >= -90.0 and dipinter <= 90.0	 
	Check	orig_error05	diplarge >= -90.0 and diplarge <= 90.0	 
	Check	orig_error06	dipsmall >= -90.0 and dipsmall <= 90.0	 
	Check	orig_error07	maginter >= 0.0	 
	Check	orig_error08	maglarge >= 0.0	 
	Check	orig_error09	magsmall >= 0.0	 
	Check	orig_error10	stx > 0.0	 
	Check	orig_error11	sty > 0.0	 
	Check	orig_error12	stz > 0.0	 
	Check	orig_error13	sxx > 0.0	 
	Check	orig_error14	sxy > 0.0	 
	Check	orig_error15	sxz > 0.0	 
	Check	orig_error16	syy > 0.0	 
	Check	orig_error17	syz > 0.0	 
	Check	orig_error18	stt > 0.0	 
	Check	orig_error19	szz > 0.0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
origin	Identifying	One To Zero or More	Ori__Err_Ori			orid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE origin_error(
    orid        NUMBER(15, 0)    NOT NULL,
    sxx         NUMBER(7, 3),
    syy         NUMBER(7, 3),
    szz         NUMBER(7, 3),
    stt         NUMBER(7, 3),
    sxy         NUMBER(7, 3),
    sxz         NUMBER(7, 3),
    syz         NUMBER(7, 3),
    stx         NUMBER(7, 3),
    sty         NUMBER(7, 3),
    stz         NUMBER(7, 3),
    azismall    NUMBER(5, 2),
    dipsmall    NUMBER(4, 2),
    magsmall    NUMBER(7, 5),
    aziinter    NUMBER(5, 2),
    dipinter    NUMBER(4, 2),
    maginter    NUMBER(7, 5),
    azilarge    NUMBER(5, 2),
    diplarge    NUMBER(4, 2),
    maglarge    NUMBER(7, 5),
    lddate      DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT orig_error01 CHECK (aziinter >= 0.0 and aziinter <= 360.0),
    CONSTRAINT orig_error02 CHECK (azilarge >= 0.0 and azilarge <= 360.0),
    CONSTRAINT orig_error03 CHECK (azismall >= 0.0 and azismall <= 360.0),
    CONSTRAINT orig_error04 CHECK (dipinter >= -90.0 and dipinter <= 90.0),
    CONSTRAINT orig_error05 CHECK (diplarge >= -90.0 and diplarge <= 90.0),
    CONSTRAINT orig_error06 CHECK (dipsmall >= -90.0 and dipsmall <= 90.0),
    CONSTRAINT orig_error07 CHECK (maginter >= 0.0),
    CONSTRAINT orig_error08 CHECK (maglarge >= 0.0),
    CONSTRAINT orig_error09 CHECK (magsmall >= 0.0),
    CONSTRAINT orig_error10 CHECK (stx > 0.0),
    CONSTRAINT orig_error11 CHECK (sty > 0.0),
    CONSTRAINT orig_error12 CHECK (stz > 0.0),
    CONSTRAINT orig_error13 CHECK (sxx > 0.0),
    CONSTRAINT orig_error14 CHECK (sxy > 0.0),
    CONSTRAINT orig_error15 CHECK (sxz > 0.0),
    CONSTRAINT orig_error16 CHECK (syy > 0.0),
    CONSTRAINT orig_error17 CHECK (syz > 0.0),
    CONSTRAINT orig_error18 CHECK (stt > 0.0),
    CONSTRAINT orig_error19 CHECK (szz > 0.0),
    CONSTRAINT orerrkey01 PRIMARY KEY (orid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Ori__Err_Ori FOREIGN KEY (orid)
    REFERENCES origin(orid)
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

remark

Table Name	remark	
Owner Name		
Primary Keys	commid,lineno	
Definition	Comments	
Columns 

Column Name	Domain	Datatype	Null	Definition	
commid		NUMBER(15, 0)	N	Comment Identifier	 
lineno		NUMBER(15, 0)	N	Comment line number. This integer attribute is assigned as a sequence number for multiple line comments. The combination of commid and lineno is unique	 
remark		VARCHAR2(80)	Y	Descriptive text. This single line of text is an arbitrary comment about a record in the database. The comment is linked to its parent relation only by forward reference from commid in the tuple of the relation of interest	 
lddate		DATE	Y	Load date. Date and time that the record was created, in Oracle date datatype	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
lddate	Default		SYS_EXTRACT_UTC(SYSTIMESTAMP)	 
	Check	remark01	commid > 0	 
	Check	remark02	lineno > 0	 
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
remark origin	Identifying	One To Zero or More					NO	NO	 
DDL Code 

CREATE TABLE remark(
    commid    NUMBER(15, 0)    NOT NULL,
    lineno    NUMBER(15, 0)    NOT NULL,
    remark    VARCHAR2(80),
    lddate    DATE             DEFAULT SYS_EXTRACT_UTC(SYSTIMESTAMP),
    CONSTRAINT remark01 CHECK (commid > 0),
    CONSTRAINT remark02 CHECK (lineno > 0),
    CONSTRAINT remkey01 PRIMARY KEY (commid, lineno)
    USING INDEX
        LOGGING
)
TABLESPACE PI000
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

remark origin

Table Name	remark origin	
Owner Name		
Primary Keys	lineno,commid,orid	
Definition		
Columns 

Column Name	Domain	Datatype	Null	Definition	
lineno		NUMBER(15, 0)	N	Comment line number. This integer attribute is assigned as a sequence number for multiple line comments. The combination of commid and lineno is unique	 
commid		NUMBER(15, 0)	N	Comment Identifier	 
orid		NUMBER(15, 0)	N	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	 
Defaults, Rules and Check Constraints 

Column	Type	Name	Restriction	
Foreign Keys 

 Parent Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Supertype	Deferrable	
remark	Identifying	One To Zero or More				lineno, commid	NO	NO	 
origin	Identifying	One To Zero or More				orid	NO	NO	 
 Child Relationships: 

Table Name	Type	Cardinality	Constraint Name	Verb Phrase	Inverse Phrase	Foreign Keys	Is Subtype	Deferrable	
DDL Code 

CREATE TABLE "remark origin"(
    lineno    NUMBER(15, 0)    NOT NULL,
    commid    NUMBER(15, 0)    NOT NULL,
    orid      NUMBER(15, 0)    NOT NULL,
    CONSTRAINT PK60 PRIMARY KEY (lineno, commid, orid)
    USING INDEX
        LOGGING, 
    CONSTRAINT Refremark111 FOREIGN KEY (commid, lineno)
    REFERENCES remark(commid, lineno),
    CONSTRAINT Reforigin112 FOREIGN KEY (orid)
    REFERENCES origin(orid)
)
LOGGING
NOPARALLEL
NOCACHE
NOCOMPRESS
;

Oracle Sequence Summary Report

Name	ObjectType	
NCEDCDBA.AMPSEQ	Sequence	
NCEDCDBA.ARSEQ	Sequence	
NCEDCDBA.COMMSEQ	Sequence	
NCEDCDBA.COSEQ	Sequence	
NCEDCDBA.EVSEQ	Sequence	
NCEDCDBA.MAGSEQ	Sequence	
NCEDCDBA.MECDATASEQ	Sequence	
NCEDCDBA.MECFREQSEQ	Sequence	
NCEDCDBA.MECSEQ	Sequence	
NCEDCDBA.ORSEQ	Sequence	

Oracle Sequence Detail Report

NCEDCDBA.AMPSEQ

Name	NCEDCDBA.AMPSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key Amp.ampid	
SQL 

CREATE SEQUENCE NCEDCDBA.AMPSEQ
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    CACHE 20
    ORDER
	
NCEDCDBA.ARSEQ

Name	NCEDCDBA.ARSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key Arrival.arid	
SQL 

CREATE SEQUENCE NCEDCDBA.ARSEQ
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    CACHE 20
    ORDER
	
NCEDCDBA.COMMSEQ

Name	NCEDCDBA.COMMSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key Remark.commid	
SQL 

CREATE SEQUENCE NCEDCDBA.COMMSEQ 
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    NOCYCLE
    CACHE 20
    ORDER
	
NCEDCDBA.COSEQ

Name	NCEDCDBA.COSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key Coda.coid	
SQL 

CREATE SEQUENCE NCEDCDBA.COSEQ 
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    NOCYCLE
    CACHE 20
    ORDER
	
NCEDCDBA.EVSEQ

Name	NCEDCDBA.EVSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key Event.evid	
SQL 

CREATE SEQUENCE NCEDCDBA.EVSEQ 
    START WITH 60000000
    INCREMENT BY 1
    NOMINVALUE
    NOMAXVALUE
    NOCYCLE
    CACHE 20
    ORDER
	
NCEDCDBA.MAGSEQ

Name	NCEDCDBA.MAGSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key Netmag.magid	
SQL 

CREATE SEQUENCE NCEDCDBA.MAGSEQ 
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    NOCYCLE
    CACHE 20
    ORDER
	
NCEDCDBA.MECDATASEQ

Name	NCEDCDBA.MECDATASEQ	
ObjectType	Sequence	
Description 

Sequence for primary key MecData.mecdataid	
SQL 

CREATE SEQUENCE NCEDCDBA.MECDATASEQ
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    CACHE 20
    NOORDER
	
NCEDCDBA.MECFREQSEQ

Name	NCEDCDBA.MECFREQSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key MecFreq.mecfreqid	
SQL 

CREATE SEQUENCE NCEDCDBA.MECFREQSEQ
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    CACHE 20
    NOORDER
	
NCEDCDBA.MECSEQ

Name	NCEDCDBA.MECSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key Mec.mecid	
SQL 

CREATE SEQUENCE NCEDCDBA.MECSEQ 
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    NOCYCLE
    CACHE 20
    ORDER
	
NCEDCDBA.ORSEQ

Name	NCEDCDBA.ORSEQ	
ObjectType	Sequence	
Description 

Sequence for primary key Origin.orid	
SQL 

CREATE SEQUENCE NCEDCDBA.ORSEQ 
    START WITH 2
    INCREMENT BY 5
    NOMINVALUE
    NOMAXVALUE
    NOCYCLE
    CACHE 20
    ORDER