This application was put together at the request of the Emergency Rental Assistance Program team. They wanted an easy way to quickly look up whether an address fell within a low to moderate income census tract. This data is provided by HUD and more information can be found here. The layer used is a nation wide data set with a filter put on it to focus on census tracts in Orange County, Florida with >50% low to moderate income population.

{{description}}

Abstract

A crosswalk dataset matching US ZIP codes to corresponding census tracts

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

Census tract definition

A census tract, census area, census district or meshblock is a geographic region defined for the purpose of taking a census. Sometimes these coincide with the limits of cities, towns or other administrative areas and several tracts commonly exist within a county. In unincorporated areas of the United States these are often arbitrary, except for coinciding with political lines.

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

2020 Census Tract to MCD lookup table

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2020 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2010 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area.

This data layer is an element of the Oregon GIS Framework. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

USA Census Tracts for Urban Search and Rescue. This layer can be used for search segment planning. Census Tracts generally contain between 1,200 and 8,000 people, with an optimum size of 4,000 people and the boundaries generally follow existing roads and waterways. The field segment_designation is the last 5 digits of the unique identifier and matches the field in the SARCOP Segment layer.This layer presents the USA 2020 Census Tract boundaries of the United States in the 50 states and the District of Columbia. It is updated annually as Tract boundaries change. The geography is sourced from US Census Bureau 2020 TIGER FGDB (National Sub-State) and edited using TIGER Hydrology to add a detailed coastline for cartographic purposes. Geography last updated May 2022.Attribute fields include 2020 total population from the US Census PL94 data.

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.

Simple municipal name/GEOID lookup table. The table combines GEOID with census county names and municipal names. Stored as view in the demographics schema.

U.S. Census BlocksThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), displays Census Blocks in the United States. A brief description of Census Blocks, per USCB, is that "Census blocks are statistical areas bounded by visible features such as roads, streams, and railroad tracks, and by nonvisible boundaries such as property lines, city, township, school district, county limits and short line-of-sight extensions of roads." Also, "the smallest level of geography you can get basic demographic data for, such as total population by age, sex, and race."Census Block 1007Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Census Blocks) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 69 (Series Information for 2020 Census Block State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (U.S. Census Blocks - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: What are census blocksFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

Context

There are a number of Kaggle datasets that provide spatial data around New York City. For many of these, it may be quite interesting to relate the data to the demographic and economic characteristics of nearby neighborhoods. I hope this data set will allow for making these comparisons without too much difficulty.

Exploring the data and making maps could be quite interesting as well.

Content

This dataset contains two CSV files:

1. nyc_census_tracts.csv

   This file contains a selection of census data taken from the ACS DP03 and DP05 tables. Things like total population, racial/ethnic demographic information, employment and commuting characteristics, and more are contained here. There is a great deal of additional data in the raw tables retrieved from the US Census Bureau website, so I could easily add more fields if there is enough interest.

   I obtained data for individual census tracts, which typically contain several thousand residents.

2. census_block_loc.csv

   For this file, I used an online FCC census block lookup tool to retrieve the census block code for a 200 x 200 grid containing New York City and a bit of the surrounding area. This file contains the coordinates and associated census block codes along
   with the state and county names to make things a bit more readable to users.

   Each census tract is split into a number of blocks, so one must extract the census tract code from the block code.

Acknowledgements

The data here was taken from the American Community Survey 2015 5-year estimates (https://factfinder.census.gov/faces/nav/jsf/pages/index.xhtml).

The census block coordinate data was taken from the FCC Census Block Conversions API (https://www.fcc.gov/general/census-block-conversions-api)

As public data from the US government, this is not subject to copyright within the US and should be considered public domain.

A Qualified Census Tract (QCT) is any census tract (or equivalent geographic area defined by the Census Bureau) in which at least 50% of households have an income less than 60% of the Area Median Gross Income (AMGI). HUD has defined 60% of AMGI as 120% of HUD's Very Low Income Limits (VLILs), which are based on 50% of area median family income, adjusted for high cost and low income areas.

Census tracts are small, relatively permanent geographic entities within counties (or the statistical equivalents of counties) delineated by a committee of local data users. Generally, census tracts have between 2,500 and 8,000 residents and boundaries that follow visible features. When first established, census tracts are to be as homogeneous as possible with respect to population characteristics, economic status, and living conditions. (www.census.gov)

Census Tracts from the 2020 US Census for New York City clipped to the shoreline. These boundary files are derived from the US Census Bureau's TIGER project and have been geographically modified to fit the New York City base map. Because some census tracts are under water not all census tracts are contained in this file, only census tracts that are partially or totally located on land have been mapped in this file.

All previously released versions of this data are available on the DCP Website: BYTES of the BIG APPLE. Current version: 25d

Census Tracts from 2020. The TIGER/Line shapefiles are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2020 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2010 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area.

The 2019 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some states and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

Census Tract boundaries within Bexar County. A census tract is a geographic region defined for the purpose of taking a census. Usually these coincide with the limits of cities, towns or other administrative areas and several tracts commonly exist within a county. In unincorporated areas of the United States these are often arbitrary, except for coinciding with political lines. In the United States, census tracts are subdivided into block groups and census blocks. According to the U.S. Census Bureau: Census tracts are designed to be relatively homogeneous units with respect to population characteristics, economic status, and living conditions, census tracts average about 4,000 inhabitants.

US Northeast Census Tracts contains the US Census tract geometries used as the unit of analysis for network metrics. The file "northeast_tracts.shp" includes a merged dataset with the borders of all census tracts in Connecticut, Maine, Massachusetts, New Hampshire, New York, Rhode Island, and Vermont. All other files in this repository are the original state-by-state sources used to create the final merged dataset. Census Tracts The 2020 census tract file is based on the 2020 Census. The following fields are included: USPS: United States Postal Service state abbreviation. GEOID: Geographic identifier — fully concatenated geographic code (State FIPS, County FIPS, Census Tract number). GEOIDFQ: Fully qualified geographic identifier — used to join with data.census.gov data tables. ALAND: Land area (square meters) — created for statistical purposes only. AWATER: Water area (square meters) — created for statistical purposes only. ALAND_SQMI: Land area (square miles) — created for statistical purposes only. AWATER_SQMI: Water area (square miles) — created for statistical purposes only. INTPTLAT: Latitude (decimal degrees). The first character is blank or “–” denoting North or South latitude respectively. INTPTLONG: Longitude (decimal degrees). The first character is blank or “–” denoting East or West longitude respectively. The .shp file in this repository includes its required companion files for correct GIS operation: .shx (spatial index), .dbf (attribute table), .prj (projection information), and .cpg (character encoding).

This dataset contains census tract-level social determinants of health (SDOH) measures from the American Community Survey 5-year data for the entire United States—50 states and the District of Columbia. Data were downloaded from data.census.gov using Census API and processed by the Centers for Disease Control and Prevention (CDC), Division of Population Health, Epidemiology and Surveillance Branch. The project was funded by the Robert Wood Johnson Foundation in conjunction with the CDC Foundation. These measures complement existing PLACES measures, including PLACES SDOH measures (e.g., health insurance, routine check-up). These data can be used together with PLACES data to identify which health and SDOH issues overlap in a community to help inform public health planning. To access spatial data, please use the ArcGIS Online service: https://cdcarcgis.maps.arcgis.com/home/item.html?id=d51009ea78b54635be95c6ec9955ec17.

Lookup table matching 2020 census tract geographies to their Philadelphia Planning District for aggregations of tract-level data to each of the 18 Planning Districts. Note, the 2020 census tracts were intentionally delineated to align with Philadelphia Planning districts, unlike the prior geography vintages.