Source catalog

Source tables and coverage.

Page 17 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.

National Inventory of Dams, county counts by hazard potential and primary purpose

Original publisher: U.S. Army Corps of Engineers. Publisher documentation and methods.

Dams by hazard potential and primary purpose (National Inventory of Dams, county)

Data period
Inventory file dated 2026-10-30 (publisher "Data Last Updated"), retrieved 2026-11-04; last-modified not stated.
Geography vintage
Counties as named in the NID file, matched to this site’s county roster by exact state and normalised county name (the file has no FIPS codes); Connecticut planning regions, Alaska areas that do not match, and names shared by a county and an independent city are Not reported
Units and scope
Dams: number of dam records in the National Inventory of Dams. Storage: acre-feet (NID storage).
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
3,023 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.

Displayed here

Explore the topic: Energy and utility measures

Coverage and interpretation
  • Counts of dams in the National Inventory of Dams as of the file dated 2026-10-30 (retrieved 2026-11-04), not a count of every dam in the country: the inventory covers dams that meet federal or state size and hazard criteria. Each record is a dam or associated structure as the NID lists it; associated structures such as saddle dams are counted as listed.
  • Hazard potential is the NID classification by the potential consequences of failure (High, Significant, Low, Undetermined), as published. It is not a rating of condition or of the chance of failure.
  • Primary purpose is the first purpose recorded for the dam, collapsed into the groups shown; Other purposes combines Other, Fish and Wildlife Pond, Tailings, Grade Stabilization, Debris Control and Navigation. A dam with no primary purpose in the file is shown as not stated, not inferred.
  • NID storage is in acre-feet as reported by the dam’s regulator or owner, over the dams that report one; blank and 0 are treated as no figure. A total is a sum of reported figures and is not the water held today.
  • Dam names, owners, rivers, coordinates and inspection or condition records are not used or shown.
  • Counts are for the area; they are not divided by population or area and places are not compared.
  • County rows are matched on name, not on a code. A dam with a blank county, a county name that does not exactly match one roster county, or a name shared by a county and an independent city (such as Baltimore, Fairfax or Richmond) appears on the state page but on no county page. Connecticut’s file uses the old counties and has no county pages.

National Inventory of Dams, state counts by hazard potential and primary purpose

Original publisher: U.S. Army Corps of Engineers. Publisher documentation and methods.

Dams by hazard potential and primary purpose (National Inventory of Dams, state)

Data period
Inventory file dated 2026-10-30 (publisher "Data Last Updated"), retrieved 2026-11-04; last-modified not stated.
Geography vintage
States, the District of Columbia and Puerto Rico, matched on the state name in the file
Units and scope
Dams: number of dam records in the National Inventory of Dams. Storage: acre-feet (NID storage).
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.

Displayed here

Explore the topic: Energy and utility measures

Coverage and interpretation
  • Counts of dams in the National Inventory of Dams as of the file dated 2026-10-30 (retrieved 2026-11-04), not a count of every dam in the country: the inventory covers dams that meet federal or state size and hazard criteria. Each record is a dam or associated structure as the NID lists it; associated structures such as saddle dams are counted as listed.
  • Hazard potential is the NID classification by the potential consequences of failure (High, Significant, Low, Undetermined), as published. It is not a rating of condition or of the chance of failure.
  • Primary purpose is the first purpose recorded for the dam, collapsed into the groups shown; Other purposes combines Other, Fish and Wildlife Pond, Tailings, Grade Stabilization, Debris Control and Navigation. A dam with no primary purpose in the file is shown as not stated, not inferred.
  • NID storage is in acre-feet as reported by the dam’s regulator or owner, over the dams that report one; blank and 0 are treated as no figure. A total is a sum of reported figures and is not the water held today.
  • Dam names, owners, rivers, coordinates and inspection or condition records are not used or shown.
  • Counts are for the area; they are not divided by population or area and places are not compared.
  • State figures count every dam the file places in the state, including dams that cannot be placed on a county page; they are not summed from the county tables. Dams in territories without a page here (such as Guam) are not shown.

