Bam, Iran – Earthquake detection with the ASAR instrument of ENVISAT

Author
Nico Trebbin
Published
07/06/2013

 The purpose of this article

The devastating major earthquake which occured on December 23, 2003 with a moment magnitude of 6.6, that caused a huge number of human casualties, as well as major destructions in Bam and the surrounding Kerman province in Iran, had been the topic of several geophysical studies in the past 10 years. Furtunately, and due to the scientific effort of the seismological societey, the basic processes that induced the earthquake are well known by now. This short article should provide some useful information for processing spaceborne Radar data for the detection of earthquakes and faults. For this purpose I have chosen ASARAdvanced Synthetic Aperture Radar data from the ENVISAT mission before and after the event to determine the structural differences and rupture zones induced by the earthquake.

The data sets provided by ESA are:

subset_9_of_ENVISAT-ASA_IMS_1PXPDE20040211_061300_000000142024_00120_10194_0013_ML.dim

subset_10_of_ENVISAT-ASA_IMS_1PNUPA200331203_061259_000000162022_00120_09192_0099_ML.dim

Which processing steps were applied to the product?

As post-processing is very important for Radar data, several corrections and image processing algorithms have to be applied on the data. According to the product name the Single-Look Complex (SLC) image data is a high-resolution, narrow swath products based on data acquired at one of seven subswaths. It is intended for SAR image quality assessment, calibration and interferometric or wind/wave applications. A small number of corrections and interpolations are performed like the preprocessing (for all data the same; i.e. I/Q bias removal, I/Q gain imbalance correction, I/Q non-orthogonality correction), a Doppler Centroid Estimation and a Range Doppler Image Formation. To obtain the Doppler Centroid Estimation for the high-resolution Image Mode of the product, the Multi-Look Cross Correlation Method is used.

Figure 1: Multilook processed image of Bam, Iran from 3rd December 2003, with the airport in the north east of Bam

Figure 1: Multilook processed image of Bam, Iran from 3rd December 2003, with the airport in the north east of Bam

NEST Multilook Operator

The original SAR images with inherent speckle noise were processed with the Multilook Operator to reduce the speckle noise by incoherently combining several images as if they corresponded to different looks of the same scene and to produce an image with nominal image pixel size (azimuth to range ratio of 5:1, reprocessed to 1:1). As a result, the final images approximately have square pixel spacing.

Speckle Noise

The speckle effect is a result of the interference of many waves of the same frequency, having different phases and amplitudes, which add together to give a resultant wave whose amplitude, and therefore intensity, varies randomly. When a surface is illuminated by a light wave, according to diffraction theory, each point on an illuminated surface acts as a source of secondary spherical waves. The light at any point in the scattered light field is made up of waves which have been scattered from each point on the surface.

Range and Azimuth Direction obtained from the metadata

The original intensity image has num_output_lines=5000, num_samples_per_line=1200 with an azimuth_looks=1.0 and range_looks=1.0. The processed image has num_output_lines=1000 with azimuth_looks=5.0. Therefore the azimuth direction is from north to south whereas the range direction is from west to east.

Why is the automatic coregistration necessary?

The process accurately co-register the master image (11th February 2004) with the slave image (3rd December 2003). For this purpose the master image is used as a reference image and the slave image is overlayed in a way that each pixel of the slave image corresponds to the same geoposition pixel in the master image. Due to the fact that both images are complex images and that the scene described by the images is in a flat area the build-in algorithm ensures a matching accuracy of better than 0.05 pixels. For complex images the registration is achieved by maximizing the coherence between master and slave images at a series of imagettes defined across the image. After the registration, a warp function is created which maps the master-slave Ground Control Points (GCP) of the slave image into pixels in the master image.

What information can be obtained out of the residual file?

The Create Stack Operator allows collocating two spatially overlapping products. Collocating two products implies that the pixel values of one product (the slave) are resampled into the geographical raster of the other (the master). When two products are collocated, the band data of the slave product is resampled into the geographical raster of the master product. In order to establish a mapping between the samples in the master and the slave rasters, the geographical position of a master sample is used to find the corresponding sample in the slave raster. The calculation of the new pixel value is performed by weighting the 36 (for the chosen settings) surrounding pixels.

Report ASAR II_cubic_convolution

Figure 2: Cubic convolution resampling method for 16 (4×4) sourrounding pixels


Parse 0

RMS mean = 1.2889993312800754

RMS std = 3.7586558379704043

Parse 1

RMS mean = 0.02553238345095844

RMS std = 0.022476339664258316

Parse 2

