top of page
Writer's pictureArpit Shah

Landslide Hazard Mapping Workflows - Risk Modeling, Analysis & Detection

Updated: 5 days ago

Introduction


Depiction of Major types of Landslide Movement initially developed by Varnes D (1978) and refined in its current form by Hungr O, Leroueil S, Picarelli L (2014). Source: Springer Nature
Figure 1: Depiction of Major types of Landslide Movement initially developed by Varnes D (1978) and refined in its current form by Hungr O, Leroueil S, Picarelli L (2014). Source: Springer Nature

While the sliding of large masses of snow is called an 'Avalanche' - a topic that I've covered previously, the sliding of rock, debris, earth or soil is termed as a 'Landslide' - a phenomena which impacts us more often, quite literally.


Both these hazards are a form of Mass wasting - a down-slope movement of material under the influence of gravity. Mudslides - a liquefied and faster debris and dirt flow - is another type of Mass wasting and is highly devastating too.


Initially developed by geologist David Varnes in 1978 and subsequently refined by several researchers over time, Landslides can be classified as per their type of movement under six broad categories: Fall, Topple, Slide, Spread, Flow and Slope Deformation (Figure 1)

 

Section Hyperlinks:


5. Conclusion and About the Firm

 

India encounters several Landslide incidents - 61 have been recorded within the first 8 months of 2021 itself. The vicious slant of Slope and the pull of Gravity are essentially the key influencing factors of Landslides. Rainfall, Loose Soil, Ground Deformation also contribute towards the formation of this hazard. The Geological Survey of India (GSI), a scientific agency operated by the government, indicates that 'about 0.42 million sq. km or 12.6% of land area, excluding snow-covered area, are prone to landslide hazard' - an astounding threat.


Landslide Hazard Analysis & Mapping workflows involve the use of surface datasets such as terrain, slope and other influencing parameters obtained from topographic, aerial and remote sensing mediums which are subsequently processed on geospatial platforms (GIS) to identify locations which are susceptible to Landslide. GSI has created-

a) region-specific Landslide forecasting models using Rainfall and Land Slope as its main variables &

b) site-specific Landslide Forecasting models using advanced scientific instruments at eight sites in India currently. As per GSI, 90% of the landslides occurring in India is linked to rainfall - hence, this variable is given extra weightage in their predictive models.

In this post, I will demonstrate 3 Landslide workflows a) Creating a Landslide Risk Model b) Identifying at-risk Stakeholders and Infrastructure using a Landslide Risk Model and c) Rapid Detection of Landslide location using Radar Satellite Imagery. These would help you obtain an end-to-end picture of the subject matter as well as understand the capabilities of modern geotechnology.


You may view a demonstration of all the three workflows from the video below-


Video 1: Mapping & Analyzing Landslide Hazard using powerful Location Analytics platforms

 

1. Creating a Landslide Risk Model


Landslide Risk models need to be re-evaluated after major events such as earthquakes, wildfires, heavy rainfall etc. because the terrain / surface characteristics tend to change after such events making certain areas more susceptible to Landslides. In this workflow, I will demonstrate the creation of a new Landslide Risk Model after the occurence of a wildfire in the study area.


Much thanks to Learn ArcGIS for the training resources

Burn Scar, California Wildfire
Figure 2: First, I will load the layer containing the area affected by Wildfire i.e. Burn Scar within California, USA
Loading an Elevation layer
Figure 3: Next, I'll add an Elevation layer. Whiter shades indicate areas of high Elevation and vice versa.
Converting Elevation Layer to Slope Layer
Figure 4: I have converted the Elevation layer into a more relevant 'Slope' layer (green to red symbology). Green areas have the lowest slant i.e. Slope whereas Red areas have the highest slant / Slope - the latter are highly susceptible to Landslides
Mean Rainfall layer added to the project
Figure 5: Next, I have added a Mean Rainfall layer to my project. Whiter shades indicate areas of high Mean Rainfall and vice versa. Areas affected by higher rainfall are more susceptible to Landslides as the surface becomes slippery.
Multispectral Imagery - RGB Visualization
Figure 6: The final layer which I'll use is Multispectral Imagery (RGB visualization) acquired by Landsat satellite. Using it, I'll compute the Vegetation Density. Sparser the Vegetation, looser the Soil and more susceptible it will be to Landslides.

