| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
Once the data variables are created from all data sources, these are used to calculate Risk score for each revenue circle.
IDS-DRR defines Risk as the combination of factors Flood Hazard, Vulnerability, Exposure and Government Response
Variables are used to model each of these factor scores at first. The factor scores are then used to model the comprehensive Risk Score.
sum_population and total_hhd variables are considered for the calculation. (add other variables as required)
Use min_max scaler to scale these variables for each month.
Sum the scaled variables of sum_population and total_hhd
Find mean and standard deviation of the sum calculated above.
Then find the exposure factor score using the following criteria:
exposure.py is the code that runs above steps.
Input -- MASTER_VARIABLES.csv
Output -- factor_scores_l1_exposure.csv
inundation_intensity_mean_nonzero, inundation_intensity_sum, drainage_density, max_rain and mean_rain variables are considered for the calculation. Other variables as required can be added.
Using the following table, calculate class for both these variables, for each revenue circle in each month.
hazard.py is the code that runs above steps.
Input -- MASTER_VARIABLES.csv
Output -- factor_scores_l1_hazard.csv
Losses and Damages data is generally not available for disaster risk assessments. But when available, DRR literature suggests that it be used in the assessment of Vulnerability of the region [3][4]
Assam State Disaster Management Authority (ASMDA) has been collecting data on flood related damages through a system called FRIMS. We used this damages data along with data on socio-economic vulnerability to assess disaster vulnerability of each revenue circle in Assam.
For this, we leveraged a method called Data Envelopment Analysis (DEA)
DEA basically takes certain input variables and output variables for each decision making unit (Revenue Circle, in our case). And then DEA calculates Efficiency for each decision making unit. We used this approach in the following way:
vulnerability.py is the code that runs above steps.
Input -- MASTER_VARIABLES.csv
Output -- factor_scores_l1_vulnerability.csv
Tender variables (total sum and SDRF tenders) variables are considered for the calculation. (Other variables as required can be added)
Calculate cumulative sum of money spent in each Financial Year.
Use min_max scaler to scale these variables for each month.
Sum all the scaled variables
Find mean and standard deviation of the sum calculated above.
Then find the government-response factor score using the following criteria:
govtresponse.py is the code that runs above steps.
Input -- MASTER_VARIABLES.csv
Output -- factor_scores_l1_government-response.csv
Once the factor scores are calculated for each revenue circle, we use these factor scores to calculate the comprehensive risk-score for each revenue circle. We use TOPSIS for this.
topsis.py is the Python module that implements TOPSIS.
topsis_riskscore.py is the code that uses the above module to calculate risk score.
TOPSIS requires a weight to each factor. We've considered the following weights based on literature survey
| Factor | Weight |
|---|---|
| Flood Hazard | 4 |
| Vulnerability | 2 |
| Government Response | 2 |
| Exposure | 1 |
Output -- risk_score_final.csv
| Back | FazBrowse Home | New Git URL |