OpenFEMA Dataset: Hazard Mitigation Assistance Projects - v2
Entity Name | HazardMitigationAssistanceProjects |
---|---|
API Endpoint | https://www.fema.gov/api/open/v2/HazardMitigationAssistanceProjects |
Update Frequency | R/P1D |
Program URL | https://www.fema.gov/grants/mitigation |
Category | Hazard Mitigation |
Keywords | mitigation |
Deprecation Date | 2023-01-31 |
Deprecation Message | A newer version of this OpenFEMA dataset has been released. This older dataset version will be archived by 1/31/2023. The following page details the latest version of this data set: https://www.fema.gov/openfema-data-page/hazard-mitigation-assistance-projects-v3. |
Deprecation New URL | https://www.fema.gov/openfema-data-page/hazard-mitigation-assistance-projects-v3 |
Description
The dataset contains funded projects (financial obligation to grantee) under the Hazard Mitigation Assistance (HMA) grant programs. 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 Pre-Disaster Mitigation (PDM) grant program. This dataset also contains data from the HMA grant programs that were eliminated by the 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 .
If 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.
Full Data
Format | Address | Record Count | Approximate File Size |
---|---|---|---|
csv | Link to csv | 32521 | small (10MB - 50MB) |
json | Link to json | 32521 | small (10MB - 50MB) |
jsona | Link to jsona | 32521 | small (10MB - 50MB) |
jsonl | Link to jsonl | 32521 | small (10MB - 50MB) |
Data Fields
Name | Title | Type | Description | Is Searchable |
---|---|---|---|---|
region | Region |
smallint
|
Number (1-10) used to represent the Region associated with the project | yes |
stateNumberCode | State Number Code |
text
|
FIPS code corresponding to the State (e.g., 51 represents Virginia/VA) associated with the project | yes |
state | State |
text
|
Full name of the State (e.g., Virginia) associated with the project | yes |
countyCode | County Code |
text
|
FIPS code uniquely identifying the primary county (e.g., 011 represents Broward County) associated with the project. Note, projects can be associated with more than one county (see the Project Counties field) and are often reported as Statewide (e.g., 000 represents Statewide) | yes |
county | County |
text
|
Full name of the primary county (e.g., Broward) associated with the project. Note, projects can be associated with more than one county (see the Project Counties field) and are often reported as Statewide (e.g., 000 represents Statewide) | yes |
programArea | Program Area |
text
|
Hazard Mitigation Assistance grant program areas such as FMA - Flood Mitigation Assistance grant program, HMGP - Hazard Mitigation Grant Program, LPDM -Legislative Pre-disaster Mitigation grant program, PDM - Pre-disaster Mitigation grant program, RFC - Repetitive Flood Claims grant program, SRL - Severe Repetitive Loss grant program | yes |
projectIdentifier | Project Identifier |
text
|
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 |
projectType | Project Type |
text
|
Project, or activity, type(s) for the project. When a project involves more than one type/activity, a semicolon-delimited list of types/activities is displayed | yes |
projectTitle | Project Title |
text
|
Title of the project. This field is no longer available by the OpenFEMA API. This information can requested through the standard FOIA process. | yes |
projectCounties | Project Counties |
text
|
County, or Counties, associated with the project. When a project involves more than one county, a semicolon-delimited list of counties is displayed | yes |
numberOfProperties | Number Of Properties |
smallint
|
Proposed number of properties to be mitigated by the project | yes |
numberOfFinalProperties | Number Of Final Properties |
smallint
|
Actual number of properties mitigated by the project | yes |
status | Status |
text
|
Current status of the project. The following options for status are: Approved: Refers to HMGP projects that have been approved for award by FEMA and for which funds have been obligated Awarded: Refers to PDM and FMA projects from before FY2004 that have been approved for award by FEMA and for which funds have been obligated Obligated: Refers to PDM and FMA projects from FY2004 onward and FY19 BRIC projects that have been approved for award by FEMA and for which funds have been obligated Completed: Refers to FMA projects from FY2003 and earlier that were approved for award and fiscally reconciled at the end of the performance period Closed: Refers to all HMGP and PDM projects and FMA projects from FY2004 onward that were approved for award and fiscally reconciled at the end of the performance period. Please note that there might be projects in these categories that do not meet these definitions. | yes |
subgrantee | Subgrantee |
text
|
Name of the subgrantee involved in the project | yes |
costSharePercentage | Cost Share Percentage |
decimal
|
Proposed percentage of the project cost to be covered by FEMA | yes |
projectAmount | Project Amount |
decimal
|
Total cost of the project as submitted in the project application | yes |
federalShareObligated | Federal Share Obligated |
decimal
|
Federal share obligated for eligible activities | yes |
programFy | Program FY |
smallint
|
The fiscal year the disaster declaration date for disaster programs; the fiscal year from the Project Identifier for non-disaster programs (e.g., 2005 from PDMC-PJ-04-AL-2005-001) | yes |
dateInitiallyApproved | Date Initially Approved |
date
|
Date the project was initially approved by FEMA. For HMGP projects, this date is based on the Regional Directors signature date for the first amendment that was approved | yes |
dateApproved | Date Approved |
date
|
Date the project was approved by FEMA. For HMGP projects, this date is based on the Regional Directors signature date for the latest amendment that was approved | yes |
dateClosed | Date Closed |
date
|
Date the project was closed by FEMA | yes |
disasterNumber | Disaster Number |
smallint
|
Sequentially assigned number used to designate an event or incident declared as a disaster. For more information on the disaster process, https://www.fema.gov | yes |
grantee | Grantee |
text
|
Name of the grantee (recipient) to which the grant is awarded. The grantee (recipient) is accountable for the use of the funds provided by FEMA and is responsible for disbursing those funds to the subgrantee (subrecipient) | yes |
benefitCostRatio | Benefit Cost Ratio |
decimal
|
The Benefit-Cost Ratio (BCR) is a numerical expression of the cost-effectiveness of a project. The BCR is derived from a project's total net benefits divided by its total project cost. Composite BCRs of 1.0 or greater have more benefits than costs, and are therefore cost-effective | yes |
netValueBenefits | Net Value Benefits |
decimal
|
Net present value of benefits from the Benefit-Cost Analysis that represents the amount of benefits that will occur for the life of the project | yes |
granteeTribalIndicator | Grantee Tribal Indicator |
boolean
|
Indicates if the grantee (recipient) is Tribal | yes |
subgranteeTribalIndicator | Subgrantee Tribal Indicator |
boolean
|
Indicates if the subgrantee (subrecipient) is Tribal | yes |
id | ID |
uuid
|
Unique ID assigned to the record | yes |
See Also
Access the metadata API calls for additional information: