Page 20 of 28. Choose a displayed profile to read the values. A source period is not a promise of current conditions or complete county coverage.
More data displayed here
These source products supply tables already selected for our topic guides. Open a displayed profile to read the values with their source context. This catalog does not cover every U.S. dataset or every source retained by LocalFactBook.
Each table keeps its own data period and geography vintage. Coverage counts profiles with a nonempty table, including tables containing missing values; it does not mean every measure is reported. Display permission does not grant downloads, redistribution or API access.
openFDA food, drug and device enforcement reports (recall enforcement data)
Recall events by product type and FDA classification, 2021 to 2025, firms in this state
Data period
Enforcement report dates 2021-01-01 to 2025-12-31, five years combined
Geography vintage
The 50 States, the District of Columbia and Puerto Rico, by the state the source prints for the recalling firm; records for firms outside these (foreign firms, other territories, no state) are not on these pages
Units and scope
Count of distinct recall events over the five years by product type and classification as the FDA publishes it.
States / equivalents with this table
52 of 52 supported profiles
Counties / equivalents with this table
0 of 3,222 supported profiles
This table's extension metadata provides the period above; it does not provide a separately verified publisher release identifier or retrieval date.
These are counts of recall events reported in FDA enforcement reports and classified by the FDA, counted by the state of the firm that carried out the recall, not where the product was sold or where anyone was harmed, and not a measure of how safe a state's products are. A recall event is one FDA event identifier; one event can cover many products and is counted once.
The year is the date the recall appeared in the FDA Enforcement Report, which can be later than when the firm began the recall. Classification is the FDA's own: Class I is a reasonable probability of serious adverse health consequences or death, Class II a temporary or medically reversible health consequence, Class III unlikely to cause adverse health consequences. Recalls not yet classified are counted in the product totals only. An event with products in more than one class is counted in each class.
Zero is a count of zero events in the complete set of enforcement reports retrieved for that state, year and product type, not a missing value. Large firms and states with many manufacturers have more recalls; counts are not adjusted for the number of firms. Names of firms are not shown.
Food, drug and device recall events by year, firms in this state (FDA enforcement reports)
Data period
Enforcement report dates 2021-01-01 to 2025-12-31 (five calendar years)
Geography vintage
The 50 States, the District of Columbia and Puerto Rico, by the state the source prints for the recalling firm; records for firms outside these (foreign firms, other territories, no state) are not on these pages
Units and scope
Count of distinct recall events per year and product type, and per year and FDA classification (all product types).
States / equivalents with this table
52 of 52 supported profiles
Counties / equivalents with this table
0 of 3,222 supported profiles
This table's extension metadata provides the period above; it does not provide a separately verified publisher release identifier or retrieval date.
These are counts of recall events reported in FDA enforcement reports and classified by the FDA, counted by the state of the firm that carried out the recall, not where the product was sold or where anyone was harmed, and not a measure of how safe a state's products are. A recall event is one FDA event identifier; one event can cover many products and is counted once.
The year is the date the recall appeared in the FDA Enforcement Report, which can be later than when the firm began the recall. Classification is the FDA's own: Class I is a reasonable probability of serious adverse health consequences or death, Class II a temporary or medically reversible health consequence, Class III unlikely to cause adverse health consequences. Recalls not yet classified are counted in the product totals only. An event with products in more than one class is counted in each class.
Zero is a count of zero events in the complete set of enforcement reports retrieved for that state, year and product type, not a missing value. Large firms and states with many manufacturers have more recalls; counts are not adjusted for the number of firms. Names of firms are not shown.
OpenFEMA Disaster Declarations Summaries, version 2
A declaration is a federal decision to make assistance available. It is not a measure of damage, deaths or cost, and a county without one may still have been hit.
Each row counts declarations for one type of incident. A single event can bring several declarations, such as an emergency and then a major disaster.
Declarations for COVID-19 are recorded as Biological incidents and designated nearly every county in 2020.
Statewide and tribal designations without a county code are not counted. Declarations are added continuously, so the count can rise.
These are county figures, not figures for any city or place within the county.
OpenFEMA Disaster Declarations Summaries, version 2
These are counts of declarations, not damage, deaths, cost or aid. A declaration is a federal decision to make assistance available; a state without one in a year may still have been hit.
A major disaster, an emergency and a fire management assistance declaration are counted separately, so a single event can appear in more than one. Each disaster number in a state is counted once however many of its counties were designated.
Incident groups follow the incident type FEMA records: hurricane includes tropical storm, typhoon and tropical depression; severe storm includes tornado, straight-line winds, winter storm, severe ice storm, snowstorm and coastal storm; other is every remaining type, including biological (COVID-19), earthquake and landslide.
The year is the calendar year of the declaration date, not of the event, and 2026 is partial. Declarations are added continuously, so counts can rise.
A zero is a complete count with no declaration of that kind, because the source lists every declaration it has. Tribal declarations are not counted in a state.
OpenFEMA Hazard Mitigation Grant Program Disaster Summaries, version 3, with Hazard Mitigation Assistance Subapplications, version 2
The Hazard Mitigation Grant Program (HMGP) funds projects that reduce future disaster losses after a federal disaster declaration. These figures are money committed (obligated), not money paid, and not disaster damage or total federal aid.
Rows are by the calendar year a disaster was declared, not the year funds were obligated. Funds obligated are the project funds in FEMA’s disaster summaries; management costs are not included. A disaster that has not obligated project funds shows no dollars.
A declared disaster with HMGP funding is one FEMA disaster number in one state that has an HMGP summary record; it counts all three programs FEMA lists (HMGP, HMGP Post Fire and Fire Management Assistance HMGP).
Projects are Hazard Mitigation Assistance subapplications of type Project under those programs, placed in the state and declaration year of their disaster. Plans, 5 percent initiative, management cost and pending-type records are not counted. Counts for recent disasters are low because projects are still being submitted.
A state with no declared disaster in a year shows zero declarations and projects, because the source is a complete list of its summaries; dollars there are Not reported, never zero. A declaration whose obligation FEMA left blank adds nothing to the dollars.
Disasters in Micronesia, the Marshall Islands and Palau have no Census state code and are not shown. FEMA does not publish the benefiting county for these projects, so there are no county tables.
OpenFEMA Housing Assistance Program Data - Owners and Renters, version 2
Individuals and Households Program registrations and FEMA-approved amounts, disasters declared 2017 to date (FEMA)
Data period
Disasters declared 2017-01-01 through 2026-10-27 (ten calendar years, 2026 partial); amounts approved as of the data refresh; retrieved 2026-11-04
Geography vintage
County names as FEMA reports them with the state, matched exactly to Census counties by state and normalized name; no county code in the source; Connecticut’s former counties are not matched to planning regions
Units and scope
Number of disasters and valid registrations, and whole U.S. dollars approved by FEMA (not adjusted for inflation).
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
2,384 of 3,222 supported profiles
This table's extension metadata provides the period above; it does not provide a separately verified publisher release identifier or retrieval date.
These are amounts FEMA approved for households under its Individuals and Households Program, not damage and not total losses. They cover valid registrations for disasters declared from January 1, 2017 (ten calendar years, the last one partial) in counties FEMA designated for Individual Assistance. Housing assistance is repair, replacement and rental assistance; other needs assistance is personal property, transportation, medical, dental, funeral, moving and similar items. The program does not include Public Assistance to governments, flood insurance payments, Small Business Administration loans, insurance, other agencies’ programs or private losses.
A valid registration is a household application received in an Individual Assistance county during the registration period; it is not a household that received aid, and approved dollars are for the households FEMA approved. Owners and renters are separate FEMA tallies and are added here. Dollars are approved amounts as of the data’s refresh, not adjusted for inflation, and change as cases are amended. The source total can differ from the sum of its listed housing and other needs amounts, so the three amounts are shown as FEMA reports them and are not forced to add.
The period is set by the date each disaster was declared. A disaster counts for a county when the county has valid registrations for it. FEMA publishes these figures by disaster and ZIP code with a county name but no county code, so counties are matched to this site’s counties by exact state and county name (case, accents, punctuation, “Saint” and “St.” and the county type word only); rows whose county text is a city, tribe, island area or anything else not matched exactly, and Connecticut’s former counties, are in no table and are not guessed.
Privacy rule: FEMA’s figures are already counts and dollar totals, never applicants. A county-disaster combination with fewer than 10 valid registrations (owners plus renters) is small enough to be suppressed, and its registrations and dollars are not published or added into any figure on this site. A county’s figures are shown only when none of its disasters in the period was under 10 registrations; a county with any such disaster has no table, and Not reported is not zero.
These are county figures, not figures for any city, ZIP code or place within the county, and they say nothing about the severity of any disaster or the need of a place.
OpenFEMA NFIP Redacted Policies v3 and NFIP Redacted Claims v3
These figures describe flood insurance bought through the National Flood Insurance Program (NFIP), not flood risk. A county with few policies is not a county with little flooding, because people choose whether to insure, lenders require it only in mapped high-risk areas, and some homes carry private flood insurance that is not counted here.
Policies in force are the policy records whose effective date is on or before, and whose termination date is after, the as-of date shown. FEMA counts one policy per insured unit, so a condominium association policy counts once for each unit it insures. Coverage in force is the total of the building and contents coverage limits on those policies. It is the maximum the policies could pay, not the value of the property or a prediction of loss.
Paid claims are NFIP claims whose building, contents and increased-cost-of-compliance payments add up to more than zero. The total paid is the sum of those payments as recorded, before recoveries such as salvage and subrogation, and includes the negative adjustments FEMA records when a check is reissued. Dollars are as paid in the year of the claim, not adjusted for inflation. The claims file begins with losses in 1978.
FEMA publishes a county code for each claim. The policies file has no separate county column, so the county of a policy is the first five digits (state and county FIPS code) of the Census block group identifier FEMA assigns to the insured address. Nothing else, such as a ZIP code or coordinates, is used to place a record in a county. Records without a usable code are not assigned to any county.
FEMA still reports Connecticut by its former counties, which the Census planning regions on this site replaced, so Connecticut is omitted. Where FEMA uses a county code that is not in this site’s county list, a county with no records in that state is Not reported rather than zero; other counties show a zero only when FEMA’s files carry no policy or claim for them.
This is FEMA’s public redacted data and it is revised monthly. No individual policy or claim is shown or kept; only county counts and sums are.
These are county figures, not figures for any city or place within the county.
OpenFEMA Public Assistance Funded Projects Details, version 2
Public Assistance projects and federal share obligated, disasters declared 2017 to date (FEMA)
Data period
Projects of disasters declared 2017-01-01 through 2026-09-01 (ten calendar years, 2026 partial); federal share obligated as of the data refresh of 2026-11-02; retrieved 2026-11-03
Geography vintage
Applicant county FIPS codes as FEMA reports them (state code plus county code), matched to Census counties by code; Connecticut’s former counties are not matched to planning regions
Units and scope
Number of projects and whole U.S. dollars of federal share obligated (not adjusted for inflation).
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
2,867 of 3,222 supported profiles
This table's extension metadata provides the period above; it does not provide a separately verified publisher release identifier or retrieval date.
These are federal obligations for Public Assistance projects, not total damage and not all spending on a disaster. They are the federal share FEMA has obligated, as of the data’s refresh, for projects of disasters declared from January 1, 2017 (ten calendar years, the last one partial). Public Assistance reimburses governments and certain nonprofits for eligible emergency work and for repairing or replacing public facilities; it does not include FEMA aid to individuals and households, flood insurance payments, hazard mitigation grants, other federal agencies’ programs, insurance, state or local spending, or private losses.
The period is set by the year each disaster was declared, not the year the money was obligated or the work was done; a project can be obligated years after its declaration, so recent declarations are incomplete, and amounts change as projects are amended, closed out or de-obligated. The figures are obligations (money committed), not payments received. The newest disaster year in the file is partial.
A project is one Public Assistance project (project worksheet). Only projects whose eligibility status is Eligible are counted; Ineligible, Withdrawn and Pending Eligibility Review projects are set aside. “Projects with federal share obligated” counts the eligible projects with more than $0 obligated so far; an eligible project with nothing yet obligated counts in Projects only. One project can cover work in several places and is assigned to a single county.
The county is the applicant’s location as FEMA records it, not necessarily where the damage or the work occurred. Records whose county FEMA gives as Statewide, or leaves blank, are state-level applicants; they are included in the state figures and in no county, and a Statewide record is never given the county code FEMA attaches to it. Records with no state FIPS code (applicants such as some tribes, and territories outside this site’s state list) are in no table.
Categories are FEMA’s Public Assistance damage categories A to G, I and Z. Emergency protective measures (B) also includes donated-resource emergency work, and Management and administrative costs (Z) combines FEMA’s management cost, direct administrative cost and Section 324 management cost descriptions. Dollars are as obligated, not adjusted for inflation, and are shown rounded to whole dollars with the exact cents kept in the source field.
A place with no row in a category has no eligible project of that category in this file; a place with no table has no eligible project assigned to it. Neither is shown as zero. The figures describe federal funding for public projects and say nothing about the severity of any disaster or the need of a place.
FEMA still codes Connecticut by its former eight counties (09001 to 09015), which the Census planning regions on this site replaced, and publishes no crosswalk, so no Connecticut county has a table and nothing is allocated to a planning region; the Connecticut state figures include every Connecticut record. County tables add to less than the state figure because state-level applicants belong to no county. Areas join to this site’s counties by FIPS code only (state code plus county code, zero-padded); no name matching is used.
These are county figures, not figures for any city or place within the county.
OpenFEMA Public Assistance Funded Projects Details, version 2
Public Assistance projects and federal share obligated, disasters declared 2017 to date (FEMA)
Data period
Projects of disasters declared 2017-01-01 through 2026-09-01 (ten calendar years, 2026 partial); federal share obligated as of the data refresh of 2026-11-02; retrieved 2026-11-03
Geography vintage
State FIPS codes as FEMA reports them (the 50 states, the District of Columbia and Puerto Rico; other territories are not shown)
Units and scope
Number of projects and whole U.S. dollars of federal share obligated (not adjusted for inflation).
States / equivalents with this table
52 of 52 supported profiles
Counties / equivalents with this table
0 of 3,222 supported profiles
This table's extension metadata provides the period above; it does not provide a separately verified publisher release identifier or retrieval date.
These are federal obligations for Public Assistance projects, not total damage and not all spending on a disaster. They are the federal share FEMA has obligated, as of the data’s refresh, for projects of disasters declared from January 1, 2017 (ten calendar years, the last one partial). Public Assistance reimburses governments and certain nonprofits for eligible emergency work and for repairing or replacing public facilities; it does not include FEMA aid to individuals and households, flood insurance payments, hazard mitigation grants, other federal agencies’ programs, insurance, state or local spending, or private losses.
The period is set by the year each disaster was declared, not the year the money was obligated or the work was done; a project can be obligated years after its declaration, so recent declarations are incomplete, and amounts change as projects are amended, closed out or de-obligated. The figures are obligations (money committed), not payments received. The newest disaster year in the file is partial.
A project is one Public Assistance project (project worksheet). Only projects whose eligibility status is Eligible are counted; Ineligible, Withdrawn and Pending Eligibility Review projects are set aside. “Projects with federal share obligated” counts the eligible projects with more than $0 obligated so far; an eligible project with nothing yet obligated counts in Projects only. One project can cover work in several places and is assigned to a single county.
The county is the applicant’s location as FEMA records it, not necessarily where the damage or the work occurred. Records whose county FEMA gives as Statewide, or leaves blank, are state-level applicants; they are included in the state figures and in no county, and a Statewide record is never given the county code FEMA attaches to it. Records with no state FIPS code (applicants such as some tribes, and territories outside this site’s state list) are in no table.
Categories are FEMA’s Public Assistance damage categories A to G, I and Z. Emergency protective measures (B) also includes donated-resource emergency work, and Management and administrative costs (Z) combines FEMA’s management cost, direct administrative cost and Section 324 management cost descriptions. Dollars are as obligated, not adjusted for inflation, and are shown rounded to whole dollars with the exact cents kept in the source field.
A place with no row in a category has no eligible project of that category in this file; a place with no table has no eligible project assigned to it. Neither is shown as zero. The figures describe federal funding for public projects and say nothing about the severity of any disaster or the need of a place.
State figures add every eligible project whose state FIPS code is the state’s, including state-level applicants and Connecticut’s former counties, so a state is more than its county tables add to. Puerto Rico is shown as a separate state-level geography; Guam, the U.S. Virgin Islands, American Samoa and the Northern Mariana Islands are not shown.
OPM Federal Workforce Data, Employment dataset, September 2025 and September 2024 snapshots (version 1), summed to duty-station state and agency
Counts are federal civilian employees in the executive branch personnel data reported to the Office of Personnel Management (OPM), by the state of their official duty station, as of the September snapshot. They are not residents of the state and not all government workers: military personnel, postal employees, the legislative and judicial branches and state and local government are outside the source.
OPM withholds the duty-station location of a large share of employees (for example some defense, intelligence and law enforcement positions). Those employees appear in no state, so every state count is a lower bound and the shares shown are shares of employees with a published U.S. state duty station, not of all federal employees.
Employees with a U.S. territory, foreign or invalid duty station are outside these state counts. Agencies are the publisher’s agency names; the largest five by count in the state are shown, and an agency with no row in the other month is Not reported for that month, not zero.
September 2026 is OPM’s newest snapshot but OPM flags it as incomplete for the Department of War, so the two most recent complete September snapshots (2025 and 2024) are shown. A later OPM release can revise earlier snapshots.
Federal civilian employees by duty-station state (OPM)
Data period
September 2025 and September 2024 snapshots (retrieved 2026-11-04)
Geography vintage
States and the District of Columbia by two-digit FIPS code as published by OPM; territories and foreign locations excluded
Units and scope
Number of federal civilian employees (headcount), and share of employees with a published U.S. state duty station.
States / equivalents with this table
51 of 52 supported profiles
Counties / equivalents with this table
0 of 3,222 supported profiles
This table's extension metadata provides the period above; it does not provide a separately verified publisher release identifier or retrieval date.
Counts are federal civilian employees in the executive branch personnel data reported to the Office of Personnel Management (OPM), by the state of their official duty station, as of the September snapshot. They are not residents of the state and not all government workers: military personnel, postal employees, the legislative and judicial branches and state and local government are outside the source.
OPM withholds the duty-station location of a large share of employees (for example some defense, intelligence and law enforcement positions). Those employees appear in no state, so every state count is a lower bound and the shares shown are shares of employees with a published U.S. state duty station, not of all federal employees.
Employees with a U.S. territory, foreign or invalid duty station are outside these state counts. Agencies are the publisher’s agency names; the largest five by count in the state are shown, and an agency with no row in the other month is Not reported for that month, not zero.
September 2026 is OPM’s newest snapshot but OPM flags it as incomplete for the Department of War, so the two most recent complete September snapshots (2025 and 2024) are shown. A later OPM release can revise earlier snapshots.
OSHA Inspection and Violation data, state and fiscal year totals
Counts and dollar totals of OSHA inspections and cited violations in the Department of Labor bulk files retrieved 2026-11-04, not a measure of workplace safety, injuries or compliance. The files hold inspections by federal OSHA and by state-plan agencies as reported to OSHA; coverage and reporting differ by state.
Fiscal years run 1 October to 30 September. An inspection counts in the fiscal year of its open date and a violation in the fiscal year of its issuance date, so a violation can fall in a later fiscal year than its inspection. Recent fiscal years can still change: cases open, citations are issued after the inspection, and contested citations are revised.
Each violation takes its state from the inspection with the same activity number (the inspection site state). Violation records marked deleted in the source are excluded. Violations and inspections at sites outside the 50 states, the District of Columbia and Puerto Rico are not shown.
Violation types are as coded by OSHA: Serious, Willful, Repeat, Other-than-serious and Unclassified; any other or blank code is counted in its own row. Counts are cited violations (citation items), not workplaces, workers or hazards.
Initial penalty is the penalty first proposed for a violation; current penalty is the penalty after later adjustment, settlement or decision, as last recorded. A violation with a blank penalty amount contributes nothing to a total and is not treated as zero; a total is Not reported when no violation in the row has an amount, and the number of violations with an amount is shown beside each total. Penalty totals are not comparable between states without that count.
A year with no recorded inspection for the state is Not reported, never zero. Establishment names, addresses, owners and individual cases are not used or shown. Counts are for the state; they are not divided by employment or population and states are not compared.