Differences between revisions 2 and 22 (spanning 20 versions)

Discussion on package BasicEventDescription

Quick navigation: go to package

Waveform | Common | StationCharacterization | SeismicSource | ResourceMetadata | Borehole | BasicEventDescription | SiteCharacterization | VSTypes | StrongMotion | BasicEventDescriptionTypes | Filter | Hydraulic |

In current package (BasicEventDescription): go to class

MomentTensor | FocalMechanism | Amplitude | StationMagnitudeContribution | Magnitude | StationMagnitude | OriginUncertainty | Arrival | Origin | Pick | Event | EventParameters |

BasicEventDescription overview page

BasicEventDescription class diagram

MomentTensor [element]

This class represents a moment tensor solution for an event. It is an optional part of a FocalMechanism description.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.publicID (type co:ResourceReference)

Resource identifier of MomentTensor.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.derivedOriginID (type co:ResourceReference)

Refers to the publicID of the Origin derived in the moment tensor inversion.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.momentMagnitudeID (type co:ResourceReference)

Refers to the publicID of the Magnitude object which represents the derived moment magnitude.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.tensor (type bedt:Tensor)

Tensor object holding the moment tensor elements.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.scalarMoment (type co:RealQuantity)

Scalar moment as derived in moment tensor inversion. Unit: Nm

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.variance (type :RealQuantity)

Variance of moment tensor inversion.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.varianceReduction (type :RealQuantity)

Variance reduction of moment tensor inversion, given in percent (Dreger 2003). This is a goodness-of-fit measure.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.filterID (type co:ResourceReference)

Resource identifier of the filter setup used in moment tensor inversion.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.greensFunctionID (type co:ResourceReference)

Resource identifier of the Green’s function used in moment tensor inversion.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.methodID (type co:ResourceReference)

Resource identifier of the method used for moment-tensor inversion.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.category (type bedt:MomentTensorCategory)

Category of moment tensor inversion. Valid entries are from MomentTensorCategory.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.clvd (type :RealQuantity)

CLVD (compensated linear vector dipole) parameter obtained from moment tensor inversion (decimal fraction between 0 and 1).

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.doubleCouple (type :RealQuantity)

Double couple parameter obtained from moment tensor inversion (decimal fraction between 0 and 1).

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.inversionType (type bedt:MTInversionType)

Type of moment tensor inversion. Users should avoid to give contradictory information in inversionType and methodID. Valid entries are from MTInversionType.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.iso (type co:RealQuantity)

Isotropic part obtained from moment tensor inversion (decimal fraction between 0 and 1).

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.sourceTimeFunction (type bedt:SourceTimeFunction)

Source time function used in moment-tensor inversion.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.creationInfo (type rm:CreationInfo)

see CreationInfo

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

MomentTensor.dataUsed (type bedt:DataUsed)

Describes waveform data used for moment-tensor inversion.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism [element]

This class describes the focal mechanism of an event. It includes different descriptions like nodal planes, principal axes, and a moment tensor. The moment tensor description is provided by objects of the class MomentTensor which can be specified as child elements of FocalMechanism.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.publicID (type co:ResourceReference)

Resource identifier of FocalMechanism.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.triggeringOriginID (type co:ResourceReference)

Refers to the publicID of the triggering origin.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.nodalPlanes (type bedt:NodalPlanes)

Nodal planes of the focal mechanism.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.principalAxes (type bedt:PrincipalAxes)

Principal axes of the focal mechanism.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.methodID (type co:ResourceReference)

Resource identifier of the method used for determination of the focal mechanism.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.azimuthalGap (type float)

Largest azimuthal gap in distribution of stations used for determination of focal mechanism. Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.misfit (type float)

Fraction of misfit polarities in a first-motion focal mechanism determination. Decimal fraction between 0 and 1.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.stationDistributionRatio (type float)

Station distribution ratio (STDR) parameter. Indicates how the stations are distributed about the focal sphere (Reasenberg and Oppenheimer 1985). Decimal fraction between 0 and 1.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.stationPolarityCount (type int)

Number of station polarities used for determination of focal mechanism.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.evaluationMode (type co:EvaluationMode)

see EvaluationMode

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.evaluationStatus (type co:EvaluationStatus)

