This resource is a member of a series. 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, 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.

This data includes several different tables presenting counts of births by race (total, Black, white) by Census Tract aggregated over a five-year period (2014-18). Data extracted from Pennsylvania's Vital Statistics Database with the following disclaimer: "These data were provided by the Pennsylvania Department of Health. The Department specifically disclaims responsibility for any analyses, interpretations, or conclusions."

Census tract of residence was determined using address-level data. Records were excluded from analysis if address was missing or unmatched to a census tract (≈1% records). Census tracts starting with 980x.xx, 981x.xx, and 982x.xx were also excluded due to a geocoding error. 2014 used a different methodology to assign census tract compared to years 2015-2018.

Counts < 5 are censored and displayed as "None". Census-tract-level counts may not equal county-level counts when summed due to censored data or missing data. For cause of death, underlying cause of death from the death certificate is used and is categorized based on ICD-10 codes, defined below.

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

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

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

USE geoid TO JOIN DATA DOWNLOADED FROM DATA.CENSUS.GOV The TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) System (MTS). The TIGER/Line Shapefiles contain a standard geographic identifier (GEOID) for each entity that links to the GEOID in the data from censuses and surveys. The TIGER/Line Shapefiles do not include demographic data from surveys and censuses (e.g., Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program). Other, non-census, data often have this standard geographic identifier as well. Data from many of the Census Bureau’s surveys and censuses, including the geographic codes needed to join to the TIGER/Line Shapefiles, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/). Census Tracts are small, relatively permanent statistical subdivisions of a county or statistically equivalent entity that can be updated by local participants prior to each decennial census as part of the Census Bureau’s Participant Statistical Areas Program (PSAP). The Census Bureau delineates census tracts in situations where no local participant responded or where state, local, or tribal governments declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of statistical data. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. A census tract usually covers a contiguous area; however, the spatial size of census tracts varies widely depending on the density of settlement. Census tract boundaries are delineated with the intention of being maintained over a long time so that statistical comparisons can be made from census to census. Census tracts occasionally are split due to population growth or merged as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow nonvisible 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. Tribal census tracts are a unique geographic entity defined within federally recognized American Indian reservations and off-reservation trust lands and can cross state and county boundaries. The tribal census tracts may be completely different from the standard county-based census tracts defined for the same area. (see “Tribal Census Tract”). Downloaded from https://www2.census.gov/geo/tiger/TIGER2022/TRACT/ on June 22, 2023

This resource is a member of a series. 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, 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.

Geospatial data about Allentown, Pennsylvania Census Tracts with Population (2000). Export to CAD, GIS, PDF, CSV and access via API.

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The 2015 State Geodatabase for Pennsylvania contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census
        Tract, County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs have the same first digit of their 4-digit census block number from the same
        decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within BG 3 within that
        census tract. BGs coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and
        Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A BG usually covers a contiguous area but never crosses
        county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban
        areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. The BG boundaries in this release
        are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        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. 

        An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD),
        which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state,
        but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have
        other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated
        to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state
        in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide
        with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial
        census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily
        have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. 

        The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also included. The boundaries
        of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and
        Annexation Survey (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include
        legally-recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census,
        the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs
        for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical
        unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county
        subdivisions. The boundaries of most legal MCDs are as of January 1, 2013, as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). The boundaries of all CCDs, delineated in 21 states, are those as reported as part of the Census Bureau's Participant Statistical Areas
        Program (PSAP) for the 2010 Census.

The 2022 cartographic boundary KMLs 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 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.

The Allegheny County 2000-2010 Census Tract Relationship File shows how 2010 Census tracts in Allegheny County, Pennsylvania relate to the 2000 Census tracts. Each record (row) consists of one unique relationship between a 2000 Census tract/2010 Census tract spatial set where a spatial set is the unique area shared by the record’s 2000 and 2010 tracts. Changes in tracts involve area, land area, population, and/or housing unit counts. Specifically, each record specifies the area, land area, population, and housing unit counts that were transferred to the record’s 2010 tract (TRACT10) from the record’s 2000 tract. The 2000 area (AREA00), land area (AREALAND00), population (POP00), and housing unit count (HU00) for the record is the standardized 2010 value for the record’s 2000 tract (TRACT00). These are the values to use when comparing 2010 population and housing unit counts to those values in the 2000 Census for a particular tract.

The relationship file provides the information necessary to conduct a decennial analysis between the 2000 and 2010 Censuses for a particular tract. Steps to use this file for a decennial analysis follow:

1. Obtain the population and/or housing unit count from the 2000 Census for the tract of interest.