Now that I have all the necessary layers for the Risk Model loaded onto the GIS software, I will proceed to create a Geoprocessing Chain as depicted in the image below. This is essentially the technical procedure i.e. the 'methodology' used to generate the Risk Model. Instead of running one command at-a-time, I'll run this graph of sequential commands (Figure 7 below) which will automatically proceed to generate the final output at the click of a button.

Geo-Processing Workflow - Landslide Risk Model
Figure 7: Geo-Processing Workflow - Landslide Risk Model

So what does the processing steps constitute?


At first, the GIS software will compute and convert the Multispectral Satellite Imagery layer into a Normalized Difference Vegetation Index (NDVI) layer. NDVI helps to delineate which surface features have more chlorophyll i.e. the presence of healthy vegetation from those which have less / no chlorophyll (unhealthy vegetation, urban areas, barren land etc.). This Vegetation Density information is a vital component of the Risk Model as dense vegetation holds the Soil together whereas sparse or no Vegetation makes the Soil more susceptible to breaking-up i.e. more vulnerable to Landslides.


The Remap processing steps applied to all the three layers helps to 'classify' the pixel values into distinct categories.

I am asking the GIS software to convert all pixels in the Rainfall layer with values ranging from 0 to 15 into Category 1 (pixel value of 1 i.e.), from 15 to 20 into Category 2, and so on
Figure 8: I am asking the GIS software to convert all pixels in the Rainfall layer with values ranging from 0 to 15 into Category 1 (pixel value of 1 i.e.), from 15 to 20 into Category 2, and so on
Weighted Sum Geoprocessing Tool in ArcGIS Pro
Figure 9: Weighted Sum Geoprocessing Tool

The Weighted Sum part of the processing chain allows me to combine the pixel values of all the three Remapped layers into a new weighted value output layer.


In the model that I'm working on, I've assigned the NDVI layer a higher weightage (2 out of 4 i.e. 50% as depicted in Figure 9 on your right) whereas Slope and Rainfall remapped pixel values have been assigned the weightage of 25% each, respectively. This is because the researchers feel that, given the Wildfire, it is the Vegetation Density which will be the most important causative factor for a Landslide.


With the INT command, I are asking the GIS software to truncate the weighted pixel values into integers and using the Clip command next will allow me to to restrict the extent of the Weighted Value layer to the Burn Scar layer i.e. the area affected by Wildfire as there is no need to re-evaluate the previous Risk Model for the territory outside the Burn Scar which has the same surface characteristics as before.


Once I run the processing chain (Figure 7), the final output is generated (Figure 10 below) - the region affected by the Wildfire has been assigned Risk scores ranging from 7 to 15. The higher the scores (whiter pixels), higher the possibility of a Landslide affecting that place.

Landslide Risk Model Output
Figure 10: Landslide Risk Model Output
I am modifying the symbology to present the output in a better way. The darker shades of Red denote those areas that are more susceptible to Landslides and vice versa
Figure 11: I am modifying the symbology to present the output in a better way. The darker shades of Red denote those areas that are more susceptible to Landslides and vice versa

I hope you were able to appreciate how advanced technology is used to process multiple geospatial data layers into a Landslide Risk Model - the processing happens lightning-quick too. As I never forget to emphasize, the quality of geospatial data is as important as the software's capabilities.

 

2. Identifying at-Risk Stakeholders & Infrastructure from a Landslide Risk Model

