Filter by:
7 results matching current filter selection Apply or Reset ?
  • Netherlands Red Cross
    Updated August 15, 2017 | Dataset date: Jul 14, 2017
    A crude version of the INFORM risk-framework is applied to Enumeration Areas (which is unofficial, but is deeper than admin-3), in Southern Malawi. This is done specifically for area selection regarding the ECHO2 project in 3 TA's: Mwambo (Zomba district), Makhwira (Chikwawa district) and Ndamera (Nsanje district). Scope Enumeration areas are retrieved from http://www.masdap.mw/layers/geonode%3Aeas_bnd. These are used, because we want to prioritize on a deeper level than Traditional Authority (admin-3) level, and there are no other official boundaries available. The dataset in principle data for the whole of Malawi, but contains 4 filters, which can be applied, which are the following: Filter_south: this filters out only the South of Malawi, for which the drough and flood analysis has been carried out (see details below). Filter_district: contains all EA's from the 3 pre-identified districts Zomba, Chikwawa and Nsanje. Filter_TA: contains all EA's from the 3 pre-identified TAs Mwambo, Makhwira and Ndamera. Filter_GVH: there are also 44 Group Village Heads pre-identified for the project. As these GVH's are points on a map, all EA's are selected here which have a GVH within their boundaries or very close to their boundaries. INFORM risk-framework The INFORM framework (http://www.inform-index.org/) is applied to assess risk per community, which is considered the main criteria for prioritization within the project. Because of low data availability we apply a crude version for now, with only some important indicators of the framework actually used. Since we feel that these indicators (see below) still constitute together a current good assessment of risk, and we want to stimulate the use and acceptance of the INFORM-framework, we choose to use it anyway. The INFORM risk-score consists of 3 main components: hazards, vulnerability and coping capacity. Hazard: For hazard we focus - in line with the ECHO2 project - on floods and droughts only. Analysis has been carried out (see more details below), to determine flood and drought risk on a scale from 0-10 with a resolution of 250meter grid cells. This has subsequently been aggregated to Enumeration Areas, by taking a population-weighted average. Thereby taking into account where people actually live within the Enumeration Areas. (Population data source: Worldpop: http://www.worldpop.org.uk/data/summary/?doi=10.5258/SOTON/WP00155) Vulnerability: Vulnerability is operationalized here through poverty incidence. Poverty rate (living below $1.25/day) is retrieved from Worldpop (http://www.worldpop.org.uk/data/summary/?doi=10.5258/SOTON/WP00157) and again transformed from a 1km resolution grid to Enumeration Areas through a population-weighted average. Lack of Coping capacity: Coping capacity is measured through traveltimes to various facilities, namely traveltime to nearest hospistal, traveltime to nearest trading centre and traveltime to nearest secondary school. Together these are all proxies of being near/far to facilities, and thereby an indicator of having higher/lower coping capacity. See https://510.global/developing-and-field-testing-a-remoteness-indicator-in-malawi/ for more information on how these traveltimes were calculated and validated. Use All features are stored in a CSV, but can easily be joined to the geographic shapefile to make maps on EACODE. Flood and Drought calculations Drought layer The drought risk map was created by analyzing rainfall data in the past 20 years using standard precipitation index (SPI) , which is a widely used index in drought analysis. Based on SPI6 values for the period October-march, which is the main rainy season in Malawi. Each pixel is classified to drought or no drought for each year based on SPI6 values, drought year if SPI value for a pixel is less than -1. Next, relative frequency is calculated, the number of times drought has occurred in the considered 20 year period. This frequency is then converted to probability of drought occurrence in a given year. We validated our analysis by comparing NDVI values for the drought year against long term average values. Flood layer To identify flood moments in Malawi Landsat imagery was studied (1984-2017). Floods were clearly evidenced in 9 dates. For the clearest and most representative layers the mNDWI (modified Normalized Water Index) was calculated. The index mNDWI (McFeeters 1996; Xu 2006) for Landsat bands is calculated as follows: (b2GREEN-b7MIRSWIR/b2GREEN+b7MIRSWIR). In this variation of the index the higher values are the wettest. A threshold was applied to the mNDWI to separate flood from non-flood or water from non-water pixels. The resulting layers were aggregated and the final stretched from 0-10, where 0 are the pixels where no flood is expected while pixels with 10 are where most frequent flood has been evidenced and therefore expected. The largest flood was observed in 2015, as the scenes were cloudy the flood extent was manually interpreted from several scenes. The evidenced flood dates are: 29 Feb. 1988 low flood, 19 march 1989, 17 march 1997, Feb 1998, March 1999 low flood, 2001 since February 16 until end of April, 2007 17 February since early Feb., 2008 Feb. medium flood, 2015 January – March. The water bodies in this layer are not represented and have a value of 0 like the rest of land where flood is absent.
  • Netherlands Red Cross
    Updated June 8, 2017 | Dataset date: Jun 1, 2017
    Product This priority index was derived by combining a detailed flood extent mapping with detailed human settlement geo-data. Both sources were combined to produce the location and magnitude of population living in flooded areas. This was subsequently aggregated to admin-4 areas (GND) as well as admin-3 areas (DS divisional). The flood extent mapping was derived in turn by combining two sources: Flood extent maps could be produced rather faster using satellite imageries captured by either optical sensors or Synthetic Aperture Radar (SAR) sensors. In most places flood is cause by heavy rainfall which means in most cases cloud is present, this is a limitation for optical sensors as they can’t penetrate clouds. Radar sensors are not affected by cloud, which make them more useful in presence of cloud. In This analysis we analyzed sentinel2 optical image from May 28th and Sentinel 1 SAR image from May 30th. Then we combine the two results adding up the flood extents. Main cloud covered areas and permanent water bodies are removed from the flood extent map using the Sentinel 2 cloud mask. The scale/resolution of the flood extent map is 30mts where as the permanent water body map has 250m scale resolution. This will introduce some discrepancy: part of flood extent map could be permanent water body. Scope Analysis focused on 4 districts in South-West Sri Lanka based on news reports (https://www.dropbox.com/s/n0qdqe7qfgq6fyv/special_situation.pdf?dl=0). Based on the admin-3-level analysis, highest percentages of population living in flooded areas were seen in Matara district. Admin-4 level analysis concentrated only on Matara district for that reason. Caveats The dataset is showing percentage flooded. The data has not yet been corrected for small populations. We believe the product is currently pointing to the high priority areas. In the shp or csv files the user of this data could easily correct for small populations, if there is a wish to target on the amount of people affected. Data used from partners The human settlement data was retrieved from http://ciesin.columbia.edu/data/hrsl/. Facebook Connectivity Lab and Center for International Earth Science Information Network - CIESIN - Columbia University. 2016. High Resolution Settlement Layer (HRSL). Source imagery for HRSL © 2016 DigitalGlobe. Accessed 01-06-2017. The Radar imagery analysis was done by NASA JPL, whose input in this product has been crucial. Visualization An example map is available here: http://bit.ly/SriLankaFloodMap Linked data Admin boundaries 3 and 4 can be found here (link on OBJECT_ID): https://data.humdata.org/group/lka?q=&ext_page_size=25&sort=score+desc%2C+metadata_modified+desc&tags=administrative+boundaries#dataset-filter-start How to use The ratio column in the SHPs or CSVs can be multiplied by 100 to get the percentage of flooding in the area.
  • Netherlands Red Cross
    Updated May 19, 2017 | Dataset date: Nov 22, 2016
    Blog post about this prediction can be found here: http://bit.ly/2fWF2jq The predicted priority index of Typhoon Haima is produced by a machine learning algorithm that was trained on four past typhoons: Haiyan, Melor, Hagupit and Rammasun. It uses base line data for the whole country, combined with impact data of windspeeds and rains, and trained on counts by the Philippine government on people affected and houses damaged. First run The Priority Index is a 1-5 classification that can be used to identify the worst hit areas: those that need to be visited for further assessments or support first. Second run The model now predicts two things: a weighted index between partially damaged and completely damaged, where partially damaged is counted as 25% of the completely damaged. This has proven to give he highest accuracy. the precentage of total damage (damaged houses versus all houses) The absolute number of houses damaged / people affected is insufficiently validated at the moment, and should just be used for further trainng and ground-truthing. Data sources: Administrative boundaries (P_Codes) - Philippines Government; Published by GADM and UN OCHA (HDX) Census 2015 (population) - Philippine Statistics Authority; received from UN OCHA (HDX) Avg. wind speed (km/h) - University College London Typhoon path - University College London Houses damaged - NDRRMC Rainfall - GPM Poverty - Pantawid pamilyang pilipino program (aggregated) For the second run of the algorithm we also included: Roof and wall materials New geographical features The result of different models can be found in the file 'Typhoon Haima - performance of different models - second run.csv' A note on how to interpret this. date running date alg_date same alg_model name of the algorithm used alg_predict_on name of the learning variable alg_use_log i s the learning variable transformed in log code_version version of the learn.py code All the columns with feat_ indicates the importance of that feature, if not present that feature was not used. learn_matrix name of the learning matrix with the 5 typhoons run_name unique run name (pickle files and csv files have this name for this model) typhoon_to_predict name of a new typhoon to predict val_accuracy accuracy based on 10 categories of damage 0% 10% 20% … val_perc_down perc of underpredicted categories val_perc_up perc of overpredicted categories Val_best_score best r2 score Val_stdev_best_score error on best score based on the CV Val_score_test r2 score on the test set (this should be around +- 5% of the previus number to not overfit Val_mean_error_num_houses average error on the number of houses val_median_error_num_houses median val_std_error_num_houses std deviation of the errors (lower is better) Algorithm developed by 510.global the data innovation initiative of the Netherlands Red Cross.
    • XLSX
    • CSV
    • 400+ Downloads
    • This dataset updates: Never
  • OCHA Ethiopia
    Updated April 4, 2017 | Dataset date: Feb 18, 2016
    The table shows prioritization for WASH, ES/NFI clusters, Hotspot classification and relief food beneficiaries by woreda (admin level 3). The relief food beneficiaries are based on meher assessment findings.
    • XLS
    • 200+ Downloads
    • This dataset updates: Every three months
  • Netherlands Red Cross
    Updated February 7, 2017 | Dataset date: Dec 26, 2016
    This dataset contains: windspeeds of Typhoon Nina rainfall of Typhoon Nina Priority Index of Typhoon Nina The predicted priority index of Typhoon Nina is produced by a machine learning algorithm that was trained on five past typhoons: Haiyan, Melor, Hagupit and Rammasun and Haima, It uses base line data for the whole country, combined with impact data of windspeeds and rains, and trained on counts by the Philippine government on houses damaged and completely destroyed. The output is a weighted index between partially damaged and completely damaged, where partially damaged is counted as 25% of the completely damaged. This has proven to give he highest accuracy. The absolute number of houses damaged / people affected is insufficiently validated at the moment, and should just be used for further trainng and ground-truthing. Scoring The model has an best r2 score of 0.794933727 and an accuracy of 0.699470899 Data sources: Administrative boundaries (P_Codes) - Philippines Government; Published by GADM and UN OCHA (HDX) Census 2015 (population) - Philippine Statistics Authority; received from UN OCHA (HDX) Avg. wind speed (mph) - University College London Typhoon path - University College London Houses damaged - NDRRMC Rainfall - GPM Poverty - Pantawid pamilyang pilipino program (aggregated) Roof and wall materials New geographical features All the columns with feat_ indicates the importance of that feature, if not present that feature was not used. learn_matrix name of the learning matrix with the 5 typhoons run_name unique run name (pickle files and csv files have this name for this model) typhoon_to_predict name of a new typhoon to predict val_accuracy accuracy based on 10 categories of damage 0% 10% 20% … val_perc_down perc of underpredicted categories val_perc_up perc of overpredicted categories Val_best_score best r2 score Val_stdev_best_score error on best score based on the CV Val_score_test r2 score on the test set (this should be around +- 5% of the previus number to not overfit Val_mean_error_num_houses average error on the number of houses val_median_error_num_houses median val_std_error_num_houses std deviation of the errors (lower is better) Algorithm developed by 510.global the data innovation initiative of the Netherlands Red Cross.
  • BRC Maps Team
    Updated October 20, 2016 | Dataset date: Mar 19, 2015
    An index to target those in poverty and affected by cyclone Pam. Methodology and contact available on tab in spreadsheet.
  • BRC Maps Team
    Updated October 20, 2016 | Dataset date: Apr 8, 2015
    A priority index created for use in the response to Typhoon Maysak using a combination of pre-disaster and disaster data
    • XLSX
    • 100+ Downloads
    • This dataset updates: Never