RMS mean = 0.0241239868209786

RMS std = 0.02009919619001828

 

For the parse 0, every valid GCP is used to resample the projected output product (by Cubic Convolution) of the slave image. The respective RMS errors in x- (row) and y- (column) direction are listed in the residual file. All GCP-pairs of the master and slave image that exceed the RMS threshold defined previously are excluded from the 2nd parse of the same routine. As a result, the RMS mean gets better by each use of the Cubic Convolution. As the RMS values below show, the accuracy increases significantly from Parse 0 to Parse 1, but only very poor from Parse 1 to Parse 2. As the desired accuracy of 0.05 was already reached in Parse 1, the process could have been stopped after the first parse.

Automatic co-registered image with calculation of the coherence and Multilook processed with post earthquake event as master image and prior earthquake as slave image. Interessiting in this image are the areas indicated in red because it might represent a crack/surface rupture induced by the earthquake.

Figure 3: Automatic co-registered image with calculation of the coherence and Multilook processed with post earthquake event as master image and prior earthquake as slave image. Interessiting in this image are the areas indicated in red because it might represent a crack/surface rupture induced by the earthquake.

Multilook processed image with overlayed orthorectified optical satellite imagery of Bam, Iran

Figure 4: Multilook processed image with overlayed orthorectified optical (RGB) satellite imagery of Bam and the surrounding region Kerman. The green areas are vegetation and the greyish to brownish structures are builidings and roads. The satellite image was obtained 2009, but the extent of the city Bam remained nearly constant over the time. The red arrows indicate the satellite azimuth and range direction at the time the radar image was acquired.

 

 

Coherence as an indicator for geophysical processes

The definition of coherence is the similarity of the co-registered GCP-pairs (by Coarse Registration and Fine Registration by performing a cross-correlation of master and slave imagettes) and a computation of the best sub-pixel shift of GCP such that the slave imagette at the new GCP position gives the maximum coherence with the master imagette according to Powell’s method. Assuming I1 and I2 be RxC imagettes and I*2 is the complex conjugate of I2, coherence is computed by:

coherence = \frac{\left | \sum_{r=0}^{R-1} \sum_{c=0}^{C-1} I_{1}(r,c) I_{2}\ast (r,c) \right |}{\left ( \sum_{r=0}^{R-1} \sum_{c=0}^{C-1}\left | I_{1}(r,c)\right |^{2} \sum_{r=0}^{R-1} \sum_{c=0}^{C-1} \left | I_{2}(r,c) \right |^{2} \right )^\frac{1}{2}}

Method:

The coherence in this scene is computed with a 10×2 (azimuth x range due to the 5:1 looks ratio) sliding window in two steps:

  1. First for each pixel in the imagette, a 10×2 window centered at the pixel is determined for both master and slave imagettes, and coherence is computed for the two windows using equation above.
  2. Average coherences computed for all pixels in the imagette to get the final coherence for the imagette.
    The low coherence areas (dark spots) correspond mainly to building structures like houses and roads as well as vegetation, whereas the high coherence areas (bright spots) correspond to the surrounding desert in the scene. Due to the earthquake, a phase-shift occured on the building structures (destroyed buildings) and the vegetation differs naturally with each image. Therefore the coherence value is very low for the city area whereas the surrounding desert isn’t effected that much, because the phase-shift is quite low (except for the new crack) due to a lack of horizontal or vertical displacement and therefore low differentiation.

The low coherence areas (dark spots) in Figure 3 correspond mainly to building structures like houses and roads as well as vegetation, whereas the high coherence areas (bright spots) correspond to the surrounding desert in the scene. Due to the earthquake, a phase-shift occured on the building structures (destroyed buildings) and the vegetation differs naturally with each image. Therefore the coherence value is very low for the city area whereas the surrounding desert isn’t effected that much, because the phase-shift is quite low (except for the new crack) due to a lack of horizontal or vertical displacement and therefore low differentiation. See Figure 4 for a more natural looking image of the scene.

Why do we have to remove the topographic phase?

InSAR is normally applied for estimating topography. Here we are interesting in the displacement only, meaning that we need to subtract the phase difference caused by topography. That can be done if a DEM is available or by means of a third SAR image. The topography around Bam is rather flat, and therefore the interferogram doesn’t change much.

The interferogram and estimate of the displacement

This interferogram (Figure 5) represents contours of ground displacements towards and away from the Envisat satellite that occurred during the earthquake (each fridge corresponds to half the wavelength of the radar = 2.8cm). There is a two-quadrant pattern consistent (in this descending orbit image) with a near-vertical strike-slip fault oriented north-south (Figure 6). The ground moved approximately 30cm towards the satellite in the south-east quadrant, and approximately 15cm away from the satellite in the north-east quadrant.