see EvaluationStatus

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.creationInfo (type rm:CreationInfo)

see CreationInfo

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.momentTensor (type bed:MomentTensor)

see MomentTensor

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

FocalMechanism.waveformID (type wf:WaveformStreamID)

Refers to a set of waveform streams from which the focal mechanism was derived.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude [element]

This class represents a quantification of the waveform anomaly, usually a single amplitude measurement or a measurement of the visible signal duration for duration magnitudes.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.publicID (type co:ResourceReference)

Resource identifier of Amplitude.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.genericAmplitude (type co:RealQuantity)

Measured amplitude value for the given waveformID. Note that this attribute can describe different physical quantities, depending on the type and category of the amplitude. These can be, e.g., displacement, velocity, or a period. If the only amplitude information is a period, it has to specified here, not in the period attribute. The latter can be used if the amplitude measurement contains information on, e.g., displacement and an additional period. Since the physical quantity described by this attribute is not fixed, the unit of measurement cannot be defined in advance. However, the quantity has to be specified in SI base units. The enumeration given in attribute unit provides the most likely units that could be needed here. For clarity, using the optional unit attribute is highly encouraged.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.type (type string)

String that describes the type of amplitude using the nomenclature from Storchak et al. (2003). Possible values include unspecified amplitude reading (A), amplitude reading for local magnitude (AML), amplitude reading for body wave magnitude (AMB), amplitude reading for surface wave magnitude (AMS), and time of visible end of record for duration magnitude (END). It has a maximum length of 32 characters.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.unit (type bedt:AmplitudeUnit)

This attribute provides the most likely measurement units for the physical quantity described in the genericAmplitude attribute. Possible values are specified as combinations of SI base units. Allowed values are from AmplitudeUnit.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.category (type bedt:AmplitudeCategory)

This attribute describes the way the waveform trace is evaluated to derive an amplitude value. This can be just reading a single value for a given point in time (point), taking a mean value over a time interval (mean), integrating the trace over a time interval (integral), specifying just a time interval (duration), or evaluating a period (period). Allowed values are from AmplitudeCategory.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.period (type co:RealQuantity)

Dominant period in the timeWindow in case of amplitude measurements. Not used for duration magnitude. Unit: s

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.timeWindow (type co:TimeWindow)

Description of the time window used for amplitude measurement. Recommended for duration magnitudes.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.waveformID (type wf:WaveformStreamID)

Identifies the waveform stream on which the amplitude was measured.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.pickID (type co:ResourceReference)

Refers to the publicID of an associated Pick object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.filterID (type co:ResourceReference)

Identifies the filter or filter setup used for filtering the waveform stream referenced by waveformID.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.methodID (type co:ResourceReference)

Describes the method of amplitude determination.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.magnitudeHint (type string)

Type of magnitude the amplitude measurement is used for. For valid values see class Magnitude. String value with a maximum length of 32 characters.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.scalingTime (type co:TimeQuantity)

Scaling time for amplitude measurement.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.snr (type float)

Signal-to-noise ratio of the spectrogram at the location the amplitude was measured.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.evaluationMode (type co:EvaluationMode)

see EvaluationMode

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.evaluationStatus (type co:EvaluationStatus)

see EvaluationStatus

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.creationInfo (type rm:CreationInfo)

see CreationInfo

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Amplitude.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitudeContribution [element]

This class describes the weighting of magnitude values from several StationMagnitude objects for computing a network magnitude estimation.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitudeContribution.stationMagnitudeID (type co:ResourceReference)

Refers to the publicID of a StationMagnitude object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitudeContribution.residual (type float)

Residual of magnitude computation.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitudeContribution.weight (type float)

Weight of the magnitude value from class StationMagnitude for computing the magnitude value in class Magnitude. Note that there is no rule for the sum of the weights of all station magnitude contributions to a specific network magnitude. In particular, the weights are not required to sum up to unity.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude [element]

Describes a magnitude which can, but does not need to be associated with an origin. Association with an origin is expressed with the optional attribute originID. It is either a combination of different magnitude estimations, or it represents the reported magnitude for the given event.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.publicID (type co:ResourceReference)

Resource identifier of Magnitude.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.mag (type co:RealQuantity)

Resulting magnitude value from combining values of type StationMagnitude. If no estimations are available, this value can represent the reported magnitude.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.type (type string)