National Register of Historic Places, properties listed, file dated May 22, 2026, counted by county

Original publisher: National Park Service, U.S. Department of the Interior. Publisher documentation and methods.

Properties listed in the National Register of Historic Places (NPS, county)

Data period
National Register listings as of the NPS file dated May 22, 2026 (file Last-Modified Fri, 22 May 2026 17:53:35 GMT; NPS page “Last updated: June 4, 2026”)
Geography vintage
Counties by exact normalized (state, county name) match of the NPS file to this site’s county list; the file has no county code; Connecticut former counties are not matched
Units and scope
Listings: number of listed properties (a count, not people).
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
3,140 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.

Displayed here

Explore the topic: Population and growth

Coverage and interpretation
  • Counts of properties listed in the National Register of Historic Places in the National Park Service file dated May 22, 2026, not a count of historic buildings that exist or a statement about their condition or protection. “Listed” means the property is on the Register; it is different from “eligible” (found to meet the criteria, not listed) and from “delisted” (removed from the Register). The NPS file carries only the status Listed, and every row in it has that status; no eligible, pending or delisted records are in it or counted.
  • A listing is an original listing record: the file’s Request Type values Single and Multiple (properties listed on their own or under a multiple property submission). Records that document an action on an existing listing or a non-listing (additional documentation, resubmission, boundary change, move, National Historic Landmark designation action, federal determination of eligibility, multiple-property cover sheet, and one record with no request type) are left out, so the totals are smaller than the number of rows in the file. The same listing repeated in the file is counted once.
  • A district, a building complex or a multiple-property listing is one listing, whatever number of buildings, structures, sites or objects it contains; the number of contributing resources is not published here. A property in more than one county is a separate listing record in each county the file names.
  • Resource category is the file’s Category of Property (building, district, site, structure, object), compared without regard to capitalization; a few records leave it empty and are shown in their own row. National Historic Landmarks are the listings with a landmark designation date in the file; the count is not a count of landmark districts or of all National Park Service units.
  • The file names a county and a state but carries no county FIPS code. Counties are matched to this site’s county list by exact normalized name within the state (case, accents and punctuation ignored, “Saint” and “St.” treated alike, the words County, Parish, Borough, Census Area and city dropped from this site’s names). A file name that matches no county, or more than one county of the state, is never guessed: it has no county table. In particular the file’s Virginia, Maryland and Missouri names that stand for both a county and an independent city of the same name cannot be told apart, and Alaska names from earlier borough and census-area boundaries do not match today’s. Connecticut is listed under its eight former counties, so Connecticut planning regions have no table.
  • Property names, addresses, cities and coordinates are not published here; only counts. Totals are not divided by population or area, and places are not compared or ordered.
  • Public data of the National Park Service, U.S. Department of the Interior (works of a federal agency). Source line: National Park Service, National Register of Historic Places Program. This site is not endorsed by the National Park Service.
  • County figures: the listings the file assigns to this county by name. They do not sum to the state total, because listings in county names without a county table (see the state page) are in the state total only.

National Register of Historic Places, properties listed, file dated May 22, 2026, counted by state

Original publisher: National Park Service, U.S. Department of the Interior. Publisher documentation and methods.

Properties listed in the National Register of Historic Places (NPS, state)

Data period
National Register listings as of the NPS file dated May 22, 2026 (file Last-Modified Fri, 22 May 2026 17:53:35 GMT; NPS page “Last updated: June 4, 2026”)
Geography vintage
States, the District of Columbia and Puerto Rico by the state name in each record
Units and scope
Listings: number of listed properties (a count, not people).
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.

Displayed here

Explore the topic: Population and growth

