Monitoring glacier lake outburst locations in Norway using Sentinel 1- and -2

Abstract ID: 3.10926 | Accepted as Talk | Talk/Oral | TBA | TBA

Liss Marie Andreassen (0)
Enzenhofer, Ursula (1), Kjøllmoen, Bjarne, Lappe, Ronja (1), Elvehøy, Hallgeir
Liss Marie Andreassen ((0) Section for Glaciers, Ice and Snow, Norwegian Water Resources and Energy Directorate, Middelthunsgate 29, 0368, Oslo, Not Applicable, PK)
Enzenhofer, Ursula (1), Kjøllmoen, Bjarne, Lappe, Ronja (1), Elvehøy, Hallgeir

(0) Section for Glaciers, Ice and Snow, Norwegian Water Resources and Energy Directorate, Middelthunsgate 29, 0368, Oslo, Not Applicable, PK
(1) Norwegian University of Science and Technology, Trondheim, Norway

(1) Norwegian University of Science and Technology, Trondheim, Norway

Categories: Hazards, Water Resources
Keywords: glacier, glacier lake, Sentinel, field observations

Categories: Hazards, Water Resources
Keywords: glacier, glacier lake, Sentinel, field observations

A jøkulhlaup or Glacier Lake Outburst Flood (GLOF) is a sudden release of water from a glacier lake. In mainland Norway more than 160 GLOF events from 30 glacier lake locations are registered. The water source can be a glacier-dammed lake, a pro-glacial moraine-dammed lake or water stored within, under or on the glacier. One example is Nedre Demmevatn, a glacier dammed lake at the north side of the outlet glacier Rembesdalskåka, Hardangerjøkulen. Catastrophic jøkulhlaups occurred in 1893 og 1937 and led to construction of drainage tunnels to avoid the outburst floods. Since 2014 annual GLOFs have occurred due to the glacier thinning. Repeat glacier lake inventories from satellite data has revealed a growth in glacier lakes in the recent decades due to glacier retreat. About 40 glacier lakes with potential for GLOFs are currently monitored using Sentinel-1 and -2 data. In this study we give an overview of registered GLOF events in Norway and we present ongoing field investigations on Nedre Demmevatnet that are carried out to better understand the processes. We also discuss possibilities for improving standard mapping techniques for glacier lakes. Manual or semi automatic methods are commonly used, often requiring labour-intensive post-processing to improve accuracy. Recent advancements in machine learning offer promising alternatives, enabling more efficient and accurate mapping by integrating multiple input data sources. We present a fully automated workflow, implemented in Google Earth Engine and Python, that is expected to improve the efficiency and reproducibility of glacier lake mapping. A comparison of the results with Norway’s most recent glacier lake inventory from 2018/19 shows further glacier retreat with associated lake expansion and formation of new lakes.

N/A
NAME:
TBA
BUILDING:
TBA
FLOOR:
TBA
TYPE:
TBA
CAPACITY:
TBA
ACCESS:
TBA
ADDITIONAL:
TBA
FIND ME:
>> Google Maps

Limits: min. 3 words, max. 30 words or 200 characters

Choose the session you want to submit an abstract. Please be assured that similar sessions will either be scheduled consecutively or merged once the abstract submission phase is completed.

Select your preferred presentation mode
Please visit the session format page to get a detailed view on the presentation timings
The final decision on oral/poster is made by the (Co-)Conveners and will be communicated via your My#IMC dashboard

Please add here your abstract meeting the following requirements:
NO REFERNCES/KEYWORDS/ACKNOWEDGEMENTS IN AN ABSTRACT!
Limits: min 100 words, max 350 words or 2500 characters incl. tabs
Criteria: use only UTF-8 HTML character set, no equations/special characters/coding
Copy/Paste from an external editor is possible but check/reformat your text before submitting (e.g. bullet points, returns, aso)

Add here affiliations (max. 30) for you and your co-author(s). Use the row number to assign the affiliation to you and your co-author(s).
When you hover over the row number you are able to change the order of the affiliation list.

1
1

Add here co-author(s) (max. 30) to your abstract. Please assign the affiliation(s) of each co-author in the "Assigned Aff. No" by using the corresponding numbers from the "Affiliation List" (e.g.: 1,2,...)
When you hover over the row number you are able to change the order of the co-author list.

1
2
3
4
1
1
2
3
4
1
Close