Describes the type of magnitude. This is a free-text field because it is impossible to cover all existing magnitude type designations with an enumeration. Possible values are unspecified magitude (M), local magnitude (ML), body wave magnitude (Mb), surface wave magnitude (MS), moment magnitude (Mw), duration magnitude (Md), coda magnitude (Mc), MH, Mwp, M50, M100, etc.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.originID (type co:ResourceReference)

Reference to an origin’s publicID if the magnitude has an associated Origin.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.methodID (type co:ResourceReference)

Identifies the method of magnitude estimation. Users should avoid to give contradictory information in methodID and type.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.stationCount (type int)

Number of used stations for this magnitude computation.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.azimuthalGap (type float)

Azimuthal gap for this magnitude computation. Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.evaluationMode (type co:EvaluationMode)

see EvaluationMode

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.evaluationStatus (type co:EvaluationStatus)

see EvaluationStatus

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.creationInfo (type rm:CreationInfo)

see CreationInfo

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.stationMagnitudeContribution (type bed:StationMagnitudeContribution)

see StationMagnitudeContribution.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Magnitude.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude [element]

This class describes the magnitude derived from a single waveform stream.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.publicID (type co:ResourceReference)

Resource identifier of StationMagnitude.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.originID (type co:ResourceReference)

Reference to an origin’s publicID if the StationMagnitude has an associated Origin.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.mag (type co:RealQuantity)

Estimated magnitude.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.type (type string)

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.amplitudeID (type co:ResourceReference)

Identifies the data source of the StationMagnitude. For magnitudes derived from amplitudes in waveforms (e. g., local magnitude ML), amplitudeID points to publicID in class Amplitude.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.methodID (type co:ResourceReference)

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.waveformID (type wf:WaveformStreamID)

Identifies the waveform stream. This element can be helpful if no amplitude is referenced, or the amplitude is not available in the context. Otherwise, it would duplicate the waveformID provided there and can be omitted.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.creationInfo (type rm:CreationInfo)

see CreationInfo

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

StationMagnitude.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

OriginUncertainty [element]

This class describes the location uncertainties of an origin. The uncertainty can be described either as a simple circular horizontal uncertainty, an uncertainty ellipse according to IMS1.0, or a confidence ellipsoid. If multiple uncertainty models are given, the preferred variant can be specified in the attribute preferredDescription.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

OriginUncertainty.preferredDescription (type bedt:OriginUncertaintyDescription)

Preferred uncertainty description. Allowed values are from OriginUncertaintyDescription.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

OriginUncertainty.horizontalUncertainty (type float)

Circular confidence region, given by single value of horizontal uncertainty. Unit: m

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

OriginUncertainty.maxHorizontalUncertainty (type float)

Semi-major axis of confidence ellipse. Unit: m

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

OriginUncertainty.minHorizontalUncertainty (type float)

Semi-minor axis of confidence ellipse. Unit: m

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

OriginUncertainty.azimuthMaxHorizontalUncertainty (type float)

Azimuth of major axis of confidence ellipse. Measured clockwise from South-North direction at epicenter. Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

OriginUncertainty.confidenceEllipsoid (type bedt:ConfidenceEllipsoid)

see ConfidenceEllipsoid

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

OriginUncertainty.confidenceLevel (type float)

Confidence level of the uncertainty, given in percent.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival [element]

Successful association of a pick with an origin qualifies this pick as an arrival. An arrival thus connects a pick with an origin and provides additional attributes that describe this relationship. Usually qualification of a pick as an arrival for a given origin is a hypothesis, which is based on assumptions about the type of arrival (phase) as well as observed and (on the basis of an earth model) computed arrival times, or the residual, respectively. Additional pick attributes like the horizontal slowness and backazimuth of the observed wave—especially if derived from array data—may further constrain the nature of the arrival.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.publicID (type co:ResourceReference)

Resource identifier of Arrival.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.pickID (type co:ResourceReference)

Refers to a publicID of a Pick.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.phase (type bedt:Phase)

Phase identification. For possible values, please refer to the description of the Phase type.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.timeCorrection (type float)

Time correction value. Usually, a value characteristic for the station at which the pick was detected, sometimes also characteristic for the phase type or the slowness. Unit: s

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.azimuth (type float)

