View metadata for key information about this dataset.For questions about this dataset, contact darshna.patel@phila.gov. For technical assistance, email maps@phila.gov.

To provide a base for very generalized maps or used as an outline in conjunction with other data layers. Establishes City Limits for City's Standard Boundary Format. This layer was updated on July 22, 2012.

Municipal boundaries for DVRPC Region with Philadelphia's County Planning Areas. Municipal Boundaries have been edited by DVRPC to create a more accurate, seemless regional dataset for the DVRPC region and its surrounding area. This dataset was compiled from multiple sources. Original data sources (in order of drawing rank): DVRPC - for Mercer, Burlington, Camden, Gloucester counties in NJ (an adaptation of NJOIT's Mun Bounds) and Bucks, Montgomery, Philadelphia, Chester, and Delaware counties in PA. In most cases, boundaries have been adjusted to align with parcel data. Due to the name change from Washington Twp to Robbinsville Twp in Mercer County, the unique ID (GEOID) for this municipality has changed from 3402177210 to 3402163850 . However, if you download 2000 census data from the Bureau's website, the unique ID (GEOID) for Robbinsville Township will still be 3402177210 in the census data…you will have to manually change its GEOID to 3402163850 in order to get the 2000 data to join to the MCD file correctly. Edited in April 2021 to match PCPC's planning district boundaries and numbers dated 2013

View metadata for key information about this dataset.Center City District encompasses 120 blocks and more than 4500 individual properties. The mission is to keep Center City clean, safe, and fun. CCD also makes physical improvements to center city by installing and maintain lighting, signs, banners trees and landscape. For questions about this dataset, contact publicsafetygis@phila.gov. For technical assistance, email maps@phila.gov.

This layer was developed to aid the Surveys Division in planning, modifying and referencing the streets within a city plan of the City of Philadelphia. Examples include: building new streets, modifying existing streets, or observing current streets.

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

Municipal boundaries for Pennsylvania, New Jersey, Maryland, Delaware, and the District of Columbia with ortho-rectified municipal boundaries for the DVRPC Region. Municipal Boundaries have been edited by DVRPC to create a more accurate, seemless regional dataset for the DVRPC region and its surrounding area. Original data sources (in order of drawing rank): DVRPC - for Mercer, Burlington, Camden, Gloucester counties in NJ (an adaptation of NJOIT's Mun Bounds) and Bucks, Montgomery, Philadelphia, Chester, and Delaware counties in PA. In most cases, boundaries have been adjusted to align with parcel data. NJOIT - remaining NJ counties (2008) PennDOT - remaining PA counties (2009) DE State Office of Mgmt & Budget - Delaware municipalities (2002) MD State Hwy Administration - Maryland municipalities (2003) NOTE: NJ's coast has been clipped or unioned to ESRI's data CD detailed state boundary

The boundaries of the four designated pilot areas included in the Philly Rising program. Philly Rising focuses on areas with chronic quality of life concerns and works with residents and community groups to address neighborhood issues.

The Center City District (CCD) is a business improvement district. The mission is to keep Center City clean, safe, and fun. CCD also makes phyiscal improvements to center city by installing and maintain lighting, signs, banners trees and landscape. This layer displays their policing boundary.

Boundaries of Registered Community Organizations (RCO) as established under the City of Philadelphia Zoning Code enacted December 15, 2011 and made effective August 22, 2012.

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.

View metadata for key information about this dataset.Boundaries are based on existing City zoning districts with revised codes applied per enactment of the new Zoning Code of December 2011, made effective August 22, 2012. District boundaries are unchanged from the previous zoning with the exception of certain CMX2 / CMX2.5 splits.For questions about this dataset, contact darshna.patel@phila.gov. For technical assistance, email maps@phila.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.

Trouble downloading or have questions about this City dataset? Visit the OpenDataPhilly Discussion Group

Center City District encompasses 120 blocks and more than 4500 individual properties. The mission is to keep Center City clean, safe, and fun. CCD also makes phyiscal improvements to center city by installing and maintain lighting, signs, banners trees and landscape.

CLICK HERE to view metadata. For any questions or technical assistance please email maps@phila.gov.

The data is used to determine the day of sanitation collection (rubbish and recycling) for a given location and set of households in the City of Philadelphia. The file is also used to aggregate data such as households, tonnage, and mileage. This polygon layer has an accompanying arc layer. Certain arcs in the arc layer contain data signifying information relating it to the polygon layer. It can tell you if both sides of the arc belong to one of the bounding polygons. All the arcs, including those with no boundary info, have naming attributes for labeling the polygon borders.

A comprehensive inventory of all trees within the limits of the City of Philadelphia. This dataset is a snapshot in time from 2021 and will update yearly.

About the G.M. Hopkins Maps

History and Background of the Maps

Maps produced by the G.M. Hopkins Company have made a lasting impression on the boundaries of many American cities. Between 1870 and 1940, the company produced over 175 atlases and real estate plat maps that primarily covered the Eastern sea board, including cities, counties, and townships in 18 different states and the District of Columbia. In the early years, the company produced county atlases, but gradually focused on city plans and atlases. They were among the first publishers to create a cadastral atlas, a cross between a fire insurance plat and a county atlas prevalent in the 1860s-1870s. These real estate or land ownership maps (also known as plat maps) not only depict property owners, but show lot and block numbers, dimensions, street widths, and other buildings and landmarks, including churches, cemeteries, mills, schools, roads, railroads, lakes, ponds, rivers, and streams.

Originally named the G.M. Hopkins and Company, the map-making business was jointly founded in 1865 in Philadelphia, Pa., by the Hopkins brothers, G.M. and Henry. The true identity of G.M. Hopkins remains somewhat of a mystery even today. “G.M.” either stands for Griffith Morgan or George Morgan. There are three different possibilities for the confusion over his identity. “Either the compilers of the earlier [city] directories were negligent; G.M. Hopkins changed his first name; or there were two G.M. Hopkins (father and son) working for the same firm” (Moak, Jefferson M. Philadelphia Mapmakers. Philadelphia: Shackamaxon Society, 1976, p. 258).

http://digital.library.pitt.edu/abouthp/#hopkins

There are currently 65 Police Service Areas (PSA) boundaries in Philadelphia with two to four per District. These boundaries replaced a much smaller boundary, Sectors in 2009. In several Districts, PSA's split Sector boundaries and therefore a historical comparison would not necessarily be accurate.

Trouble downloading or have questions about this City dataset? Visit the OpenDataPhilly Discussion Group

View metadata for key information about this dataset.A Police Captain is responsible for each district. Districts are subdivided into sectors. Several districts are aggregated into divisions.See also the related datasets:Police DivisionsPolice Service AreasFor questions about this dataset, contact publicsafetygis@phila.gov. For technical assistance, email maps@phila.gov.