2. Find a record in the relationship file where the tract of interest appears in the TRACT00 field.

3. Compare the population (POP00) and housing unit count (HU00) from the relationship file record to the 2000 Census population and housing unit count found in step 1.

This data was prepared by Lisa Over as a course project for LIS 2970 Open Government Data in the Master of Library Science Program at the University of Pittsburgh.

This dataset lists the total population 18 years and older by census block in Connecticut before and after population adjustments were made pursuant to Public Act 21-13. PA 21-13 creates a process to adjust the U.S. Census Bureau population data to allow for most individuals who are incarcerated to be counted at their address before incarceration. Prior to enactment of the act, these inmates were counted at their correctional facility address. The act requires the CT Office of Policy and Management (OPM) to prepare and publish the adjusted and unadjusted data by July 1 in the year after the U.S. census is taken or 30 days after the U.S. Census Bureau’s publication of the state’s data. A report documenting the population adjustment process was prepared by a team at OPM composed of the Criminal Justice Policy and Planning Division (OPM CJPPD) and the Data and Policy Analytics (DAPA) unit. The report is available here: https://portal.ct.gov/-/media/OPM/CJPPD/CjAbout/SAC-Documents-from-2021-2022/PA21-13_OPM_Summary_Report_20210921.pdf Note: On September 21, 2021, following the initial publication of the report, OPM and DOC revised the count of juveniles, reallocating 65 eighteen-year-old individuals who were incorrectly designated as being under age 18. After the DOC released the updated data to OPM, the report and this dataset were updated to reflect the revision.

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

Geospatial data about Allentown, Pennsylvania Census Block Groups With Population (2010). Export to CAD, GIS, PDF, CSV and access via API.

Summary File 2 contains 100-percent United States decennial Census data, which is the information compiled from the questions asked of all people and about every housing unit. Population items include sex, age, race, Hispanic or Latino origin, household relationship, and group quarters occupancy. Housing items include occupancy status, vacancy status, and tenure (owner-occupied or renter- occupied). The 100-percent data are presented in 36 population tables ("PCT") and 11 housing tables ("HCT") down to the census tract level. Each table is iterated for 250 population groups: the total population, 132 race groups, 78 American Indian and Alaska Native tribe categories (reflecting 39 individual tribes), and 39 Hispanic or Latino groups. The presentation of tables for any of the 250 population groups is subject to a population threshold of 100 or more people, that is, if there were fewer than 100 people in a specific population group in a specific geographic area, their population and housing characteristics data are not available for that geographic area.

description: Environmental Justice areas in this guide have been defined by the Pennsylvania Department of Environmental Protection. The Department defines an environmental justice area as any census tract where at least 20 percent of the population lives in poverty, and/or 30 percent or more of the population is minority.; abstract: Environmental Justice areas in this guide have been defined by the Pennsylvania Department of Environmental Protection. The Department defines an environmental justice area as any census tract where at least 20 percent of the population lives in poverty, and/or 30 percent or more of the population is minority.

