origin

origin

Logical Entity Name	origin
Default Table Name	origin
Definition	Data on event location

origin Attributes

Attribute/Logical Rolename Domain Datatype NULL Definition

orid (PK) NUMERIC(15, 0) NO 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 (FK) NUMERIC(15, 0) NO Event identifier. Each event is assigned a unique integer which identifies it in a database. It is possible for several records in the Origin relation to have the same evid. This indicates there are several opinions about the location of the event. The evid does not have to be identical to the local network’s event identifier, which is stored in the Origin table. This allows merging data for a single event from multiple sources without insisting that database evid is identical to the source’s local event identifier

prefmag (FK) NUMERIC(15, 0) YES Preferred magnitude. This attribute holds the magnitude identifier, magid, that points to the preferred magnitude for a seismic event or an origin

prefmec (FK) NUMERIC(15, 0) YES 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) YES Comment identification. This is a key used to point to free-form comments entered in the Remark relation. These comments store additional information about a tuple in another relation. Within the Remark relation, there may be many tuples with the same commid and different lineno, but the same commid will appear in only one other tuple among the rest of the relations in the database

bogusflag NUMERIC(1, 0) NO This field describes whether an origin is bogus or not

datetime NUMERIC(25, 10) NO The date of associated with information in the record, in true epoch format

lat NUMERIC(9, 7) NO Latitude. This attribute is the geographic latitude. Locations north of the equator have positive latitudes

lon NUMERIC(10, 7) NO Longitude. This attribute is the geographic longitude. Longitudes are measured positive east of the Greenwich meridian

depth NUMERIC(7, 3) YES 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) YES 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) YES Type of location

algorithm VARCHAR(15) YES Algorithm used. This is a brief textual description of the algorithm used to compute a seismic origin

algo_assoc VARCHAR(80) YES Association algorithm used. This is a textual description of the algorithm used for associating the data

auth VARCHAR(15) NO The auth field specifies the source of the information. This may be a network identifier (FDSN or otherwise), or any other string indicating the source of the information in the record

subsource VARCHAR(8) YES A second identifier to specify the system or process that derived the data. e.g., the origin's AUTH is CI, but the subsource (the solution) was computed by JIGGLE

datumhor VARCHAR(8) YES Datum type for horizontal (latitude and longitude) coordinates

datumver VARCHAR(8) YES Datum type for depth or elevation

gap NUMERIC(4, 1) YES Gap in azimuthal coverage

distance NUMERIC(7, 3) YES Distance from the origin to the nearest station

wrms NUMERIC(5, 3) YES This attribute denotes the weighted RMS

stime NUMERIC(6, 3) YES Origin time error. This attribute denotes the standard deviation of the origin time

erhor NUMERIC(7, 3) YES Horizontal error. This attribute denotes the location uncertainty that accompanies the location

sdep NUMERIC(7, 3) YES Depth error. This is the standard deviation of the depth estimate

erlat NUMERIC(7, 3) YES Error in latitude. This is the standard deviation of the latitude estimate

erlon NUMERIC(7, 3) YES Error in longitude. This is the standard deviation of the longitude estimate

totalarr NUMERIC(5, 0) YES 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) YES 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) YES This attribute denotes the number of phases with non-zero output weights used in hypocenter calculation

nbs NUMERIC(4, 0) YES Number of S phase readings with non-zero output weights

nbfm NUMERIC(4, 0) YES Number of P first motions with non-zero input weights

locevid VARCHAR(12) YES 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) YES This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad

fdepth VARCHAR(1) YES This attribute indicates if the depth was fixed or not to compute the solution

fepi VARCHAR(1) YES This attribute indicates if the epicenter was fixed or not to compute the solution

ftime VARCHAR(1) YES This attribute indicates if the origin time was fixed or not to compute the solution

vmodelid VARCHAR(2) YES 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) YES 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) YES This flag describes whether an observation was generated automatically, by a human, or has been saved, finalized or canceled

crust_type VARCHAR(1) YES 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) YES 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) YES 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 YES Load date. Date and time that the record was created, in Oracle date datatype

origin Keys

Key Name Key Type Keys

orkey01 PrimaryKey orid

origin Relationships

Parent Relationships:

Entity Name Type Cardinality Business Name VerbPhrase InversePhrase 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 VerbPhrase InversePhrase 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 Check Constraints

Check Constraint Name CheckConstraint

origin02 datumhor in ('NAD27','WGS84')

origin03 datumver in ('NAD27','WGS84','AVERAGE')

origin04 depth >= -10.0 and depth <= 1000.0

origin05 distance >= 0.0

origin06 erhor >= 0.0

origin07 erlat >= 0.0

origin08 erlon >= 0.0

origin09 fdepth in ('y','n')

origin10 fepi in ('y','n')

origin11 ftime in ('y','n')

