Changes between Initial Version and Version 1 of Strong_Motion_Message_Format


Ignore:
Timestamp:
01/19/12 16:18:35 (10 years ago)
Author:
branden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Strong_Motion_Message_Format

    v1 v1  
     1{{{ 
     2StongmotionII Format 
     3 
     4(last revised April 16, 2002) 
     5Each TYPE_STRONGMOTIONII message is intended to contain information for one 
     6channel only, with optional event association information. 
     7 
     8Field units with multiple channels will produce multiple TYPE_STRONGMOTIONII 
     9messages.  
     10 
     11All measurements in the Earthworm TYPE_STRONGMOTIONII message are assumed to be 
     12positive. Any other negative value will result in unpredictable behavior from 
     13strong motion applications. If you have sources that may produce signed values 
     14for PGA, PGV, PGD, or RSA values, you must be sure to change these to absolute 
     15values before they are put into this message. 
     16 
     17Message format: everything in quotes is present verbatim in the message. Other 
     18fields are described below. Unless otherwise shown, fields are separated by 
     19spaces. Lines are separated by ASCII newline characters. 
     20 
     21"SNCL:" sta.comp.net.loc 
     22"TIME:" date-time 
     23"ALT:" alternate date-time "CODE:" altcode 
     24"PGA:" pga "TPGA:" tpga 
     25"PGV:" pgv "TPGV:" tpgv 
     26"PGD:" pgd "TPGD:" tpdg 
     27"RSA:" nrsa"/"pdrsa rsa"/"pdrsa rsa... 
     28"QID:" qid qauthor 
     29 
     30All lines and fields must be present. Null values are described for applicable 
     31fields. 
     32 
     33 
     34sta.comp.net.loc: Station, component, network, and location codes with `.' 
     35between adjacent fields. Fields may be any length between 1 and (6, 8, 8, 2) 
     36characters in length, respectively. Use `-' if no value is used for the 
     37location code. 
     38 
     39 
     40date-time: time in the format yyyy/mm/dd hh:mm:ss.sss (year, month, day, hour, 
     41minute, seconds to thousandths. This time is the main timestamp for the 
     42message. If the message came from an SM box in the field, then this is the 
     43trigger time reported by the box. If the message came from a module processing 
     44continuous telemetry, then this is the pick time or earliest of PGA, PGV, or 
     45PGD time. If no value is available for this or any other time, fill the field 
     46with the null date-time "0000/00/00 00:00:00.000". 
     47 
     48 
     49alternate date-time: same format as above. This is the optional alternate 
     50timestamp for the message. This field is provided as a sanity check or 
     51correction of the main timestamp(t). This timestamp could be assigned by an 
     52acquisition module, database loader, human, or other. The author type of this 
     53timestamp is determined by altcode (see below). 
     54 
     55 
     56altcode: Required if alternate date-time is specified. Code specifying the 
     57source of the alternate date-time field. Possible values: 
     58 Value:         Description: 
     59   0           Code for no alternate time. 
     60   1           Code for an alternate time derived by a program module that 
     61                  receives a message from a box in the field.  
     62   2           Code for an alternate time derived by the database or strong 
     63                  motion database insertion module.  
     64   3           Code for an alternate time derived by a Human (who has 
     65                  hopefully reviewed the data).  
     66 
     67 
     68pga: The Peak Ground Acceleration(PGA) for this message. (cm/s/s) 
     69tpga: Time of the pga, yyyy/mm/dd hh:mm:ss.sss 
     70pgv: The Peak Ground Velocity(PGV) for this message. (cm/s) 
     71tpgv: Time of the pgv, yyyy/mm/dd hh:mm:ss.sss 
     72pgd: The Peak Ground Displacement(PGD) for this message. (cm) 
     73tpgd: Time of the pgd, yyyy/mm/dd hh:mm:ss.sss 
     74 
     75 
     76Any values not available for pga, pgv, and pgd should be assigned -1.0, the 
     77null value. 
     78 
     79 
     80nrsa: Number of response spectral acceleration (RSA) pairs. Valid value range 
     81      is 0 - 20  
     82pdrsa rsa: space-separated pair where pdrsa is the period at which RSA values 
     83           are given; rsa is the response spectral acceleration (cm/s/s). Each 
     84      pair of values is preceed by the "/" character. All the values must 
     85      appear on one line. 
     86 
     87}}}