Locked History Actions

Diff for "QuakeML2.0/StrongMotionDiscussion"

Differences between revisions 15 and 28 (spanning 13 versions)
Revision 15 as of 2014-10-30 09:22:18
Size: 24175
Comment:
Revision 28 as of 2015-07-23 06:57:59
Size: 30649
Editor: kaestli
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
[[QuakeML2.0/MarsquakeDiscussion|Marsquake]] |
Line 38: Line 37:
Line 40: Line 38:
== SurfaceRupture ==

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''

== SurfaceRupture [type] ==

Some hints (flag, text, reference) on whether an event reportedly produced surface rupture.

----
''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''
Line 53: Line 53:
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''
If this flag is used, it is recommended to provide either text or literature evidence.

----
''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''

Note that although maybe given in text or literature, there is no parametric representation of uncertainty.<<BR>>
PhilippKästli, 2015-06-30
Line 64: Line 68:
TODO What evidence supports the presence of surface rupture? (This field allows for amplification-specific classification, however no classification is currently enforced.)
Line 75: Line 79:
TODO Bibliographic information on the most relevant paper supporting the statement made in '''SurfaceRupture.evidence'''
Line 83: Line 87:


Line 88: Line 89:
Line 90: Line 90:
== Rupture ==

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''

== Rupture [element] ==

