This page has not been translated into Español. Visit the Español page for resources in that language.
OpenFEMA Dataset: Non-Disaster and Assistance to Firefighter Grants - v1
The Grant Programs Directorate strategically and effectively administers and manages FEMA grants to ensure critical and measurable results for customers and stakeholders. The grants represented in this dataset are Preparedness (Non-Disaster or ND) Grants and Assistance to Firefighters Grants (AFG).
ND Grants and AFG are awarded and managed differently within the Grants Program Directorate (GPD) and should be treated with discretion.
The only measure in this dataset is Award Amount. It is an additive measure that can be applied across multiple dimensions to create various views of the data.
AFG awards are assigned to individual Fire Departments. ND Grants are typically assigned to state agencies; however, exceptions do exist such as Port Security Grant Program which is assigned to port areas and not States. It is important to know that when looking at Award Amount by State it does not mean the State actually received that money. In addition, some grant programs may have pass-through requirements where the recipient State is required to sub-grant a minimum amount of the award and only retain a portion of the award.
Grants guidance is described in the Funding Opportunity Announcement (FOA). Each grant program has its own grant guidance containing eligibility requirements, program objectives, and funding restrictions which are published annually. FOAs are public documents and may be found online at www.fema.gov/grants.
For more information on grants, visit https://www.fema.gov/grants/preparedness and https://www.fema.gov/grants/preparedness/firefighters
If you have media inquiries about this dataset, please email the FEMA News Desk at FEMA-News-Desk@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.
|Formato||Dirección||Record Count||Approximate File Size|
|csv||Link to csv||66534||tiny (< 10MB)|
|json||Link to json||66534||tiny (< 10MB)|
|jsona||Link to jsona||66534||tiny (< 10MB)|
|The agreed upon term for the number assigned to each individual award within the grant program and fiscal year. Each award number is unique to that year and recipient. This is sometimes referred to as 'Contract Number', 'Purchase Order Number', or 'Obligation Number'||yes|
|Represents the government budget fiscal year, which is from October 1st - September 30th. Note: Some grant programs are budgeted for a fiscal year and spent in another ' i.e. multi-year funded awards place money from current fiscal year appending a prior award number||yes|
|The program name and fiscal year in which the money was appropriated. Name of the grant program from grants.gov and set in the funding notification announcement. This term is also referred to in other sources as 'Solicitation' or 'Grant Title'||yes|
|Abbreviation for Program Name. NOTE: FIELD NOT AVAILABLE AT THIS TIME.||yes|
|The state in which the awardee is located. This is also referred to as 'Vendor State Code'||yes|
|The amount of allocated funds that are obligated to an awardee. While this is synonymous to 'Obligated Amount', Award Amount is the agreed upon term for use in R&IM reports. Note: Funds can be de-obligated so this amount is not final until award is closed. Therefore, in reports, terms such as 'Initial Award Amount' and 'Current Award Amount' can and should be used where necessary||yes|
|Vendor States are assigned to a geographic regions. There are 58 US states and territories and each is assigned to 1 of 10 regions. Regions are 1-5 are rolled up to Eastern and 6-10 are Western||yes|
|This term refers to the award recipient, as documented in IFMIS. This field is also known as 'Awardee', 'Grantee', 'Recipient' or 'Project' (the latter only in ARRA Reporting)||yes|
|Unique ID assigned to the record||yes|
|MD5 Hash of fields and values of the record||no|
|lastRefresh||Last Refresh Date||
|Date the record was last updated in the API data store||yes|
Access the metadata API calls for additional information: