State, County and City FIPS (Federal Information Processing Standards) codes are a set of numeric designations given to state, cities and counties by the U.S. federal government. All geographic data submitted to the FRA must have a FIPS code.

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.

Context

Dataset created to link between County - State Name, State-County FIPS, and ZIP Code.

Acknowledgements

Data Sources

• US HUD

https://www.huduser.gov/portal/datasets/usps.html

• Census Bureau

https://www2.census.gov/geo/docs/reference/codes/files/national_county.txt https://www.census.gov/geo/reference/codes/cou.html

Data cleaned by Data4Democracy and hosted originally on Data.World: https://github.com/Data4Democracy/zip-code-to-county https://data.world/niccolley/us-zipcode-to-county-state

ZCTA data from USPS 6.2017 release.

Image from Reddit.

description: The US Census Bureau's online County Look-up Tool provides the unique 3-digit code for the Identification of Counties and Equivalent Entities of the United States, its Possessions, and Insular Areas.; abstract: The US Census Bureau's online County Look-up Tool provides the unique 3-digit code for the Identification of Counties and Equivalent Entities of the United States, its Possessions, and Insular Areas.

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

Context

There is no story behind this data.

These are just supplementary datasets which I plan on using for plotting county wise data on maps.. (in particular for using with my kernel : https://www.kaggle.com/stansilas/maps-are-beautiful-unemployment-is-not/)
As that data set didn't have the info I needed for plotting an interactive map using highcharter .

Content

Since I noticed that most demographic datasets here on Kaggle, either have state code, state name, or county name + state name but not all of it i.e county name, fips code, state name + state code.

Using these two datasets one can get any combination of state county codes etc.

States.csv has State name + code
US counties.csv has county wise data.

Acknowledgements

Picture : https://unsplash.com/search/usa-states?photo=-RO2DFPl7wE
Counties : https://www.census.gov/geo/reference/codes/cou.html
State :

Inspiration

Not Applicable.

The dataset contains a hierarchal listing of New York State counties, cities, towns, and villages, as well as official locality websites

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.

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.

Zip archive of files (one per state and sex) of county-level life tables from 1928-2019 by 5yr age group in R-binary (.rds) format. We group low-population counties and geographically coterminous neighbors (1084 total) together into county-groups (401 total) with historically consistent boundaries that exceed a minimum population threshold of 10,000 at any time point in our series. County groupings never cross state borders. 2071 counties are left ungrouped. A comma-separated variable lookup table linking the 1084 individual counties (by FIPS code) to the 401 groups are available in the USMDBcountyGroupings.csv. The individual counties in the life table files are identified by their FIPS code.

A comma-separated variable lookup table linking the 1084 individual counties (by FIPS code) to the 401 groups.

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

1. 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.

2. 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.

Montgomery County is an Exception Grantee, meaning that the highest quartile of block groups for low- and moderate-income percent constitute the areas where Area Benefit may be applied, even though all areas contain less than 51% low- and moderate-income persons. Montgomery County’s exception threshold for 2023 is 42.88%. 160 block groups qualify based on this threshold.You can search for and download the latest Low to Moderate Income Population by Block Group data for the entire United States from HUD here.Data Dictionary:GEOIDThis is the concatenation of State, County, Tract, and Block Group FIPS codes.SOURCE GEONAMEThe name of the block group, place, county, or county subdivision.STUSABThe state abbreviation.COUNTYNAMEThe Name of the County.STATEThe numeric Federal Information Process Standards (FIPS) state code.COUNTYThe numeric Federal Information Processing Standards (FIPS) county code.TRACTThe numeric code for the census tract. In other publications or reports, the code sometimes appears as a 2 digit decimal XXXX.XX.BLKGRPThe block group code.LOWThe count of Low-income persons.LOWMODThe count of Low- and Moderate-income persons.LMMIThe count of Low-, Moderate-, and Medium-income persons for the NSP programs..LOWMODUNIVPersons with the potential for being deemed Low-, Moderate- and Middle-income. Use as the denominator for LOW, LOWMOD, and LMMI %'s.LOWMOD_PCTThe percentage of Low- and Moderate-income persons. Calculated from LOWMOD divided by LOWMODUNIV.UCLOWMODThe uncapped count of Low- and Moderate-income persons.UCLOWMOD_PThe percentage of uncapped Low- and Moderate-income persons. Calculated from UCLOWMOD divided by LOWMODUNIV.MOE LOWMOD PCTThe margin of error (MOE) for the LOWMOD_PCT.MOE UCLOWMOD PCTThe margin of error (MOE) for the UCLOWMOD_PCT.

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

(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.

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.

Two major changes to the Uniform Crime Reports (UCR) county-level files were implemented beginning with the 1994 data. A new imputation algorithm to adjust for incomplete reporting by individual law enforcement jurisdictions was adopted. Within each county, data from agencies reporting 3 to 11 months of information were weighted to yield 12-month equivalents. Data for agencies reporting less than 3 months of data were replaced with data estimated by rates calculated from agencies reporting 12 months of data located in the agency's geographic stratum within its state. Secondly, a new Coverage Indicator was created to provide users with a diagnostic measure of aggregated data quality in a particular county. Data from agencies reporting only statewide figures were allocated to the counties in the state in proportion to each county's share of the state population.In the arrest files (Parts 1-3 and 5-7), data were estimated for agencies reporting 0 months based on the procedures mentioned above. However, due to the structure of the data received from the FBI, estimations could not be produced for agencies reporting 0 months in the crimes reported files (Parts 4 and 8). Offense data for agencies reporting 1 or 2 months are estimated using the above procedures. Users are encouraged to refer to the codebook for more information.No arrest data were provided for Washington, DC, and Florida. Limited arrest data were available for Illinois and Kentucky. Limited offense data were available for Illinois, Kentucky, Mississippi, Missouri, Montana, and South Dakota.UCR program staff at the Federal Bureau of Investigation (FBI) were consulted in developing the new adjustment procedures. However, these UCR county-level files are not official FBI UCR releases and are being provided for research purposes only. Users with questions regarding these UCR county-level data files can contact the National Archive of Criminal Justice Data at ICPSR.Users should note that there are no records in the data for the borough of Denali, Alaska (FIPS code 02068) in any of the collections of the Uniform Crime Reporting Program Data [United States]: County-Level Detailed Arrest and Offense Data from 1990 to 2003. The borough of Denali, Alaska (FIPS code 02068) was created from part of the Yukon-Koyukuk Census Area (FIPS code 02290) an unpopulated part of the Southeast Fairbanks Census Area (FIPS code 02240) effective December 7, 1990. Since no agency records for either arrests or crimes reported from Denali were present in any of the original FBI files, no data for the borough of Denali, Alaska appear in any the ICPSR collections for these years. This data collection contains county-level counts of arrests and offenses for Part I offenses (murder, rape, robbery, aggravated assault, burglary, larceny, auto theft, and arson) and counts of arrests for Part II offenses (forgery, fraud, embezzlement, vandalism, weapons violations, sex offenses, drug and alcohol abuse violations, gambling, vagrancy, curfew violations, and runaways). Datasets: DS0: Study-Level Files DS1: Arrests, All Ages DS2: Arrests, Adult DS3: Arrests, Juveniles DS4: Crimes Reported DS5: Allocated Statewide Data for Arrests, All Ages DS6: Allocated Statewide Data for Arrests, Adults DS7: Allocated Statewide Data for Arrests, Juveniles DS8: Allocated Statewide Data for Crimes Reported County law enforcement agencies in the United States.