This tool--a simple csv or Stata file for merging--gives you a fast way to assign Census county FIPS codes to variously presented county names. This is useful for dealing with county names collected from official sources, such as election returns, which inconsistently present county names and often have misspellings. It will likely take less than ten minutes the first time, and about one minute thereafter--assuming all versions of your county names are in this file. There are about 3,142 counties in the U.S., and there are 77,613 different permutations of county names in this file (ave=25 per county, max=382). Counties with more likely permutations have more versions. Misspellings were added as I came across them over time. I DON'T expect people to cite the use of this tool. DO feel free to suggest the addition of other county name permutations.

This is a listing of Federal Information Processing Standard (FIPS) codes for each of the 67 counties in Pennsylvania. Information gathered from census data - https://www.census.gov/library/reference/code-lists/ansi.html For more technical details :

Federal Information Processing Standards Publications (FIPS PUBS) are issued by the National Institute of Standards and Technology (NIST) after approval by the Secretary of Commerce pursuant to Section 111 (d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235.

Federal Information Processing Standard (FIPS) 6-4, Counties and Equivalent Entities of the U.S., Its Possessions, and Associated Areas -- 90 Aug 31 , provides the names and codes that represent the counties and other entities treated as equivalent legal and/or statistical subdivisions of the 50 States, the District of Columbia, and the possessions and freely associated areas of the United States. Counties are considered to be the "first-order subdivisions" of each State and statistically equivalent entity, regardless of their local designations (county, parish, borough, etc.).

A listing of NYS counties with accompanying Federal Information Processing System (FIPS) and US Postal Service ZIP codes sourced from the NYS GIS Clearinghouse.

This is a lookup table containing various data related to cities, townships, unorganized territories (CTUs) and any divisions created by county boundaries splitting them. These are termed Minor Civil Division (MCDs) by the Census Bureau. The table encompases the Twin Cities 7-county metropolitan area. It is intended to be a Council wide master lookup table for these entites. It contains official federal and state unique identifiers for CTUs and MCDs as well as identifiers created and used by other organizations. The table also contains historical MCDs dating back to the 1990s and a few other non-MCD records that are of importance to Met. Council use of this table.

The County CTU Lookup Table relates to the Counties and Cities & Townships, Twin Cities Metropolitan Area dataset here: https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-metro-counties-and-ctus

NOTES:

- On 5/28/2014 a new field was added to reflect the new community designations defined in the Council's Thrive MSP 2040 regional plan - COMDES2040

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lake St. Croix Beach was incorrect. It was changed from 2394379 to 2395599 to match GNIS.

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lilydale was incorrect. It was changed from 2394457 to 2395708 to match GNIS.

- On 11/9/2010 it was discovered that the CTU ID used for the City of Crystal was incorrect. It was changed from 2393541 to 2393683 to match GNIS.

- Effective April 2008, a change was made in GNIS to match the FIPS place codes to the "civil" feature for each city instead of the "populated place" feature. Both cities and townships are now "civil" features within GNIS. This means that the official GNIS unique ID for every city in Minnesota has changed.

- As of January 1, 2006, the five digit FIPS 55-3 Place codes that were used as unique identifiers in this dataset (CTU_CODE and COCTU_CODE fields) were officially retired by the Federal governement. They are replaced by a set of integer codes from the Geographic Names Information System (GNIS_CODE field). Both codes will be kept in this database, but the GNIS_CODE is considered the official unique identifier from this point forward. The GNIS codes are also slated to become official ANSI codes for these geographic features. While GNIS treats these codes as 6 to 8 digit integer data types, the Census Bureau formats them as 8 digit text fields, right justified with leading zeros included.

- The Census Bureau will continue to create FIPS 55 Place codes for new cities and townships through the 2010 Census. After that, no new FIPS 55 codes will be created. Note that for townships that wholly incorporate into cities, the same FIPS 55 code will be used for the new city. (GNIS creates a new ID for the new city.)

- Cities and townships have also been referred to as ''MCDs'' (a Census term), however this term technically refers to the part of each city or township within a single county. Thus, a few cities in the metro area that are split by county boundaries are actually comprised of two different MCDs. This was part of the impetus for a proposed MN state data standard that uses the ''CTU'' terminology for clarity.

- A variety of civil divisions of the land exist within the United States. In Minnesota, only three types exist - cities, townships and unorganized territories. All three of these exist within the Twin Cities seven county area. The only unorganized territory is Fort Snelling (a large portion of which is occupied by the MSP International Airport).

- Some cities are split between two counties. Only those parts of cities within the 7-county area are included.

- Prior to the 2000 census, the FIPS Place code for the City of Greenwood in Hennepin County was changed from 25928 to 25918. This dataset reflects that change.

Abstract (en): This data collection contains FIPS codes for state, county, county subdivision, and place, along with the 1990 Census tract number for each side of the street for the urban cores of 550 counties in the United States. Street names, including prefix and/or suffix direction (north, southeast, etc.) and street type (avenue, lane, etc.) are provided, as well as the address range for that portion of the street located within a particular Census tract and the corresponding Census tract number. The FIPS county subdivision and place codes can be used to determine the correct Census tract number when streets with identical names and ranges exist in different parts of the same county. Contiguous block segments that have consecutive address ranges along a street and that have the same geographic codes (state, county, Census tract, county subdivision, and place) have been collapsed together and are represented by a single record with a single address range. 2006-01-12 All files were removed from dataset 551 and flagged as study-level files, so that they will accompany all downloads. (1) Due to the number of files in this collection, parts have been eliminated here. For a complete list of individual part names designated by state and county, consult the ICPSR Website. (2) There are two types of records in this collection, distinguished by the first character of each record. A "0" indicates a street name/address range record that can be used to find the Census tract number and other geographic codes from a street name and address number. A "2" indicates a geographic code/name record that can be used to find the name of the state, county, county subdivision, and/or place from the FIPS code. The "0" records contain 18 variables and the "2" records contain 10 variables.

This CT Planning Regions layer consists of individual polygons representing each of the 169 municipalities that make up the state of Connecticut.

This feature layer is directly derived from the 'https://geodata.ct.gov/datasets/CTDOT::ct-municipalities/about' rel='nofollow ugc'>CTDOT Municipalities feature layer geometry, created by CT Department of Transportation. The municipalities are dissolved into their associated regional Councils of Governments.

This feature layer includes US Census Federal Information Processing Standards (FIPS) codes that are associated with each municipality. This was included based on information from 'https://www.census.gov/programs-surveys/geography/technical-documentation/county-changes/2020.html' rel='nofollow ugc'>Connecticut County to County Subdivision Crosswalk from the US Census.

This reference table contains data elements for the 58 Counties in California that can be used to join to other data sets. This data includes the following fields:DHCS County CodeCounty NameCounty Region CodeCounty Region DescriptionFIPS County Code (xxx)FIPS State Code + FIPS County Code (06xxx)North/South Indicator

This data set contains county estimates of nitrogen and phosphorus content of animal wastes produced annually for the years 1982, 1987, and 1992. The estimates are based on animal populations for those years from the 1992 Census of Agriculture (U.S. Bureau of the Census, 1995) and methods for estimating the nutrient content of manure from the Soil Conservation Service (1992). The data set includes several components.. Spatial component - generalized county boundaries in ARC/INFO format/1/, including nine INFO lookup tables containing animal counts and nutrient estimates keyed to the county polygons using county code. (The county lines were not used in the nutrient computations and are provided for displaying the data as a courtesy to the user.) The data is organized by 5-digit state/county FIPS (Federal Information Processing Standards) code. Another INFO table lists the county names that correspond to the FIPS codes. Tabular component - Nine tab-delimited ASCII lookup tables of animal counts and nutrient estimates organized by 5-digit state/county FIPS (Federal Information Processing Standards) code. Another table lists the county names that correspond to the FIPS codes. The use of trade names is for identification purposes only and does not constitute endorsement by the U.S. Geological Survey.

Abstract

A crosswalk dataset matching US ZIP codes to corresponding county codes

Documentation

The denominators used to calculate the address ratios are the ZIP code totals. When a ZIP is split by any of the other geographies, that ZIP code is duplicated in the crosswalk file.

**Example: **ZIP code 03870 is split by two different Census tracts, 33015066000 and 33015071000, which appear in the tract column. The ratio of residential addresses in the first ZIP-Tract record to the total number of residential addresses in the ZIP code is .0042 (.42%). The remaining residential addresses in that ZIP (99.58%) fall into the second ZIP-Tract record.

So, for example, if one wanted to allocate data from ZIP code 03870 to each Census tract located in that ZIP code, one would multiply the number of observations in the ZIP code by the residential ratio for each tract associated with that ZIP code.

https://redivis.com/fileUploads/4ecb405e-f533-4a5b-8286-11e56bb93368%3E" alt="">(Note that the sum of each ratio column for each distinct ZIP code may not always equal 1.00 (or 100%) due to rounding issues.)

County definition

In the United States, a county is an administrative or political subdivision of a state that consists of a geographic region with specific boundaries and usually some level of governmental authority. The term "county" is used in 48 U.S. states, while Louisiana and Alaska have functionally equivalent subdivisions called parishes and boroughs, respectively.

Further reading

The following article demonstrates how to more effectively use the U.S. Department of Housing and Urban Development (HUD) United States Postal Service ZIP Code Crosswalk Files when working with disparate geographies.

Wilson, Ron and Din, Alexander, 2018. “Understanding and Enhancing the U.S. Department of Housing and Urban Development’s ZIP Code Crosswalk Files,” Cityscape: A Journal of Policy Development and Research, Volume 20 Number 2, 277 – 294. URL: https://www.huduser.gov/portal/periodicals/cityscpe/vol20num2/ch16.pdf

Contact information

Questions regarding these crosswalk files can be directed to Alex Din with the subject line HUD-Crosswalks.

Acknowledgement

This dataset is taken from the U.S. Department of Housing and Urban Development (HUD) office: https://www.huduser.gov/portal/datasets/usps_crosswalk.html#codebook

This is a polygon dataset for county boundaries as well as for city, township and unorganized territory (CTU) boundaries in the Twin Cities 7-county metropolitan area. The linework for this dataset comes from individual counties and is assembled by the Metropolitan Council for the MetroGIS community. This is a MetroGIS Regionally Endorsed dataset https://metrogis.org/.

The County CTU Lookup Table here https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-counties-and-ctus-lookup
is also included in this dataset and contains various data related to cities, townships, unorganized territories (CTUs) and any divisions created by county boundaries splitting them is also included in the dataset.

This dataset is updated quarterly. This dataset is composed of three shape files and one dbf table.
- Counties.shp = county boundaries
- CTUs.shp = city, township and unorganized territory boundaries
- CountiesAndCTUs.shp = combined county and CTU boundaries
- CountyCTULookupTable.dbf = various data related to CTUs and any divisions created by county boundaries splitting them is also included in the dataset, described here: https://gisdata.mn.gov/dataset/us-mn-state-metc-bdry-counties-and-ctus-lookup

NOTES:

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lake St. Croix Beach was incorrect. It was changed from 2394379 to 2395599 to match GNIS.

- On 3/17/2011 it was discovered that the CTU ID used for the City of Lilydale was incorrect. It was changed from 2394457 to 2395708 to match GNIS.

- On 11/9/2010 it was discovered that the CTU ID used for the City of Crystal was incorrect. It was changed from 2393541 to 2393683 to match GNIS.

- Effective April 2008, a change was made in GNIS to match the FIPS place codes to the "civil" feature for each city instead of the "populated place" feature. Both cities and townships are now "civil" features within GNIS. This means that the official GNIS unique ID for every city in Minnesota has changed.

- The five digit CTU codes in this dataset are identical to the Federal Information Processing Standard (FIPS) ''Place'' codes. They are also used by the Census Bureau and many other organizations and are proposed as a MN state data coding standard.

- Cities and townships have also been referred to as ''MCDs'' (a census term), however this term technically refers to the part of each city or township within a single county. Thus, a few cities in the metro area that are split by county boundaries are actually comprised of two different MCDs. This was part of the impetus for a proposed MN state data standard that uses the ''CTU'' terminology for clarity.

- The boundary line data for this dataset comes from each county.

- A variety of civil divisions of the land exist within the United States. In Minnesota, only three types exist - cities, townships and unorganized territories. All three of these exist within the Twin Cities seven county area. The only unorganized territory is Fort Snelling (a large portion of which is occupied by the MSP International Airport).

- Some cities are split between two counties. Only those parts of cities within the 7-county area are included.

- Prior to the 2000 census, the FIPS Place code for the City of Greenwood in Hennepin County was changed from 25928 to 25918. This dataset reflects that change.

From https://www.census.gov/hhes/commuting/data/jtw_workerflow.html as of March 29, 2017:These files were compiled from STF-S-5, Census of Population 1990: Number of Workers by County of Residence by County of Work [http://doi.org/10.3886/ICPSR06123.v1]. For the six New England States (CT, ME, MA, NH, RI, VT), data are provided for Minor Civil Divisions (MCDs) instead of for counties.For any State, or for the entire nation, there are four files to choose from, depending on the sort order and format you may find most useful.The sort order refers to whether the county of residence or the county of work is the main focus. If you are most interested in the number of people who live in a county, and want to know where they go to work, you should download one of the files sorted by county of residence. These files will show you all the work destinations for people who live in each county.On the other hand, if you are most interested in the people who work in a county, and want to know where they come from, you should download one of the files sorted by county of work. These files will show you all the origins for people who work in each county.The files have also been created in two formats: DBF and ASCII. The DBF files are directly accessible by a number of database, spreadsheet, and geographic information system programs. The ASCII files are more general purpose and may be imported into many software applications.Record Layouts Record Layout for ASCII (Plain Text) Files [TXT - 2K] coxcoasc.txtRecord Layout for DBF Files [TXT - 2K]coxcodbf.txtThe link to the FIPS Lookup File [ed.: absent when archived] can be used to access a list of FIPS State codes and the corresponding State names. In the county-to-county worker flow files, only the State codes are used. The files do not contain State names.United States county-to-county worker flow files: 1990 Residence County USresco.txt USresco.zip USresco.dbf USresco.dbf.zipWork County USwrkco.txt USwrkco.zip USwrkco.dbf USwrkco.dbf.zip [Ed.: the original site also had state files. These were not downloaded, as they simply split the United States file into smaller chunks.]

"This file provides digital data for all 1990 precensus map features, the associated 1990 census initial tabulation geographic area codes, such as 1990 census block numbers, and the codes for the Jan. 1, 1990 political areas on both sides of each line segment of every mapped feature. The data contain basic information on 1990 census geographic area codes, feature names, and address ranges in the form of ten ""Record Types."" The Census Bureau added four new record types in response to some us er and vendor requests to provide point and area information contained in the Census Bureau's Precensus Map sheets that is not contained in the Precensus TIGER/Line files. The record types include: Basic data records (individual Feature Segment Records), shape coordinate points (feature shape records), additional decennial census geographic area codes, index to alternate feature names, feature name list, additional address range and zip code data, landmark features, area landmarks, area boundaries, and polygon location. Each segment record contains appropriate decennial census and FIPS geographic area codes, latitude/longitude coordinates, the name of the feature (including the relevant census feature class code identifying the segment by category), and, for areas formerly covered by the GBF/DIME-Files, the address ranges and ZIP code associated with those address ranges for each side of street segments. For other areas, the TIGER?Line files do not contain address ranges or ZIP Codes. The shape records provide coordinate values that describe the shape of those feature segments that are not straight."

Harvard CGA Geotweet Census Archive is a subset of Harvard CGA Geotweet Archive v2.0 enriched with nationwide census data. It contains the tweet and user identification records along with census variables for more than 2 billion geo-tagged tweets from January 2012 to July 2023. This dataset is available to the academic community at large, unlike the Harvard CGA Geotweet Archive v2.0 which is under Twitter's redistribution policy restriction for public sharing. It could serve as cross-validation data for publications that used data from Harvard CGA Geotweet Archive v2.0 . If you are interested in accessing this archive, please fill out our Geotweet Request Form. Before requesting or receiving Tweet IDs, requestors must agree to Twitter's Terms of Service, Twitter's Privacy Policy, and Twitter's Developer Policy . Geotweets IDs data provided by CGA can only be used for not-for-profit research and academic purposes. Recipients may not share CGA provided Tweet IDs or content derived from them without written permission from the CGA. Citations: If you use the Geotweet Archive in your research please reference it: "Harvard CGA Geotweet IDs Archive". ======================================================== Schema of Geotweet Census Archive Field name_TYPE_Description message_id----TEXT----Tweet ID user_id ----TEXT----User ID number fips ----FLOAT----County fips code county ----TEXT----County name state ----TEXT----State abbreviation GEOID20 ----FLOAT----Census block geoid

(SEE SUPPLEMENTAL INFORMATION SECTION FOR FILE-SPECIFIC INFORMATION.)Digital orthophoto quarter-quads are now available for most of the United States and its Territories. Quarter-quad DOQs cover an area measuring 3.75-minutes longitude by 3.75-minutes latitude. Quarter-quad DOQs are available in both Native and GeoTIFF formats. Native format consists of an ASCII keyword header followed by a series of 8-bit binary image lines for B/W and 24-bit band-interleaved-by-pixel (BIP) for color. DOQs in native format are cast to the Universal Transverse Mercator (UTM) projection and referenced to either the North American Datum (NAD) of 1927 (NAD27) or the NAD of 1983 (NAD83). GeoTIFF format consists of a georeferenced Tagged Image File Format (TIFF), with all geographic referencing information embedded within the .tif file. DOQs in GeoTIFF format are cast to the UTM projection and referenced to NAD83. The average file size of a B/W quarter quad is 40-45 megabytes, and a color file is generally 140-150 megabytes. Quarter-quad DOQs are distributed on CD-ROM, DVD, and File Transfer Protocol (FTP) as uncompressed files.A downloadable software is available (DOQQ-to-GeoTIFF conversion) which will convert a DOQ image from Native to GeoTIFF format in either NAD27 or NAD83. NOTE: This EML metadata file does not contain important geospatial data processing information. Before using any NWT LTER geospatial data read the arcgis metadata XML file in either ISO or FGDC compliant format, using ArcGIS software (ArcCatalog > description), or by viewing the .xml file provided with the geospatial dataset.

Abstract (en): The CFFR covers federal expenditures or obligations for the following categories: grants, salaries and wages, procurement contracts, direct payments for individuals, other direct payments, direct loans, guaranteed or insured loans, and insurance. Information available in the CFFR data file includes the government identification code, program identification code, object/assistance type code, amount in whole dollars, and FIPS code. For each unique government unit code all programs are listed, and for each program all records with different object categories are listed. The Geographic Reference File contains the names and governmental unit codes for all state, county, and subcounty areas in the country. In addition, the file contains associated geographic codes (FIPS, GSA, MSA, and Census Bureau place codes), the 1986 population, and the congressional districts serving each government unit. The Program Identification File contains program identification codes and their respective program titles. Federal government expenditures or obligations in state, county, and subcounty areas of the United States. United States Territories and the District of Columbia are included. 2006-01-18 File CB9364.PDF was removed from any previous datasets and flagged as a study-level file, so that it will accompany all downloads.

This dataset contains records for each public elementary and secondary education agency in the 50 states, the District of Columbia, United States territories (American Samoa, Guam, Puerto Rico, the Virgin Islands, and the Marshall Islands), and Department of Defense schools outside of the United States for 1994-1995. Data were reported to the Bureau of the Census for the National Center for Education Statistics by the state coordinators. Each record provides state and federal identification numbers, agency name, address, and telephone number, county name and FIPS code, agency type code, student counts, graduates and other completers counts, and other codes for selected characteristics of the agency. In addition, grade span, number of schools operated by the agency, and number of classroom teachers were aggregated.

RateWatch provides 3 datasets containing interest rates for deposits, loans and fees at branch level for U.S. financial institutions covering over 96,000 locations. Data is gathered from institutions of all types and sizes. The largest depth of data is around consumer products such as CDs, Savings, Checking, Money Markets, Auto Loans, Home Equity Loans and Mortgages. Within each category, details are available for multiple terms and/or dollar tiers. Data includes several identifying fields including institution name, address, routing number, asset size, institution type, MSA codes, latitude, longitude, state and city FIPS code. Consult relevant data dictionary for more information. File structure: text delimited (delimiter: pipe). "Join" file provides cross reference between an institution's rate setting location and its other branches. A given Institution may have multiple rate setting locations that may vary by product type. DATA AVAILABLE FOR YEARS: 2001-2024 (2025-02-05)

PLACES sample dataset for Middlesex county, Massachusetts (FIPS code 25017). Feature-rich, parcel-level, open-source data with associated geometries (polygons and points), synthesized using the Private-Land Conservation Evidence System (PLACES, www.placeslab.org/places). For a full set of available indicators, including those requiring third-party licenses, consult the PLACES variable dictionary at https://placeslab.org/dictionary.

The Toxics Release Inventory (TRI) data provides information about toxic substances released into the environment or managed through recycling, energy recovery, and treatment in the United States. Annual releases are compiled and reported by the U.S. Environmental Protection Agency (EPA) and shared on the TRI Website. The TRI covers over 650 chemicals and chemical groupings across a broad range of industries. Chemicals covered are linked to cancer or other chronic human health effects, tied to significant adverse human health effects, or significant adverse environmental effects.

This data is obtained from the EPA’s API. Users can also query the EPA's website for this information by using the links to each table listed as HTML resources below and supplying the State FIPS Code of "42003" to limit the results returned to only Allegheny County on the Search Criteria page.

Support for Health Equity datasets and tools provided by Amazon Web Services (AWS) through their Health Equity Initiative.