Performing a small analysis here. A main road runs within the Wildfire affected are. I am highlighting those spots where the Landslide susceptibility scores are very high (>12). Larger the circle, higher the score, greater the Landslide risk there
Figure 12: Performing a small analysis to begin with . A road traverses the Wildfire-affected zone. I've asked GIS to mark those spots where the Risk scores are very high (>12). Larger the circle, higher the Score & greater the Landslide risk there

While I had demonstrated the process of creating a Landslide Risk Model in the previous workflow, now I shall use an already-prepared Risk Model over a new study area - Boulder County within Colorado, USA - to identify those stakeholders and infrastructure which are at most risk from Landslides, given a recent wildfire as well as given the fact that the a Landslide is most threatening not at the point of origin but when enough debris accumulate in a steep, downward flow especially after heavy rainfall.


Much thanks to Learn ArcGIS for the training resources

Just as the previous workflow output, the darkest shades in this Risk Model output have the highest risk and vice versa. Slope, Aspect (Orientation i.e. Direction of Slope) and Soil Type were the input parameters used to create this model
Figure 13: Just as the previous workflow output, the darkest shades in this Risk Model output have the highest risk and vice-versa. Slope, Aspect (Orientation i.e. Direction of Slope) and Soil Type were the input parameters used to create this model
I've filtered the model to display only the highest risk zones (dark-brown). Also added another data layer - that of Blocks (like Pin Codes). The larger the circle in the map, the higher the Population is of that Block
Figure 14: I've filtered the model to display only the highest risk zones (dark-brown). Also added another data layer - that of Blocks (like Pin Codes). The larger the circle in the map, the higher the Population is of that Block
Next, I've added 'Floodways' data layer to the map. The blue-shaded line segments depict where water accumulates and channels downward after rainfall
Figure 15: Next, I've added 'Floodways' data layer to the map. The blue-shaded line segments depict where water accumulates and channels downward after rainfall
I asked GIS to create a 200-metre Buffer around the Floodways. Technically termed as 'Flood Fringe' these would be the regions which are at risk of being inundated in the event of flooding after heavy rainfall
Figure 16: I asked GIS to create a 200-metre Buffer around the Floodways. Technically termed as 'Flood Fringe' these would be the regions which are at risk of being inundated in the event of flooding after heavy rainfall

Time for some Analysis.


Let me hover around a few cities falling within the Risk Model's extent....

The city of Lyons has a much lesser population. However, the Floodways pass the city exactly on top of major roads. The high-Landslide risk zone at the confluence of the floodway in the southern portion is of particular concern
Figure 17: The city of Boulder in Boulder County has several floodways in high population zones. The western edges are at the confluence of high-landslide risk zones as well. Undesirable and concerning.
The city of Lyons has a much lesser population. However, the Floodways pass the city exactly on top of major roads. The high-Landslide risk zone at the confluence of the floodway in the southern portion is of particular concern
Figure 18 The city of Lyons has a much lesser population. However, the Floodways pass the city exactly on top of major roads. The high-Landslide risk zone at the confluence of the floodway in the southern portion is of particular concern
The City of Louisville appears to be the least at-risk as the dense population blocks are clustered away from the Floodways and high-risk Landslide zones. The main roads are far away too, reducing the danger to vehicles & commercial infra
Figure 19: The City of Louisville appears to be the least at-risk as the dense population blocks are clustered away from the Floodways and high-risk Landslide zones. The main roads are far away too, reducing the danger to vehicles & commercial infra

Next, the 'Enrich Layer' geoprocessing tool helps me to add demographic and socio-economic data (acquired by the software developer) to the map. These new geospatial data attributes will help me to analyze the risk in a more in-depth manner.

