- Why is SHELDUS™ no longer free?
- What are the restrictions and limitations to the use of SHELDUS™ data?
- What is the difference between a subscription and pay-as-you-go?
- How often do I need to renew my subscription?
- Why can I not download data?
- Do I really need to update data that I already have? Why are the data for historic years not the same between versions?
- Which aggregation query provides me the most detailed SHELDUS™ data?
- What are the data sources for SHELDUS™?
- What is the difference between SHELDUS™ and NCDC Storm Data?
- What is the correct reference for SHELDUS™ data?
- Why am I asked to pay when I already have a subscription?
- Why does loss information vary between different SHELDUS™ releases?
- What does the asterisk (*) next to a county name mean?
- Why are loss figures different when querying SHELDUS™ for individual hazards versus querying simultaneously?
- Does SHELDUS™ contain information on Puerto Rico, Guam, or other U.S. territories?
- What information is contained in the data download file?
- How can I map SHELDUS™ data?
- How does SHELDUS™ distribute losses?
- Why do I have so many “similar” loss estimates for different counties?
- Why can't I join the SHELDUS™ attribute table via FIPS codes in GIS?
- Why are losses for Hurricane Katrina or any other named event in SHELDUS™ lower than reported elsewhere?
- Why do losses in my county include coastal hazards when my county is not a coastal county?
- How are coastal hazards defined?
- What is a FIPS code?
- What is the GLIDE number?
- What is a presidential disaster declaration?
- What is a peril?
- What are hazard days?
- Why does my aggregation result include hazards that I did not select?
- How are landslide losses estimated?
Why is SHELDUS™ no longer free?
SHELDUS™ requires ongoing maintenance resulting in personnel and technical expenses, which HVRI can no longer absorb. Updates since SHELDUS™ version 5.1 had no support from any federal, state, local, or private stakeholders except the South Carolina Emergency Management Division. SHELDUS™ was only initially supported by grants from the National Science Foundation (Grant No. 99053252 and 0220712) and the University of South Carolina's Office of the Vice President for Research.
What are the restrictions and limitations to the use of SHELDUS™ data?
The use of SHELDUS™ data are limited according to the SHELDUS™ Terms and Conditions.
What is the difference between a subscription and pay-as-you-go?
A SHELDUS™ subscription allows users unlimited SHELDUS™ data aggregation downloads for the duration of the current version. The pricing for pay-as-you-go downloads is a one-time cost. Pay-as-you-go is available for raw and aggregated data along with downloads related to named events, PDDs, and GLIDEs. Subscriptions only provide access to aggregated data. Aggregation is currently not available for named events, PDDs, and GLIDEs. The pricing for pay-as-you-go downloads is determined by the number of database records queried. For more information on pricing see Products.
How often do I need to renew my subscription?
A new subscription is required with each annual release of SHELDUS™ (e.g., SHELDUS™ 15.0). The annual release occurs generally in July. Subscriptions are not valid for 12 months and are tied to database releases. Mid-year releases of SHELDUS™ (e.g., 15.1) do not require a new subscription.
Do I really need to update data that I already have? Why are the data for historic years not the same between versions?
We constantly update the entire database. Such updates include both changes in the number of records (i.e. additions and deletions) as well as edits to existing records. Thus, no changes in the number of records in a year does not imply that no changes to the data occurred. For example, changes between Version 12 and older (free versions) and Version 14 are significant. The table below highlights these changes--both in the numbers of records as well as in the annual dollar amounts. Version 14 contains nearly 20,000 records and $18 billion in total losses more than Version 12 for the same time period (1960-2012).
|Year||Change in Number of Records between Versions 12 and 14||Difference in Total Losses between Versions 12 and 14|
Why can I not download data?
The most likely reason is that your subscription membership has not been verified. Please check your email inbox for a verification email received from firstname.lastname@example.org. Subscriptions should be set-up using official business, agency, or university email accounts.
Which aggregation query provides me the most detailed SHELDUS™ data?
Aggregating data by county, year/month, and hazard will generate the most highly resolved SHELDUS™ data possible.
What are the data sources for SHELDUS™?
The main data sources for the earlier versions of SHELDUS™ were hardy copy versions of "Storm Data and Unusual Weather Phenomena" by the National Climatic Data Center (NCDC). Starting in 2009, SHELDUS™ utilizes digital NCDC Storm Data records. Geological information originates from the National Centers for Environmental Information (formerly National Geophysical Data Center) and U.S. Geological Survey. Please see the metadata section for more detailed information.
What is the difference between SHELDUS™ and NCDC Storm Data?
SHELDUS™ is a loss and hazard database. The National Climatic Data Center’s Storm Data database is an event database. SHELDUS™ includes any loss event across all types of natural hazards including geological. SHELDUS™ can be used to determine the frequency of loss-causing events. NCDC’s Storm Data includes all weather events irrespective of loss. NCDC’s Storm Data can be used to determine the frequency of a hazard. SHELDUS™ includes loss and hazard information dating back to 1960 for all 18 hazard types. NCDC’s Online Storm Data dates back to 1960 only for tornadoes, thunderstorm wind, and hail. Reporting for all other NCDC Online Storm Data hazards begins in 1996. SHELDUS™ offers inflation adjustment. This allows for temporal aggregation and comparison of losses over time. NCDC’s Storm Data reports current losses. SHELDUS™ applies conservative estimates to losses. Whenever losses are reported as a range (e.g., $5,000 to $50,000), SHELDUS™ selects the lower bound of the range (e.g., $5,000). NCDC reports all events prior to 1994/95 as a range. NCDC’s Online Storm Data offers the midpoint of such a loss range (e.g., $25,000) resulting in a seemingly higher loss than what is reported in SHELDUS™. SHELDUS™ data have been geocoded to allow for spatial aggregation. NCDC’s Storm Data should not be aggregated without further processing – although many users erroneously do.
Reasons why SHELDUS™ data can be aggregated without additional processing steps: Events affecting multiple counties: SHELDUS™ equally distributes loss information across affected counties. By contrast, NCDC’s Storm Data reports the event’s total loss independent of how many counties were affected resulting in an overestimation of losses for individual counties.
Events reported by forecast zone: NWS forecast zones can consist of multiple counties or parts of multiple counties, especially in mountains areas. Furthermore, during the 1980s and 1990s, forecast zones were much larger than today and frequently encompassed several counties. SHELDUS™ knows which county belongs into which forecast zone and has tracked these changes over time. Whenever, a forecast zone covers multiple counties, SHELDUS™ equally distributes loss information across the counties within the forecast zone. NCDC does not distribute loss information across multiple counties belonging to the same forecast zone resulting again in an overestimation of losses for individual counties.
Events involving multiple hazards: SHELDUS™ equally distributes loss information across the hazard types. NCDC’s Online Storm Data does not include multiple hazard events.
What is the correct reference for SHELDUS™ data?
Hazards & Vulnerability Research Institute (2016). The Spatial Hazard Events and Losses Database for the United States, Version 15.2 [Online Database]. Columbia, SC: University of South Carolina. Available from http://www.sheldus.org
Why am I asked to pay when I already have a subscription?
This can happen for three reasons. First, your subscription may have not been verified leaving your account inactive for aggregated data downloads. Second, your account has been activated but you did not select some form of data aggregation. Without selecting an aggregation, the database presumes that you want to download raw data, which is not included in the subscription. Or third, you selected to download records by PDD, GLIDE, or named event. These search options allow only for raw data download, which again is not part of the subscription. are not
Why does loss information vary between different SHELDUS™ releases?
SHELDUS™ is updated annually. Updates can include additional year(s) as well as corrections and/or additions to historic information. This changes the loss information between releases. It is therefore strongly recommended to always use the most recent SHELDUS™ release.
What does the asterisk (*) next to a county name mean?
The asterisk (*) identifies counties that no longer exist. The following changes in regard to counties are reflected in SHELDUS™.
By 1960: There were 3,133 counties and county equivalents.
By 1970: There were 3,142 counties and county equivalents. Princess Ann County, VA was absorbed by Virginia Beach city in 1963. Menominee County, WI was carved out of Shawano County, WI in 1961. Ormsby, NV was consolidated with Carson City/32510 in 1969. Salem, VA/51775 became independent of Roanoke, VA/51161 in 1968. Bedford City, VA/51515 became independent of Bedford, VA/51019 in 1968. Emporia, VA/51595 became independent of Greensville, VA/51081 in 1967. Lexington, VA/51678 became independent of Rockbridge, VA/51153 in 1965. Fairfax City, VA/51600 became independent of Fairfax, VA/51059 in 1961.
By 1980: There were 3,137 counties and county equivalents. Washabaugh, SD/46131 ceased to exist and was added to Jackson, SD/46071 in 1979. City of Nansemond, VA/51123 ceased to exist and was added to City of Suffolk, VA/51800 in 1972. Poquoson/51735 became independent of York County/51199 in 1975. Manassas, VA/51683 became independent of Prince William, VA/51153 in 1975. Manassas Park, VA/51685 became independent of Prince William, VA/51153 in 1975. Dillingham, AK/2070, North Slope, AK/2185 and Valdez-Cordova, AK/2261 were formed. The following Alaska counties ceased to exist: Angoon/2030, Barrow/2040, Cordova-McCarthy/2065, Kenai-Cook Inlet/2120, Kuskokwim/2160, Outer Ketchikan/2190, Prince of Wales/2200, Skagway-Yakutat/2230, Upper Yukon/2250, Valdez-Chitina-Whittier/2260.
By 1990: There were 3,141 counties and county equivalents. La Paz, AZ/04012 was formed from part of Yuma County, AZ in 1982. Cibola, NM/35006 was formed from part of the western portion of Valencia County, NM in 1981. Aleutian Islands, AK/2010 ceased to exist in 1987. Aleutians East, AK/2013 and Aleutians West, AK/2016 were formed from Aleutian Islands in 1987. Lake and Peninsula, AK/2164 was created from parts of Dillingham, AK/2070 in 1989. Northwest Arctic, AK/2188 was formed from Kobuk, AK/2140 and unpopulated parts of North Slope, AK/2185 in 1986. Kobuk, AK/2140 ceased to exist in 1986.
By 2000: There were 3,141 counties and county equivalents. Denali, AK/2068 was formed from parts of Yukon-Koyukuk, AK/2290 and unpopulated parts of Southeast Fairbanks, AK/2240 in 1990. Skagway-Hoonah-Angoon AK/2232 was formed from Skagway-Yakutat-Angoon, AK/2231 in 1992. Yakutat, AK/2282 was formed from Skagway-Yakutat-Angoon, AK/2231 in 1992. Skagway-Yakutat-Angoon, AK/2231 ceased to exist in 1992. Yellowstone National Park, MT/30113 ceased to exist and added to Gallatin, MT/30031 in 1997. South Boston, VA/51780 ceased to exist and was added to Halifax, VA/51083 in 1995. Dade, FL/12025 was renamed to Miami-Date, FL/12086 in 1997.
By 2010: There were 3,143 counties and county equivalents. Broomfield, CO/8014 was formed in parts from Adams, CO/8001, Boulder, CO/8013, Jefferson, CO/8059, and Weld, CO/8123 in 2001. Clifton Forge, VA/51560 ceased to exist and was added to Alleghany, VA/51005 in 2001. Hoonah-Angoon, AK/2105 was formed in 2007. Skagway-Hoonah-Angoon, AK/2232 ceased to exist in 2007. Skagway, AK/2230 was formed from Skagway-Hoonah-Angoon, AK/2232 in 2007. Petersburg, AK/2195 was formed from parts of Wrangell-Petersburg, AK/2280 in 2008. Wrangell-Petersburg, AK/2280 ceased to exist in 2008. Prince of Wales-Hyder, AK/2198 was formed from Prince of Wales-Outer Ketchikan after Outer Ketchikan was annexed by Ketchikan, AK/2130 in 2008. Prince of Wales-Outer Ketchikan, AK/2130 ceased to exist in 2008. Wrangell, AK/2275 formed from parts of Wrangell-Petersburg, AK/2280 and parts of Prince of Wales-Outer Ketchikan, AK/2201 in 2008.
Since 2010: Bedford City, VA/51515 ceased to exist in 2013. Shannon, SD/46113 and Wade Hampton, AK/02270 ceased to exist in 2015.
Why are loss figures different when querying SHELDUS™ for individual hazards versus querying simultaneously?
Querying simultaneously is the preferred option since there will be no duplicate records. Individual hazard queries can lead to a duplication of losses because the aggregation procedure runs on a singular hazard. For example, a loss event caused by flooding and thunderstorm wind will be returned twice by SHELDUS™ when querying by flooding or wind only. When querying for both hazards at the same time, the loss will be split between both hazard types.
Does SHELDUS™ contain information on Puerto Rico, Guam, or other U.S. territories?
No, the database includes only loss information for the 50 U.S. states.
What information is contained in the data download file?
Depending on your query selection, the download will list the temporal information (year, month, and/or quarter), spatial information (FIPS code, county, state), damage information (crop and property damage, fatalities, injuries), and hazard type(s). Please see the metadata section for more detailed information on the naming convention of table columns
How can I map SHELDUS™ data?
The easiest way to map the downloaded information is to link it using the FIPS code. Spatial information (shapefiles) are available from our products section.
How does SHELDUS™ distribute losses?
In case of multi-county events, SHELDUS™ distributes losses equally between the affected counties. For instance, a thunderstorm event affecting Richland and Lexington County in South Carolina and causing property damages of $50,000 will be entered into the database as an event affecting Richland County with $25,000 and Lexington County with $25,000 worth of damage.
Why do I have so many “similar” loss estimates for different counties?
Any time an event, particularly a large scale event, affects multiple counties, SHELDUS™ distributes losses equally. When a query is fairly narrow with a small time window or only few counties, the chance is high that SHELDUS™ returns nearly identical information. Furthermore, between 1960 and 1995, NCDC’s Storm Data provided logarithmic loss estimates ($50, $50-500, $500-5000, $50,000-500,000, $5,000,000-50,000,000, etc.) instead of a specific estimate. In addition, the spatial resolution of historic NCDC Storm Data was low. Damage was frequently reported for larger regions rather than specific counties. This results in seemingly “similar” estimates for many, particularly, historic events given the loss distribution applied by SHELDUS™. Starting in 1995, NCDC’s Storm Data began reporting exact dollar figures and the spatial resolution increased as well. Thus, loss information starting in 1995/96 is spatially and monetarily more accurate than during years prior.
Why can't I join the SHELDUS™ attribute table via FIPS codes in GIS?
The most likely reason for this problem is that the FIPS code columns are formatted differently. The SHELDUS™ FIPS code column is formatted as text.
Why are losses for Hurricane Katrina or any other named event, PDD, or GLIDE in SHELDUS™ lower than reported elsewhere?
SHELDUS™ reflects loss estimates as reported by NCDC’s Storm Data, etc. We manually match SHELDUS™ records based on location, time, and hazard type to a named event, PDD, or GLIDE.
Why do losses in my county include coastal hazards when my county is not a coastal county?
Because of inaccuracies in the spatial identification of hazard events within NCDC’s Storm Data reports, there are instances in SHELDUS™ where inland counties will contain property and/or crop losses from coastal hazard events. This issue mainly occurs when an event is labeled as a "statewide" event by NCDC in which each county receives an equal percentage of losses irrespective of spatial location or hazard event type. Hence, a hazard event identified as "flooding, winter weather, coastal storm" which is given a statewide locational identifier is treated as an event which impacted each county equally. Therefore, inland counties may at times be attributed with events and losses that seem incapable of occurring.
How are coastal hazards defined?
Hazards such as high tide, tidal wave, rouge tide, beach erosion, high seas, heavy surf, etc. are classified as coastal hazard. For more information see Coastal Event Types.
What is a FIPS code?
The Federal Information Processing Standard (FIPS) provides the names and codes that represent the counties and other entities treated as equivalent legal and/or statistical subdivisions of the 50 States, the District of Columbia, and the possessions and freely associated areas of the United States. The last three digits of the FIPS code refer to the county whereas the preceding one or two digits identify the state. Changes of FIPS codes are published by the National Institute of Standards and Technology (NIST) after approval by the Secretary of Commerce. Questions concerning the list of entities and their assigned codes are to be addressed to the Maintenance Agency: Office of the Chief, Geography Division, Bureau of the Census, Washington, DC 20233. For information on changes to FIPS codes and county names see U.S. Census Sustantial Changes to Counties and county Equivalent Entities or go to the metadata.
What is the GLIDE number?
The GLIDE number is an internationally recognized global identifier for large-scale events. GLIDE numbers are issued by members of the GLIDE initiative and upon request. SHELDUS™ does not include all U.S.-related GLIDE numbers nor is there a GLIDE number for every large-scale U.S. event. SHELDUS™ includes only GLIDE numbers for selected major events, given a GLIDE number exists. For more information see the GLIDE website.
What is a presidential disaster declaration?
FEMA issues numbers for presidential disaster declarations (PDD) by state. For every state, FEMA lists so-called designated counties affected by the event. SHELDUS™ does not include all PDDs. SHELDUS™ includes only PDDs for selected major events. For more information see presidential disaster declarations.
What is a peril?
The Integrated Research on Disaster Risk (IRDR) program developed the peril classification system to help standardize losses databases. A peril is a hazard event that can be classified into one of six categories: Geophysical, Hydrological, Meteorological, Climatological, Biological, or Extraterrestrial. For more information see IRDR Peril Classification and Hazard Glossary.
What are hazard days?
Hazard days are days in which a loss (property, crop, injury, or fatality) occurred from a hazard. A count of hazard days will only be returned when data is aggregated.
Why does my aggregation result include hazards that I did not select?
There are many records in SHELDUS™ where the loss was caused by multiple hazards (e.g., Wind and Hail). The aggregation algorithm splits the losses equally between all involved hazard types. This can lead to the reporting of hazard types that were not originally part of your search. We recommend to either ignore those hazards or assign them to another hazard type that was part of your query.
How are landslide losses estimated?
Landslide loss estimates were primarily gathered from the 2015 NWSI 10-1605 Storm Data. If there was no basis for the loss amount, $99 was entered as the property loss. See Metadata for details.