Coverage and interpretation
  • Counts of properties listed in the National Register of Historic Places in the National Park Service file dated May 22, 2026, not a count of historic buildings that exist or a statement about their condition or protection. “Listed” means the property is on the Register; it is different from “eligible” (found to meet the criteria, not listed) and from “delisted” (removed from the Register). The NPS file carries only the status Listed, and every row in it has that status; no eligible, pending or delisted records are in it or counted.
  • A listing is an original listing record: the file’s Request Type values Single and Multiple (properties listed on their own or under a multiple property submission). Records that document an action on an existing listing or a non-listing (additional documentation, resubmission, boundary change, move, National Historic Landmark designation action, federal determination of eligibility, multiple-property cover sheet, and one record with no request type) are left out, so the totals are smaller than the number of rows in the file. The same listing repeated in the file is counted once.
  • A district, a building complex or a multiple-property listing is one listing, whatever number of buildings, structures, sites or objects it contains; the number of contributing resources is not published here. A property in more than one county is a separate listing record in each county the file names.
  • Resource category is the file’s Category of Property (building, district, site, structure, object), compared without regard to capitalization; a few records leave it empty and are shown in their own row. National Historic Landmarks are the listings with a landmark designation date in the file; the count is not a count of landmark districts or of all National Park Service units.
  • The file names a county and a state but carries no county FIPS code. Counties are matched to this site’s county list by exact normalized name within the state (case, accents and punctuation ignored, “Saint” and “St.” treated alike, the words County, Parish, Borough, Census Area and city dropped from this site’s names). A file name that matches no county, or more than one county of the state, is never guessed: it has no county table. In particular the file’s Virginia, Maryland and Missouri names that stand for both a county and an independent city of the same name cannot be told apart, and Alaska names from earlier borough and census-area boundaries do not match today’s. Connecticut is listed under its eight former counties, so Connecticut planning regions have no table.
  • Property names, addresses, cities and coordinates are not published here; only counts. Totals are not divided by population or area, and places are not compared or ordered.
  • Public data of the National Park Service, U.S. Department of the Interior (works of a federal agency). Source line: National Park Service, National Register of Historic Places Program. This site is not endorsed by the National Park Service.
  • State figures include every listing the file assigns to the state, including listings in county names that could not be matched to a county of this site. Listings in American Samoa, Guam, the Northern Mariana Islands, the U.S. Virgin Islands, the freely associated states and other non-state areas in the file have no page here.

National Risk Index version 1.20 (December 2025), county table (NRI_Table_Counties.zip, NRI_Table_Counties.csv)

Original publisher: Federal Emergency Management Agency (FEMA), National Risk Index. Publisher documentation and methods.

Modeled expected annual loss by natural hazard (FEMA, county)

Data period
National Risk Index version 1.20, December 2025 (file last modified Thu, 18 Dec 2025 22:05:16 GMT, retrieved 2026-11-02); 3,232 county rows
Geography vintage
FEMA’s county list for this release, joined to this site’s counties by five-digit FIPS code (Connecticut planning regions as coded by FEMA)
Units and scope
Dollars of modeled average annual loss (Expected Annual Loss).
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
3,222 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.

Displayed here

Explore the topic: Environment and hazards

