|
Size: 5107
Comment:
|
← Revision 4 as of 2015-06-24 12:52:30 ⇥
Size: 6244
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 36: | Line 36: |
| TODO | Reference to a stream description in an inventory. This is mostly equivalent to the combination of networkCode, stationCode, locationCode, and channelCode. However, additional information, e. g., sampling rate, can be referenced by the resourceURI. It is recommended to use resourceURI as a flexible, abstract, and unique stream ID that allows to describe different processing levels, or resampled/filtered products of the same initial stream, without violating the intrinsic meaning of the legacy identifiers (network, station, channel, and location codes). However, for operation in the context of legacy systems, the classical identifier components are supported. |
| Line 47: | Line 53: |
| TODO | Network code. String with a maximum length of 8 characters. |
| Line 58: | Line 64: |
| TODO | Station code. String with a maximum length of 8 characters. |
| Line 69: | Line 75: |
| TODO | Channel code. String with a maximum length of 8 characters. |
| Line 80: | Line 86: |
| TODO | Location code. String with a maximum length of 8 characters. |
| Line 91: | Line 97: |
| TODO | Resource identifier for the waveform stream. QuakeML adopts in many places resource descriptors with a well-defined syntax for unambiguous resource identification. Resource identifiers are designed to be backward compatible with existing descriptors. |
Discussion on package Waveform
Quick navigation: go to package
Waveform | Common | StationCharacterization | SeismicSource | ResourceMetadata | Borehole | BasicEventDescription | SiteCharacterization | VSTypes | StrongMotion | BasicEventDescriptionTypes | Filter | Hydraulic |
In current package (!Waveform): go to class
WaveformStreamID | PeakMotion |
WaveformStreamID [type]
Reference to a stream description in an inventory. This is mostly equivalent to the combination of networkCode, stationCode, locationCode, and channelCode. However, additional information, e. g., sampling rate, can be referenced by the resourceURI. It is recommended to use resourceURI as a flexible, abstract, and unique stream ID that allows to describe different processing levels, or resampled/filtered products of the same initial stream, without violating the intrinsic meaning of the legacy identifiers (network, station, channel, and location codes). However, for operation in the context of legacy systems, the classical identifier components are supported.
Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21
WaveformStreamID.networkCode (type string)
Network code. String with a maximum length of 8 characters.
Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21
WaveformStreamID.stationCode (type string)
Station code. String with a maximum length of 8 characters.
Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21
WaveformStreamID.channelCode (type string)
Channel code. String with a maximum length of 8 characters.
Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21
WaveformStreamID.locationCode (type string)
Location code. String with a maximum length of 8 characters.
Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21
WaveformStreamID.resourceURI (type co:ResourceReference)
Resource identifier for the waveform stream. QuakeML adopts in many places resource descriptors with a well-defined syntax for unambiguous resource identification. Resource identifiers are designed to be backward compatible with existing descriptors.
Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21
PeakMotion [type]
TODO
Discussion area: please fill in your comments below (between the horizontal lines) and tag with your user name and the date of your comment.
Example: FabianEuchner, 2014-10-21
PeakMotion.motion (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
PeakMotion.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
PeakMotion.atTime (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
PeakMotion.frequency (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
PeakMotion.method (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