Azimuth of station as seen from the epicenter. Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.distance (type float)

Epicentral distance. Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.takeoffAngle (type co:RealQuantity)

Angle of emerging ray at the source, measured against the downward normal direction. Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.timeResidual (type float)

Residual between observed and expected arrival time assuming proper phase identification and given the earthModelID of the Origin, taking into account the timeCorrection. Unit: s

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.horizontalSlownessResidual (type float)

Residual of horizontal slowness and the expected slowness given the current origin (refers to attribute horizontalSlowness of class Pick). Unit: s / deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.backazimuthResidual (type float)

Residual of backazimuth and the backazimuth computed for the current origin (refers to attribute backazimuth of class Pick). Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.timeWeight (type float)

Weight of the arrival time for computation of the associated Origin. Note that the sum of all weights is not required to be unity.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.horizontalSlownessWeight (type float)

Weight of the horizontal slowness for computation of the associated Origin. Note that the sum of all weights is not required to be unity.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.backazimuthWeight (type float)

Weight of the backazimuth for computation of the associated Origin. Note that the sum of all weights is not required to be unity.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.earthModelID (type co:ResourceReference)

Earth model which is used for the association of Arrival to Pick and computation of the residuals.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.creationInfo (type rm:CreationInfo)

see CreationInfo

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Arrival.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin [element]

This class represents the focal time and geographical location of an earthquake hypocenter, as well as additional meta-information. Origin can have objects of type OriginUncertainty and Arrival as child elements.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.publicID (type co:ResourceReference)

Resource identifier of Origin.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.time (type co:TimeQuantity)

Focal time.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.longitude (type co:RealQuantity)

Hypocenter longitude, with respect to the World Geodetic System 1984 (WGS84) reference system (National Imagery and Mapping Agency 2000). Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.latitude (type co:RealQuantity)

Hypocenter latitude, with respect to the WGS84 reference system. Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.depth (type co:RealQuantity)

Depth of hypocenter with respect to the nominal sea level given by the WGS84 geoid (Earth Gravitational Model, EGM96, Lemoine et al. 1998). Positive values indicate hypocenters below sea level. For shallow hypocenters, the depth value can be negative. Note: Other standards use different conventions for depth measurement. As an example, GSE 2.0, defines depth with respect to the local surface. If event data is converted from other formats to QuakeML, depth values may have to be modified accordingly. Unit: m

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.type (type bedt:OriginType)

Describes the Origin type. Allowed values are from OriginType.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.depthType (type bedt:OriginDepthType)

Type of depth determination. Allowed values are from OriginDepthType.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.epicenterFixed (type boolean)

Boolean flag. True if epicenter was kept fixed for computation of Origin.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.timeFixed (type boolean)

Boolean flag. True if focal time was kept fixed for computation of the Origin.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.methodID (type co:ResourceReference)

Identifies the method used for locating the event.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.earthModelID (type co:ResourceReference)

Identifies the earth model used in methodID.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.referenceSystemID (type co:ResourceReference)

Identifies the reference system used for hypocenter determination. This is only necessary if a modified version of the standard (with local extensions) is used that provides a non-standard coordinate system.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.quality (type bedt:OriginQuality)

Additional parameters describing the quality of an Origin determination.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.region (type string)

Can be used to decribe the geographical region of the epicenter location. Useful if an event has multiple origins from different agencies, and these have different region designations. Note that an event-wide region can be defined in the description attribute of an Event object. The user has to take care that this information corresponds to the region attribute of the preferred Origin. String with maximum length of 255 chars.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.evaluationMode (type co:EvaluationMode)

Evaluation mode of Origin. Allowed values are from EvaluationMode.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.evaluationStatus (type co:EvaluationStatus)

Evaluation status of Origin. Allowed values are from EvaluationStatus.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.creationInfo (type rm:CreationInfo)

CreationInfo for the Origin object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.originUncertainty (type bed:OriginUncertainty)

see OriginUncertainty

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.arrival (type bed:Arrival)

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Origin.compositeTime (type bedt:CompositeTime)

Supplementary information on time of rupture start. Complex descriptions of focal times of historic events are possible, see description of the CompositeTime type. Note that even if compositeTime is used, the mandatory time attribute has to be set, too. It has to be set to the single point in time (with uncertainties allowed) that is most characteristic for the event.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick [element]

