Size: 61147
Comment:
|
Size: 68080
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 957: | Line 957: |
TODO | 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'''. |
Line 968: | Line 970: |
TODO | Preferred uncertainty description. Allowed values are from [[QuakeML2.0/BasicEventDescriptionTypesDiscussion#class_OriginUncertaintyDescription|OriginUncertaintyDescription]]. |
Line 979: | Line 981: |
TODO | Circular confidence region, given by single value of horizontal uncertainty. Unit: m |
Line 990: | Line 993: |
TODO | Semi-major axis of confidence ellipse. Unit: m |
Line 1001: | Line 1005: |
TODO | Semi-minor axis of confidence ellipse. Unit: m |
Line 1012: | Line 1017: |
TODO | Azimuth of major axis of confidence ellipse. Measured clockwise from South-North direction at epicenter. Unit: deg |
Line 1023: | Line 1030: |
TODO | see [[QuakeML2.0/BasicEventDescriptionTypesDiscussion#class_ConfidenceEllipsoid|ConfidenceEllipsoid]] |
Line 1034: | Line 1041: |
TODO | Confidence level of the uncertainty, given in percent. |
Line 1237: | Line 1244: |
TODO | 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 [[#class_OriginUncertainty|OriginUncertainty]] and [[#class_Arrival|Arrival]] as child elements. |
Line 1248: | Line 1256: |
TODO | Resource identifier of ''Origin''. |
Line 1259: | Line 1267: |
TODO | 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.<<BR>> Example: FabianEuchner, 2014-10-21'' ---- <<Anchor(attribute_Origin.longitude)>> '''Origin.longitude''' (type [[QuakeML2.0/CommonDiscussion#class_RealQuantity|co:RealQuantity]]) Hypocenter longitude, with respect to the World Geodetic System 1984 (WGS84) reference system (National Imagery and Mapping Agency 2000). Unit: deg |
Line 1270: | Line 1291: |
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.<<BR>> Example: FabianEuchner, 2014-10-21'' ---- <<Anchor(attribute_Origin.longitude)>> '''Origin.longitude''' (type [[QuakeML2.0/CommonDiscussion#class_RealQuantity|co:RealQuantity]]) TODO |
Hypocenter latitude, with respect to the WGS84 reference system. Unit: deg |
Line 1292: | Line 1303: |
TODO | 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 |
Line 1303: | Line 1319: |
TODO | Describes the Origin type. Allowed values are from [[QuakeML2.0/BasicEventDescriptionTypesDiscussion#class_OriginType|OriginType]]. |
Line 1314: | Line 1330: |
TODO | Type of depth determination. Allowed values are from [[QuakeML2.0/BasicEventDescriptionTypesDiscussion#class_OriginDepthType|OriginDepthType]]. |
Line 1325: | Line 1341: |
TODO | Boolean flag. True if epicenter was kept fixed for computation of ''Origin''. |
Line 1336: | Line 1352: |
TODO | Boolean flag. True if focal time was kept fixed for computation of the ''Origin''. |
Line 1347: | Line 1363: |
TODO | Identifies the method used for locating the event. |
Line 1358: | Line 1374: |
TODO | Identifies the earth model used in '''methodID'''. |
Line 1369: | Line 1385: |
TODO | 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. |
Line 1380: | Line 1398: |
TODO | Additional parameters describing the quality of an ''Origin'' determination. |
Line 1391: | Line 1409: |
TODO | 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. |
Line 1402: | Line 1424: |
TODO | Evaluation mode of ''Origin''. Allowed values are from [[QuakeML2.0/CommonDiscussion#class_EvaluationMode|EvaluationMode]]. |
Line 1413: | Line 1435: |
TODO | Evaluation status of ''Origin''. Allowed values are from [[QuakeML2.0/CommonDiscussion#class_EvaluationStatus|EvaluationStatus]]. |
Line 1424: | Line 1446: |
TODO | [[QuakeML2.0/ResourceMetadataDiscussion#class_CreationInfo|CreationInfo]] for the ''Origin'' object. |
Line 1436: | Line 1458: |
TODO | see [[#class_OriginUncertainty|OriginUncertainty]] |
Line 1446: | Line 1468: |
TODO | see [[#class_Arrival|Arrival]] |
Line 1456: | Line 1478: |
TODO | Additional comments. |
Line 1466: | Line 1488: |
TODO | 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. |
Line 1656: | Line 1681: |
TODO | 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, [[#class_Origin|Origin]], [[#class_Magnitude|Magnitude]], [[#class_StationMagnitude|StationMagnitude]], and [[#class_FocalMechanism|FocalMechanism]]are child elements of ''Event''. In BED-RT (real-time) all these elements are on the same hierarchy level as child elements of [[#class_EventParameters|EventParameters]]. The association of origins, magnitudes, and focal mechanisms to a particular event is expressed using references inside ''Event''. |
Line 1667: | Line 1700: |
TODO | Resource identifier of ''Event''. |
Line 1678: | Line 1711: |
TODO | Refers to the '''publicID''' of the preferred [[#class_Origin|Origin]] object. |
Line 1689: | Line 1722: |
TODO | Refers to the '''publicID''' of the preferred [[#class_Magnitude|Magnitude]] object. |
Line 1700: | Line 1733: |
TODO | Refers to the '''publicID''' of the preferred [[#class_FocalMechanism|FocalMechanism]] object. |
Line 1711: | Line 1744: |
TODO | Describes the type of an event (Storchak et al. 2012). Allowed values are from [[QuakeML2.0/BasicEventDescriptionTypesDiscussion#class_EventType|EventType]]. |
Line 1722: | Line 1755: |
TODO | Denotes how certain the information on event type is (Storchak et al. 2012). Allowed values are from [[QuakeML2.0/BasicEventDescriptionTypesDiscussion#class_EventTypeCertainty|EventTypeCertainty]]. |
Line 1733: | Line 1767: |
TODO | [[QuakeML2.0/ResorceMetadataDiscussion#class_CreationInfo|CreationInfo]] for the '''Event''' object. |
Line 1755: | Line 1789: |
TODO | see [[QuakeML2.0/BasicEventDescriptionDiscussion#class_Amplitude|Amplitude]] |
Line 1765: | Line 1799: |
TODO | see [[QuakeML2.0/BasicEventDescriptionDiscussion#class_Magnitude|Magnitude]] |
Line 1775: | Line 1809: |
TODO | see [[QuakeML2.0/BasicEventDescriptionDiscussion#class_StationMagnitude|StationMagnitude]] |
Line 1785: | Line 1819: |
TODO | see [[QuakeML2.0/BasicEventDescriptionDiscussion#class_Origin|Origin]] |
Line 1795: | Line 1829: |
TODO | see [[QuakeML2.0/BasicEventDescriptionDiscussion#class_Pick|Pick]] |
Line 1805: | Line 1839: |
TODO | [[QuakeML2.0/ResorceMetadataDiscussion#class_Comment|Comment]] for the '''Event''' object. |
Line 1815: | Line 1849: |
TODO | Additional event description, like earthquake name, Flinn-Engdahl region, etc. |
Line 1827: | Line 1861: |
TODO | In the bulletin-type (non real-time) model, this class serves as a container for [[#class_Event|Event]] objects. In the real-time version, it can hold objects of type [[#class_Event|Event]], [[#class_Origin|Origin]], [[#class_Magnitude|Magnitude]], [[#class_StationMagnitude|StationMagnitude]], [[#class_FocalMechanism|FocalMechanism]], [[#class_Reading|Reading]], [[#class_Amplitude|Amplitude]], and [[#class_Pick|Pick]]. |
Line 1836: | Line 1872: |
'''EventParameters.publicID''' (type [[QuakeML2.0/CommonDiscussion#class_ResourceReference|co:ResourceReference]]) TODO |
'''!EventParameters.publicID''' (type [[QuakeML2.0/CommonDiscussion#class_ResourceReference|co:ResourceReference]]) Resource identifier of ''!EventParameters'' object. |
Line 1847: | Line 1883: |
'''EventParameters.description''' (type string) TODO |
'''!EventParameters.description''' (type string) Description string that can be assigned to the earthquake catalog, or collection of events. |
Line 1858: | Line 1894: |
'''EventParameters.creationInfo''' (type [[QuakeML2.0/ResourceMetadataDiscussion#class_CreationInfo|rm:CreationInfo]]) TODO |
'''!EventParameters.creationInfo''' (type [[QuakeML2.0/ResourceMetadataDiscussion#class_CreationInfo|rm:CreationInfo]]) [[#class_CreationInfo|CreationInfo]] for the earthquake catalog. |
Line 1870: | Line 1906: |
'''EventParameters.event''' (type [[QuakeML2.0/BasicEventDescriptionDiscussion#class_Event|bed:Event]]) TODO |
'''!EventParameters.event''' (type [[QuakeML2.0/BasicEventDescriptionDiscussion#class_Event|bed:Event]]) see [[#class_Event|Event]] |
Line 1880: | Line 1916: |
'''EventParameters.comment''' (type [[QuakeML2.0/ResourceMetadataDiscussion#class_Comment|rm:Comment]]) TODO |
'''!EventParameters.comment''' (type [[QuakeML2.0/ResourceMetadataDiscussion#class_Comment|rm:Comment]]) Additional comments. |
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]
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
MomentTensor.publicID (type co:ResourceReference)
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
MomentTensor.derivedOriginID (type co:ResourceReference)
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
MomentTensor.momentMagnitudeID (type co:ResourceReference)
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
MomentTensor.tensor (type bedt:Tensor)
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
MomentTensor.scalarMoment (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
MomentTensor.variance (type :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
MomentTensor.varianceReduction (type :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
MomentTensor.filterID (type co:ResourceReference)
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
MomentTensor.greensFunctionID (type co:ResourceReference)
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
MomentTensor.methodID (type co:ResourceReference)
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
MomentTensor.category (type bedt:MomentTensorCategory)
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
MomentTensor.clvd (type :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
MomentTensor.doubleCouple (type :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
MomentTensor.inversionType (type bedt:MTInversionType)
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
MomentTensor.iso (type :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
MomentTensor.sourceTimeFunction (type bedt:SourceTimeFunction)
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
MomentTensor.creationInfo (type rm:CreationInfo)
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
MomentTensor.comment (type rm:Comment)
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
MomentTensor.dataUsed (type bedt:DataUsed)
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
FocalMechanism [element]
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
FocalMechanism.publicID (type co:ResourceReference)
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
FocalMechanism.triggeringOriginID (type co:ResourceReference)
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
FocalMechanism.nodalPlanes (type bedt:NodalPlanes)
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
FocalMechanism.principalAxes (type bedt:PrincipalAxes)
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
FocalMechanism.methodID (type co:ResourceReference)
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
FocalMechanism.azimuthalGap (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
FocalMechanism.misfit (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
FocalMechanism.stationDistributionRatio (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
FocalMechanism.stationPolarityCount (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
FocalMechanism.evaluationMode (type co:EvaluationMode)
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
FocalMechanism.evaluationStatus (type co:EvaluationStatus)
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
FocalMechanism.creationInfo (type rm:CreationInfo)
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
FocalMechanism.momentTensor (type bed:MomentTensor)
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
FocalMechanism.comment (type rm:Comment)
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
FocalMechanism.waveformID (type wf:WaveformStreamID)
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
Amplitude [element]
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
Amplitude.publicID (type co:ResourceReference)
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
Amplitude.genericAmplitude (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
Amplitude.type (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
Amplitude.unit (type bedt:AmplitudeUnit)
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
Amplitude.category (type bedt:AmplitudeCategory)
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
Amplitude.period (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
Amplitude.timeWindow (type co:TimeWindow)
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
Amplitude.waveformID (type wf:WaveformStreamID)
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
Amplitude.pickID (type co:ResourceReference)
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
Amplitude.filterID (type co:ResourceReference)
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
Amplitude.methodID (type co:ResourceReference)
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
Amplitude.magnitudeHint (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
Amplitude.scalingTime (type co:TimeQuantity)
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
Amplitude.snr (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
Amplitude.evaluationMode (type co:EvaluationMode)
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
Amplitude.evaluationStatus (type co:EvaluationStatus)
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
Amplitude.creationInfo (type rm:CreationInfo)
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
Amplitude.comment (type rm:Comment)
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
StationMagnitudeContribution [element]
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
StationMagnitudeContribution.stationMagnitudeID (type co:ResourceReference)
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
StationMagnitudeContribution.residual (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
StationMagnitudeContribution.weight (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
Magnitude [element]
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
Magnitude.publicID (type co:ResourceReference)
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
Magnitude.mag (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
Magnitude.type (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
Magnitude.originID (type co:ResourceReference)
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
Magnitude.methodID (type co:ResourceReference)
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
Magnitude.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
Magnitude.azimuthalGap (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
Magnitude.evaluationMode (type co:EvaluationMode)
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
Magnitude.evaluationStatus (type co:EvaluationStatus)
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
Magnitude.creationInfo (type rm:CreationInfo)
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
Magnitude.stationMagnitudeContribution (type bed:StationMagnitudeContribution)
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
Magnitude.comment (type rm:Comment)
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
StationMagnitude [element]
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
StationMagnitude.publicID (type co:ResourceReference)
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
StationMagnitude.originID (type co:ResourceReference)
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
StationMagnitude.mag (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
StationMagnitude.type (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
StationMagnitude.amplitudeID (type co:ResourceReference)
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
StationMagnitude.methodID (type co:ResourceReference)
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
StationMagnitude.waveformID (type wf:WaveformStreamID)
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
StationMagnitude.creationInfo (type rm:CreationInfo)
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
StationMagnitude.comment (type rm:Comment)
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
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)
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]
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
Arrival.publicID (type co:ResourceReference)
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
Arrival.pickID (type co:ResourceReference)
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
Arrival.phase (type bedt:Phase)
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
Arrival.timeCorrection (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
Arrival.azimuth (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
Arrival.distance (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
Arrival.takeoffAngle (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
Arrival.timeResidual (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
Arrival.horizontalSlownessResidual (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
Arrival.backazimuthResidual (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
Arrival.timeWeight (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
Arrival.horizontalSlownessWeight (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
Arrival.backazimuthWeight (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
Arrival.earthModelID (type co:ResourceReference)
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
Arrival.creationInfo (type rm:CreationInfo)
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
Arrival.comment (type rm:Comment)
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
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)
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)
see 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]
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
Pick.publicID (type co:ResourceReference)
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
Pick.time (type co:TimeQuantity)
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
Pick.waveformID (type wf:WaveformStreamID)
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
Pick.methodID (type co:ResourceReference)
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
Pick.filterID (type co:ResourceReference)
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
Pick.backazimuth (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
Pick.horizontalSlowness (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
Pick.slownessMethodID (type co:ResourceReference)
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
Pick.onset (type bedt:PickOnset)
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
Pick.phaseHint (type bedt:Phase)
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
Pick.polarity (type bedt:PickPolarity)
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
Pick.evaluationMode (type co:EvaluationMode)
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
Pick.evaluationStatus (type co:EvaluationStatus)
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
Pick.creationInfo (type rm:CreationInfo)
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
Pick.comment (type rm:Comment)
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 [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)
see 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)
see 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)
see 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)
see 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