Coverage and interpretation
  • These are modeled estimates of average annual loss from FEMA’s National Risk Index (version 1.20, December 2025), not a forecast of losses in any year, not a count of past events or past damage, and not a statement about any property. Expected Annual Loss is FEMA’s average yearly loss in dollars to buildings, population and agriculture from each natural hazard, built from hazard frequency, the value exposed and a historic loss ratio.
  • Population loss is monetized by FEMA at $13.7 million per fatality or per 10 injuries, so the population dollar figure is a statistical-life equivalent, not an economic cost that anyone pays. Combined figures are the sum across hazards, with the total equal to buildings plus the population dollar equivalent plus agriculture.
  • A county page shows each hazard’s total Expected Annual Loss and the combined total; the split into buildings, population and agriculture and the exposure are shown on the state page only, and annualized frequency and historic loss ratios are not shown, to keep the page compact. A hazard FEMA does not assess for a county, or does not report a value for, has no row; that is not zero. A zero shown is a zero in the source.
  • Some hazards are assessed for fewer consequence types: drought is assessed for agriculture only, and avalanche, coastal flooding, earthquake, ice storm, landslide, lightning, tsunami and volcanic activity have no agriculture component. State figures are the sum of the county values FEMA reports for the state’s counties, shown only where the quantity is additive (losses and exposure); a state cell sums the counties that have a value and a state with no county value for a quantity shows Not reported.
  • Exposure on the state page is the total value in dollars FEMA treats as exposed to a hazard (buildings, population equivalent and agriculture together). Figures are not adjusted for inflation or updated between FEMA releases. Counties are FEMA’s county list for this release (the nine Connecticut planning regions, Alaska boroughs and census areas, Virginia independent cities and Puerto Rico municipios); FEMA’s American Samoa, Guam, Northern Mariana Islands and U.S. Virgin Islands rows are not used. These are county figures and state figures; nothing is allocated to cities or places.
  • The National Risk Index draws on many third-party hazard, exposure and loss inputs, some licensed by FEMA; this site publishes only FEMA’s aggregate county quantities. Display only; export, API and commercial use have not been reviewed. FEMA does not endorse this site.

Modeled expected annual loss by natural hazard (FEMA, state)

Data period
National Risk Index version 1.20, December 2025 (file last modified Thu, 18 Dec 2025 22:05:16 GMT, retrieved 2026-11-02); 3,232 county rows
Geography vintage
FEMA’s county list for this release, joined to this site’s counties by five-digit FIPS code (Connecticut planning regions as coded by FEMA)
Units and scope
Dollars of modeled average annual loss (Expected Annual Loss).
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.

Displayed here

Explore the topic: Environment and hazards

Coverage and interpretation
  • These are modeled estimates of average annual loss from FEMA’s National Risk Index (version 1.20, December 2025), not a forecast of losses in any year, not a count of past events or past damage, and not a statement about any property. Expected Annual Loss is FEMA’s average yearly loss in dollars to buildings, population and agriculture from each natural hazard, built from hazard frequency, the value exposed and a historic loss ratio.
  • Population loss is monetized by FEMA at $13.7 million per fatality or per 10 injuries, so the population dollar figure is a statistical-life equivalent, not an economic cost that anyone pays. Combined figures are the sum across hazards, with the total equal to buildings plus the population dollar equivalent plus agriculture.
  • A county page shows each hazard’s total Expected Annual Loss and the combined total; the split into buildings, population and agriculture and the exposure are shown on the state page only, and annualized frequency and historic loss ratios are not shown, to keep the page compact. A hazard FEMA does not assess for a county, or does not report a value for, has no row; that is not zero. A zero shown is a zero in the source.
  • Some hazards are assessed for fewer consequence types: drought is assessed for agriculture only, and avalanche, coastal flooding, earthquake, ice storm, landslide, lightning, tsunami and volcanic activity have no agriculture component. State figures are the sum of the county values FEMA reports for the state’s counties, shown only where the quantity is additive (losses and exposure); a state cell sums the counties that have a value and a state with no county value for a quantity shows Not reported.
  • Exposure on the state page is the total value in dollars FEMA treats as exposed to a hazard (buildings, population equivalent and agriculture together). Figures are not adjusted for inflation or updated between FEMA releases. Counties are FEMA’s county list for this release (the nine Connecticut planning regions, Alaska boroughs and census areas, Virginia independent cities and Puerto Rico municipios); FEMA’s American Samoa, Guam, Northern Mariana Islands and U.S. Virgin Islands rows are not used. These are county figures and state figures; nothing is allocated to cities or places.
  • The National Risk Index draws on many third-party hazard, exposure and loss inputs, some licensed by FEMA; this site publishes only FEMA’s aggregate county quantities. Display only; export, API and commercial use have not been reviewed. FEMA does not endorse this site.

National Transit Database, 2022 - 2025 NTD Annual Data - Metrics (report year 2025)

Original publisher: U.S. Department of Transportation, Federal Transit Administration. Publisher documentation and methods.

