DOI: 10.5281/zenodo.7930539
title: Natural Disaster Trends

description: <strong>Data fields</strong> <code>Disaster_Group</code>: EM-DAT stores different types of disasters: natural, technological and complex. The dataset has been filtered to contain only natural disasters so this column is "Natural" for all rows but kept for compatibility reasons. <code>Disaster_Subgroup</code>: Every natural disaster is assigned to one of the following six subgroups: <em>Biological, Geophysical, Climatological, Hydrological, Meteorological and Extra-terrestrial</em> to describe the type of natural disaster. No missing values are present for this attribute. <code>Disaster_type</code>: For every natural disaster event one main disaster type is identified. If two or more disasters are related because they are consequences of each other, then this information is encoded in the attributes <code>Associated_Dis</code> and <code>Associated_Dis2</code>. No missing values are present for this attribute. <code>Disaster Sub-Type</code>: Subdivision related to the attribute <code>Disaster_type</code> so that a the disaster type Storm can be further classified as tropical, extra-tropical or convective storm. <code>Disaster Sub-Sub Type</code>: Any appropriate sub-division of the disaster sub-type (not applicable for all disaster sub-types). Types of natural disasters could be further broken down using two more categories which would be available in the database. For example, the Disaster type <em>Storm</em> could be further subdivided into <em>Tropical storm</em>, <em>Extra-tropical storm</em> or <em>Convective storm</em>. Even a further subdivision of the category <em>Convective storm</em> would be possible. Since the analysis is aimed at detecting trends on a high level, the classification of each event based on the attributes <code>Disaster_Subgroup</code> and <code>Disaster _Type</code> was considered sufficient and the further subdivisions into <code>Disaster sub-type</code> and <code>Disaster Subsubtype</code> is only intended to be considered for detailed analysis. The full table is shown in the Appendix. <code>Associated_Dis</code>: Secondary event triggered by a natural disaster (i.e. Landslide for a flood, explosion after an earthquake, ...) <code>Associated_Dis2</code>: Another secondary event triggered by a natural disaster. (i.e. Landslide for a flood, explosion after an earthquake, ...) Example: If a tsunami is triggered by an earthquake, then the attribute <code>Disaster_Type</code> would be <em>Earthquake</em>, the attribute <code>Disaster_Subtype</code> would be <em>Ground movement</em> and the attribute <code>Associated_Dis</code> would be <em>Tsunami/Tidal wave</em>. <code>Country</code>: The country in which the disaster has occurred or had an impact. If a disaster has affected more than one country, a seperate entry is created in the database for each country affected. No missing values are present for this attribute. <code>ISO</code>: Unique 3-letter code for each country defined by ISO 3166. No missing values are present for this attribute. <code>Region</code>: The region to which the country belongs, based on the UN regional division. No missing values are present for this attribute. <code>Continent</code>: The continent to which the country belongs. No missing values are present for this attribute. <code>Start_Year</code>: The year when the disaster occurred. No missing values are present for this attribute. <code>End Year</code>: The year when the disaster ended. No missing values are present for this attribute. For sudden-impact disasters also the month and the day are well defined and available. For disaster situations developing gradually over a longer time period (i.e. drought) with no specific start date the day attribute is empty. For our questions the exact date plays a subordinate role and therefore the year of the beginning of the disaster is completely sufficient for our analysis. <code>Total_Deaths</code>: Number of people who lost their life because the event happened plus the number of people whose whereabouts since the disaster are unknown, and presumed dead based on official figures. Missing values present for approx. 25% of all events. <code>No_Affected</code>: Number of people which requiring immediate assistance during an emergency situation. The indicator affected is often reported and is widely used by different actors to convey the extent, impact, or severity of a disaster in non-spatial terms. In case that no values for the attribute <code>Total_Deaths</code> are available this attribute could be used as a proxy. <strong>Appendix</strong> <strong>Disaster </strong> <strong>Group</strong> <strong>Disaster </strong> <strong>Sub-Group</strong> <strong>Disaster </strong> <strong>Type</strong> <strong>Disaster </strong> <strong>Sub-Type</strong> <strong>Disaster </strong> <strong>Sub-Sub Type</strong> <strong>Natural</strong> Geophysical Earthquake Ground movement Tsunami Volcanic activity Ash fall Lahar Pyroclastic flow Lava flow Mass Movement Meteorological Storm Tropical storm Extra-tropical storm Convective storm Derecho Hail Lightning/thunderstorm Rain Tornado Sand/dust storm Winter storm/blizzard Storm/surge Wind Severe Storm Extreme Temperature Cold wave Heat Wave Severe winter conditions Snow/ice Frost/freeze Fog Hydrological Flood Coastal flood Riverine flood Flash flood Ice jam flood Landslide Avalanche (snow, debris, mudflow, rock fall) Wave action Rogue wave Seiche Climatological Drought Drought Glacial Lake outburst Wildfire Forest fires Land fire: Brush, bush, pasture Biological Epidemic Viral diseases Bacterial diseases Parasitic diseases Fungal diseases Prion diseases Insect Infestation Locust Grasshopper Animal accident Extra-terrestrial Impact Airburst Space weather Energic particles Geomagnetic storm Shockwave Sourced from https://public.emdat.be/about.