Numerous categories of authoritative datasets are included in Esri's ArcGIS Online GIS platform
Figure 20: Numerous categories of authoritative datasets are included in Esri's ArcGIS Online GIS platform
By enriching the project with population data (at a more granular level than existing block-wise population information), I can determine those-at risk in a better way.
Figure 21: By enriching the project with population data (at a more granular level than existing block-wise population information), I can determine those-at risk in a better way.
Next, I've run a geoprocessing command which filters the view to depict only those Floodways which intersect high-risk Landslide Zones on its path. These yellow areas will be exposed to severe debris flooding in the event of a Landslide.
Figure 22: Next, I've run a geoprocessing command which filters the view to depict only those Floodways which intersect high-risk Landslide Zones on its path. These yellow areas will be exposed to severe debris flooding in the event of a Landslide.
Evidently, the entire yellow stretch in Fig. 21 is not at high risk though. The flow of debris tends to stop after a certain distance. Hence, I've visualized in green here those areas which are <1 km from the intersection of Landslide + Floodways layer
Figure 23: Evidently, the entire yellow stretch in Fig. 21 is not at high risk though. The flow of debris tends to stop after a certain distance. Hence, I've visualized in green here those areas which are <1 km from the intersection of Landslide + Floodways layer
High-risk zones enriched with multiple data-points
Figure 24: High-risk zones enriched with multiple data-points

These green zones (Figure 23) are the prime areas of concern. I proceed to enrich this layer with more data. Now, besides Population, I can study other relevant parameters such as Housing units, Property density, Road density, and number of Elderly persons in the highest at-risk areas. This will help the authorities to fine-tune their preventive measures for these zones.


To summarize, GIS helped me to expand the landslide risk model to identify stakeholders and infrastructure at the highest risk.

 

3. Rapid Detection of Landslide location using Radar Remote Sensing


While the two workflows discussed previously involved the generation of an Early Warning System (EWS) to identify high-Landslide Risk areas and determine the stakeholders and infrastructure who'd be potentially affected, in this third and final workflow, I'll demonstrate how to quickly detect where the Landslide has occurred using Sentinel-1's Synthetic Aperture Radar (SAR) Satellite Imagery.


In the era we live in, one can posit that Landslides are already being detected quickly - footage of flowing debris are quickly captured and circulated in the news and on social media. That being said, knowing the exact location of Landslide initiation and its exact extent is beyond the reach of a common man's handheld device (unless he/she has a Drone 😌). Moreover, many Landslides may not be spotted when there are no human settlements and infrastructure nearby and yet, they are equally necessary to be detected and studied.


Much thanks to RUS Copernicus for the training resources. Processing done on SNAP software


The process of detecting Landslides entails analyzing two SAR Imagery datasets over the same extent and close to each other in terms of timeline - one 'before' the suspected date/time of Landslide and another 'after' it. The next step involves observing discernible changes in the surface features to see if it demonstrates properties indicative of a Landslide - mainly changes in the shape and position of rocks i.e. Deformation.


Radar Imagery has useful characteristics which make it much more advantageous to use over Optical Imagery - it is able to penetrate Cloud cover and can can be acquired even during night-time due to the presence of Microwave Transmitter onboard the Satellite. Optical Imagery, on the other hand, is captured passively - source of illumination being Sunlight - and hence, it can only be acquired during the day-time and atmospheric hindrances such as Cloud cover impact its ability to capture accurate reflectance values of surface features.


The study area for this workflow is Fagraskógarfjall in Iceland where I plan to detect whether and where the Landslide has occured and its spread-

This is how raw Radar Imagery looks like (in VH band). Unappealing compared to natural-looking Optical Imagery. However, the underlying data is immense and using relevant geoprocessing tools, interesting phenomena can be detected
Figure 25: This is how raw Radar Imagery looks like (in VH band). Unappealing compared to natural-looking Optical Imagery. However, the underlying data is immense and using relevant geoprocessing tools, interesting phenomena can be detected

The processing steps, especially the second part as depicted in Figure 27, are much more technical than what was deployed in the previous two workflow demonstrations (in case you wish to know more about the second part which involves Differential Interferometry, refer my Deformation Mapping for Volcano Detection post), hence I have chosen not to explain it in detail in this already-very-large post.


