This dataset contains FEMA applicant-level data for the Individuals and Households Program (IHP). All PII information has been removed. The location is represented by county, city, and zip code. This dataset contains Individual Assistance (IA) applications from DR1439 (declared in 2002) to those declared over 30 days ago. The full data set is refreshed on an annual basis and refreshed weekly to update disasters declared in the last 18 months. This dataset includes all major disasters and includes only valid registrants (applied in a declared county, within the registration period, having damage due to the incident and damage within the incident period). Information about individual data elements and descriptions are listed in the metadata information within the dataset.rnValid registrants may be eligible for IA assistance, which is intended to meet basic needs and supplement disaster recovery efforts. IA assistance is not intended to return disaster-damaged property to its pre-disaster condition. Disaster damage to secondary or vacation homes does not qualify for IHP assistance.rnData comes from FEMA's National Emergency Management Information System (NEMIS) with raw, unedited, self-reported content and subject to a small percentage of human error.rnAny financial information is derived from NEMIS and not FEMA's official financial systems. Due to differences in reporting periods, status of obligations and application of business rules, this financial information may differ slightly from official publication on public websites such as usaspending.gov. This dataset is not intended to be used for any official federal reporting. rnCitation: The Agency’s preferred citation for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page, Citing Data section: https://www.fema.gov/about/openfema/terms-conditions.rnDue to the size of this file, tools other than a spreadsheet may be required to analyze, visualize, and manipulate the data. MS Excel will not be able to process files this large without data loss. It is recommended that a database (e.g., MS Access, MySQL, PostgreSQL, etc.) be used to store and manipulate data. Other programming tools such as R, Apache Spark, and Python can also be used to analyze and visualize data. Further, basic Linux/Unix tools can be used to manipulate, search, and modify large files.rnIf you have media inquiries about this dataset, please email the FEMA News Desk at FEMA-News-Desk@fema.dhs.gov or call (202) 646-3272. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.rnThis dataset is scheduled to be superceded by Valid Registrations Version 2 by early CY 2024.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Analysis of ‘Initial Claims By County (All Programs)’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/bc31fe5c-49c7-4a1b-9190-78fa17248dca on 26 January 2022.
--- Dataset description provided by original source is as follows ---
Initial Claims by County (all programs) - The number of claims submitted for all UI programs. Initial claims totals are not representative of the number of individuals filing as a claimant can have multiple initial claims.
∙ Initial Claims by County - The data provided is the number of Unemployment Insurance (UI) initial claim counts, which includes new claims, additional claims, and transitional claims.
• A "new claim" is the first claim for a benefit year period (e.g., for the regular UI program it is 52 weeks). An individual would only have one new claim during a benefit year period.
• An "additional claim" is when another claim is filed during the same benefit year and there is intervening work between the current claim and the previous claim. For example, an individual files a new claim, goes back to work, gets laid off and files another claim before the benefit year period of the first claim expires. An individual can have multiple additional claims during the same benefit year if the individual meets the eligibility requirements.
• A "transitional claim" is when a claimant is still collecting benefits at the end of their benefit year period and had sufficient wage earnings during that year to start up a new claim once the first benefit year period ends.
∙ The data by county represents the mailing address given by the claimant at the time of filing for UI. It is possible that an individual can reside in a different county than their mailing address. Also, this information does not represent the county where the individual worked. It is also possible that a claimant could have moved or changed their mailing address after filing for UI which would not be reflected here. Data for claimants residing outside of California but collecting benefits are not included in these figures nor are invalid addresses in California where a county cannot be determined.
"∙ Initial claims does not represent total individuals as an individual can have multiple claims. For example, someone may begin collecting UI benefits, then go off UI to return to work, then get laid off and go back on UI. In this example, the individual would have
two claim counts. "
∙ Data includes the regular UI program and the federal extended benefit programs. The Federal extended benefit programs are:
∙ Emergency Unemployment Compensation (EUC) Tier 1 - California began paying benefits in July 2008.
∙ Emergency Unemployment Compensation (EUC) Tier 2 - California began paying benefits in January 2009, payments retroactive to November 2008.
∙ Emergency Unemployment Compensation (EUC) Tier 3 - California began paying benefits in December 2009, payments retroactive to November 2009.
∙ Emergency Unemployment Compensation (EUC) Tier 4 - California began paying benefits in January 2010, payments retroactive to December 2009.
∙ FED-ED - California began paying benefits May 2009, payments retroactive to February 2009.
--- Original source retains full ownership of the source dataset ---
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The projection is State Plane Coordinate System 1983. The horizontal accuracy meets Guidelines and specifications for DFIRM production.
The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The projection is Universal Transverse Mercator. The horizontal accuracy meets Guidelines and specifications for DFIRM production.
This Seniors, Community and Social Services (SCSS) dataset describes the monthly Income Support caseload in Alberta, including two client groups: those Expected to Work (ETW) and those who have Barriers to Full Employment (BFE). Income Support provides financial benefits to individuals and families who do not have the resources to meet their basic needs, like food, clothing, and shelter. The caseload is defined as the number of households categorized as ETW or BFE during a specific reporting period. Most commonly, this is reported as the average volume for a specific period (e.g., annually). The composition of the caseload is made up of single individuals, lone-parent families, couples with children and couples without children. In April 2018, a breakdown of the number of caseloads by SCSS Regions was added to provide greater context. NOTE: (1) - Due to a change in how region information is tracked within source systems, region caseloads have been updated as of January 2025 to include an additional category 'Unknown', reflecting new postal codes being introduced to the data record within source systems. This change has been retroactively applied to all past data. (2) - All regions report that the primary factor for reduced Income Support caseloads from April-2020 is due to Albertans accessing the federal government’s Canada Emergency Response Benefit (CERB).
Not seeing a result you expected?
Learn how you can add new datasets to our index.
This dataset contains FEMA applicant-level data for the Individuals and Households Program (IHP). All PII information has been removed. The location is represented by county, city, and zip code. This dataset contains Individual Assistance (IA) applications from DR1439 (declared in 2002) to those declared over 30 days ago. The full data set is refreshed on an annual basis and refreshed weekly to update disasters declared in the last 18 months. This dataset includes all major disasters and includes only valid registrants (applied in a declared county, within the registration period, having damage due to the incident and damage within the incident period). Information about individual data elements and descriptions are listed in the metadata information within the dataset.rnValid registrants may be eligible for IA assistance, which is intended to meet basic needs and supplement disaster recovery efforts. IA assistance is not intended to return disaster-damaged property to its pre-disaster condition. Disaster damage to secondary or vacation homes does not qualify for IHP assistance.rnData comes from FEMA's National Emergency Management Information System (NEMIS) with raw, unedited, self-reported content and subject to a small percentage of human error.rnAny financial information is derived from NEMIS and not FEMA's official financial systems. Due to differences in reporting periods, status of obligations and application of business rules, this financial information may differ slightly from official publication on public websites such as usaspending.gov. This dataset is not intended to be used for any official federal reporting. rnCitation: The Agency’s preferred citation for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page, Citing Data section: https://www.fema.gov/about/openfema/terms-conditions.rnDue to the size of this file, tools other than a spreadsheet may be required to analyze, visualize, and manipulate the data. MS Excel will not be able to process files this large without data loss. It is recommended that a database (e.g., MS Access, MySQL, PostgreSQL, etc.) be used to store and manipulate data. Other programming tools such as R, Apache Spark, and Python can also be used to analyze and visualize data. Further, basic Linux/Unix tools can be used to manipulate, search, and modify large files.rnIf you have media inquiries about this dataset, please email the FEMA News Desk at FEMA-News-Desk@fema.dhs.gov or call (202) 646-3272. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.rnThis dataset is scheduled to be superceded by Valid Registrations Version 2 by early CY 2024.