Phase-Interferogram with topographic correction of the scene

Figure 5: Phase-Interferogram with topographic correction of the scene and applied colour palette spectrum.spd

Interferogram with overlayed optical image data and indicated faults. The new fault (A'-B') occurred approximately 4km west of the known fault (A-B)

Figure 6: Interferogram with overlayed optical image data and indicated faults. The new fault (A’-B’) occurred approximately 4km west of the known fault (A-B)

Nico Trebbin is a geophysicist and future satellite application engineer who studied at the LMU/TUM in Munich and is currently working at DLR

Test
Owner and Data Controller
Nico Trebbin Owner contact email: support@nicomedia.de

Types of Data collected

Among the types of Personal Data that this Application collects, by itself or through third parties, there are: first name, last name, email address, Usage Data, username, website and Cookies. Complete details on each type of Personal Data collected are provided in the dedicated sections of this privacy policy or by specific explanation texts displayed prior to the Data collection. Personal Data may be freely provided by the User, or, in case of Usage Data, collected automatically when using this Application. Unless specified otherwise, all Data requested by this Application is mandatory and failure to provide this Data may make it impossible for this Application to provide its services. In cases where this Application specifically states that some Data is not mandatory, Users are free not to communicate this Data without consequences to the availability or the functioning of the Service. Users who are uncertain about which Personal Data is mandatory are welcome to contact the Owner. Any use of Cookies – or of other tracking tools – by this Application or by the owners of third-party services used by this Application serves the purpose of providing the Service required by the User, in addition to any other purposes described in the present document and in the Cookie Policy, if available. Users are responsible for any third-party Personal Data obtained, published or shared through this Application and confirm that they have the third party’s consent to provide the Data to the Owner.

Mode and place of processing the Data

Methods of processing

The Owner takes appropriate security measures to prevent unauthorized access, disclosure, modification, or unauthorized destruction of the Data. The Data processing is carried out using computers and/or IT enabled tools, following organizational procedures and modes strictly related to the purposes indicated. In addition to the Owner, in some cases, the Data may be accessible to certain types of persons in charge, involved with the operation of this Application (administration, sales, marketing, legal, system administration) or external parties (such as third-party technical service providers, mail carriers, hosting providers, IT companies, communications agencies) appointed, if necessary, as Data Processors by the Owner. The updated list of these parties may be requested from the Owner at any time.

Legal basis of processing

The Owner may process Personal Data relating to Users if one of the following applies:
  • Users have given their consent for one or more specific purposes.
  • Note: Under some legislations the Owner may be allowed to process Personal Data until the User objects to such processing (“opt-out”), without having to rely on consent or any other of the following legal bases. This, however, does not apply, whenever the processing of Personal Data is subject to European data protection law;
  • provision of Data is necessary for the performance of an agreement with the User and/or for any pre-contractual obligations thereof;
  • processing is necessary for compliance with a legal obligation to which the Owner is subject;
  • processing is related to a task that is carried out in the public interest or in the exercise of official authority vested in the Owner;
  • processing is necessary for the purposes of the legitimate interests pursued by the Owner or by a third party;
In any case, the Owner will gladly help to clarify the specific legal basis that applies to the processing, and in particular whether the provision of Personal Data is a statutory or contractual requirement, or a requirement necessary to enter into a contract.

Place

The Data is processed at the Owner’s operating offices and in any other places where the parties involved in the processing are located. Depending on the User’s location, data transfers may involve transferring the User’s Data to a country other than their own. To find out more about the place of processing of such transferred Data, Users can check the section containing details about the processing of Personal Data. Users are also entitled to learn about the legal basis of Data transfers to a country outside the European Union or to any international organization governed by public international law or set up by two or more countries, such as the UN, and about the security measures taken by the Owner to safeguard their Data. If any such transfer takes place, Users can find out more by checking the relevant sections of this document or inquire with the Owner using the information provided in the contact section.

Retention time

Personal Data shall be processed and stored for as long as required by the purpose they have been collected for. Therefore:
  • Personal Data collected for purposes related to the performance of a contract between the Owner and the User shall be retained until such contract has been fully performed.
  • Personal Data collected for the purposes of the Owner’s legitimate interests shall be retained as long as needed to fulfill such purposes. Users may find specific information regarding the legitimate interests pursued by the Owner within the relevant sections of this document or by contacting the Owner.