origin12 gap >= 0.0 and gap <= 360.0

origin15 nbfm >= 0

origin16 nbs >= 0

origin17 ndef >= 0

origin18 orid > 0

origin19 quality >= 0.0 and quality <= 1.0

origin20 type in ('H','h','C','c','A','a','D','d','u','U','n','N')

origin21 stime >= 0.0

origin23 wrms >= 0.0

origin24 sdep >=0.0

origin25 totalarr >=0

origin26 totalamp >= 0

origin28 rflag in ('a','h','f','A','H','F','i','I','c','C')

origin30 crust_type in ('H','T','E','L','V')

origin31 gtype in ('l','r','t')

Attribute/Logical Rolename	Domain	Datatype	NULL	Definition
orid		NUMERIC(15, 0)	NO	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)	NO	Event identifier. Each event is assigned a unique integer which identifies it in a database. It is possible for several records in the Origin relation to have the same evid. This indicates there are several opinions about the location of the event. The evid does not have to be identical to the local network’s event identifier, which is stored in the Origin table. This allows merging data for a single event from multiple sources without insisting that database evid is identical to the source’s local event identifier
prefmag		NUMERIC(15, 0)	YES	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)	YES	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)	YES	Comment identification. This is a key used to point to free-form comments entered in the Remark relation. These comments store additional information about a tuple in another relation. Within the Remark relation, there may be many tuples with the same commid and different lineno, but the same commid will appear in only one other tuple among the rest of the relations in the database
bogusflag		NUMERIC(1, 0)	NO	This field describes whether an origin is bogus or not
datetime		NUMERIC(25, 10)	NO	The date of associated with information in the record, in true epoch format
lat		NUMERIC(9, 7)	NO	Latitude. This attribute is the geographic latitude. Locations north of the equator have positive latitudes
lon		NUMERIC(10, 7)	NO	Longitude. This attribute is the geographic longitude. Longitudes are measured positive east of the Greenwich meridian
depth		NUMERIC(7, 3)	YES	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)	YES	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)	YES	Type of location
algorithm		VARCHAR(15)	YES	Algorithm used. This is a brief textual description of the algorithm used to compute a seismic origin
algo_assoc		VARCHAR(80)	YES	Association algorithm used. This is a textual description of the algorithm used for associating the data
auth		VARCHAR(15)	NO	The auth field specifies the source of the information. This may be a network identifier (FDSN or otherwise), or any other string indicating the source of the information in the record
subsource		VARCHAR(8)	YES	A second identifier to specify the system or process that derived the data. e.g., the origin's AUTH is CI, but the subsource (the solution) was computed by JIGGLE
datumhor		VARCHAR(8)	YES	Datum type for horizontal (latitude and longitude) coordinates
datumver		VARCHAR(8)	YES	Datum type for depth or elevation
gap		NUMERIC(4, 1)	YES	Gap in azimuthal coverage
distance		NUMERIC(7, 3)	YES	Distance from the origin to the nearest station
wrms		NUMERIC(5, 3)	YES	This attribute denotes the weighted RMS
stime		NUMERIC(6, 3)	YES	Origin time error. This attribute denotes the standard deviation of the origin time
erhor		NUMERIC(7, 3)	YES	Horizontal error. This attribute denotes the location uncertainty that accompanies the location
sdep		NUMERIC(7, 3)	YES	Depth error. This is the standard deviation of the depth estimate
erlat		NUMERIC(7, 3)	YES	Error in latitude. This is the standard deviation of the latitude estimate
erlon		NUMERIC(7, 3)	YES	Error in longitude. This is the standard deviation of the longitude estimate
totalarr		NUMERIC(5, 0)	YES	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)	YES	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)	YES	This attribute denotes the number of phases with non-zero output weights used in hypocenter calculation
nbs		NUMERIC(4, 0)	YES	Number of S phase readings with non-zero output weights
nbfm		NUMERIC(4, 0)	YES	Number of P first motions with non-zero input weights
locevid		VARCHAR(12)	YES	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)	YES	This attribute denotes the quality of an origin, an arrival, or a mechanism. 1.0 = good, 0.0 = bad
fdepth		VARCHAR(1)	YES	This attribute indicates if the depth was fixed or not to compute the solution
fepi		VARCHAR(1)	YES	This attribute indicates if the epicenter was fixed or not to compute the solution
ftime		VARCHAR(1)	YES	This attribute indicates if the origin time was fixed or not to compute the solution
vmodelid		VARCHAR(2)	YES	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)	YES	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)	YES	This flag describes whether an observation was generated automatically, by a human, or has been saved, finalized or canceled
crust_type		VARCHAR(1)	YES	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)	YES	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)	YES	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	YES	Load date. Date and time that the record was created, in Oracle date datatype

Entity Name	Type	Cardinality	Business Name	VerbPhrase	InversePhrase	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

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