Public transit service and ridership (FTA National Transit Database, state)

Data period
NTD report year 2025 (data.transportation.gov table last modified Fri, 16 Oct 2026 13:13:59 GMT).
Geography vintage
The 50 states and the District of Columbia, matched on the FIPS code of the headquarters state abbreviation in the file
Units and scope
Unlinked passenger trips are boardings counted each time a passenger boards a vehicle; vehicle revenue miles are miles vehicles travel in revenue service.
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.

Displayed here

Explore the topic: Energy and utility measures

Coverage and interpretation
  • Agencies report to the FTA by their headquarters state. Service across a state line (for example a regional authority) is counted entirely in the headquarters state, so a state total is not the service operated within its borders.
  • Unlinked passenger trips count every boarding, so one journey with a transfer counts more than once; they are not a count of riders. Vehicle revenue miles exclude deadhead, operator training, maintenance testing, school bus and charter service.
  • Full, Reduced and Rural Reporters file different amounts of detail; every record that reports the two measures is included. Some agencies and modes are not required to report, so the totals are not every public transportation trip in the state.
  • A value the source leaves blank is Not reported, never zero. Totals add the reported values only. Values the FTA flags as questionable are shown as published.
  • State totals only; the source does not give county service-area detail for fixed-route service, so no county pages are built. The five territories in the file are not on the release roster.

National Transportation Atlas Database Aviation Facilities (FAA NASR airport data) and FAA calendar year 2025 passenger boarding (enplanement) data, aggregated to county counts

Original publisher: U.S. Department of Transportation, Federal Aviation Administration and Bureau of Transportation Statistics. Publisher documentation and methods.

Public-use airports and passenger boardings (FAA)

Data period
FAA NASR airport records effective 2026/10/29 (retrieved 2026-11-04); passenger boardings (enplanements) for calendar year 2025
Geography vintage
Counties named by the FAA (state and county name, no code) and matched by exact name to the Census counties on this site; Connecticut cannot be matched
Units and scope
Facilities: counts of public-use, operational FAA records. Passenger boardings: counts of enplaned passengers in the calendar year shown, as the FAA defines them. Counts, not rates.
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
3,099 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.

Displayed here

Explore the topic: Environment and hazards

Coverage and interpretation
  • Counts of facilities and passenger boardings as the Federal Aviation Administration (FAA) records them, not a measure of air service, airport size or quality, and not rates. Facilities are the records in the FAA National Airspace System Resource (NASR) airport data, as published by the Bureau of Transportation Statistics in the National Transportation Atlas Database “Aviation Facilities” layer, and counted once each.
  • A facility is counted here when the FAA records it as open for public use (facility use code PU) and operational (status O). Private-use facilities and facilities the FAA lists as closed are not counted. Type and ownership are the FAA codes, named as the FAA names them; a public-use facility can be privately owned. Airport names, addresses and coordinates are not shown.
  • Passenger boardings are the FAA’s calendar-year passenger boarding (enplanement) counts, a calendar year being January 1 through December 31, taken from the FAA Air Carrier Activity database and published in “Enplanements at All Commercial Service Airports” (primary and nonprimary commercial service airports). A boarding counts at the airport where the passenger boards, not where the passenger lives or finishes the trip. The FAA publishes the preliminary figures first and the final figures about eight months after the year ends. Boardings appear only where the FAA list has an airport in the area; areas without one show no boardings row.
  • The FAA records a county name and a state, not a county code. Each record was matched to a Census county by exact state and county name, after removing capitalization, punctuation and the words County, Parish, Borough, Census Area, Municipality and Municipio. A record whose name matches nothing in the current Census list, or matches both a county and an independent city of the same name (for example Fairfax, Franklin, Richmond or Roanoke in Virginia), is not assigned to any county and is never guessed. Where a state has such records, a county with none assigned shows no table, and a county that does have records carries a note that its count could be lower.
  • Connecticut is Not reported by county: the FAA still names Connecticut’s former counties, which the Census planning regions on this site replaced, and the two cannot be matched by name. Alaska’s FAA county names include boroughs and census areas that the Census Bureau has since renamed, divided or merged; those records are not assigned.
  • These are county figures, not figures for any city or place within the county.
  • Not reported is not zero: a value that cannot be placed is Not reported.