Description of some boundary parameters of the the actually experienced slip process. This is kept separate from the concept of 'fault' (as a geological feature supposed (or: observed) to be capable to host rupture processes.

----
''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''

While the peak motion part of the schema is actively used, and thus got relevant peer review, the rupture description has been specified in the framework of the NERA project, however, afaik, it is not actively used. I am not sure whether it is adequate to host a detailed rupture description (referring to the EQ source process, corresponding models, in-situ observation and complex analysis results) in the same schema as the non-time-dynamic instrumental peak motion observations. Time line and audience could be too different<<BR>>
PhilippKästli, 2015-06-30
Line 103: Line 108:
TODO Globally unique identifier.
Line 114: Line 119:
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''
Reference to the fault on which the rupture happened. Note that while geometry is different, it is currently implied that rupture happenes on a single fault, or a subset of it.

----
''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''

With a future, more elaborate fault description (including potentially capabilities to describe distinct fault sections, and coherent faults), this linking is subject to change.<<BR>>

PhilippKästli, 2015-06-30
Line 125: Line 134:
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''
Maximum relative displacement on the fault plain.

----
''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''

Maybe we need also a mean displacement?<<BR>>
PhilippKästli, 2015-06-30
Line 136: Line 148:
TODO rupture area in [m^2]
Line 147: Line 159:
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''
Length of the rupture area in the direction of its largest extent, measured on the rupture plain and given in [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.<<BR>>
Example: FabianEuchner, 2014-10-21''

Is it relevant to distinguish between the longest extension and the longest horizontal extension? (in large quakes, horizontal orientation of the largest linear extent is typically implied)<<BR>>
PhilippKästli, 2015-06-30
Line 158: Line 173:
TODO Largest extension of the rupture area perpendicular to the line of its largest extent (measured on the rupture plain and given in [m])
Line 169: Line 184:
TODO Moment release on the part of the rupture area not deeper than 5 km below surface, in [N*m]
Line 180: Line 195:
TODO Duration of the coherent rupture process, in [s]
Line 191: Line 206:
TODO description of the geometry of the rupture "plain" in Well Known Text format (https://en.wikipedia.org/wiki/Well-known_text) - types polygon or multipolygon recommended; in addition curvepolygon and circularstring are possible.
Line 201: Line 216:

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''
.
mean rupture velocity in [m/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.<<BR>>
Example: FabianEuchner, 2014-10-21''

Question to the NERA community: The differentiation between SlipVelocity and RuptureVelocity is not clear to me.<<BR>>
PhilippKästli, 2015-06-30
Line 213: Line 231:
TODO Presence of one or more shallow asperities within the top 5 km below surface
Line 224: Line 242:
TODO Depth of the shallowest relevant asperity, in [m]
Line 235: Line 253:
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''
mean slip velocity, in [m/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.<<BR>>
Example: FabianEuchner, 2014-10-21''

Question to the NERA community: The differentiation between SlipVelocity and RuptureVelocity is not clear to me.<<BR>>
PhilippKästli, 2015-06-30
Line 246: Line 268:
TODO in [Pa]
Line 257: Line 279:
TODO
cfr. type definition of surface rupture
Line 268: Line 289:
TODO phase velocity divided by shearwave velocity of the ruptured medium
Line 284: Line 305:


This is probably an error: The Footwall/HangingWall indicator (indicating the relationship between backazimuth and rupture orientation) should be a property of the StrongMotionRecord, not of the rupture.<<BR>>
CarloCauzzi / PhilippKästli 2015-07-23

Line 289: Line 316:
'''Rupture.referredStudy''' (type [[QuakeML2.0/HydraulicDiscussion#class_LiteratureSource|LiteratureSource]])

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''
----


'''Rupture.referredStudy''' (type [[QuakeML2.0/ResourceMetadataDiscussion#class_LiteratureSource|rm:LiteratureSource]])

Relevant literature source for this rupture parametrization.

----
''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''
----
Line 302: Line 326:
Line 304: Line 327:
== OriginRecordReference ==

TODO

== OriginRecordReference [element] ==

Link between an origin and a waveform record. Note that one waveform record may be linked to multiple concurrencing origins (location results) of the same event, resulting in different distance metrics.
Line 317: Line 341:
TODO Globally unique identifier of the waveform record (reference, foreign key)
Line 328: Line 352:
TODO Shortest distance between recording station and rupture surface, in [m]
Line 339: Line 363:
TODO Shortest distance from the recording site to the seismogenic portion of the ruptured area (Campbell, 1997).
Line 350: Line 374:
TODO Shortest distance from a site to the surface projection of the rupture surface, in [m]
Line 361: Line 385:
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''
(Smallest) angle between the vector of the main rupture direction, and the line from hypocenter to the recording station; in [degrees].

----
''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''

"Line from Hypocenter to recording station": Direct connection or fastest wave path?<<BR>>
PhilippKaestli, 2015-07-21
Line 372: Line 400:
TODO Closest distance between the station and the ruptured area on the fault plane; in [meters]
Line 383: Line 411:
TODO Length of the pre-event window of the waveform data provided in the referenced record, assuming the origin time of the referring origin. In [seconds]
Line 394: Line 422:
TODO minimum length after last exceeding a shaking threshold at a given station, typically a parameter of triggered sm instrumentation;
Line 402: Line 430:


Line 407: Line 432:
Line 409: Line 433:
== OriginDescription ==

TODO

== OriginDescription [element] ==

Conceptually an extension of a BasicEventDescription.origin for some elements/attributes of relevance (by now, the number of strong motion traces available, and the rupture description.
Line 422: Line 447:
TODO Unique identifier of the OriginDescription instance.
Line 433: Line 458:
TODO Public Identifier referring to the (BasicEventDescription) origin which is extended here.
Line 444: Line 469:
TODO number of waveforms (datasets from individual streams) available for, and linked to this event.
Line 455: Line 480:
TODO Data provenance
Line 465: Line 490:
'''OriginDescription.rupture''' (type [[QuakeML2.0/HydraulicDiscussion#class_Rupture|Rupture]])

TODO
'''OriginDescription.rupture''' (type [[QuakeML2.0/StrongMotionDiscussion#class_Rupture|sm:Rupture]])

see [[QuakeML2.0/StrongMotionDiscussion#class_Rupture|sm:Rupture]].
Line 475: Line 500:
'''OriginDescription.originRecordReference''' (type [[QuakeML2.0/HydraulicDiscussion#class_OriginRecordReference|OriginRecordReference]])

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''
----


'''OriginDescription.originRecordReference''' (type [[QuakeML2.0/StrongMotionDiscussion#class_OriginRecordReference|sm:OriginRecordReference]])

Reference element to describe the many:many relationship between traces from different stations/streams, and one or multiple concurrencing origins derive from them.

----
''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''
----
Line 488: Line 510:
Line 490: Line 511:
== StrongMotionRecord ==

TODO

== StrongMotionRecord [element] ==

Description of a (processed) waveform file representing the recorded motion snipplet from one data channel for one seismic event.
Line 503: Line 525:
TODO Globally unique, public identifier of the waveform (URI).
Line 514: Line 536:
TODO Time of the first recorded sample (typically without uncertainty)
Line 525: Line 547:
TODO Duration of the recording; in [seconds]
Line 536: Line 558:
TODO Reference to the registration parameters of the recording channel: network, station, sensorlocation, 3-letter-channel indicator, plus a data field for a non-structured unique identifier
Line 547: Line 569:
TODO Public identifier as a reference (foreign key) to a filter chain object ( see [[QuakeML2.0/FilterDiscussion#class_FilterChain|wf:FilterChain]]
Line 558: Line 580:
TODO File resource pointer (with metadata) for the (binary or ascii) waveform data.
Line 569: Line 591:
TODO ground motion unit the trace represents after applying the gain, expressed in an expression of SI base units (e.g. "m/s", "m/s**2")
Line 580: Line 602:
TODO Denominator of the fraction representing the number of samples per second.
Line 591: Line 613:
TODO Numerator of the fraction representing the number of samples per second.

The concept of expressing a natural floating point value is similar to the sampling rate as represented in GFZ's inventory XML or FDSN's stationXML (SampleRateRatio)
Line 602: Line 626:
TODO Contact information of the data owner (as this includes also intellectual property on the reprocessing procedure, it may be different from the station owner.)
Line 613: Line 637:
TODO Creation metadata of the trace/waveform file.
Line 623: Line 647:
'''StrongMotionRecord.peakMotion''' (type [[QuakeML2.0/HydraulicDiscussion#class_PeakMotion|PeakMotion]])

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''
----


'''StrongMotionRecord.peakMotion''' (type [[QuakeML2.0/WaveformDiscussion#class_PeakMotion|wf:PeakMotion]])

individual peak motion value. Different peak motion values derived from the same waveform file may refer to different metrices (velocity, acceleration, duration...), and/or different processing methods

----
''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''
----
Line 636: Line 657:
Line 638: Line 658:
== StrongMotionParameters ==

TODO

== StrongMotionParameters [element] ==

Top level element of this QuakeML package
Line 651: Line 672:
TODO unique identificator of the QuakeML/StrongMotionParameters document
Line 662: Line 683:
TODO Free text description of the document
Line 673: Line 694:
Data provenance of the document

----
''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_StrongMotionParameters.originDescription)>>
'''StrongMotionParameters.originDescription''' (type [[QuakeML2.0/StrongMotionDiscussion#class_OriginDescription|sm:OriginDescription]])

(see respective type 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.<<BR>>
Example: FabianEuchner, 2014-10-21''
----

<<Anchor(attribute_StrongMotionParameters.strongMotionRecord)>>
'''StrongMotionParameters.strongMotionRecord''' (type [[QuakeML2.0/StrongMotionDiscussion#class_StrongMotionRecord|sm:StrongMotionRecord]])

(see respective type 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.<<BR>>
Example: FabianEuchner, 2014-10-21''
----

<<Anchor(attribute_StrongMotionParameters.comment)>>
'''StrongMotionParameters.comment''' (type [[QuakeML2.0/ResourceMetadataDiscussion#class_Comment|rm:Comment]])

Comment on a StrongmotionDescription document.

----
''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''
----
[[#page_top|top of page]]


--------

<<Anchor(class_FootwallHangingwallIndicator)>>
== FootwallHangingwallIndicator [enumeration] ==
Line 678: Line 745:
----

    

<<Anchor(attribute_StrongMotionParameters.originDescription)>>
'''StrongMotionParameters.originDescription''' (type [[QuakeML2.0/HydraulicDiscussion#class_OriginDescription|OriginDescription]])

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_StrongMotionParameters.strongMotionRecord)>>
'''StrongMotionParameters.strongMotionRecord''' (type [[QuakeML2.0/HydraulicDiscussion#class_StrongMotionRecord|StrongMotionRecord]])

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_StrongMotionParameters.comment)>>
'''StrongMotionParameters.comment''' (type [[QuakeML2.0/HydraulicDiscussion#class_Comment|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.<<BR>>
Example: FabianEuchner, 2014-10-21''
----



[[#page_top|top of page]]
--------

<<Anchor(class_StrongMotion)>>
== StrongMotion ==

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_StrongMotion.strongmotionparameters)>>
'''StrongMotion.strongmotionparameters''' (type [[QuakeML2.0/HydraulicDiscussion#class_StrongMotionParameters|StrongMotionParameters]])

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''
----



[[#page_top|top of page]]


--------

<<Anchor(class_FootwallHangingwallIndicator)>>
== FootwallHangingwallIndicator ==


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''
Line 759: Line 750:

Discussion on package StrongMotion

Quick navigation: go to package

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

In current package (StrongMotion): go to class

SurfaceRupture | Rupture | OriginRecordReference | OriginDescription | StrongMotionRecord | StrongMotionParameters | FootwallHangingwallIndicator |


StrongMotion overview page

(!) StrongMotion class diagram


SurfaceRupture [type]

Some hints (flag, text, reference) on whether an event reportedly produced surface rupture.


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


SurfaceRupture.observed (type boolean)

If this flag is used, it is recommended to provide either text or literature evidence.


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

Note that although maybe given in text or literature, there is no parametric representation of uncertainty.
PhilippKästli, 2015-06-30


SurfaceRupture.evidence (type string)

What evidence supports the presence of surface rupture? (This field allows for amplification-specific classification, however no classification is currently enforced.)


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


SurfaceRupture.literatureSource (type rm:LiteratureSource)

Bibliographic information on the most relevant paper supporting the statement made in SurfaceRupture.evidence


Discussion area: please fill in 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


Rupture [element]

Description of some boundary parameters of the the actually experienced slip process. This is kept separate from the concept of 'fault' (as a geological feature supposed (or: observed) to be capable to host rupture processes.


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

While the peak motion part of the schema is actively used, and thus got relevant peer review, the rupture description has been specified in the framework of the NERA project, however, afaik, it is not actively used. I am not sure whether it is adequate to host a detailed rupture description (referring to the EQ source process, corresponding models, in-situ observation and complex analysis results) in the same schema as the non-time-dynamic instrumental peak motion observations. Time line and audience could be too different
PhilippKästli, 2015-06-30


Rupture.publicID (type co:ResourceReference)

Globally unique identifier.


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


Rupture.faultID (type co:ResourceReference)

Reference to the fault on which the rupture happened. Note that while geometry is different, it is currently implied that rupture happenes on a single fault, or a subset of it.


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

With a future, more elaborate fault description (including potentially capabilities to describe distinct fault sections, and coherent faults), this linking is subject to change.

PhilippKästli, 2015-06-30


Rupture.displacement (type co:RealQuantity)

Maximum relative displacement on the fault plain.


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

Maybe we need also a mean displacement?
PhilippKästli, 2015-06-30


Rupture.area (type co:RealQuantity)

rupture area in [m^2]


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


Rupture.length (type co:RealQuantity)

Length of the rupture area in the direction of its largest extent, measured on the rupture plain and given in [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

Is it relevant to distinguish between the longest extension and the longest horizontal extension? (in large quakes, horizontal orientation of the largest linear extent is typically implied)
PhilippKästli, 2015-06-30


Rupture.width (type co:RealQuantity)

Largest extension of the rupture area perpendicular to the line of its largest extent (measured on the rupture plain and given in [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


Rupture.momentReleaseTop5km (type co:RealQuantity)

Moment release on the part of the rupture area not deeper than 5 km below surface, in [N*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


Rupture.riseTime (type co:RealQuantity)

Duration of the coherent rupture process, in [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


Rupture.ruptureGeometryWKT (type string)

description of the geometry of the rupture "plain" in Well Known Text format (https://en.wikipedia.org/wiki/Well-known_text) - types polygon or multipolygon recommended; in addition curvepolygon and circularstring are possible.


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


Rupture.ruptureVelocity (type co:RealQuantity) . mean rupture velocity in [m/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

Question to the NERA community: The differentiation between SlipVelocity and RuptureVelocity is not clear to me.
PhilippKästli, 2015-06-30


Rupture.shallowAsperity (type boolean)

Presence of one or more shallow asperities within the top 5 km below surface


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


Rupture.shallowAsperityDepth (type co:RealQuantity)

Depth of the shallowest relevant asperity, in [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


Rupture.slipVelocity (type co:RealQuantity)

mean slip velocity, in [m/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

Question to the NERA community: The differentiation between SlipVelocity and RuptureVelocity is not clear to me.
PhilippKästli, 2015-06-30


Rupture.stressdrop (type co:RealQuantity)

in [Pa]


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


Rupture.surfaceRupture (type sm:SurfaceRupture)

cfr. type definition of surface rupture


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


Rupture.vr_to_vs (type co:RealQuantity)

phase velocity divided by shearwave velocity of the ruptured medium


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


Rupture.fwHwIndicator (type sm:FootwallHangingwallIndicator)

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

This is probably an error: The Footwall/HangingWall indicator (indicating the relationship between backazimuth and rupture orientation) should be a property of the StrongMotionRecord, not of the rupture.
CarloCauzzi / PhilippKästli 2015-07-23


Rupture.referredStudy (type rm:LiteratureSource)

Relevant literature source for this rupture parametrization.


Discussion area: please fill in 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


OriginRecordReference [element]

Link between an origin and a waveform record. Note that one waveform record may be linked to multiple concurrencing origins (location results) of the same event, resulting in different distance metrics.


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


OriginRecordReference.strongMotionRecordID (type co:ResourceReference)

Globally unique identifier of the waveform record (reference, foreign key)


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


OriginRecordReference.distRupturedArea (type co:RealQuantity)

Shortest distance between recording station and rupture surface, in [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


OriginRecordReference.campbellDistance (type co:RealQuantity)

Shortest distance from the recording site to the seismogenic portion of the ruptured area (Campbell, 1997).


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


OriginRecordReference.joynerBooreDistance (type co:RealQuantity)

Shortest distance from a site to the surface projection of the rupture surface, in [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


OriginRecordReference.ruptureToStationAzimuth (type co:RealQuantity)

(Smallest) angle between the vector of the main rupture direction, and the line from hypocenter to the recording station; in [degrees].


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

"Line from Hypocenter to recording station": Direct connection or fastest wave path?
PhilippKaestli, 2015-07-21


OriginRecordReference.closestFaultDistance (type co:RealQuantity)

Closest distance between the station and the ruptured area on the fault plane; in [meters]


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


OriginRecordReference.preEventLength (type float)

Length of the pre-event window of the waveform data provided in the referenced record, assuming the origin time of the referring origin. In [seconds]


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


OriginRecordReference.postEventLength (type float)

minimum length after last exceeding a shaking threshold at a given station, typically a parameter of triggered sm instrumentation;


Discussion area: please fill in 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


OriginDescription [element]

Conceptually an extension of a BasicEventDescription.origin for some elements/attributes of relevance (by now, the number of strong motion traces available, and the rupture 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


OriginDescription.publicID (type co:ResourceReference)

Unique identifier of the OriginDescription instance.


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


OriginDescription.originID (type co:ResourceReference)

Public Identifier referring to the (BasicEventDescription) origin which is extended here.


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


OriginDescription.waveformCount (type int)

number of waveforms (datasets from individual streams) available for, and linked to this 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


OriginDescription.creationInfo (type rm:CreationInfo)

Data provenance


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


OriginDescription.rupture (type sm:Rupture)

see sm:Rupture.


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


OriginDescription.originRecordReference (type sm:OriginRecordReference)

Reference element to describe the many:many relationship between traces from different stations/streams, and one or multiple concurrencing origins derive from them.


Discussion area: please fill in 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


StrongMotionRecord [element]

Description of a (processed) waveform file representing the recorded motion snipplet from one data channel for one 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


StrongMotionRecord.publicID (type co:ResourceReference)

Globally unique, public identifier of the waveform (URI).


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


StrongMotionRecord.startTime (type co:TimeQuantity)

Time of the first recorded sample (typically without uncertainty)


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


StrongMotionRecord.duration (type float)

Duration of the recording; in [seconds]


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


StrongMotionRecord.waveformStreamID (type wf:WaveformStreamID)

Reference to the registration parameters of the recording channel: network, station, sensorlocation, 3-letter-channel indicator, plus a data field for a non-structured unique identifier


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


StrongMotionRecord.filterChain (type co:ResourceReference)

Public identifier as a reference (foreign key) to a filter chain object ( see wf:FilterChain


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


StrongMotionRecord.waveformFile (type rm:FileResource)

File resource pointer (with metadata) for the (binary or ascii) waveform data.


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


StrongMotionRecord.gainUnit (type string)

ground motion unit the trace represents after applying the gain, expressed in an expression of SI base units (e.g. "m/s", "m/s**2")


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


StrongMotionRecord.resampleRateDenominator (type int)

Denominator of the fraction representing the number of samples per second.


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


StrongMotionRecord.resampleRateNumerator (type int)

Numerator of the fraction representing the number of samples per second.

The concept of expressing a natural floating point value is similar to the sampling rate as represented in GFZ's inventory XML or FDSN's stationXML (SampleRateRatio)


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


StrongMotionRecord.owner (type rm:Contact)

Contact information of the data owner (as this includes also intellectual property on the reprocessing procedure, it may be different from the station owner.)


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


StrongMotionRecord.creationInfo (type rm:CreationInfo)

Creation metadata of the trace/waveform file.


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


StrongMotionRecord.peakMotion (type wf:PeakMotion)

individual peak motion value. Different peak motion values derived from the same waveform file may refer to different metrices (velocity, acceleration, duration...), and/or different processing methods


Discussion area: please fill in 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


StrongMotionParameters [element]

Top level element of this QuakeML package


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


StrongMotionParameters.publicID (type co:ResourceReference)

unique identificator of the QuakeML/StrongMotionParameters document


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


StrongMotionParameters.description (type string)

Free text description of the document


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


StrongMotionParameters.creationInfo (type rm:CreationInfo)

Data provenance of the document


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


StrongMotionParameters.originDescription (type sm:OriginDescription)

(see respective type 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


StrongMotionParameters.strongMotionRecord (type sm:StrongMotionRecord)

(see respective type 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


StrongMotionParameters.comment (type rm:Comment)

Comment on a StrongmotionDescription document.


Discussion area: please fill in 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


FootwallHangingwallIndicator [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