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.

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.

This layer is not created by the City of Philadelphia but is provided for mapping purposes. For further information about this layer, see the documentation on Census.Gov.

For matching and analyzing demographic data collected and compiled by the U.S. Census Bureau & American Community Survey(ACS) to the geography of Census Block Group boundaries within the City of Philadelphia. These boundaries can change every ten years when the decennial census is conducted. Adjusted to City's Standard Boundary Format.

DVRPC manually adjusted TIGER MCD dataset by adding Philly Planning District boundaries. To get the Planning District boundaries, census tracts were dissolved into most appropriate CPA geography. (Planning Districts are sometime referred to as County Planning Areas at DVRPC) Updated in Jan 2023 to reflect Pine Valley/Pine Hill merger (Pine Valley was incorporated into Pine Hill) 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. See https://www2.census.gov/geo/pdfs/maps-data/data/tiger/tgrshp2020/TGRSHP2020_TechDoc_Ch3.pdf for more information Downloaded from: https://www2.census.gov/geo/tiger/TGRGDB20/ on August 13, 2020

The TIGER/Line Files are shapefiles and related database files (.dbf) that 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 File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may 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. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas. Some boundary details clarified by Philadelphia City Planning Commission May 2011

Layers included in this map service at the Census Tract level are: Age, Disability, Female Population, Limited English Proficiency (LEP), Low Income, Place of Birth, Race and Zero Vehicle Households.

Describes heat vulnerability by census tract incorporating exposure and sensitivity indicators.

This layer is not created by the City of Philadelphia but is provided for mapping purposes. For further information about this layer, see the documentation on Census.Gov.

The basic unit of aggregation published by the US Census Bureau. Population statistics published for redistricting are distributed at the block level. In an urban area, this corresponds to approximately one city block. This block map has been altered to improve accuracy and align with the City of Philadelphia's street centerline.

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. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

Every ten years, with the Decennial Census, Census Tract boundaries are updated. Resources in this dataset log what tract changes have occurred since the previous decade's boundaries were released.

Population metrics are provided at the census tract, planning district, and citywide levels of geography. You can find related vital statistics tables that contain aggregate metrics on natality (births) and mortality (deaths) of Philadelphia residents as well as social determinants of health metrics at the city and planning district levels of geography. Please refer to the metadata links below for variable definitions and the technical notes document to access detailed technical notes and variable definitions.

Vital Statistics tables that contain aggregate metrics on the natality (births) of Philadelphia residents. Included in these datasets are natality metrics by planning district or citywide. You can find mortality (deaths) metrics, and social determinants of health metrics at the city and planning district levels of geography as well. Population metrics are provided at the city, planning district, and census tract levels of geography. Please refer to the metadata links below for variable definitions and this technical notes document to access detailed technical notes about the datasets.

This layer is not created by the City of Philadelphia but is provided for mapping purposes. For further information about this layer, see the documentation on Census.Gov.

Data from the Department of License and Inspections, Planning, Parks and Recreation, Heath, etc, can be viewed on this interactive map. Preset maps can be selected containing datasets from the following categories: Bike Network, Business, Construction, Gun Permit Appeals, Rental Licenses, Vacancy, Violations, and Zoning. Users can also overlay districts on the map, such as Census Tracts or Sanitation Districts. Additional datasets will be added over time. API access is available through the ArcGIS Server Map Services API interface. Trouble downloading or have questions about this City dataset? Visit the OpenDataPhilly Discussion Group

This dataset contains data from the P.L. 94-171 2020 Census Redistricting Program. The 2020 Census Redistricting Data Program provides states the opportunity to delineate voting districts and to suggest census block boundaries for use in the 2020 Census redistricting data tabulations (Public Law 94-171 Redistricting Data File). In addition, the Redistricting Data Program will periodically collect state legislative and congressional district boundaries if they are changed by the states. The program is also responsible for the effective delivery of the 2020 Census P.L. 94-171 Redistricting Data statutorily required by one year from Census Day. The program ensures continued dialogue with the states in regard to 2020 Census planning, thereby allowing states ample time for their planning, response, and participation. The U.S. Census Bureau will deliver the Public Law 94-171 redistricting data to all states by Sept. 30, 2021. COVID-19-related delays and prioritizing the delivery of the apportionment results delayed the Census Bureau’s original plan to deliver the redistricting data to the states by April 1, 2021.

