OpenFEMA Dataset: Hazard Mitigation Assistance Projects by NFIP CRS Communities - v1
|Keywords||assistance, HMA, HMGP, BRIC, PDM, FMA, SRL, RFC, NFIP, CRS|
This dataset contains funded projects under FEMA's Hazard Mitigation Assistance (HMA) grant programs by communities participating in the National Flood Insurance Program (NFIP) Community Rating System (CRS). The Hazard Mitigation Assistance Projects by NFIP CRS Communities dataset can be joined to the OpenFEMA Hazard Mitigation Assistance Funded Project dataset by the Project Identifier field. Note, not all projects in the Hazard Mitigation Assistance Funded Project dataset will associate to an NFIP CRS Community. For more information on the NFIP CRS Program, visit https://www.fema.gov/flood-insurance/rules-legislation/community-rating-system.
FEMA administers three programs that provide funding for eligible mitigation planning and projects that reduces disaster losses and protect life and property from future disaster damages. The three programs are the Hazard Mitigation Grant Program (HMGP), Flood Mitigation Assistance (FMA) grant program, and Building Resilient Infrastructure and Communities (BRIC) grant program. This dataset also contains data from the HMA grant programs that were eliminated by the Disaster Recovery Reform Act of 2018 (Pre-Disaster Mitigation (PDM) grant program) and Biggert Water Flood Insurance Reform Act of 2012 (Repetitive Flood Claims (RFC) grant program and Severe Repetitive Loss (SRL) grant program). For more information on the Hazard Mitigation Assistance grant programs, please visit: https://www.fema.gov/grants/mitigation.
This is raw, unedited data from FEMA's National Emergency Management Information System (NEMIS) and Mitigation eGrants Systems and is subject to a small percentage of human error. This dataset is not derived from FEMA's official financial system and is not intended to be used for any official federal financial reporting. Due to differences in reporting periods, status of obligations and how business rules are applied, the financial information in this dataset may differ slightly from official publication on public websites such as usaspending.gov.
Please note that jurisdictions may participate in multiple plans. This is raw, unedited data that is dependent on Regional entry, as such it is subject to human error and delayed entry of plan information. The data is updated from authoritative sources and has a minimum 24 hour delay. Citation: The agency's preferred citation for each dataset is included in its metadata. Users should also cite the date that data was accessed or retrieved from fema.gov and/or Data.gov. Finally, users must clearly state that 'FEMA and the Federal Government cannot vouch for the data or analyses derived from these data after the data have been retrieved from the Agency's website(s) and/or Data.gov.' Place name may differ from official naming standard referenced in update organization documents (i.e. Tribal name under BIA list or other authoritative source Village of, City of, etc).
If you have media inquiries about this dataset please email the FEMA News Desk FEMA-News-Desk@dhs.gov or call (202) 646-3272. For inquiries about FEMA's data and Open government program please contact the OpenFEMA team via email OpenFEMA@fema.dhs.gov.
|Format||Address||Record Count||Approximate File Size|
|csv||Link to csv||47565||tiny (< 10MB)|
|json||Link to json||47565||tiny (< 10MB)|
|jsona||Link to jsona||47565||tiny (< 10MB)|
|Single-value that uniquely identifies the project. Disaster-based projects use the convention of DR-disaster number-project number-suffix (e.g., DR-1761-0001-M) while non-disaster projects use the unique project number (e.g., FMA-PJ-10-WA-2017-006).||yes|
|Name of the community participating in the National Flood Insurance Program's Community Rating System (NFIP's CRS)||yes|
|Identifier assigned to the community participating in the National Flood Insurance Program's Community Rating System (NFIP's CRS).||yes|
|MD5 hash of fields and values of the record||yes|
|Date the record was last updated in the API data store||yes|
|Unique ID assigned to the record that does not persist between data set refreshes||yes|
Access the metadata API calls for additional information: