Locked History Actions

Diff for "QuakeML2.0/BasicEventDescriptionTypesDiscussion"

Differences between revisions 2 and 10 (spanning 8 versions)
Revision 2 as of 2014-10-30 14:38:26
Size: 37422
Comment:
Revision 10 as of 2015-06-24 13:15:48
Size: 43064
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
[[QuakeML2.0/MarsquakeDiscussion|Marsquake]] |
Line 165: Line 164:
TODO Focal times differ significantly in their precision. While focal times of instrumentally located earthquakes are
estimated precisely down to seconds, historic events have only incomplete time descriptions. Sometimes, even
contradictory information about the rupture time exist. The !CompositeTime type allows for such complex
descriptions. If the specification is given with no greater accuracy than days (i.e., no time components are
given), the date refers to local time. However, if time components are given, they have to refer to UTC.
As an example, consider a historic earthquake in California, e.g., on 28 February 1730, with no time information
given. Expressed in UTC, this day extends from 1730-02-28T08:00:00Z until 1730-03-01T08:00:00Z. Such a
specification would be against intuition. Therefore, for date-time specifications without time components, local
time is used. In the example, the !CompositeTime attributes are simply year 1730, month 2, and day 28. In
the corresponding time attribute of the origin, however, UTC has to be used. If the unknown time components
are assumed to be zero, the value is 1730-02-28T08:00:00Z.
Line 174: Line 183:
'''CompositeTime.year''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

TODO
'''!CompositeTime.year''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

Year or range of years of the event’s focal time.
Line 185: Line 194:
'''CompositeTime.month''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

TODO
'''!CompositeTime.month''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

Month or range of months of the event’s focal time.
Line 196: Line 205:
'''CompositeTime.day''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

TODO
'''!CompositeTime.day''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

Day or range of days of the event’s focal time.
Line 207: Line 216:
'''CompositeTime.hour''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

TODO
'''!CompositeTime.hour''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