National Transportation Atlas Database Aviation Facilities (FAA NASR airport data) and FAA calendar year 2025 passenger boarding (enplanement) data, aggregated to state counts

Original publisher: U.S. Department of Transportation, Federal Aviation Administration and Bureau of Transportation Statistics. Publisher documentation and methods.

Public-use airports and passenger boardings (FAA)

Data period
FAA NASR airport records effective 2026/10/29 (retrieved 2026-11-04); passenger boardings (enplanements) for calendar year 2025
Geography vintage
States as recorded by the FAA (the 50 states, the District of Columbia and Puerto Rico; other territories are not shown)
Units and scope
Facilities: counts of public-use, operational FAA records. Passenger boardings: counts of enplaned passengers in the calendar year shown, as the FAA defines them. Counts, not rates.
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.

Displayed here

Explore the topic: Environment and hazards

Coverage and interpretation
  • Counts of facilities and passenger boardings as the Federal Aviation Administration (FAA) records them, not a measure of air service, airport size or quality, and not rates. Facilities are the records in the FAA National Airspace System Resource (NASR) airport data, as published by the Bureau of Transportation Statistics in the National Transportation Atlas Database “Aviation Facilities” layer, and counted once each.
  • A facility is counted here when the FAA records it as open for public use (facility use code PU) and operational (status O). Private-use facilities and facilities the FAA lists as closed are not counted. Type and ownership are the FAA codes, named as the FAA names them; a public-use facility can be privately owned. Airport names, addresses and coordinates are not shown.
  • Passenger boardings are the FAA’s calendar-year passenger boarding (enplanement) counts, a calendar year being January 1 through December 31, taken from the FAA Air Carrier Activity database and published in “Enplanements at All Commercial Service Airports” (primary and nonprimary commercial service airports). A boarding counts at the airport where the passenger boards, not where the passenger lives or finishes the trip. The FAA publishes the preliminary figures first and the final figures about eight months after the year ends. Boardings appear only where the FAA list has an airport in the area; areas without one show no boardings row.
  • State figures use the state of the county the FAA records for each facility, so every record is counted whether or not its county could be matched. The FAA places the airports serving Washington, D.C. that stand in Virginia in Virginia. Territories other than Puerto Rico, and facilities outside the United States, are not shown.
  • Not reported is not zero: a value that cannot be placed is Not reported.

Natural Amenities Scale, county file with the six component measurements (AER-781, 1999)

Original publisher: U.S. Department of Agriculture, Economic Research Service. Publisher documentation and methods.

Natural amenities measurements (USDA Economic Research Service)

Data period
Climate means 1941-70 (Area Resource File); topography from a 1970 atlas map; water area as recorded by the Census Bureau for the 1999 report
Geography vintage
Counties and combined counties of the lower 48 states as coded in the 1999-era ERS file; matched on the five-digit FIPS code only, so a county whose code has since changed has no row
Units and scope
Temperatures, sunlight hours and humidity as ERS reports them (the file gives no units); topography as a category code; water as percent of county area.
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
3,097 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.

Displayed here

Explore the topic: Work and income