Depiction of the first part of the complex processing chain - creation of a Coregistered product
Figure 26: Depiction of the first part of the complex processing chain - creation of a Coregistered product

The end-objective of this first part of the processing chain (as depicted in Figure 26 above) which contains several operations is to make the two SAR Satellite Imagery datasets (before & after the suspected Landslide incident) cleaner, comparable and analysis-worthy in order to subsequently detect Deformation.


Once the processing is done and a Coregistered product - i.e. the before and after processed outputs stacked in a single product to facilitate pixel-to-pixel comparison - is created, I can visualize a RGB Composite of the stacked product - as depicted in Figure 27 below. This depiction contains information from both the datasets in a single-view.

RGB Composite of the Coregistered imagery stack. The dark green pixels are a candidate for the Landslide location
Figure 27: RGB Composite of the Coregistered imagery stack. The dark green pixels are a candidate for the Landslide location

To explain what you are seeing in Figure 27 above, there are four colors predominantly - the Yellow pixels denote where both before and after Imagery datasets have the the same reflectance value (Intensity), the Red pixels denote where there is a higher reflectance value in the before Imagery dataset, the Green pixels denote where there is higher reflectance value in the after Imagery dataset and Black pixels denote where there is negligible / zero reflectance value i.e. no data - these are likely to be Water bodies as Water reflects the transmitted microwaves in the opposite direction i.e. away from the Satellite's receiver resulting in negligible / no backscatter received from that surface.


It is the Green pixels that are of particular relevance in this workflow as I will stand to benefit if I know where the surface features have significantly changed in the after Imagery dataset.

Raw after and before Imagery and Coregistered Imagery laid side-by-side. Higher intensity pixels (white triangle in the first image) are spotted in the 'after' July dataset. These correspond to the dark green pixels in the RGB composite of the coregistered stack (third image)
Figure 28: Raw after and before Imagery and Coregistered Imagery laid side-by-side. Higher intensity pixels (white triangle in the first image) are spotted in the 'after' July dataset. These correspond to the dark green pixels in the RGB composite of the coregistered stack (third image)

The dark green pixels in third image of Figure 27 is indicative that there has been a significant change in the after image from July 2019 - this could be the potential Landslide location and we must inspect it further to validate it.

 
Depiction of one part of the complex processing chain - Differential Interferometry / Interferometric Processing - involved in detecting Landslides from Radar Satellite Imagery (SAR)
Figure 29: Depiction of the second part of the complex processing chain - Differential Interferometry / Interferometric Processing - involved in detecting Landslides from Radar Satellite Imagery (SAR)

The next steps involves the creation of an Interferogram. Without explaining the technicalities, what I am essentially trying to do is to compare the change in surface features using Phase and Coherence information. These will help me to ascertain the presence of Deformation which will validate that a Landslide has occured at that spot.

Phase (Left) and Coherence (Right) visualization from the generated Interferogram at the suspected Landslide location
Figure 30: Phase (Left) and Coherence (Right) visualization from the generated Interferogram at the suspected Landslide location

The loss-of-Phase i.e. a disturbance in the rainbow pattern akin to throwing a pebble in calm waters as seen in Figure 30 above is indicative of Deformation.


Besides Landslides, Deformation is also highly relevant in Earthquake and Volcano detection workflows.


To explain the 'Coherence' visualization in Figure 30 above, pixels with very low Coherence values are Black in color and those with very high Coherence values are White in color. If the reflectance values (Intensity) of the same pixel (surface area) are nearly the same in the before and after Imagery datasets, then one would see a high Coherence value for that pixel, whereas if there is a significant deviation in the before and after reflectance values (Intensity) of the same pixel (surface area), as would be the case in the event of a landslide, then one would see a low Coherence value for that pixel. For our suspected site, low Coherence pixels are clearly seen to be clustered together. Given that loss-of-Phase was also observed at the exact same spot, it is doubly validating the presence of Deformation i.e. occurence of a Landslide.