Hour or range of hours of the event’s focal time.
Line 218: Line 227:
'''CompositeTime.minute''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

TODO
'''!CompositeTime.minute''' (type [[QuakeML2.0/CommonDiscussion#class_IntegerQuantity|co:IntegerQuantity]])

Minute or range of minutes of the event’s focal time.
Line 229: Line 238:
'''CompositeTime.second''' (type [[QuakeML2.0/CommonDiscussion#class_RealQuantity|co:RealQuantity]])

TODO
'''!CompositeTime.second''' (type [[QuakeML2.0/CommonDiscussion#class_RealQuantity|co:RealQuantity]])

Second and fraction of seconds or range of seconds with fraction of the event’s focal time.
Line 240: Line 249:
'''CompositeTime.calendar''' (type string) '''!CompositeTime.calendar''' (type string)
Line 372: Line 381:
TODO This type contains various attributes commonly used to describe the quality of an origin, e. g., errors, azimuthal
coverage, etc. Origin objects have an optional attribute of the type !OriginQuality.
Line 381: Line 391:
'''OriginQuality.associatedPhaseCount''' (type int)

TODO
'''!OriginQuality.associatedPhaseCount''' (type int)

Number of associated phases, regardless of their use for origin computation.
Line 392: Line 402:
'''OriginQuality.usedPhaseCount''' (type int)

TODO
'''!OriginQuality.usedPhaseCount''' (type int)

Number of defining phases, i. e., phase observations that were actually used for computing
the origin. Note that there may be more than one defining phase per station.
Line 403: Line 414:
'''OriginQuality.associatedStationCount''' (type int)

TODO
'''!OriginQuality.associatedStationCount''' (type int)

Number of stations at which the event was observed.
Line 414: Line 425:
'''OriginQuality.usedStationCount''' (type int)

TODO
'''!OriginQuality.usedStationCount''' (type int)

Number of stations from which data was used for origin computation.
Line 425: Line 436:
'''OriginQuality.depthPhaseCount''' (type int)

TODO
'''!OriginQuality.depthPhaseCount''' (type int)

Number of depth phases (typically pP, sometimes sP) used in depth computation.
Line 436: Line 447:
'''OriginQuality.standardError''' (type float)

TODO
'''!OriginQuality.standardError''' (type float)

RMS of the travel time residuals of the arrivals used for the origin computation.
Unit: s
Line 447: Line 459:
'''OriginQuality.azimuthalGap''' (type float)

TODO
'''!OriginQuality.azimuthalGap''' (type float)

Largest azimuthal gap in station distribution as seen from epicenter. For an illustration of
azimuthal gap and secondary azimuthal gap (see below), see Fig. 5 of Bond´ar et al. (2004).
Unit: deg
Line 458: Line 472:
'''OriginQuality.secondaryAzimuthalGap''' (type float)

TODO
'''!OriginQuality.secondaryAzimuthalGap''' (type float)

Secondary azimuthal gap in station distribution, i. e., the largest azimuthal gap a
station closes.
Unit: deg
Line 469: Line 485:
'''OriginQuality.groundTruthLevel''' (type string)

TODO
'''!OriginQuality.groundTruthLevel''' (type string)

String describing ground-truth level, e. g. GT0, GT5, etc. It has a maximum length of 32
characters.
Line 480: Line 497:
'''OriginQuality.maximumDistance''' (type float)

TODO
'''!OriginQuality.maximumDistance''' (type float)

Epicentral distance of station farthest from the epicenter.
Unit: deg
Line 491: Line 509:
'''OriginQuality.minimumDistance''' (type float)

TODO
'''!OriginQuality.minimumDistance''' (type float)

Epicentral distance of station closest to the epicenter.
Unit: deg
Line 502: Line 521:
'''OriginQuality.medianDistance''' (type float)

TODO
'''!OriginQuality.medianDistance''' (type float)

Median epicentral distance of used stations.
Unit: deg
Line 518: Line 538:
TODO Generic and extensible phase description that currently contains the phase code only.
Line 529: Line 549:
TODO Phase code as given in the IASPEI Standard Seismic Phase List (Storchak et al. 2003). String with a
maximum length of 32 characters.
Line 670: Line 691:
TODO This class represents a description of the location uncertainty as a confidence ellipsoid with arbitrary orientation
in space. The orientation of a rigid body in three-dimensional Euclidean space can be described by three
parameters. We use the convention of Euler angles, which can be interpreted as a composition of three
elemental rotations (i.e., rotations around a single axis). In the special case of Euler angles we use here, the
angles are referred to as Tait-Bryan (or Cardan) angles. These angles may be familiar to the reader from their
application in flight dynamics, and are referred to as heading (yaw, \psi), elevation (attitude, pitch, \phi), and
bank (roll, \theta). For a definition of the angles, see the follwing figure (Tait-Bryan).

[[https://en.wikipedia.org/wiki/Euler_angles#/media/File:Taitbrianangles.svg|Tait-Bryan angles]]

Through the three elemental rotations, a Cartesian
system (x, y, z) centered at the epicenter, with the South-North direction x, the West-East direction y, and
the downward vertical direction z, is transferred into a different Cartesian system (X, Y , Z) centered on the
confidence ellipsoid. Here, X denotes the direction of the major axis, and Y denotes the direction of the minor
axis of the ellipsoid. Note that Figure (Tait-Bryan) can be interpreted as a hypothetical view from the interior of the Earth
to the inner face of a shell representing Earth’s surface.
The three Tait-Bryan rotations are performed as follows: (i) a rotation about the Z axis with angle \psi (heading,
or azimuth); (ii) a rotation about the Y axis with angle \phi (elevation, or plunge); and (iii) a rotation about the
X axis with angle \theta (bank). Note that in the case of Tait-Bryan angles, the rotations are performed about the
ellipsoid’s axes, not about the axes of the fixed (x, y, z) Cartesian system.

'''majorAxisPlunge''' corresponds to elevation (\phi), '''majorAxisAximuth''' corresponds to heading (\psi), and '''majorAxisRotation''' corresponds to bank (\theta).
Line 681: Line 723:
TODO Largest uncertainty, corresponding to the semi-major axis of the confidence ellipsoid.
Unit: m
Line 692: Line 735:
TODO Smallest uncertainty, corresponding to the semi-minor axis of the confidence ellipsoid.
Unit: m
Line 703: Line 747:
TODO Uncertainty in direction orthogonal to major and minor axes of the confidence
ellipsoid.
Unit: m
Line 714: Line 760:
TODO Plunge angle of major axis of confidence ellipsoid. Corresponds to Tait-Bryan angle \phi.
Unit: deg
Line 725: Line 772:
TODO Azimuth angle of major axis of confidence ellipsoid. Corresponds to Tait-Bryan angle \psi.
Unit: deg
Line 736: Line 784:
TODO This angle describes a rotation about the confidence ellipsoid’s major axis which is required
to define the direction of the ellipsoid’s minor axis. Corresponds to Tait-Bryan angle \theta.
Unit: deg

Discussion on package BasicEventDescriptionTypes

Quick navigation: go to package

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

In current package (BasicEventDescriptionTypes): go to class

SourceTimeFunction | NodalPlanes | CompositeTime | DataUsed | Axis | OriginQuality | Phase | Tensor | PrincipalAxes | ConfidenceEllipsoid | EventDescription | MTInversionType | AmplitudeUnit | MomentTensorCategory | AmplitudeCategory | OriginUncertaintyDescription | DataUsedWaveType | PickPolarity | OriginType | OriginDepthType | EventTypeCertainty | EventType | PickOnset | SourceTimeFunctionType | EventDescriptionType |


BasicEventDescriptionTypes overview page

(!) BasicEventDescriptionTypes class diagram


SourceTimeFunction [type]

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


SourceTimeFunction.decayTime (type float)

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


SourceTimeFunction.duration (type float)

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


SourceTimeFunction.riseTime (type float)

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


SourceTimeFunction.type (type bedt:SourceTimeFunctionType)

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


top of page


NodalPlanes [type]

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


NodalPlanes.nodalPlane1 (type bedt:NodalPlane)

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


NodalPlanes.nodalPlane2 (type bedt:NodalPlane)

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


NodalPlanes.preferredPlane (type int)

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


top of page


CompositeTime [type]

Focal times differ significantly in their precision. While focal times of instrumentally located earthquakes are estimated precisely down to seconds, historic events have only incomplete time descriptions. Sometimes, even contradictory information about the rupture time exist. The CompositeTime type allows for such complex descriptions. If the specification is given with no greater accuracy than days (i.e., no time components are given), the date refers to local time. However, if time components are given, they have to refer to UTC. As an example, consider a historic earthquake in California, e.g., on 28 February 1730, with no time information given. Expressed in UTC, this day extends from 1730-02-28T08:00:00Z until 1730-03-01T08:00:00Z. Such a specification would be against intuition. Therefore, for date-time specifications without time components, local time is used. In the example, the CompositeTime attributes are simply year 1730, month 2, and day 28. In the corresponding time attribute of the origin, however, UTC has to be used. If the unknown time components are assumed to be zero, the value is 1730-02-28T08:00:00Z.


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


CompositeTime.year (type co:IntegerQuantity)

Year or range of years of the event’s 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


CompositeTime.month (type co:IntegerQuantity)

Month or range of months of the event’s 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


CompositeTime.day (type co:IntegerQuantity)

Day or range of days of the event’s 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


CompositeTime.hour (type co:IntegerQuantity)

Hour or range of hours of the event’s 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


CompositeTime.minute (type co:IntegerQuantity)

Minute or range of minutes of the event’s 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


CompositeTime.second (type co:RealQuantity)

Second and fraction of seconds or range of seconds with fraction of the event’s 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


CompositeTime.calendar (type string)

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


top of page


DataUsed [type]

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


DataUsed.componentCount (type int)

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


DataUsed.longestPeriod (type float)

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


DataUsed.shortestPeriod (type float)

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


DataUsed.stationCount (type int)

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


DataUsed.waveType (type bedt:DataUsedWaveType)

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


top of page


Axis [type]

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


Axis.azimuth (type co:RealQuantity)

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


Axis.plunge (type co:RealQuantity)

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


Axis.length (type co:RealQuantity)

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


top of page


OriginQuality [type]

This type contains various attributes commonly used to describe the quality of an origin, e. g., errors, azimuthal coverage, etc. Origin objects have an optional attribute of the type OriginQuality.


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


OriginQuality.associatedPhaseCount (type int)

Number of associated phases, regardless of their use for origin 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


OriginQuality.usedPhaseCount (type int)

Number of defining phases, i. e., phase observations that were actually used for computing the origin. Note that there may be more than one defining phase per station.


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


OriginQuality.associatedStationCount (type int)

Number of stations at which the event was observed.


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


OriginQuality.usedStationCount (type int)

Number of stations from which data was used for origin 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


OriginQuality.depthPhaseCount (type int)

Number of depth phases (typically pP, sometimes sP) used in depth 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


OriginQuality.standardError (type float)

RMS of the travel time residuals of the arrivals used for the origin computation. 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


OriginQuality.azimuthalGap (type float)

Largest azimuthal gap in station distribution as seen from epicenter. For an illustration of azimuthal gap and secondary azimuthal gap (see below), see Fig. 5 of Bond´ar et al. (2004). 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


OriginQuality.secondaryAzimuthalGap (type float)

Secondary azimuthal gap in station distribution, i. e., the largest azimuthal gap a station closes. 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


OriginQuality.groundTruthLevel (type string)

String describing ground-truth level, e. g. GT0, GT5, etc. 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


OriginQuality.maximumDistance (type float)

Epicentral distance of station farthest 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


OriginQuality.minimumDistance (type float)

Epicentral distance of station closest to 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


OriginQuality.medianDistance (type float)

Median epicentral distance of used stations. 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


top of page


Phase [type]

Generic and extensible phase description that currently contains the phase code only.


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


Phase.code (type string)

Phase code as given in the IASPEI Standard Seismic Phase List (Storchak et al. 2003). String 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


top of page


Tensor [type]

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


Tensor.Mrr (type co:RealQuantity)

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


Tensor.Mtt (type co:RealQuantity)

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


Tensor.Mpp (type co:RealQuantity)

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


Tensor.Mrt (type co:RealQuantity)

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


Tensor.Mrp (type co:RealQuantity)

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


Tensor.Mtp (type co:RealQuantity)

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


top of page


PrincipalAxes [type]

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


PrincipalAxes.tAxis (type bedt:Axis)

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


PrincipalAxes.pAxis (type bedt:Axis)

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


PrincipalAxes.nAxis (type bedt:Axis)

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


top of page


ConfidenceEllipsoid [type]

This class represents a description of the location uncertainty as a confidence ellipsoid with arbitrary orientation in space. The orientation of a rigid body in three-dimensional Euclidean space can be described by three parameters. We use the convention of Euler angles, which can be interpreted as a composition of three elemental rotations (i.e., rotations around a single axis). In the special case of Euler angles we use here, the angles are referred to as Tait-Bryan (or Cardan) angles. These angles may be familiar to the reader from their application in flight dynamics, and are referred to as heading (yaw, \psi), elevation (attitude, pitch, \phi), and bank (roll, \theta). For a definition of the angles, see the follwing figure (Tait-Bryan).

Tait-Bryan angles

Through the three elemental rotations, a Cartesian system (x, y, z) centered at the epicenter, with the South-North direction x, the West-East direction y, and the downward vertical direction z, is transferred into a different Cartesian system (X, Y , Z) centered on the confidence ellipsoid. Here, X denotes the direction of the major axis, and Y denotes the direction of the minor axis of the ellipsoid. Note that Figure (Tait-Bryan) can be interpreted as a hypothetical view from the interior of the Earth to the inner face of a shell representing Earth’s surface. The three Tait-Bryan rotations are performed as follows: (i) a rotation about the Z axis with angle \psi (heading, or azimuth); (ii) a rotation about the Y axis with angle \phi (elevation, or plunge); and (iii) a rotation about the X axis with angle \theta (bank). Note that in the case of Tait-Bryan angles, the rotations are performed about the ellipsoid’s axes, not about the axes of the fixed (x, y, z) Cartesian system.

majorAxisPlunge corresponds to elevation (\phi), majorAxisAximuth corresponds to heading (\psi), and majorAxisRotation corresponds to bank (\theta).


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


ConfidenceEllipsoid.semiMajorAxisLength (type float)

Largest uncertainty, corresponding to the semi-major axis of the confidence ellipsoid. 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


ConfidenceEllipsoid.semiMinorAxisLength (type float)

Smallest uncertainty, corresponding to the semi-minor axis of the confidence ellipsoid. 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


ConfidenceEllipsoid.semiIntermediateAxisLength (type float)

Uncertainty in direction orthogonal to major and minor axes of the confidence ellipsoid. 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


ConfidenceEllipsoid.majorAxisPlunge (type float)

Plunge angle of major axis of confidence ellipsoid. Corresponds to Tait-Bryan angle \phi. 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


ConfidenceEllipsoid.majorAxisAzimuth (type float)

Azimuth angle of major axis of confidence ellipsoid. Corresponds to Tait-Bryan angle \psi. 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


ConfidenceEllipsoid.majorAxisRotation (type float)

This angle describes a rotation about the confidence ellipsoid’s major axis which is required to define the direction of the ellipsoid’s minor axis. Corresponds to Tait-Bryan angle \theta. 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


top of page


EventDescription [type]

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


EventDescription.text (type string)

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


EventDescription.type (type bedt:EventDescriptionType)

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


top of page


MTInversionType [enumeration]

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



AmplitudeUnit [enumeration]

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



MomentTensorCategory [enumeration]

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



AmplitudeCategory [enumeration]

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



OriginUncertaintyDescription [enumeration]

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



DataUsedWaveType [enumeration]

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



PickPolarity [enumeration]

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



OriginType [enumeration]

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



OriginDepthType [enumeration]

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



EventTypeCertainty [enumeration]

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



EventType [enumeration]

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



PickOnset [enumeration]

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



SourceTimeFunctionType [enumeration]

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



EventDescriptionType [enumeration]

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


top of page