-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
917 lines (675 loc) · 36.8 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
<!DOCTYPE html>
<html lang="" xml:lang="">
<head>
<title>Flood Risk Management Strategies for Kuala Lumpur, Malaysia</title>
<meta charset="utf-8" />
<meta name="author" content="Hansen Wiguna, Ahmad Farhan, Zirui Guo, Yao Wang, Tongmeng Xie" />
<script src="libs/header-attrs-2.19/header-attrs.js"></script>
<link rel="stylesheet" href="xaringan-themer.css" type="text/css" />
<link rel="stylesheet" href="custom.css" type="text/css" />
</head>
<body>
<textarea id="source">
class: center, middle, inverse, title-slide
.title[
# Flood Risk Management Strategies for Kuala Lumpur, Malaysia
]
.subtitle[
## ⚔<br/>Group: EarthSight
]
.author[
### Hansen Wiguna, Ahmad Farhan, Zirui Guo, Yao Wang, Tongmeng Xie
]
.institute[
### University College London
]
.date[
### 2023/02/23 (updated: 2023-03-22)
]
---
class: inverse, center, middle
# Outline
### 1. Context, Existing Regulations, & Problem Definition
### 2. Approach Methodology & Output
### 3. Project Management Overview
### 4. Conclusion
### 5. References
---
class: inverse, center, middle
# Context, Existing Regulations, & Problem Definition
---
# Malaysia's Disaster Risk Profile
- Malaysia had the highest percentage (67%) of the population exposed to floods among ASEAN Member States (between July 2012 and January 2019) as reported by ASEAN Coordinating Centre for Humanitarian Assistance on disaster management in March 2019.
- Monsoon and flash floods are the primary climate related natural disasters in the country.
- Nine percent of land area in Malaysia is flood prone and 4.8 million people live in areas at risk to flood.
- Worst floods in the past 30 years have occurred from 2003 onwards. The majority of natural disasters from 1998 to 2018 were natural disasters (38/51).
- Over the past 3 years, Malaysia has suffered from the heaviest floods in its history in over 2 decades, affecting states all across the nation.
---
#Flood Impacts
###Social
- Tens of thousands suffer from population displacement annually. Lives have also been lost.
###Economic
- Damages and losses across different sectors (public infrastructure, housing, business premises, private vehicles, agriculture,) amounting to £113 million / USD138.8 million / RM622.4 million in 2022 alone.
- Certain states suffer from heavier losses than others, impacting economic output and weakening their ability to recover.
###Environmental
- Exacerbates soil erosion, leading to an increase in landslides (another natural disaster Malaysia is prone to).
---
# Location Selection: Why Kuala Lumpur?
- Malaysia's capital city.
- Serves as the economic centre of Malaysia alongside the neighbouring state of Selangor (known as the Klang Valley). Damage to the federal territory and its surroundings impedes the country's economic output as most businesses are closest to the country's capital.
- KL is the most complete infrastructure-wise, will act as a benchmark for other states in terms of development goals.
We intend to introduce the proposed model across the rest of the Malaysian states if this preliminary project is deemed successful.
---
# Research Questions
- What is the current structure and practices in place to respond to natural disasters?
- What gaps can we identify within the aforementioned system?
- What current remote sensing methods are being used to acquire topographic information in Malaysia?
---
# Malaysia's Disaster Risk Reduction Framework
<div class="figure" style="text-align: center">
<img src="img/msian disaster risk framework.png" alt="flow chart" width="50%" />
<p class="caption">flow chart</p>
</div>
---
# Malaysia's Disaster Risk Reduction Framework
<div class="figure" style="text-align: center">
<img src="img/msian area of concern.png" alt="flow chart" width="50%" />
<p class="caption">flow chart</p>
</div>
---
# Gaps Identified Within Framework/Problem Definition
- Insufficient data
- Data is only sufficient enough for forecasting flood occurrence, not for the prediction of potential flood prone areas.
- Disjointed coordination between relevant stakeholders
- Framework is reactive instead of proactive, relevant authorities mobilise resources only after disaster has taken place.
- Incomplete stakeholder involvement
- Only disaster-related agencies are a part of the framework. Involvement should include all ministries affected by ramifications of natural disasters.
---
# Aims of Proposal
- To provide a more comprehensive disaster response mechanism using current remotely sensed methods.
- To ensure alignment of data-driven methods for disaster risk mitigation in line with goals set by ratified international agreements (COP26, SDG goals, C40 cities, Sendai Framework).
- To identify gaps for integration of proposed methods to existing disaster risk framework.
- To expand accessibility of findings beyond disaster response to incorporate involvement of all relevant departments and ministries.
---
class: inverse, center, middle
# Approach Methodology & Output
---
---
## Workflow and Methodology
- To make policies implementable
- Need to propose real analysis workflow
- Give prototypes illustrating how EO data and remote sensing can help
- Fit the workflow into the flood solution
- Work on the chaining of function modules and potential automisation of pipeline
- How can these facilitate minimising risks for people, governments and more
- How are information gaps closed
- How are losses prevented
- Identify persisting risks
---
## Flood Forecasting - A Quick Review
### The old-fashioned way - Hydrological model
Uses historical data on precipitation, runoff, and other factors to predict flood occurrences.
Relies on physical equations and mathematical representations of the water cycle, e.g.:
- Continuity Equation Balances water storage (∆S) with inflow (I) and outflow (O):
\begin{equation}
\Delta S = I - O
\end{equation}
- Runoff Estimation:
`$$Q = (P - Ia)^2 / (P - Ia + S)$$`
Where
- Q: direct runoff (depth)
- P: direct runoff (depth)
- Ia: initial abstraction, representing the water intercepted by vegetation, infiltration, and surface storage
- S: potential maximum retention (depth), depending on soil type, land use, antecedent moisture conditions
<div class="footnotes">
<small>
- Reference: US Army Corps of Engineers, Hydrologic Engineering Center. (n.d.). <a href="https://www.hec.usace.army.mil/software/hec-ras/" target="_blank">HEC-RAS</a>.
</small>
</div>
---
### The old-fashioned way - Hydrological model
Example of simulating watershed on a map of Digital Elevation Model (DEM)
- Continuity Equation
- Ensures the water balance
- Tracks the flow of water (through e.g. surface water, soil moisture and groundwater)
- Runoff Estimation:
- quantifying the amount of water
<video width="1440" height="300" autoplay>
<source src="vids/400SqMileWatershed.mpeg" type="video/mp4">
</video>
<div class="footnotes">
<small>
- Reference: US Army Corps of Engineers, Hydrologic Engineering Center. (n.d.). <a href="https://www.hec.usace.army.mil/software/hec-ras/" target="_blank">HEC-RAS</a>.
</small>
</div>
---
### The old-fashioned way - Hydrological model
DEM-based hydrological models
- Identify low-lying areas and floodplains in the urban landscape that are more susceptible to flooding.
- Inform decisions
- Planners: Floodplain zoning and land-use planning ( flood-resistant land uses, such as parks and recreational areas, to flood-prone regions.)
- Emergency response teams can prioritise levees and floodwalls construction in certain areas
- Design evacuation plans to minimise casualties
<div class="figure" style="text-align: center">
<img src="img/400SqMileWatershed - frame at 0m11s.jpg" alt="A frame slice of Watershed Simulation, Credit: US Army Corps of Engineers, Hydrologic Engineering Center. (n.d.). &lt;a href=&quot;https://www.hec.usace.army.mil/software/hec-ras/&quot; target=&quot;_blank&quot;&gt;HEC-RAS&lt;/a&gt;. https://doi.org/10.3390/w13243520 " width="25%" />
<p class="caption">A frame slice of Watershed Simulation, Credit: US Army Corps of Engineers, Hydrologic Engineering Center. (n.d.). <a href="https://www.hec.usace.army.mil/software/hec-ras/" target="_blank">HEC-RAS</a>. https://doi.org/10.3390/w13243520 </p>
</div>
---
class: inverse, center, middle
# Calling for a pipeline
---
### Persisting risks - Inflexibility in both time and space
### If ——
- We shift the area of interest
- Or, Progress from, say, 2022 to 2023
--
We have to redo watershed simulation with new data.
--
But we want to minimise avoidable repetitive human work, e.g., manual simulation of watershed for each date and each sub-zone of Kuala lumpur.
--
### So how do we improve temporal and spatial transferability and build a data pipeline?
--
### And what about automation?
---
### Machine-learning based prediction - A blackbox considering numerous factors
| Data Pipeline Step | Description |
| --- | --- |
| Data Acquirement | Object extraction of Multi-spetcral and Radar data for Kuala Lumpur -> Data fusion on object-based level -> Image classification to get elevation, slope, soil type, substrate, land cover, NDVI, land use, imperviousness, distance to river, and distance to road |
| Pre-processing | Standardize with EPSG:3168 coordinate system -> convert vector to raster maps -> clip to Kuala Lumpur boundarie -> resample to 1m resolution -> convert raster images to numerical data with 10m grid size using Rasterio |
| Feature Selection | Perform multicollinearity diagnosis test to exclude similar features -> Use features with VIF less than 10 in ANN models |
| Data Balancing | Balance data with oversampling and undersampling due to imbalanced flood risk distribution. Adjust non-flood areas (98%, 95%, 90% for 30-, 100-, and 1000-year events) and level 4 risk areas (0.01% and 0.06% for 30- and 100-year events) |
| Model Selection & Assessment | Apply NB, perceptron, ANN, and CNN models for 30-, 100-, and 1000-year flood events. Evaluate performance using following metrics |
---
## Flood prediction
### Metrics
Accuracy, F-beta score, and receiver operating characteristic (ROC) curve, as well as the oversampling and undersampling techniques used to address the issue of data imbalance.
---
## Flood prediction
### A comparison across models:
<div class="figure" style="text-align: center">
<img src="img/Prediction_Accuracy.png" alt="Credit: Li Z, Liu H, Luo C, Fu G. Assessing Surface Water Flood Risks in Urban Areas Using Machine Learning. Water. 2021; 13(24):3520. https://doi.org/10.3390/w13243520 " width="100%" />
<p class="caption">Credit: Li Z, Liu H, Luo C, Fu G. Assessing Surface Water Flood Risks in Urban Areas Using Machine Learning. Water. 2021; 13(24):3520. https://doi.org/10.3390/w13243520 </p>
</div>
---
class: inverse, middle
# How Can Flood Prediction Help Kuala Lumpur:
- ### How are information gaps closed
- ### How are loss prevented
- ### Identify persisting risks
---
## Flood Risk Management - Flood Prediction
Significant Savings in Case Studies
- European Union's Floods Directive: €460 million saved in avoided damages (2006-2015)
- Iowa Flood Center: $96 million saved in flood damage costs (2010-2015)
- Flood Forecasting Centre (UK): £1.2 billion saved in potential damages (2009-2014)
<div class="footnotes">
<small>
References: - European Environment Agency (2016). Flood risks and environmental vulnerability ↩
- Demir, I., & Krajewski, W. F. (2016). Towards an information system for the socially vulnerable groups during flood disasters ↩
- <a href="https://uiowa.edu/" target="_blank"->Environment Agency and Met Office (2015). Flood Forecasting Centre Five Year Review 2009-2014</a>.
</small>
</div>
---
## Are information gaps "closed"? - Managing probability
### What if ——
Due to a spatial mismatch between data scope and decision-making scope, we overlooked a location with a 99% chance of flooding and sent our response team to a place with only a 65% (what we consider to be the highest) likelihood of flooding.
--
In this scenario, the emergency response strategy fails. Therefore, keeping comprehensive data input and strategy output is essential.
--
### The trikiness of dealing with probability
--
- Should we allocate resources proportional to the probability of flood ocurrence?
--
- Or, should we design a response priority hierarchy considering both likelihood and potential harm?
--
- Decide with a function design? Human-added weights? Machine-learned weights?
---
class: inverse, center, middle
# Does Prediction Suffice?
---
## Is prediction enough for flood risk management?
### Pros and cons of ML-based flood prediction
| Pros | Cons |
| --- | --- |
| Mature tech-flow | Computation-intense |
| Promising accuracy | Prone to Data Flaws |
| Utilising ML/DL models | Cumbersome to deployment|
| Prediction Based on Abundant information | Data-expensive |
| Almost always generate outcome | But Untimely! |
---
class: inverse, center, middle
# Introducing Real-time Monitoring
---
## Flood risk management - Real-time monitoring
### Synthetic Aperture Radar (SAR)
- SAR: Active remote sensing technology that can penetrate clouds, operate day or night, and provide high-resolution imagery1
- Real-time flood monitoring: Timely and accurate information on flood extent, duration, and impact for emergency response and management
### Benefits of SAR-based flood monitoring
- Rapid assessment: Quick acquisition and processing of data, enabling faster response to flood events
- Wide-area coverage: Large-scale flood monitoring, even in remote or inaccessible areas
- All-weather capability: Reliable data collection, regardless of weather conditions or time of day
<div class="footnotes">
<small>
References: - NASA Jet Propulsion Laboratory (2021). ARIA Project. https://aria.jpl.nasa.gov/
</small>
</div>
---
<div class="figure" style="text-align: center">
<img src="img/SAR.webp" alt="FPM comparison with GSI aerial and Planet optical imagery for Fukushima. Credit: https://doi.org/10.1038/s41597-020-0443-5" width="70%" />
<p class="caption">FPM comparison with GSI aerial and Planet optical imagery for Fukushima. Credit: https://doi.org/10.1038/s41597-020-0443-5</p>
</div>
---
## Risks of Real-time Monitoring
- ### How real-time is real time?
- Does a 5-seconds delay in data transmission fail an essential decision-making?
--
- ### How to quantify tolerance thresholds in regards of delay, error and bias?
- A sharp cutoff or a fuzzy one?
--
- ### What degree of accuracy? Managing response time of
- Data acquirement, transmission and calculation
- Human-based decision-making
### Incurs extra cost. The estimation is almost always NOT deterministic.
---
class: inverse, center, middle
# When AIoT Comes In
---
## AIoT comes to aid
- Introducing AIoT (Artificial Intelligence of Things) can lead to more efficient, accurate, and timely flood prediction systems.
| MLp-Pros | ML-Cons | AIoT Solution |
| --- | --- | --- |
| Mature tech-flow | Computation-intense | Edge computing for localized data processing |
| Promising accuracy | Prone to Data Flaws | Diverse IoT data sources improve model robustness |
| Utilizing ML/DL models | Cumbersome to deployment | Scalable and modular IoT deployment |
| Prediction Based on Abundant information | Data-expensive | Edge computing and data compression reduce data costs |
| Almost always generate outcome | Untimely | Real-time data enables timely predictions and responses |
---
## AIoT comes to aid
Connects remote-sensing devices to the IoT network, enabling seamless data flow between
- Devices
- Edge computing nodes
- Cloud platforms
(Supprted by communication protocols such as MQTT, LoRaWAN, or Zigbee)
--
- To supplement EO data with real-time, hyperlocal data collected from IoT devices:
- Water level sensors
- Soil moisture sensors
- Weather stations
- To help capture local variations and enhances overall model performance, perform data fusion, i.e., combine:
- IoT-generated data
- EO data
- SAR imagery and other remote sensing datasets
---
## AIoT comes to aid
### Automatical iteration of models:
With ground truth data continuously provided by IoT devices, models are evaluated and calibrated by:
- Real-time ground truth data input from nature
- Feedback from decision-making models and human
Adaptive-learning models adjust and improve predictive capabilities over time, allowing for responding to
- Changing environmental conditions
- Extreme weather events
---
<div class="figure" style="text-align: center">
<img src="img/Iowa_alert.png" alt="Real-time water levels and stage heights with flood alert levels, and flood forecast. Credit: https://ifis.iowafloodcenter.org/ifis/" width="100%" />
<p class="caption">Real-time water levels and stage heights with flood alert levels, and flood forecast. Credit: https://ifis.iowafloodcenter.org/ifis/</p>
</div>
---
class: inverse, center, middle
# What Else Is Possible?
---
##Outlook - Automated decision-making
<div class="figure" style="text-align: center">
<img src="img/AIoT_workflow.png" alt="AIoT Architecture for auto-decision-making" width="68%" />
<p class="caption">AIoT Architecture for auto-decision-making</p>
</div>
---
##Outlook - Automated decision-making based on Real-time analytics
- Edge devices take in real-world data ->
- Edge computation nodes share computation tasks (pre-processing, training, validation, etc.) in parallel ->
- Predictions generated by ever-updating models are compared through and integrated at decision centre / A ensemble model is given ->
- Strategy coping with status quo is auto-generated
--
Vulnerable in that the system is very hackable (Data input, analysis, strategy output are all handled by AI):
- What if the edge devices in a crucial area goes offline?
- How to make sure the ensemble always weight towards maximum survival of people?
--
We emphasise the disaster awareness of human being: **All final decisions require expert review and human approval**. So the solution network can be scalable, elastic to damage, and serves the public's well-being correctly.
---
class: inverse, center, middle
# Assessing flood damage
---
## Assessing flood damage
### Overview
Considering that Malaysia does not have enough datasets for analyzing, in this case, we need to make sure that the datasets that we owned can satisfy the methodology we select.
Under this circumstance, we decide to use night light and census data to evaluate the number of people affected. The process is divided into three major steps: data pre-processing, model building and assessment.
.pull-left[
<img src="night/night.png" width="90%" style="display: block; margin: auto;" />
.small[
[Night light image of KL. Source: GEE](https://earth.google.com/web/@3.06161352,101.91436214,253.81115254a,616076.51047044d,35y,0h,0t,0r/data=CiQSIhIgMGY3ZTJkYzdlOGExMTFlNjk5MGQ2ZjgxOGQ2OWE2ZTc)
]
]
---
## Assessing flood damage
### Work flow
<div class="figure" style="text-align: center">
<img src="night/nor.png" alt="flow chart" width="100%" />
<p class="caption">flow chart</p>
</div>
---
## Assessing flood damage
### Data pre-processing
* First, the NPP-VIIRS night-light remote sensing data were resampled to 500m × 500m based on the administrative map with image cropping, Albers projection and nearest neighbor interpolation, and the negative areas were assigned a value of 0.
* Using the statistical volume method of radiation normalization to reducing the impact of cloud cover on night-light remote sensing imagery(Zhao et al. 2020).
---
## Assessing flood damage
### Work flow
<div class="figure" style="text-align: center">
<img src="night/eva.png" alt="flow chart" width="100%" />
<p class="caption">flow chart</p>
</div>
---
## Assessing flood damage
### Building model
Light index can indicate the dynamics population and economic development. To be specific, light density can represent the density of population, light area can represent the distribution of population, the tendency of urban expansion(He et al. 2022).
---
## Assessing flood damage
### Building model
`$$LD=(1/N)\sum_{i = 1}^{i=n}D N_{i}$$`
$$LA=\sum{i}, D N_{i}>1 $$
In the formula, `\(LD\)` is the average of light density, `\(LA\)` is the area of light and `\(DN_{i}\)` is the brightness of pixel.
`$$y=a\times R_{VIIRS} + b$$`
`$$y=a\times R_{VIIRS}^{2} + b\times R_{VIIRS} + c$$`
`\(y\)` is population related parameters, `\(R_{VIIRS}\)` is NPP-VIIRS night light brightness radiation value, a, b, c are constant items.
`$$P_{E}=\rho_{e} \times A_{e}$$`
`\(P_{E}\)` is the total affected population; `\(\rho_{e}\)` is the population density of the affected area; `\(A_{e}\)` is the affected area.
---
## Assessing flood damage
### Assessing model
Before and after the flood, the brightness of the lights changed significantly, and the damage of power lines, the collapse of buildings and evacuation of people caused the brightness of the lights to decrease significantly.
In that case, by comparing the images of light between before disaster and after disaster we can get the information of the disappear of light. Based on above formula and information, we can estimate how many people suffer the disaster and economic losses as well.
---
class: inverse, center, middle
#But how do we evaluate the accuracy of our model?#
---
## Assessing flood damage
### Assessing model
Before we apply we model, we can estimate the number of people firstly by using the before disaster's image and access the accuracy of our model.
`$$RE=\frac{R_{e}-R_{s}}{R_{s}}\times100\%$$`
`\(R_{e}\)` is the population of estimate, and `\(R_{s}\)` is the ture value of population.
| Relative margin of error | Level of accuracy |
| --- | --- |
|> 50%| High |
| 25% ~ 50% | Medium |
|< 25% | Low |
---
## Assessing flood damage
### Visulization
.pull-left[
<img src="night/visu1.jpg" width="100%" style="display: block; margin: auto auto auto 0;" />
]
.pull-right[
<img src="night/visu2.jpg" width="100%" style="display: block; margin: auto auto auto 0;" />
]
[Visualisation of the affected population and area in Guangxi](https://d-wanfangdata-com-cn.libproxy.ucl.ac.uk/periodical/zrzhxb202203009)
---
class: inverse, center, middle
# Project Management Overview
<div class="figure" style="text-align: center">
<img src="img/pm1.png" alt="flow chart" width="50%" />
<p class="caption">flow chart</p>
</div>
---
# Project Management Outline
.pull-left[
### 1. Phases
### 2. Project Plan
### 3. Risks and Mitigative Actions
### 4. Timeline
### 5. Resource Allocation
### 6. Value for Money
]
.pull-right[
<img src="img/pm2.png" width="80%" style="display: block; margin: auto;" />
]
---
## Project Management - Phases
<img src="img/Phases.jpeg" width="2551" style="display: block; margin: auto;" />
---
## Project Management - Project Plan / Work Package (1)
#### 1. Project initiation and stakeholder engagement (Month 1)
- Develop project charter
- Identify and engage with stakeholders (set questions)
- Establish project governance structure (National Disaster Management Agency)
#### 2. Data Collection and Analysis (Month 2-5)
- Collect relevant data, including night light data, satellite imagery, digital elevation models, and flood maps.
- Analyze historical flood data
- Preprocess the data to ensure that it is compatible with our analytical methods.
- Develop machine learning models, including naïve Bayes, perceptron, artificial neural networks (ANNs), and convolutional neural networks (CNNs).
- Train and evaluate the models using appropriate statistical metrics.
---
## Project Management - Project Plan / Work Package (2)
#### 3. Flood Risk Mapping and Mitigation Strategies (Month 6-8)
- Using DEM-based hydrological models to identify floodplain zoning (flood-resistant and flood-prone land uses)
- Produce flood risk maps using the machine learning models and interpret the results.
- Identify areas that are most vulnerable to flooding and propose potential mitigation strategies.
- Building flooding forecasting/prediction system
<img src="img/floodrisk.png" width="45%" style="display: block; margin: auto;" />
---
## Project Management - Project Plan / Work Package (3)
#### 4. Report Writing and Presentation (Month 9-10)
- Write a comprehensive report detailing the methodology and findings of the study.
- Prepare a presentation to share the results and recommendations with stakeholders.
- Showcasing and stakeholder meeting, follow up by refinement
#### 5. Monitor and Evaluate Effectiveness of Strategies (Month 11-12)
- Establish a monitoring and evaluation framework
- Conduct regular evaluations of the implemented strategies
- Provide recommendations for improvements
- Damage assessment (light data indicates disaster victims and economic loss)
---
## Project Management - Risks and Mitigative Actions
.pull-left[
1. Data Quality: Poor remote sensing data may lead to analysis errors. We will carefully assess our data sources and perform thorough quality checks during data preprocessing to reduce this risk.
2. Model Accuracy: Machine learning models may mispredict Malaysian flood risk. We'll use statistical metrics to assess our models' accuracy and adjust them to reduce this risk.
3. Stakeholder Engagement: Stakeholders may reject our findings and recommendations. We will engage stakeholders throughout the project and clearly communicate our results to mitigate this risk.
4. Human resources: clear contracts to avoid leaving mid-project.
]
.pull-right[
<img src="img/risk.png" width="80%" style="display: block; margin: auto;" />
]
---
## Project Management - Timeline
<img src="img/gantt2.jpeg" width="100%" style="display: block; margin: auto;" />
---
## Project Management - Resource Allocation (1)
.pull-left[
- Project Manager: Project managers oversee and deliver projects. To engage stakeholders, they will need project management, flood risk management, and good communication skills. This project will consume all their time.
- Data Analyst (2): The data analyst will collect, analyse, and map flood-prone areas using earth observation data. This project will consume all their time.
]
.pull-right[
<img src="img/manager.png" width="70%" style="display: block; margin: auto;" />
]
---
## Project Management - Resource Allocation (2)
.pull-left[
<img src="img/analyst.png" width="70%" style="display: block; margin: auto;" />
]
.pull-right[
- Flood Risk Management Expert/Analyst: The flood risk management expert will develop and implement flood risk management strategies, prioritise flood mitigation measures, and evaluate them regularly. This project will consume all their time.
- Stakeholder Engagement Specialist: The stakeholder engagement specialist will organise workshops, engage stakeholders, and provide project updates. This project will consume all their time.
]
---
## Project Management - Value for Money
The total budget for this project is £500,000 / USD613,515 / RM2.8 million. We will streamline the project to save money. To reduce costs, we will prioritise open-source software and free data sources. We will also create flood risk maps and mitigation strategies that the Malaysian government can use in its daily operations. This project will help Malaysian flood risk management, making it a good city investment.
<img src="img/cost.png" width="55%" style="display: block; margin: auto;" />
---
## Project Management - Deliverables
<img src="img/deliverable.png" width="85%" style="display: block; margin: auto;" />
---
## Conclusion
.pull-left[
#### Problem Definition
Nine percent of land area in Malaysia is flood prone and 4.8 million people live in areas at risk to flood.
#### Approach:
DEM-based hydrological models to identify floodplain zoning & apply NB, perceptron, ANN, and CNN models for prediction & light data for density
#### Output:
Floodplain & risk map, prediction model, and damage assessment
]
.pull-right[
#### Project Plan:
Multiple work packages with risk and mitigative actions, timeline, resource allocation, and value for money
#### Improvements:
From reactive to a more proactive approach by developing a prediction model, assessing damage in a more scalable way using earth observation data, and providing more extensive, transparent information to be used by a wider range of stakeholders.
]
---
## References
Aslam Perwaiz et al. (2020) ‘Disaster Risk Reduction in Malaysia: Status report 2020’. United Nations Office for Disaster Risk Reduction - Regional Office for Asia and Pacific Asian Disaster Preparedness Center.
‘CHA-Malaysia.pdf’ (no date). Available at: https://jfit-for-science.asia/wp-content/uploads/2019/11/CHA-Malaysia.pdf (Accessed: 19 March 2023).
Country: Malaysia (2023). Available at:
https://www.adrc.asia/management/MYS/mechanism_of_disaster_management_and_relief.html (Accessed: 20 March 2023).
Demir, I., & Krajewski, W. F. (2016). Towards an information system for the socially vulnerable groups during flood disasters. https://uiowa.edu/
Environment Agency and Met Office (2015). Flood Forecasting Centre Five Year Review 2009-2014. https://www.gov.uk/government/publications/flood-forecasting-centre-5-year-review-2009-to-2014
European Environment Agency (2016). Flood risks and environmental vulnerability. https://www.eea.europa.eu/publications/flood-risks-and-environmental-vulnerability
He, Yuanrong, Xiaorong Wang, Chunfang Chai, Deqing Yu, Yuanmao Zheng, and Dongkun Li. 2022. “Flood Damage Assessment and Visualization Based on NPP-VIIRS Nighttime Light Remote Sensing.” Journal of Natural Disaster, June, 13. https://doi.org/10.13577/j.jnd.2022.0309.
---
## References
IOWA FLOOD INFORMATION SYSTEM. https://ifis.iowafloodcenter.org/ifis/
Li, Z.; Liu, H.; Luo, C.; Fu, G. Assessing Surface Water Flood Risks in Urban Areas Using Machine Learning. Water 2021, 13, 3520. https://doi.org/10.3390/w13243520
‘Malaysia: Disaster Management Reference Handbook (June 2019)’ (2019). Center for Excellence in Disaster Management and Humanitarian Assistance.
Malaysia - Vulnerability | Climate Change Knowledge Portal (no date). Available at: https://climateknowledgeportal.worldbank.org/country/malaysia/vulnerability (Accessed: 23 February 2023).
NASA Jet Propulsion Laboratory (2021). ARIA Project. https://aria.jpl.nasa.gov/
Tay, C.W.J., Yun, SH., Chin, S.T. et al. Rapid flood and damage mapping using synthetic aperture radar in response to Typhoon Hagibis, Japan. Sci Data 7, 100 (2020). https://doi.org/10.1038/s41597-020-0443-5'
ZHA0 N，LIU Y，Hsu F C，et a1．Time series analysis of VIIRS—DNB nighttime 1ights imagery for change detection in urban areas：A case study of devastation in Puerto Rico from hurricanes Irma and Maria[J]．Applied Geography，2020，120(1)：102222
</textarea>
<style data-target="print-only">@media screen {.remark-slide-container{display:block;}.remark-slide-scaler{box-shadow:none;}}</style>
<script src="https://remarkjs.com/downloads/remark-latest.min.js"></script>
<script>var slideshow = remark.create({
"highlightStyle": "github",
"highlightLines": true,
"ratio": "16:9",
"countIncrementalSlides": false
});
if (window.HTMLWidgets) slideshow.on('afterShowSlide', function (slide) {
window.dispatchEvent(new Event('resize'));
});
(function(d) {
var s = d.createElement("style"), r = d.querySelector(".remark-slide-scaler");
if (!r) return;
s.type = "text/css"; s.innerHTML = "@page {size: " + r.style.width + " " + r.style.height +"; }";
d.head.appendChild(s);
})(document);
(function(d) {
var el = d.getElementsByClassName("remark-slides-area");
if (!el) return;
var slide, slides = slideshow.getSlides(), els = el[0].children;
for (var i = 1; i < slides.length; i++) {
slide = slides[i];
if (slide.properties.continued === "true" || slide.properties.count === "false") {
els[i - 1].className += ' has-continuation';
}
}
var s = d.createElement("style");
s.type = "text/css"; s.innerHTML = "@media print { .has-continuation { display: none; } }";
d.head.appendChild(s);
})(document);
// delete the temporary CSS (for displaying all slides initially) when the user
// starts to view slides
(function() {
var deleted = false;
slideshow.on('beforeShowSlide', function(slide) {
if (deleted) return;
var sheets = document.styleSheets, node;
for (var i = 0; i < sheets.length; i++) {
node = sheets[i].ownerNode;
if (node.dataset["target"] !== "print-only") continue;
node.parentNode.removeChild(node);
}
deleted = true;
});
})();
// add `data-at-shortcutkeys` attribute to <body> to resolve conflicts with JAWS
// screen reader (see PR #262)
(function(d) {
let res = {};
d.querySelectorAll('.remark-help-content table tr').forEach(tr => {
const t = tr.querySelector('td:nth-child(2)').innerText;
tr.querySelectorAll('td:first-child .key').forEach(key => {
const k = key.innerText;
if (/^[a-z]$/.test(k)) res[k] = t; // must be a single letter (key)
});
});
d.body.setAttribute('data-at-shortcutkeys', JSON.stringify(res));
})(document);
(function() {
"use strict"
// Replace <script> tags in slides area to make them executable
var scripts = document.querySelectorAll(
'.remark-slides-area .remark-slide-container script'
);
if (!scripts.length) return;
for (var i = 0; i < scripts.length; i++) {
var s = document.createElement('script');
var code = document.createTextNode(scripts[i].textContent);
s.appendChild(code);
var scriptAttrs = scripts[i].attributes;
for (var j = 0; j < scriptAttrs.length; j++) {
s.setAttribute(scriptAttrs[j].name, scriptAttrs[j].value);
}
scripts[i].parentElement.replaceChild(s, scripts[i]);
}
})();
(function() {
var links = document.getElementsByTagName('a');
for (var i = 0; i < links.length; i++) {
if (/^(https?:)?\/\//.test(links[i].getAttribute('href'))) {
links[i].target = '_blank';
}
}
})();
// adds .remark-code-has-line-highlighted class to <pre> parent elements
// of code chunks containing highlighted lines with class .remark-code-line-highlighted
(function(d) {
const hlines = d.querySelectorAll('.remark-code-line-highlighted');
const preParents = [];
const findPreParent = function(line, p = 0) {
if (p > 1) return null; // traverse up no further than grandparent
const el = line.parentElement;
return el.tagName === "PRE" ? el : findPreParent(el, ++p);
};
for (let line of hlines) {
let pre = findPreParent(line);
if (pre && !preParents.includes(pre)) preParents.push(pre);
}
preParents.forEach(p => p.classList.add("remark-code-has-line-highlighted"));
})(document);</script>
<script>
slideshow._releaseMath = function(el) {
var i, text, code, codes = el.getElementsByTagName('code');
for (i = 0; i < codes.length;) {
code = codes[i];
if (code.parentNode.tagName !== 'PRE' && code.childElementCount === 0) {
text = code.textContent;
if (/^\\\((.|\s)+\\\)$/.test(text) || /^\\\[(.|\s)+\\\]$/.test(text) ||
/^\$\$(.|\s)+\$\$$/.test(text) ||
/^\\begin\{([^}]+)\}(.|\s)+\\end\{[^}]+\}$/.test(text)) {
code.outerHTML = code.innerHTML; // remove <code></code>
continue;
}
}
i++;
}
};
slideshow._releaseMath(document);
</script>
<!-- dynamically load mathjax for compatibility with self-contained -->
<script>
(function () {
var script = document.createElement('script');
script.type = 'text/javascript';
script.src = 'https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-MML-AM_CHTML';
if (location.protocol !== 'file:' && /^https?:/.test(script.src))
script.src = script.src.replace(/^https?:/, '');
document.getElementsByTagName('head')[0].appendChild(script);
})();
</script>
</body>
</html>