Coverage and interpretation
  • These are component measurements from the USDA Economic Research Service Natural Amenities Scale county file (report AER-781, October 1999), not current conditions. The climate figures are means for 1941-70, the topography code comes from a 1970 national atlas map, and the water figure is the percent of county area in water. The file does not state units for the climate columns; the magnitudes are consistent with degrees Fahrenheit, mean hours of sunlight in January and percent relative humidity.
  • Only the six measurements are shown. ERS combines them into a composite amenities value and a category derived from it; neither is shown here, and no measurement is adjusted, standardized or combined.
  • The topography code is one of 21 land surface form categories, written as ERS writes it ("14 = Open hills"); where a county had more than one formation ERS assigned the category of greatest variation that appeared to apply to at least 25 percent of the county. The water percentage is the share of total county area, with coastal and Great Lakes water included as the Census Bureau tape recorded it.
  • The file covers 3,111 counties and county combinations in the lower 48 states and uses county codes of its era, so counties created or recoded since then, Alaska, Hawaii, Puerto Rico and Connecticut planning regions have no row and are not shown. For 41 combined counties (mostly independent cities in Virginia, and some in Arizona, Montana and New Mexico) ERS took the measurements from a combined adjacent county; the table says which. A value absent from the file is Not reported, never zero.

Natural Resources Revenue Data: federal onshore royalties, rents and bonuses, county

Original publisher: U.S. Department of the Interior, Office of Natural Resources Revenue. Publisher documentation and methods.

Federal royalties, rents and bonuses by lease type (ONRR, county)

Data period
Fiscal years 2022 to 2026 (October to September), file retrieved 2026-11-04
Geography vintage
Counties by the five-digit FIPS code in the ONRR file, matched to this site’s county roster by code
Units and scope
U.S. dollars collected in each fiscal year.
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
466 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.

Displayed here

Explore the topic: Energy and utility measures

Coverage and interpretation
  • Revenues are amounts ONRR reports collecting from federal onshore mineral leases: royalties, rents and bonuses. The source’s other revenue categories (other revenues, civil penalties, inspection fees) and Native American land revenues are not included. Offshore revenues and revenues not tied to a lease have no state or county and are not shown.
  • The revenue is collected from lease holders and attributed to the county of the lease; it is not income to the county, and it is not the share returned to the state or county. Revenues vary strongly from year to year with prices, production and lease sales; the most recent fiscal year may be incomplete or revised.
  • Mineral lease types are grouped as: Oil and gas; Coal; Geothermal; Wind; Hardrock and other minerals (hardrock, potassium, sodium, phosphate, clay, gilsonite, oil shale, gold, tar sands, asphalt); and rows with no lease type stated. No company, lessee or lease is named.
  • A row or year with no record is Not reported, never zero. Fiscal year runs October through September.
  • Counties and states are matched by the FIPS code in the source. A source county code that is not on this site’s roster, including code 00000 used for a single Alaska area, is not shown on any county page.

Federal revenues by type: royalties, rents and bonuses (ONRR, county)

Data period
Fiscal years 2022 to 2026 (October to September), file retrieved 2026-11-04
Geography vintage
Counties by the five-digit FIPS code in the ONRR file, matched to this site’s county roster by code
Units and scope
U.S. dollars collected in each fiscal year.
States / equivalents with this table
0 of 52 supported profiles
Counties / equivalents with this table
466 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.

Displayed here

Explore the topic: Energy and utility measures

Coverage and interpretation
  • Revenues are amounts ONRR reports collecting from federal onshore mineral leases: royalties, rents and bonuses. The source’s other revenue categories (other revenues, civil penalties, inspection fees) and Native American land revenues are not included. Offshore revenues and revenues not tied to a lease have no state or county and are not shown.
  • The revenue is collected from lease holders and attributed to the county of the lease; it is not income to the county, and it is not the share returned to the state or county. Revenues vary strongly from year to year with prices, production and lease sales; the most recent fiscal year may be incomplete or revised.
  • Mineral lease types are grouped as: Oil and gas; Coal; Geothermal; Wind; Hardrock and other minerals (hardrock, potassium, sodium, phosphate, clay, gilsonite, oil shale, gold, tar sands, asphalt); and rows with no lease type stated. No company, lessee or lease is named.
  • A row or year with no record is Not reported, never zero. Fiscal year runs October through September.
  • Counties and states are matched by the FIPS code in the source. A source county code that is not on this site’s roster, including code 00000 used for a single Alaska area, is not shown on any county page.