How earthquake data are prepared for InaSAFE Realtime

“In this module we will explain how earthquake data are extracted from BMKG shakemap products and prepared for use in InaSAFE Realtime”

In earthquake realtime we run a file drop service to which BMKG push shakemap products soon after an earthquake event. Once a shakemap is pushed and arrives on the server, a filesystem watcher detects the presence of the new file and the InaSAFE Realtime engine unpacks the product and generates a hazard layer with InaSAFE keywords and publishes it on the InaSAFE Realtime website. This process is described in the diagram below.

The website then sends the hazard layer with instructions to the InaSAFE Headless engine where it is combined with one or more exposure, aggregate and contextual datasets to produce impact layers and a report as well as ancillary data such as MMI contours. The impact layers, ancillary data and report are then published on the InaSAFE realtime web site and the report is also pushed to InaWARE.

All the derived products use the same shake event ID in their names so that the products can easily be cross referenced back to the original shakemap product provided by BMKG.

Generally, the process runs twice for each earthquake: once for the raw shakemap and then again a few minutes later when the 'corrected' shakemap arrives, that includes input from ground sensors in its generation.

You try:

Goal: To understand the various outputs created by Earthquake Realtime

Use the diagram above to list the various derivative products from the original shakemap.

Check your results:
Swap your list with a neighbouring group and see if they had the same results as you.

More about

Shakemap TIFF: The original shakemap provided by BMKG is a USGS format XML file and cannot be used directly in a GIS application. InaSAFE Realtime extracts the shake matrix to a comma delimited text file, then converts that file into a GeoTIFF by using GDAL’s gdal_grid command.

Contours: The contours generated are calculated on the 'half MMI' breaks so that the range from one contour to the next is e.g. 0.5 MMI to 1.5 MMI.

Epicentre: This is extracted as a point from the shake grid. The epicentre is used for describing the locality of the event.

Nearest affected places: This is a list of nearby settlements that is generated by InaSAFE and includes details of the population size, settlement name and MMI level each place was exposed to.

Impact map: This is the generated PDF report produced by InaSAFE Realtime. The report includes most of the above elements.

It is important to clarify that although the system is called ‘InaSAFE Realtime’, there is in fact a delay between the actual shake event and the generation of the report. This is a result of the processing overhead as the data moves through different organisations and servers where processing gets carried out. The report is typically available less than 20 minutes post event, but sometimes may take longer.

After the analysis has completed and the reports are generated, the report and data are made available on the realtime platform. The report is also published on InaWARE where it can be viewed by operations staff after the shake event.

Check your knowledge:

  1. InaSAFE Realtime produces instantaneous reports following a shake event:
    1. true
    2. false
  2. Mark all the correct statements:
    1. Nearest affected places are provided as part of the standard shake dataset from BMKG
    2. InaSAFE realtime products use the same event ID as the original shakemap
    3. When a shake event happens, there is a waiting period before the InaSAFE realtime report becomes available

Further reading: