Ground Motion Parameters Catalog
Ground Motion Parameters Catalog – General Description
Ground Motion Parameters Catalog contains data from Seismic catalog and Ground motion catalog through the event ID. That data format can be made using the application Parameters Catalog builder user guide.
The catalog is a variable in the Matlab format file and it is kept in a file MAT. The structure is an array with named fields that can contain data of various types and sizes. In the file there is only one variable, the file name and variable name are optional.
The format of the Ground Motion Parameters Catalog is made in the same manner as a catalog of seismic events and the Ground Motion Catalog.
The variable describing the catalog is a vector of structures, consisting of fields:
- field – name of field in the catalog (text value);
- type – a type of field in the catalog and way of showing the field (numeric value);
- val – column array of values. For the text the column is an array type cell with text fields. For the remaining value, the column is a numeric column.
- unit – description of the unit for individual data (text value).
- description – short description of the parameter (text value).
- fieldType – semantic meaning of the field. When some field values are similar/related then fieldType name is entered and for another case [] is entered.
The fundamental is a full catalog i.e. the variable contains the definitions of all specified fields. When some field values are missing then for the numeric data NaN (not specified) is entered and for the text null [] is entered.
The Ground Motion Parameters Catalog contains as many fields as Seismic Catalog and Ground Motion Catalog contain plus one additional - epicentral distance. Epicentral distance is calculated based on coordinates of events and stations which measured that event.
In the fields describing the events ("ID", "Time", "Lat", "Long" and at least one of Magnitude), the place of measurement ("RID", "SID", "S_name", "S_Lat", "S_Long", "S_Elevation", "R_time") and at least one of the fields of ground motion and epicentral distance values in all rows must be present.
| Field | Type | Val | unit | description | FieldType | Comments | Data format |
|---|---|---|---|---|---|---|---|
| EID | 3 | data vector | Event ID | required field from Seismic Catalog | text | ||
| Time | 5 | data vector | Event origin time | required field from Seismic Catalog, Matlab serial numerical time | double | ||
| Lat | 14,15,24,25 | data vector | deg | Latitude | required field from Seismic Catalog deg – North positive | double | |
| Long | 14,15,24,25,34,35 | data vector | deg | Longitude | required field from Seismic Catalog deg – East positive | double | |
| Depth | 11-13 | data vector | km | Hypocenter depth measured from the ground level | Hypocenter depth counted downwards from the surface (positive values below the surface) | double | |
| Elevation | 13 | data vector | km | Hypocenter elevation measured over the sea level | Hypocenter elevation counted upwards from sea level (positive values above sea level, negative values below sea level) | double | |
| Mw | 4 | data vector | Moment magnitude | 'Magnitude' | required field from Seismic Catalog when any other Magnitude is unavailable | double | |
| ML | 4 | data vector | Local magnitude | 'Magnitude' | required field from Seismic Catalog when any other Magnitude is unavailable | double | |
| RID | 3 | data vector | Registration ID | required field. ID must be linked to the name of the signal accelerogram | text | ||
| SID | 3 | data vector | Station ID | required field | text | ||
| S_name | 3 | data vector | Station name | required field | text | ||
| S_Lat | 24,25 | data vector | deg | Station latitude | required field | double | |
| S_Long | 24,25,34,35 | data vector | deg | Station longitude | required field | double | |
| S_Elevation | 10 | data vector | m | Station elevation | required field | double | |
| R_Time | 5 | data vector | Registration occurrence time | required field | double | ||
| Epicentral_dist | 22 | data vector | km | 'Epicentral distance between event and station' | required field | ||
| PGA_E | 13 | data vector | m/s^2 | Peak ground acceleration of E component | PGA | required field | double |
| PGA_N | 13 | data vector | m/s^2 | Peak ground acceleration of N component | PGA | double | |
| PVA | 13 | data vector | m/s^2 | Peak vertical acceleration | PGA | double | |
| PHA | 13 | data vector | m/s^2 | Peak horizontal acceleration | PGA | double | |
| PGA | 13 | data vector | m/s^2 | Total peak ground acceleration | PGA | double | |
| RMS_A | 21 | data vector | m/s^2 | Root-mean-square acceleration | PGA | double | |
| PGV_E | 13 | data vector | cm/s | Peak ground velocity of E component | PGV | double | |
| PGV_N | 13 | data vector | cm/s | Peak ground velocity of N component | PGV | double | |
| PVV | 13 | data vector | cm/s | Peak vertical velocity component | PGV | double | |
| PHV | 13 | data vector | cm/s | Peak horizontal velocity | PGV | double | |
| PGV | 13 | data vector | cm/s | Total peak ground velocity | PGV | double | |
| RMS_V | 21 | data vector | cm/s | Root-mean-square velocity | PGV | double | |
| PGD_E | 13 | data vector | mm | Peak ground displacement of E component | PGD | double | |
| PGD_N | 13 | data vector | mm | Peak ground displacement of N component | PGD | double | |
| PVD | 13 | data vector | mm | Peak vertical displacement component | PGD | double | |
| PHD | 13 | data vector | mm | Peak horizontal displacement | PGD | double | |
| PGD | 13 | data vector | mm | Total peak ground displacement | PGD | double | |
| RMS_D | 21 | data vector | mm | Root-mean-square displacement | PGD | double | |
| AI | 6 | data vector | m/s | Arias Intensity | double | ||
| NED | 6 | data vector | m/s^2 | Normalized Energy Density | double | ||
| ABD | 21 | data vector | s | Absolute bracketed duration | Duration | A problem with absolute durations relies on that one must prescribe for them absolute criteria. Maybe they should not be included in the catalog but to implement an appropriate service to evaluate them? | double |
| AUD | 21 | data vector | s | Absolute uniform duration | Duration | double | |
| AED | 21 | data vector | s | Absolute effective duration | Duration | double | |
| RBD | 21 | data vector | s | Relative bracketed duration | Duration | For relative durations criteria must be prescribed too but here there is a general agreement for 5% | double |
| RUD | 21 | data vector | s | Relative uniform duration | Duration | double | |
| RED | 21 | data vector | s | Relative effective duration | Duration | double |
Table 1. The general parameters in catalogue MAT format.
The Numbers of Data type:
1 – the real data without limits,
2 – the integer data,
3 – text value,
4 – the real number rounded to 0.1 (shown as 11),
5 – time in Matlab format serial time – the time display format; seconds with accuracy 1/10,
6 – the real data display in an engineering manner with one decimal place, e.g.: 3.5E6, (obsolete, recommended 2cd)
7 – the real data display in an engineering manner with two decimal place, (obsolete, recommended 2cd)
bc – (b and c are code digits) the real data display in fix-point manner with at minimum b places before decimal and c decimal place
e.g. For number 3.149.
10: „3”
11: „3.1”
12: „3.15”
20: „03”
23: „03.149”
1bc– the same manner as bc, but with place for a sign (space for sign „+”, sign - for sign „-”)
2cd– (c and d are code digits), the real data is displayed in an engineering manner, with place for a sign (space for sign „+”, sign ‘-’ for sign „-”), with c decimal place and exponent expressed by d places. The sign in exponent is always displayed.
e.g. For number 0.001:
211: „1.0E-3”
221: „1.00E-3”
212: „1.0E-03”
222: „1.00E-03”
e.g. For number 1000:
211: „1.0E+3”
221: „1.00E+3”
212: „1.0E+03”
222: „1.00E+03”