Data in this dataset contains information on population, diversity, race, ethnicity, housing, household, vacancy rate for 2020 for various geographies (county, MCD, Philadelphia Planning Districts (referred to as county planning areas [CPAs] internally, Census designated places, tracts, block groups, and blocks)

For more information on the 2020 Census, visit https://www.census.gov/programs-surveys/decennial-census/about/rdo/summary-files.html

PLEASE NOTE: 2020 Decennial Census data has had noise injected into it because of the Census's new Disclosure Avoidance System (DAS). This can mean that population counts and characteristics, especially when they are particularly small, may not exactly correspond to the data as collected. As such, caution should be exercised when examining areas with small counts. Ron Jarmin, acting director of the Census Bureau posted a discussion of the redistricting data, which outlines what to expect with the new DAS. For more details on accuracy you can read it here: https://www.census.gov/newsroom/blogs/director/2021/07/redistricting-data.html

Social determinants of health metrics at the city and planning district levels of geography. Please refer to the metadata links below for variable definitions and this technical notes document to access detailed technical notes and variable definitions. You can find related vital statistics tables that contain aggregate metrics on vital events, including natality (births) metrics and mortality (deaths) by planning district or citywide. Population metrics are provided at the city, planning district, and census tract levels of geography.

This study was designed to explore school culture and climate and their effects on school disorder, violence, and academic performance on two levels. At the macro level of analysis, this research examined the influences of sociocultural, crime, and school characteristics on aggregate-level school violence and academic performance measures. Here the focus was on understanding community, family, and crime compositional effects on disruption and violence in Philadelphia schools. This level included Census data and crime rates for the Census tracts where the schools were located (local data), as well as for the community of residence of the students (imported data) for all 255 schools within the Philadelphia School District. The second level of analysis, the intermediate level, included all of the variables measured at the macro level, and added school organizational structure and school climate, measured with survey data, as mediating variables. Part 1, Macro-Level Data, contains arrest and offense data and Census characteristics, such as race, poverty level, and household income, for the Census tracts where each of the 255 Philadelphia schools is located and for the Census tracts where the students who attend those schools reside. In addition, this file contains school characteristics, such as number and race of students and teachers, student attendance, average exam scores, and number of suspensions for various reasons. For Part 2, Principal Interview Data, principals from all 42 middle schools in Philadelphia were interviewed on the number of buildings and classrooms in their school, square footage and special features of the school, and security measures. For Part 3, teachers were administered the Effective School Battery survey and asked about their job satisfaction, training opportunities, relationships with principals and parents, participation in school activities, safety measures, and fear of crime at school. In Part 4, students were administered the Effective School Battery survey and asked about their attachment to school, extracurricular activities, attitudes toward teachers and school, academic achievement, and fear of crime at school. Part 5, Student Victimization Data, asked the same students from Part 4 about their victimization experiences, the availability of drugs, and discipline measures at school. It also provides self-reports of theft, assault, drug use, gang membership, and weapon possession at school.

This study was designed to explore school culture and climate and their effects on school disorder, violence, and academic performance on two levels. At the macro level of analysis, this research examined the influences of sociocultural, crime, and school characteristics on aggregate-level school violence and academic performance measures. Here the focus was on understanding community, family, and crime compositional effects on disruption and violence in Philadelphia schools. This level included Census data and crime rates for the Census tracts where the schools were located (local data), as well as for the community of residence of the students (imported data) for all 255 schools within the Philadelphia School District. The second level of analysis, the intermediate level, included all of the variables measured at the macro level, and added school organizational structure and school climate, measured with survey data, as mediating variables. Part 1, Macro-Level Data, contains arrest and offense data and Census characteristics, such as race, poverty level, and household income, for the Census tracts where each of the 255 Philadelphia schools is located and for the Census tracts where the students who attend those schools reside. In addition, this file contains school characteristics, such as number and race of students and teachers, student attendance, average exam scores, and number of suspensions for various reasons. For Part 2, Principal Interview Data, principals from all 42 middle schools in Philadelphia were interviewed on the number of buildings and classrooms in their school, square footage and special features of the school, and security measures. For Part 3, teachers were administered the Effective School Battery survey and asked about their job satisfaction, training opportunities, relationships with principals and parents, participation in school activities, safety measures, and fear of crime at school. In Part 4, students were administered the Effective School Battery survey and asked about their attachment to school, extracurricular activities, attitudes toward teachers and school, academic achievement, and fear of crime at school. Part 5, Student Victimization Data, asked the same students from Part 4 about their victimization experiences, the availability of drugs, and discipline measures at school. It also provides self-reports of theft, assault, drug use, gang membership, and weapon possession at school.