Size: 23532
Comment:
|
Size: 27267
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 16: | Line 16: |
[[QuakeML2.0/MarsquakeDiscussion|Marsquake]] | | |
Line 42: | Line 41: |
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'' |
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 89: | Line 93: |
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'' |
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 100: | Line 107: |
TODO | Globally unique identifier. |
Line 111: | Line 118: |
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 122: | Line 131: |
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 133: | Line 144: |
TODO | rupture area in [m^2] |
Line 143: | Line 154: |
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 155: | Line 167: |
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 166: | Line 178: |
TODO | Moment release on the part of the rupture area not deeper than 5 km below surface, in [N*m] |
Line 177: | Line 189: |
TODO | Duration of the coherent rupture process, in [s] |
Line 188: | Line 200: |
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 198: | Line 210: |
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 210: | Line 225: |
TODO | Presence of one or more shallow asperities within the top 5 km below surface |
Line 221: | Line 236: |
TODO | Depth of the shallowest relevant asperity, in [m] |
Line 232: | Line 247: |
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 243: | Line 262: |
TODO | in [Pa] |
Line 254: | Line 273: |
TODO |
cfr. type definition of surface rupture |
Line 265: | Line 283: |
TODO | phase velocity divided by shearwave velocity of the ruptured medium |
Line 288: | Line 306: |
TODO | Relevant literature source for this rupture parametrization. |
Line 300: | Line 318: |
TODO | 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 311: | Line 329: |
TODO | Globally unique identifier of the waveform record (reference, foreign key) |
Line 322: | Line 340: |
TODO | Shortest distance between recording station and rupture surface, in [m] |
Line 344: | Line 362: |
TODO | Shortest distance from a site to the surface projection of the rupture surface, in [m] |
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 |
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
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
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
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)
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
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)
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
OriginRecordReference.closestFaultDistance (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
OriginRecordReference.preEventLength (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
OriginRecordReference.postEventLength (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
OriginDescription [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
OriginDescription.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
OriginDescription.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
OriginDescription.waveformCount (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
OriginDescription.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
OriginDescription.rupture (type sm: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.
Example: FabianEuchner, 2014-10-21
OriginDescription.originRecordReference (type sm: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.
Example: FabianEuchner, 2014-10-21
StrongMotionRecord [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
StrongMotionRecord.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
StrongMotionRecord.startTime (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
StrongMotionRecord.duration (type float)
TODO
Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21
StrongMotionRecord.waveformStreamID (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
StrongMotionRecord.filterChain (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
StrongMotionRecord.waveformFile (type rm:FileResource)
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
StrongMotionRecord.gainUnit (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
StrongMotionRecord.resampleRateDenominator (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
StrongMotionRecord.resampleRateNumerator (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
StrongMotionRecord.owner (type rm:Contact)
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
StrongMotionRecord.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
StrongMotionRecord.peakMotion (type wf: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.
Example: FabianEuchner, 2014-10-21
StrongMotionParameters [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
StrongMotionParameters.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
StrongMotionParameters.description (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
StrongMotionParameters.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
StrongMotionParameters.originDescription (type sm: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.
Example: FabianEuchner, 2014-10-21
StrongMotionParameters.strongMotionRecord (type sm: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.
Example: FabianEuchner, 2014-10-21
StrongMotionParameters.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
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
FOOTWALL: footwall
HANGING_WALL: hanging wall