A pick is the observation of an amplitude anomaly in a seismogram at a specific point in time. It is not necessarily related to a seismic event.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.publicID (type co:ResourceReference)

Resource identifier of Pick.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.time (type co:TimeQuantity)

Observed onset time of signal ("pick time").

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.waveformID (type wf:WaveformStreamID)

Identifes the waveform stream.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.methodID (type co:ResourceReference)

Identifies the picker that produced the pick. This can be either a detection software program or a person.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.filterID (type co:ResourceReference)

Identifies the filter or filter setup used for filtering the waveform stream referenced by waveformID.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.backazimuth (type co:RealQuantity)

Observed backazimuth of the signal. Most relevant in array measurements. Unit: deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.horizontalSlowness (type co:RealQuantity)

Observed horizontal slowness of the signal. Most relevant in array measurements. Unit: s / deg

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.slownessMethodID (type co:ResourceReference)

Identifies the method that was used to determine the slowness.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.onset (type bedt:PickOnset)

Flag that roughly categorizes the sharpness of the onset. Allowed values are from PickOnset.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.phaseHint (type bedt:Phase)

Tentative phase identification as specified by the picker.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.polarity (type bedt:PickPolarity)

Indicates the polarity of first motion, usually from impulsive onsets. Allowed values are from PickPolarity.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.evaluationMode (type co:EvaluationMode)

see EvaluationMode

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.evaluationStatus (type co:EvaluationStatus)

see EvaluationStatus

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.creationInfo (type rm:CreationInfo)

see CreationInfo

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Pick.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event [element]

The class Event describes a seismic event which does not necessarily need to be a tectonic earthquake. An event is usually associated with one or more origins, which contain information about focal time and geographical location of the event. Multiple origins can cover automatic and manual locations, a set of location from different agencies, locations generated with different location programs and earth models, etc. Furthermore, an event is usually associated with one or more magnitudes, and with one or more focal mechanism determinations. In standard (bulletin) QuakeML-BED, Origin, Magnitude, StationMagnitude, and FocalMechanismare child elements of Event. In BED-RT (real-time) all these elements are on the same hierarchy level as child elements of EventParameters. The association of origins, magnitudes, and focal mechanisms to a particular event is expressed using references inside Event.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.publicID (type co:ResourceReference)

Resource identifier of Event.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.preferredOriginID (type co:ResourceReference)

Refers to the publicID of the preferred Origin object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.preferredMagnitudeID (type co:ResourceReference)

Refers to the publicID of the preferred Magnitude object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.preferredFocalMechanismID (type co:ResourceReference)

Refers to the publicID of the preferred FocalMechanism object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.type (type bedt:EventType)

Describes the type of an event (Storchak et al. 2012). Allowed values are from EventType.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.typeCertainty (type bedt:EventTypeCertainty)

Denotes how certain the information on event type is (Storchak et al. 2012). Allowed values are from EventTypeCertainty.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.creationInfo (type rm:CreationInfo)

CreationInfo for the Event object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.focalMechanism (type bed:FocalMechanism)

TODO

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.amplitude (type bed:Amplitude)

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.magnitude (type bed:Magnitude)

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.stationMagnitude (type bed:StationMagnitude)

see StationMagnitude

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.origin (type bed:Origin)

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.pick (type bed:Pick)

see Pick

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.comment (type rm:Comment)

Comment for the Event object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

Event.description (type bedt:EventDescription)

Additional event description, like earthquake name, Flinn-Engdahl region, etc.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

EventParameters [element]

In the bulletin-type (non real-time) model, this class serves as a container for Event objects. In the real-time version, it can hold objects of type Event, Origin, Magnitude, StationMagnitude, FocalMechanism, Reading, Amplitude, and Pick.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

EventParameters.publicID (type co:ResourceReference)

Resource identifier of EventParameters object.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

EventParameters.description (type string)

Description string that can be assigned to the earthquake catalog, or collection of events.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

EventParameters.creationInfo (type rm:CreationInfo)

CreationInfo for the earthquake catalog.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

EventParameters.event (type bed:Event)

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21

EventParameters.comment (type rm:Comment)

Additional comments.

Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21