The Owner may be allowed to retain Personal Data for a longer period whenever the User has given consent to such processing, as long as such consent is not withdrawn. Furthermore, the Owner may be obliged to retain Personal Data for a longer period whenever required to do so for the performance of a legal obligation or upon order of an authority. Once the retention period expires, Personal Data shall be deleted. Therefore, the right to access, the right to erasure, the right to rectification and the right to data portability cannot be enforced after expiration of the retention period.

The purposes of processing

The Data concerning the User is collected to allow the Owner to provide its Services, as well as for the following purposes: SPAM protection, Content commenting, Analytics and Interaction with external social networks and platforms. Users can find further detailed information about such purposes of processing and about the specific Personal Data used for each purpose in the respective sections of this document.

Detailed information on the processing of Personal Data

Personal Data is collected for the following purposes and using the following services:
Google Analytics (Google Inc.)
Comment system managed directly by WordPress
Interaction with external social networks and platforms
Akismet is a SPAM protection service provided by Automattic Inc.

The rights of Users

Users may exercise certain rights regarding their Data processed by the Owner. In particular, Users have the right to do the following:
  • Withdraw their consent at any time. Users have the right to withdraw consent where they have previously given their consent to the processing of their Personal Data.
  • Object to processing of their Data. Users have the right to object to the processing of their Data if the processing is carried out on a legal basis other than consent. Further details are provided in the dedicated section below.
  • Access their Data. Users have the right to learn if Data is being processed by the Owner, obtain disclosure regarding certain aspects of the processing and obtain a copy of the Data undergoing processing.
  • Verify and seek rectification. Users have the right to verify the accuracy of their Data and ask for it to be updated or corrected.
  • Restrict the processing of their Data. Users have the right, under certain circumstances, to restrict the processing of their Data. In this case, the Owner will not process their Data for any purpose other than storing it.
  • Have their Personal Data deleted or otherwise removed. Users have the right, under certain circumstances, to obtain the erasure of their Data from the Owner.
  • Receive their Data and have it transferred to another controller. Users have the right to receive their Data in a structured, commonly used and machine readable format and, if technically feasible, to have it transmitted to another controller without any hindrance. This provision is applicable provided that the Data is processed by automated means and that the processing is based on the User’s consent, on a contract which the User is part of or on pre-contractual obligations thereof.
  • Lodge a complaint. Users have the right to bring a claim before their competent data protection authority.

Details about the right to object to processing

Where Personal Data is processed for a public interest, in the exercise of an official authority vested in the Owner or for the purposes of the legitimate interests pursued by the Owner, Users may object to such processing by providing a ground related to their particular situation to justify the objection. Users must know that, however, should their Personal Data be processed for direct marketing purposes, they can object to that processing at any time without providing any justification. To learn, whether the Owner is processing Personal Data for direct marketing purposes, Users may refer to the relevant sections of this document.

How to exercise these rights

Any requests to exercise User rights can be directed to the Owner through the contact details provided in this document. These requests can be exercised free of charge and will be addressed by the Owner as early as possible and always within one month.
Additional information about Data collection and processing

Legal action

The User’s Personal Data may be used for legal purposes by the Owner in Court or in the stages leading to possible legal action arising from improper use of this Application or the related Services. The User declares to be aware that the Owner may be required to reveal personal data upon request of public authorities.

Additional information about User’s Personal Data

In addition to the information contained in this privacy policy, this Application may provide the User with additional and contextual information concerning particular Services or the collection and processing of Personal Data upon request. System logs and maintenance For operation and maintenance purposes, this Application and any third-party services may collect files that record interaction with this Application (System logs) use other Personal Data (such as the IP Address) for this purpose.

Information not contained in this policy

More details concerning the collection or processing of Personal Data may be requested from the Owner at any time. Please see the contact information at the beginning of this document.

How “Do Not Track” requests are handled

This Application does not support “Do Not Track” requests. To determine whether any of the third-party services it uses honor the “Do Not Track” requests, please read their privacy policies.

Changes to this privacy policy

The Owner reserves the right to make changes to this privacy policy at any time by giving notice to its Users on this page and possibly within this Application and/or – as far as technically and legally feasible – sending a notice to Users via any contact information available to the Owner. It is strongly recommended to check this page often, referring to the date of the last modification listed at the bottom.
Definitions and legal references

Legal information

This privacy statement has been prepared based on provisions of multiple legislations, including Art. 13/14 of Regulation (EU) 2016/679 (General Data Protection Regulation). This privacy policy relates solely to this Application, if not stated otherwise within this document. Latest update: June 28, 2018