Data Formats

The Data Formats section provides supported input formats and their descriptions that will be used in the simulation platform.

Stochastic Event Set

The event output generated by the OpenQuake (OQ) Engine event-based PSHA calculation workflow includes the following columns:

List of columns in the event set

Attribute	Description
event_id	A unique identifier (integer) for each earthquake in the catalogue
rup_id	Incremental number identifying the rupture
rlz_id	A unique identifier (integer) for the logic-tree realization associated with the event
year	Year of event (integer)
ses_id	A unique identifier (integer) for the stochastic event set simulation to which the event belongs

Stochastic Rupture Set

The rupture output generated by the OpenQuake (OQ) Engine event-based PSHA calculation workflow includes the following columns:

List of columns in the rupture set

Attribute	Description
rup_id	A unique identifier (integer) for each rupture
source_id	A unique identifier (integer or string) for the seismic source generating the rupture
multiplicity	How many times the rupture occurs in the effective investigation time
mag	Float specifying the magnitude of the rupture
centroid_lon	Longitude of the centroid of the rupture
centroid_lat	Latitude of the centroid of the rupture
centroid_depth	Depth (in km) of the centroid of the rupture
trt	String specifying the tectonic region type
strike	Strike angle of the rupture surface
dip	Dip angle of the rupture surface
rake	Rake angle of the rupture surface

Catalogue

GEM Hazard Modeller’s Tookit (hmtk) .csv format [1] is the main catalogue format used in the simulation platform. It includes the following columns:

List of Attributes in the Earthquake Catalogue File (* Indicates Essential)

Attribute	Description
eventID*	A unique identifier (integer) for each earthquake in the catalogue
Agency	The code (string) of the recording agency for the event solution
year*	Year of event (integer) in the range -10000 to present (events before common era (BCE) should have a negative value)
month*	Month of event (integer)
day*	Day of event (integer)
hour*	Hour of event (integer) - if unknown then set to 0
minute*	Minute of event (integer) - if unknown then set to 0
second*	Second of event (float) - if unknown set to 0.0
timeError	Error in event time (float)
longitude*	Longitude of event, in decimal degrees (float)
latitude*	Latitude of event, in decimal degrees (float)
SemiMajor90	Length (km) of the semi-major axis of the 90 % confidence ellipsoid for location error (float)
SemiMinor90	Length (km) of the semi-minor axis of the 90 % confidence ellipsoid for location error (float)
ErrorStrike	Azimuth (in degrees) of the 90 % confidence ellipsoid for location error (float)
depth*	Depth (km) of earthquake (float)
depthError	Uncertainty (as standard deviation) in earthquake depth (km) (float)
magnitude*	Homogenised magnitude of the event (float) - typically Mw
sigmaMagnitude	Uncertainty on the homogenised magnitude (float) typically Mw

Source Polygon

Standard GeoJSON format is used to define source zones or study areas. The example below shows a polygon structure used to represent a tectonic or seismic zone.

Example GeoJSON Polygon Structure

{
  "name": "sample",
  "features": [
    {
      "type": "Feature",
      "properties": {
        "id": "id"
      },
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              [-3.9115, 43.5650],
              [-3.8500, 43.5650],
              [-3.8500, 43.5200],
              [-3.9115, 43.5200],
              [-3.9115, 43.5650]
            ]
          ]
        ]
      }
    }
  ]
}

Completeness Configuration

A completeness parameter configuration file supplied as a .toml file. The toml file will set up parameters for completeness step and be modified while running the code. The configuration toml is created by the modeller.

Example toml configuration for completeness

[completeness]
num_steps = 0
step = 8
mags = [ 4.5, 5.0, 5.5, 6.0, 6.5, 7.0, 7.5,]
years = [ 1905, 1920, 1940, 1960, 1980, 2000, 2020,]
ref_mag = 4.5
ref_upp_mag = 10.0
bmin = 0.5
bmax = 1.5
last_year = 2020
optimization_criterion = "optimize"

[sources.id]

Underneath these settings, we have headers for the source. By running the workflow, we will add information of completeness and MFD parameters. The parameters inside the toml file are described below.

num_steps: Sets preferred number of steps in window.
step: Steps is used for parallelisation.
mags: List of candidate completeness magnitudes considered in the analysis.
years: List of candidate years at which catalogue completeness may have changed.
ref_mag: Reference minimum magnitude used in the Gutenberg–Richter analysis.
ref_upp_mag: Upper reference magnitude limit considered in the analysis.
bmin: Minimum allowable Gutenberg–Richter b-value during optimization.
bmax: Maximum allowable Gutenberg–Richter b-value during optimization.
last_year: Final year of the catalogue used in the completeness analysis.
optimization_criterion: Options for norm (e.g., “Optimize” or “Poisson”)