{"links":[{"href":"/api/open/v2/DisasterDeclarationsSummaries","rel":"DisasterDeclarationsSummaries","title":"Disaster Declarations Summaries is a summarized dataset describing all federally declared disasters. This dataset lists all official FEMA Disaster Declarations, beginning with the first disaster declaration in 1953 and features all three disaster declaration types: major disaster, emergency, and fire management assistance. The dataset includes declared recovery programs and geographic areas (county not available before 1964; Fire Management records are considered partial due to historical nature of the dataset).\n\nPlease note the unique structure of the disaster sequencing (due to a numbering system that originated in the 1950's-1970's):\n0001-1999     Major Disaster Declaration\n2000-2999     Fire Management\n3000-3999     Emergency Declaration (Special Emergency)\n4000-4999     Major Disaster Declaration\n5000-5999     Fire Management\n\nFor more information on the disaster declaration process, see https://www.fema.gov/disasters and https://www.fema.gov/disasters/how-declared\n\nThis is raw, unedited data from FEMA's National Emergency Management Information System (NEMIS) and as such is subject to a small percentage of human error. The dataset is primarily composed of historical data that was manually entered into NEMIS after it launched in 1998. \nAdditionally, NEMIS utilizes census data from the United States Census Bureau in which Tribal Nations are listed as localities within a State. As such, disaster declarations for Tribal Nations are currently included in State data.\nCitation: FEMA's citation requirements 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.\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq.\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/EmergencyManagementPerformanceGrants","rel":"EmergencyManagementPerformanceGrants","title":"This dataset contains EMPG recipients as reported by their State and a summary of the funded program support as reported by the Recipient in the GRT.\n\nThe EMPG Program provides resources to assist state, local, tribal and territorial governments in preparing for all hazards, as authorized by Section 662 of the Post Katrina Emergency Management Reform Act (6 U.S.C § 762) and the Robert T. Stafford Disaster Relief and Emergency Assistance Act, as amended (42 U.S.C. §§ 5121 et seq.). Title VI of the Stafford Act authorizes FEMA to make grants for the purpose of providing a system of emergency preparedness for the protection of life and property in the United States from hazards, and to vest responsibility for emergency preparedness jointly in the federal government and the states and their political subdivisions. The EMPG, from FY 2016 to the present FY, provides federal funds to assist state, local, tribal and territorial emergency management agencies to obtain the resources required to support the National Preparedness Goal's (NPG's) associated mission areas and core capabilities. The Federal Government, through the EMPG Program, provides necessary direction, coordination, and guidance, and provides necessary assistance, as authorized in this title to support a comprehensive all hazards emergency preparedness system. \n\nThe EMPG is to support a comprehensive, all-hazard emergency preparedness system by building and sustaining the core capabilities contained in the NPG's. Examples include: \n<ul><li>Completing the Threat and Hazard Identification and Risk Assessment (THIRA) process.</li><li>Strengthening a state or community's emergency management governance structure.</li><li>Updating and approving specific emergency plans.</li><li>Designing and conducting exercises that enable whole community stakeholders to examine and validate core capabilities and the plans needed to deliver them to the targets identified through the THIRA.</li><li>Targeting training and verifying identified capabilities.</li><li>Initiating or achieving a whole community approach to security and emergency management. </li></ul>\nThis dataset was first made public on 10/31/2016 and will be updated twice a year. \nFor additional details on the EMPG program visit: https://www.fema.gov/grants/preparedness/emergency-management-performance.\nThis dataset is not intended to be an official federal report, and should not be considered an official federal report. \n Citation: 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.\n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/FemaRegions","rel":"FemaRegions","title":"Provides a list of FEMA Regions including the address for each region's headquarters as well as a point in GeoJSON format that identifies headquarters and a geometry shape for the region in GeoJSON format.\n\nCitation: FEMA's citation requirements 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\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/HazardMitigationGrantProgramDisasterSummaries","rel":"HazardMitigationGrantProgramDisasterSummaries","title":"The dataset contains disaster level financial information for FEMA’s Hazard Mitigation Grant Program (HMGP). The purpose of HMGP is to help communities implement hazard mitigation measures following a Presidential Major Disaster Declaration in the areas of the State, Tribe, or Territory requested by the Governor or Tribal Executive. For more information on the Hazard Mitigation Grant Program, please visit: https://www.fema.gov/grants/mitigation\n\nHMGP (Disaster Numbers 820-1999, 4000-4999)\nSection 404 of the Stafford Act authorized the Hazard Mitigation Grant Program (HMGP). The key purpose of HMGP is to ensure that the opportunity to take critical mitigation measures to reduce the risk of loss of life and property from future disasters is not lost during the reconstruction process following a disaster. The amount of HMGP funding available to the Applicant is based upon the total Federal assistance to be provided by FEMA for disaster recovery under the Presidential major disaster declaration.\n\nFire Management Assistance Grant (FMAG) HMGP (Disaster Numbers 5084-5117)\nSection 570 of the Fiscal Year 2015 DHS Appropriations Act authorized FEMA to provide HMGP assistance as a result of an FMAG declaration. FMAG HMGP was run as a pilot program and funding was provided as a national aggregate calculation based on an average of historical FMAG designations from the last five years.\n\nHMGP Post Fire (Disaster Numbers 5154-5999)\nSection 1204 of the Disaster Recovery Reform Act of 2018 amended Section 404 of the Stafford Act to authorize FEMA to provide HMGP assistance in any area affected by a major disaster, or any area affected by a fire for which assistance was provided under Section 420 Fire Management Assistance Grant (FMAG). Funding from multiple events is aggregated into one grant under the first declaration. The Aggregation is reset at the beginning of each fiscal year and remains in effect for that year.\n\nThis dataset contains hazard mitigation grant program disasters assistance information from FEMA’s mitigation grant systems and as such is subject to a small percentage of human error. The financial information is derived from FEMA’s mitigation grant systems, not FEMA's official financial systems. Due to differences in reporting periods, status of obligations and how business rules are applied, 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 financial reporting.\n\nIn some cases, data was not provided by the subrecipient, recipient, and/or entered into FEMA’s mitigation grant systems. The information is likely available as part of the paper file which is considered the file of record.\n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/HousingAssistanceOwners","rel":"HousingAssistanceOwners","title":"This dataset is generated by FEMA's Individual Assistance (IA) reporting team to share data on FEMA's Housing Assistance program for house owners within the state, county, and zip code where the registration is valid for the declarations, starting with disaster declaration DR1439 (declared in November 2002). It contains aggregated, non-PII data. Core data elements include number of applicants, county, zip code, inspections, severity of damage, and assistance provided. \n\nData is self-reported and subject to human error. For example, when an applicant registers online, they enter their street and city address. While the county is inferred by the system, it may be overridden by the applicant. Similarly, with a call center registration, the Human Services Specialist (HSS) representatives are instructed to ask in what county the applicant resides, but the applicant has the right to choose the county. To learn more about disaster assistance please visit https://www.fema.gov/individual-disaster-assistance.\n\nThe financial information is derived from NEMIS and not FEMA's official financial systems. Due to differences in reporting periods, status of obligations and how business rules are applied, 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 financial reporting.\n\nFEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq\n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/HousingAssistanceRenters","rel":"HousingAssistanceRenters","title":"This dataset was generated by FEMA's Individual Assistance (IA) reporting team to share data on FEMA's Housing Assistance program for house renters within the state, county, and zip code where the registration is valid for the declarations, starting with disaster declaration DR1439 (declared in 2002). It contains aggregated, non-PII data. Core data elements include number of applicants, county, zip code, inspections, severity of damage, and assistance provided. \n\nData is self-reported and subject to human error. For example, when an applicant registers online, they enter their street and city address. While the county is inferred by the system, it may be overridden by the applicant. Similarly, with a call center registration, the Human Services Specialist (HSS) representatives are instructed to ask in what county the applicant resides, but the applicant has the right to choose the county. To learn more about disaster assistance please visit https://www.fema.gov/individual-disaster-assistance.\n\nThe financial information is derived from NEMIS and not FEMA's official financial systems. Due to differences in reporting periods, status of obligations and how business rules are applied, 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 financial reporting.\n\nFEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq\n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/RegistrationIntakeIndividualsHouseholdPrograms","rel":"RegistrationIntakeIndividualsHouseholdPrograms","title":"This dataset contains aggregated, non-PII data from Housing Assistance Program reporting authority within FEMA’s Recovery Directorate to share data on registrations and Individuals and Households Program (IHP) for declarations starting from disaster declaration number 4116, segmented by city where registration is valid. Additional core data elements include: valid call center registrations, valid web registrations, valid mobile registrations, IHP eligible, IHP amount, HA eligible, HA amount, ONA eligible, and ONA amount.\n\nIHP is intended to help with critical expenses that cannot be covered in other ways. The IHP is not intended to return all homes or belongings to their pre-disaster condition. In some cases, IHP may only provide enough money, up to the program limits, for you to return an item to service. Secondary or vacation residencies do not qualify. Visit for more information about the program: https://www.fema.gov/assistance/individual\n\nThis is raw, unedited data from FEMA's National Emergency Management Information System (NEMIS) and as such is subject to a small percentage of human error. \n\nThe financial information is derived from NEMIS and not FEMA's official financial systems.  Due to differences in reporting periods, status of obligations and how business rules are applied, 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 financial reporting.\n\nFEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq\n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/FimaNfipClaims","rel":"FimaNfipClaims","title":"Congress passed the National Flood Insurance Act (NFIA), 42 U.S.C. 4001 in 1968, creating the National Flood Insurance Program (NFIP) in order to reduce future flood losses through flood hazard identification, floodplain management, and providing insurance protection. The Department of Housing and Urban Development (HUD) originally administered the NFIP, and Congress subsequently transferred the NFIP to FEMA upon its creation in 1979. FEMA and insurance companies participating in FEMA's Write Your Own (WYO) program offer NFIP insurance coverage for building structures as well as for contents and personal property within the building structures to eligible and insurable properties. The WYO program began in 1983 with NFIP operating under Part B of the NFIA and allows FEMA to authorize private insurance companies to issue the Standard Flood Insurance Policy (SFIP) as FEMA's fiduciary and fiscal agent. FEMA administers NFIP by ensuring insurance applications are processed properly; determining correct premiums; renewing, reforming, and cancelling insurance policies; transferring policies from the seller of the property to the purchaser of the property in certain circumstances; and processing insurance claims. \n\nThe paid premiums of SFIPs and claims payments for damaged property are processed through the National Flood Insurance Fund (NFIF). NFIF was established by the National Flood Insurance Act of 1968 (42 U.S.C. 4001, et seq.), and is a centralized premium revenue and fee-generated fund that supports NFIP, which holds these U.S. Treasury funds. \n\nThis dataset provides details on NFIP claims transactions. It is derived from the NFIP system of record, staged in the NFIP reporting platform and redacted to protect policy holder personally identifiable information.\n\nThe Flood Insurance Claims Manual located at https://agents.floodsmart.gov/manuals, provides claims guidance to WYOs, vendors, adjusters, and examiners so that policyholders experience consistent and reliable service. The Manual provides processes for handling claims from the notice of loss to final payment. A direct link to the manual is:  https://agents.floodsmart.gov/sites/default/files/media/document/2025-09/fema_nfip-FloodInsuranceManual-October2025-508c.pdf. All revisions in PDF format are located under the \"Transaction Record Reporting and Processing (TRPP) Plan\" expandable heading.\n\nThis dataset represents more than 2,000,000 claims transactions. In order to improve accessibility, we have one compressed file. Due to the file size we recommend using Access, SQL, or another programming/data management tool to visualize and manipulate the data, as Excel will not be able to process files this large without data loss. The dataset will be updated approximately monthly and will have a lag with the system of record. \n \nThis dataset is not intended to be an official federal report, and should not be considered an official federal report. \n \nFEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions.\n\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq.\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/FimaNfipPolicies","rel":"FimaNfipPolicies","title":"Congress passed the National Flood Insurance Act (NFIA), 42 U.S.C. 4001 in 1968, creating the National Flood Insurance Program (NFIP) in order to reduce future flood losses through flood hazard identification, floodplain management, and providing insurance protection. The Department of Housing and Urban Development (HUD) originally administered the NFIP, and Congress subsequently transferred the NFIP to FEMA upon its creation in 1979. FEMA and insurance companies participating in FEMA's Write Your Own (WYO) program offer NFIP insurance coverage for building structures as well as for contents and personal property within the building structures to eligible and insurable properties. The WYO program began in 1983 with NFIP operating under Part B of the NFIA and allows FEMA to authorize private insurance companies to issue the Standard Flood Insurance Policy (SFIP) as FEMA's fiduciary and fiscal agent. FEMA administers NFIP by ensuring insurance applications are processed properly; determining correct premiums; renewing, reforming, and cancelling insurance policies; transferring policies from the seller of the property to the purchaser of the property in certain circumstances; and processing insurance claims. \n\nThe paid premiums of SFIPs and claims payments for damaged property are processed through the National Flood Insurance Fund (NFIF). NFIF was established by the National Flood Insurance Act of 1968 (42 U.S.C. 4001, et seq.), and is a centralized premium revenue and fee-generated fund that supports NFIP, which holds these U.S. Treasury funds. \n\nThis dataset provides details on NFIP policy transactions. It is derived from the NFIP system of record, staged in the NFIP reporting platform and redacted to protect policy holder personally identifiable information.\n\nThe Flood Insurance Claims Manual located at https://agents.floodsmart.gov/manuals, provides NFIP underwriting policies and processes to enable effective and consistent program implementation. A direct link to the manual is: https://agents.floodsmart.gov/sites/default/files/media/document/2025-09/fema_nfip-FloodInsuranceManual-October2025-508c.pdf. All revisions in PDF format are located under the \"Transaction Record Reporting and Processing (TRPP) Plan\" expandable heading. \n\n\nThis dataset represents more than 80,000,000 policy transactions. In order to improve accessibility, we have one compressed file. Due to the file size we recommend using Access, SQL, or another programming/data management tool to visualize and manipulate the data, as Excel will not be able to process files this large without data loss. The dataset will be updated approximately monthly and will have a lag with the system of record. \n \nThis dataset is not intended to be an official federal report, and should not be considered an official federal report. \n \nFEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions.\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq.\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/HmaSubapplications","rel":"HmaSubapplications","title":"This dataset contains Hazard Mitigation Assistance (HMA) subapplications/subgrants from the FEMA Grants Outcomes (FEMA GO) system (FEMA’s new grants management system). FEMA GO started accepting Flood Mitigation Assistance (FMA) and Building Resilient Infrastructure and Communities (BRIC) subapplications in Fiscal Year 2020. FEMA GO is projected to support the Hazard Mitigation Grant Program (HMGP) in Calendar Year 2023. For details on HMA subgrants not captured in FEMA GO, visit https://www.fema.gov/openfema-data-page/hazard-mitigation-assistance-projects-v4.\n\nThis dataset contains information on the HMA subapplications/subgrants that have been submitted to or awarded in FEMA GO, as well as amendments made to the awarded subgrants. Sensitive information, such as Personally Identifiable Information (PII), has been removed to protect privacy. The information in this dataset has been deemed appropriate for publication to empower public knowledge of mitigation activities and the nature of HMA grant programs. For more information on the HMA grant programs, visit: https://www.fema.gov/grants/mitigation. For more information on FEMA GO, visit: https://www.fema.gov/grants/guidance-tools/fema-go.\n\nThis dataset comes from the source system mentioned above and is subject to a small percentage of human error. In some cases, data was not provided by the subapplicant, applicant, and/or entered into FEMA GO. The financial information in this dataset is not derived from FEMA's official financial systems. Due to differences in reporting periods, status of obligations, and how business rules are applied, this financial information may differ slightly from official publication on public websites such as https://www.usaspending.gov. This dataset is not intended to be used for any official federal financial reporting.\nFEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions.\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq.\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/HazardMitigationAssistanceProjectsByNfipCrsCommunities","rel":"HazardMitigationAssistanceProjectsByNfipCrsCommunities","title":"This dataset contains the communities identified in the Hazard Mitigation Assistance (HMA) subapplications/subgrants from the NEMIS Mitigation and eGrants grants management systems. For details on the  communities identified in the Hazard Mitigation Assistance (HMA) subapplications/subgrants not captured in these systems, visit https://www.fema.gov/openfema-data-page/hma-subapplications-nfip-crs-communities-v1.\n\nThis dataset contains information on the communities participating in the National Flood Insurance Program (NFIP) Community Rating System (CRS) identified in the HMA subapplications/subgrants that have been submitted to or awarded in source systems mentioned above, as well as amendments made to the awarded subgrants. Sensitive information, such as Personally Identifiable Information (PII), has been removed to protect privacy. The information in this dataset has been deemed appropriate for publication to empower public knowledge of mitigation activities and the nature of HMA grant programs. For more information on the HMA grant programs, visit: https://www.fema.gov/grants/mitigation. \n\nThis dataset comes from the source systems mentioned above and is subject to a small percentage of human error. In some cases, data was not provided by the subapplicant, applicant, and/or entered into the grant management system. Due to the voluntary nature of the Hazard Mitigation Assistance Programs, not all communities in this dataset will be mitigated. This dataset is not intended to be used for any official federal financial reporting. \n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/MissionAssignments","rel":"MissionAssignments","title":"A mission assignment (MA) is a work order issued by FEMA to another Federal agency in anticipation of, or in response to, a Presidential declaration of an emergency or major disaster. Mission assignments are authorized by the Robert T. Stafford Disaster Relief and Emergency Assistance Act (Stafford Act). More information about MAs is available at https://www.fema.gov/partnerships/mission-assignments. The Stafford Act, as amended, directs FEMA to publish regularly updated mission assignment data on its website. Please read this entire page, as it contains important notes for understanding how to use this dataset correctly. \n\nThis updated version provides a history of FEMA mission assignment activity for incidents or disaster declarations occurring on or after October 1, 2012. It expands on the previous version by adding pre-declaration (“surge”) MA activity, subject to a two-week delay. It also adds several new data points (“fields”), renames others, and removes those deemed no longer relevant. Together, these changes provide a more holistic view of MA activity in response to incidents and declarations occurring in fiscal year 2013 and later.\n\nFEMA tracks mission assignment activity in relation to overarching incidents (such as Hurricane Ian, Tropical Storm Lee, or the Calf Canyon Fire), as well as to the emergency or major disaster declarations that may result in one or more impacted states, tribes, or territories. Surge activity is identified by code ‘7220’ in the Declaration Number and ‘SU’ in the Declaration Type. \n\nEach row (“record”) in this dataset represents a mission assignment “action,” which is either the creation of a new mission assignment, or the amendment of an existing assignment. These actions are uniquely identified by a combination of MA Number with MA Amendment Number (which is zero for a new MA and increases by one for each MA amendment). Action ID also serves as a unique record number for each MA action. \n\nThe details of a mission assignment often change over time as needs for support evolve. Mission assignments are amended for certain changes, such as periods of performance, points of contact, costs, and/or cost share percentages. However, mission assignments involving changes to the statement of work or funding source (surge account, emergency declaration, or major disaster declaration) are re-issued as new mission assignments; they are not amended. When this happens, funding from the preceding mission assignment generally is de-obligated from the initial funding source and re-obligated under the new mission assignment, along with any cost adjustments if needed. To understand all actions associated with a particular mission assignment, group the records in this dataset by MA Number. (Note: This will not group re-issued mission assignments with their predecessors.)\n\nBecause certain characteristics can change over the life of a mission assignment, the most recent amendment generally contains the most up-to-date information for that mission assignment, except for costs (explained next). \n\nObligation amounts do not reflect actual costs incurred; they reflect the anticipated amount of money needed to fund the work described. Obligation amounts are based on best estimates, which include cushions designed to ensure adequate resources are available to address the stated needs. As better estimates become available, obligation amounts are adjusted via mission assignment amendments. \n\nTo determine all estimated costs associated with a particular mission assignment, group the records in this dataset by MA Number and sum the obligation amounts for each action by MA Number. Over time, this sum will approach and eventually should match actual mission assignment costs, once billing and reimbursement activity is complete.\n \nCost shares are treated differently and are not as easily summed. FEMA has created a set of MA-specific fields to use in summary reporting. The MA POP start date, MA POP end date, MA state/tribe/territory cost share percentage, MA federal cost share percentage, and MA Priority in each MA action show the correct values for the MA Number as a whole, based on the most recent MA amendment. Similarly, the MA state/tribe/territory cost share amount and MA federal cost share amount show the correct amounts for each MA action, calculated using the percentages from the most recent MA amendment. \n\nConversely, the POP start date, POP end date, state/tribe/territory cost share percentage, federal cost share percentage, and priority show the values that were correct at the time of each MA action. Further, the state/tribe territory cost share amount and federal cost share amount show the amounts that were correct at the time of each MA action. \n\nFor these reasons, the MA state/tribe/territory cost share amount and MA federal cost share amount values can be summed by MA Number, whereas the state/tribe/territory cost share amount and federal cost share amount values cannot. All cost shares are calculated by multiplying the applicable cost share percentage by the obligation amount.\n\nIn rare instances, mission assignments for disasters declared prior to October 1, 2012 may not yet be fiscally closed. Those mission assignments are not reflected in this dataset, nor are any mission assignment actions taken on or after October 1, 2012 that relate to those disaster declarations. \n\nDue to administrative changes over time, Agency names for certain MA actions may contain text such as \"DO NOT USE\" or \"AMENDMENT.\" These agency names should be ignored in favor of the plain language names also associated with those same Agency IDs in other MA records.\n\nThis dataset is not intended to be used for any official federal financial reporting and should not be considered an official federal report.\n\nCitation: 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.\n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/PublicAssistanceGrantAwardActivities","rel":"PublicAssistanceGrantAwardActivities","title":"This dataset contains data on Public Assistance project awards (obligations), including the project obligation date(s); dollar amount of Federal Share Obligated for each project and its obligation date(s); FEMA Region; State; Disaster Declaration Number; descriptive cause of the declaration (Incident Type); Entity requesting public assistance (Applicant Name); and distinct name for the repair, replacement or mitigation work listed for assistance (Project Title).  \n\nAs part of disaster declarations, the President can make federal funding (Public Assistance) available through FEMA to eligible state, local and tribal governments and certain private nonprofit organizations. This is done on a cost-sharing basis for emergency work and the repair, replacement, or mitigation work for facilities damaged by the disaster event. \n\nAs part of Congressional bill HR 152 - the Sandy Recovery Improvement Act of 2013, FEMA is providing the following information for our stakeholders: Region, Disaster Declaration Number, Disaster Type, State, Applicant, County, Damage Category Code, Federal Share Obligated, and Date Obligated.\n\nNote: FEMA obligates funding for a project directly to the Recipient (State or Tribe). It is the Recipient's responsibility to ensure that the eligible subrecipient (listed in the dataset as Applicant Name) receives the award funding.\n\nThis dataset lists details about project versions (occurring when the scope/cost changes for a project). Versions adjust the cost of the project  with positive additions called obligations and subtractions called deobligations. Combined, they reconcile to reflect the Total Federal Share Obligation, but reconciliation occurs over the life of the project - sometimes years after the declaration date. The prior version of this dataset included project obligations within a seven-day period prior to the listed date. This version includes obligations from 1998 to present, excluding obligations uploaded on the same day as the publication. Open projects still under pre-obligation processing are not represented. For more information on the Public Assistance process see: https://www.fema.gov/assistance/public/process\n\nThis is raw, unedited data from FEMA's Emergency Management Mission Integrated Environment (EMMIE) system and as such is subject to a small percentage of human error. The financial information is derived from EMMIE and not FEMA's official financial systems. Due to differences in reporting periods, status of obligations and how business rules are applied, 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 financial reporting.\n\nFEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq\n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/IndividualsAndHouseholdsProgramValidRegistrations","rel":"IndividualsAndHouseholdsProgramValidRegistrations","title":"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 IA applications from DR1439 (declared in 2002) to those declared over 30 days ago. The full data set is refreshed on an annual basis. A weekly refresh occurs to update disasters declared in the last 18 months. Valid Registrations includes all major disasters and only valid registrants.\n\nIHP is intended to meet basic needs and supplement disaster recovery efforts. The IHP 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. \n\nThis is raw, unedited data from FEMA's National Emergency Management Information System (NEMIS) and as such is subject to a small percentage of human error. \n\nAny financial information is derived from NEMIS and not FEMA's official financial systems. Due to differences in reporting periods, status of obligations and how business rules are applied, 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 financial reporting.\n\nThis dataset is not intended to be an official federal report and should not be considered an official federal report. \n\nCitation: 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.\n\nDue 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.  \n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2/PublicAssistanceFundedProjectsDetails","rel":"PublicAssistanceFundedProjectsDetails","title":"The Public Assistance Funded Projects Details dataset contains obligated (financial obligation to grantee) Public Assistance projects, lists public assistance recipients designated as applicants in the data, and a list of every funded, individual project, called project worksheets. Open projects still under pre-obligation processing are not represented. Applicant details can be obtained by relating this dataset with the OpenFEMA Public Assistance Applicants dataset using the Applicant ID field.\n\nFEMA provides supplemental Federal disaster grant assistance for debris removal, emergency protective measures, and the repair, replacement, or restoration of disaster-damaged, publicly owned facilities and the facilities of certain Private Non-Profit (PNP) organizations through the PA Program (CDFA Number 97.036). The PA Program also provides 406 hazard mitigation funding for damaged facilities during the recovery process to encourage protection from future events. See FEMA PA Hazard Mitigation: https://www.fema.gov/assistance/public/hazard-mitigation\n\nData comes from FEMA's Applicant Case Tracker (FAC-Trax), which includes the Grants Manager (GM) database.  This raw unedited data is subject to a small percentage of human error. The financial information is derived from GM 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 www.usaspending.gov. This dataset is not intended to be used for any official federal reporting.                 \n\nThe data has been incorporated into a graphic visualization at Public Assistance Program Summary of Obligations: https://www.fema.gov/data-visualization/public-assistance-program-summary-obligations. Questions pertaining to the data visualizations should be addressed to EnterpriseAnalytics@fema.dhs.gov.\n\nFEMA's terms and conditions and citation requirements for datasets (API usage or file downloads) can be found on the OpenFEMA Terms and Conditions page: https://www.fema.gov/about/openfema/terms-conditions\n\nFor answers to Frequently Asked Questions (FAQs) about the OpenFEMA program, API, and publicly available datasets, please visit: https://www.fema.gov/about/openfema/faq\n\nIf you have media inquiries about this dataset, please email the FEMA Press Office at FEMA-Press-Office@fema.dhs.gov. For inquiries about FEMA's data and Open Government program, please email the OpenFEMA team at OpenFEMA@fema.dhs.gov.","type":"application/json"},{"href":"/api/open/v2","rel":"self","title":"API Version 2 datasets","type":"application/json"},{"href":"/api/open","rel":"parent","title":"API version discovery","type":"application/json"}],"meta":{"version":2,"datasetCount":15,"lifeCycleStage":"PUBLISHED"}}