From the Slider below, you can clearly see the Coherence output tallies with Google Earth Basemap for that location (which depicts the known location of the Fagraskógarfjall Landslide in Iceland).


To summarize, the Rapid Detection of Landslide location was validated using four observations-

a) Higher Intensity reflectances in the after Satellite Imagery Dataset,

b) RGB Composite of the Coregistered Stack confirming the same (Dark Green pixels),

c) Loss of Phase in the Coregistered Stack, &

d) Low Coherence in the Coregistered Stack


Each of these observations are independently needed to confirm the occurrence of Landslide at that particular location


Thus, you have witnessed how Remote Sensing helps in the rapid detection of Deformation - strong evidence that a Landslide has occured at that spot. Not only can this procedure be done quickly (processing in SNAP software is a breeze with an industry-grade computer system + the Satellite constellation's revisit time to the same location is also low at ~6 days), it is also cost-effective when compared to Ground-based, Instrument-intensive techniques of landslide detection.


That being said, I had tried to replicate this Landslide Detection workflow on known, recent Indian Landslide sites such as in Mizoram and Kerala states of India. After spending literally several days, my output didn't validate the occurrence of the Landslide at those locations. I suspect Sentinel-1's SAR Imagery works best on large Landslide zones as its spatial resolution is average (1 pixel = 100 sq. m). This in no way is a drawback of the Differential Interferometry technique - rather, I believe that other, higher resolution commercial Radar Imagery satellites would be better suited for the detection of Landslides with a smaller spread. Commercial service providers can direct their Satellite to the study area on-demand so this is an advantage as well in terms of acquiring the after / post-incident Imagery dataset in quick-time.


That being said, one must be wary of Imagery datasets obtained immediately prior and post the Landslide has occured - Landslides are preceded by heavy Rainfall and succeeded by heavy Flooding - Water, as I had mentioned earlier in this post, reflects the Microwave energy transmitted by the Satellite in the opposite direction i.e. away from its receiver. Therefore, both the before and after Imagery datasets would show very low reflectance values in the pixels where the Landslide has occured. This would hamper the accurate detection of Landslide because the methodology of Differential Interferometry for Deformation is based on detecting significant change in reflectances over the same surface feature over two or more time periods. I think this is the reason why my analysis for Mizoram and Kerala Landslides was not successful - both the regions are prone to heavy-rainfall virtually throughout the year and therefore, my selection of the before-incident Imagery hampered a positive outcome. Difficult to know when those locations had a continuous spell of no-rain days which would be ideal to obtain an Imagery dataset!


Hope you enjoyed the Landslide Hazard Mapping Workflows on Risk Modeling, Analysis & Detection covered in this post.

 

ABOUT US


Intelloc Mapping Services | Mapmyops.com is based in Kolkata, India and engages in providing Mapping solutions that can be integrated with Operations Planning, Design and Audit workflows. These include but are not limited to - Drone ServicesSubsurface Mapping ServicesLocation Analytics & App DevelopmentSupply Chain ServicesRemote Sensing Services & Wastewater Treatment. The services can be rendered pan-India, some even globally, and will aid an organization to meet its stated objectives especially pertaining to Operational Excellence, Cost Reduction, Sustainability and Growth.


Broadly, our area of expertise can be split into two categories - Geographic Mapping and Operations Mapping. The Infographic below highlights our capabilities.

Mapmyops (Intelloc Mapping Services) - Range of Capabilities and Problem Statements that we can help address
Mapmyops (Intelloc Mapping Services) - Range of Capabilities and Problem Statements that we can help address

Our 'Mapping for Operations'-themed workflow demonstrations can be accessed from the firm's Website / YouTube Channel and an overview can be obtained from this flyer. Happy to address queries and respond to documented requirements. Custom Demonstration, Training & Trials are facilitated only on a paid-basis. Looking forward to being of service.


Regards,

596 views
bottom of page