This layer contains block level 2020 Decennial Census redistricting data as reported by the U.S. Census Bureau for the state of Pennsylvania. The attributes come from the 2020 Public Law 94-171 (P.L. 94-171) tables.Data download date: August 12, 2021Census tables: P1, P2, P3, P4, H1, P5, HeaderDownloaded from: Census FTP siteProcessing Notes:Data was downloaded from the U.S. Census Bureau FTP site, imported into SAS format and joined to the 2020 TIGER boundaries. Boundaries are sourced from the 2020 TIGER/Line Geodatabases. Boundaries have been projected into Web Mercator and each attribute has been given a clear descriptive alias name. No alterations have been made to the vertices of the data.Each attribute maintains it's specified name from Census, but also has a descriptive alias name and long description derived from the technical documentation provided by the Census. For a detailed list of the attributes contained in this layer, view the Data tab and select "Fields". The following alterations have been made to the tabular data:Joined all tables to create one wide attribute table:P1 - RaceP2 - Hispanic or Latino, and not Hispanic or Latino by RaceP3 - Race for the Population 18 Years and OverP4 - Hispanic or Latino, and not Hispanic or Latino by Race for the Population 18 Years and OverH1 - Occupancy Status (Housing)P5 - Group Quarters Population by Group Quarters Type (correctional institutions, juvenile facilities, nursing facilities/skilled nursing, college/university student housing, military quarters, etc.)HeaderAfter joining, dropped fields: FILEID, STUSAB, CHARITER, CIFSN, LOGRECNO, GEOVAR, GEOCOMP, LSADC.GEOCOMP was renamed to GEOID and moved be the first column in the table, the original GEOID was dropped.Placeholder fields for future legislative districts have been dropped: CD118, CD119, CD120, CD121, SLDU22, SLDU24, SLDU26, SLDU28, SLDL22, SLDL24 SLDL26, SLDL28.P0020001 was dropped, as it is duplicative of P0010001. Similarly, P0040001 was dropped, as it is duplicative of P0030001.In addition to calculated fields, County_Name and State_Name were added.The following calculated fields have been added (see long field descriptions in the Data tab for formulas used): PCT_P0030001: Percent of Population 18 Years and OverPCT_P0020002: Percent Hispanic or LatinoPCT_P0020005: Percent White alone, not Hispanic or LatinoPCT_P0020006: Percent Black or African American alone, not Hispanic or LatinoPCT_P0020007: Percent American Indian and Alaska Native alone, not Hispanic or LatinoPCT_P0020008: Percent Asian alone, Not Hispanic or LatinoPCT_P0020009: Percent Native Hawaiian and Other Pacific Islander alone, not Hispanic or LatinoPCT_P0020010: Percent Some Other Race alone, not Hispanic or LatinoPCT_P0020011: Percent Population of Two or More Races, not Hispanic or LatinoPCT_H0010002: Percent of Housing Units that are OccupiedPCT_H0010003: Percent of Housing Units that are VacantPlease note these percentages might look strange at the individual block level, since this data has been protected using differential privacy.**To protect the privacy and confidentiality of respondents, data has been protected using differential privacy techniques by the U.S. Census Bureau. This means that some individual blocks will have values that are inconsistent or improbable. However, when aggregated up, these issues become minimized. The pop-up on this layer uses Arcade to display aggregated values for the surrounding area rather than values for the block itself.Additional links:U.S. Census BureauU.S. Census Bureau Decennial CensusAbout the 2020 Census2020 Census2020 Census data qualityDecennial Census P.L. 94-171 Redistricting Data Program

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.

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.

*USE geoid TO JOIN DATA DOWNLOADED FROM DATA.CENSUS.GOV*The TIGER/Line Shapefiles are extracts of selected geographic and cartographic information from the Census Bureau's Master Address File (MAF)/Topologically Integrated Geographic Encoding and Referencing (TIGER) System (MTS).The TIGER/Line Shapefiles contain a standard geographic identifier (GEOID) for each entity that links to the GEOID in the data from censuses and surveys. The TIGER/Line Shapefiles do not include demographic data from surveys and censuses (e.g., Decennial Census, Economic Census, American Community Survey, and the Population Estimates Program). Other, non-census, data often have this standard geographic identifier as well. Data from many of the Census Bureau’s surveys and censuses, including the geographic codes needed to join to the TIGER/Line Shapefiles, are available at the Census Bureau’s public data dissemination website (https://data.census.gov/).Public Use Microdata Areas (PUMAs) are statistical geographic areas for the dissemination of decennial census and American Community Survey (ACS) Public Use Microdata Sample files in which the Census Bureau provides selected extracts of raw data from a small sample of census records that are screened to protect confidentiality. The ACS also uses the PUMAs as a tabulation geographic entity.For the 2020 Census, the State Data Centers in each state, the District of Columbia, and Puerto Rico are involved in the delineation of the 2020 PUMAs. Counties and census tracts are used to define PUMAs, and each PUMA must include at least 100,000 people based on the 2020 Census published counts. For the 2020 Census in Guam and the U.S. Virgin Islands, the Census Bureau establishes a single, separate PUMA for each of these two Island Areas. American Samoa and the Commonwealth of the Northern Mariana Islands do not have PUMAs, because the total population of each is under 100,000 people.Downloaded from https://www2.census.gov/geo/tiger/TIGER2022/PUMA/ on June 22, 2023

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. Public Use Microdata Areas (PUMAs) are decennial census areas that permit the tabulation and dissemination of Public Use Microdata Sample (PUMS) data, American Community Survey (ACS) data, and data from other census and surveys. For the 2020 Census, the State Data Centers (SDCs) in each state, the District of Columbia, and the Commonwealth of Puerto Rico had the opportunity to delineate PUMAS within their state or statistically equivalent entity. All PUMAs must nest within states and have a minimum population threshold of 100,000 persons. 2020 PUMAs consist of census tracts and cover the entirety of the United States, Puerto Rico and Guam. American Samoa, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands do not contain any 2020 PUMAs because the population is less than the minimum population requirement. Each PUMA is identified by a 5-character numeric census code that may contain leading zeros and a descriptive name. The 2020 PUMAs will appear in the 2022 TIGER/Line Shapefiles.