Name: Philly Planning Land Use

Display Field: C_DIG1DESC

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Citywide land use as determined by the City Philadelphia Planning Commission (PCPC). Prepared for Philadelphia2035, the City’s comprehensive development plan, to support the zoning reform remapping and the District Planning projects. For more information on the Philadelphia2035 comprehensive planning process, see www.phila2035.org Land use classifications are activity-based. Each land unit has only one land use designation interpreted by a 1, 2 or 3-digit code. Specificity of a land use description increases from the one to three digit code. Example: 1= Residential, 1.2 = Residential Medium Density, and 1.2.1 = Residential Rowhouse.Land use features are derived from Philadelphia Water Department tax parcel boundaries (2009 to current release date) and from other GIS datasets prepared by City departments including: planimetric features, transportation right-of-ways (ROW), parks and open space, and water. Land use boundaries are typically coincident with PWD tax parcel boundaries, where tax parcel boundaries are available to define units of land. In some cases multiple land activities on a single parcel and been individual represented as individual polygons of land use. This land use feature class is under revision through 2014. Updates will be made to correct attributes and features and to populate 3-digit codes based upon field verifications made by PCPC staff. Land use field surveys will be conducted for each of the 18 Planning District beginning in 2011 as part of the Philadelphia2035 Compressive Planning process. For areas not yet updated by a Planning District field survey, land use designations are qualified estimates derived from the Office of Property Assessment data (see details under “Development Process” below). LineageThe land use feature class has been field checked and corrected for selected Planning Districts as follows. The year of the update is in parentheses: Central (2012)Central Northeast (2013)Lower North (2013)Lower Northeast (2012)Lower Northwest (2013)Lower South (2011)River Wards (2014)South (2014)West Park (2011)University Southwest (2012)Also includes portions of Lower Schuylkill (2012) in Lower Southwest and portions of the North district along the Amtrak corridor (2013).Field checks and updates are planned for the remaining Planning Districts as part of the Philadelpia2035 comprehensive planning process.Hunting Park West (2015)North Delaware (2015)Lower Southwest (2015)Germantown (2015)Portions along Roosevelt Boulevard (2015)Landuse Codes and DescriptionsLanduse codes are organized from the 1-digit to 3-digit level. Specificity of land use increases with each increasing digit. Coded numeric values are stored as integers. Full text descriptions are contained in separate string fields. Values in the 3-digit code and description fields may not be fully populated, indicating that these features have not been field verified, or that this level of specificity cannot be accurately assigned. All features are attributed at the 1- and 2-digit levels.Key Attribute Fieldsc_Dig1 - 1-digit level land use coding, numeric code.c_Dig2 - 2-digit level land use coding, numeric code.1.0 Residential 1.1 Residential Low Density1.2 Residential Medium Density1.3 Residential High Density2.0 Commercial2.1 Commercial Consumer2.2 Commercial Business and Professional2.3 Commercial Mixed Residential 3.0 Industrial 4.0 Civic/Institution5.0 Transportation6.0 Culture/Recreation6.1 Culture/Amusement6.2 Active Recreation7.0 Park/Open Space7.1 Park/Open Space7.2 Cemetery8.0 Water9.0Vacant or Other9.1 Vacant Land9.2 Other/Unknownc_Dig3 - 3-digit level land use coding, numeric code.c_Dig1Desc - 1-digit level land use text description.c_Dig2Desc - 2-digit level land use text description.c_Dig3Desc - 3-digit level land use text description.YEAR - the year to which the land use codes are current. If year 2010, this reflects land use codes that have NOT been field surveyed and the codes were assigned as described in the "Development Process" below.Development ProcessThe PCPC acquired the Philadelphia Water Department's (PWD) tax parcel boundary feature class (2009) for use as base layer geometry. This parcel base does not contain transportation, park, or water features required for identification of land uses for every unit of land across the entire city. Separate feature classes were acquired by the PCPC to represent all other land features streets, highways and rail right of ways, rail yards, parks and open space, parking lots and sidewalks, and marine terminals. Multiple feature classes were merged into a single feature class in ArcGIS 9x to produce a seamless fabric of land and water features citywide. Gaps in the spatial fabric persisted where feature classes did not topologically align. Gaps, slivers and overlaps between features, resulting from the merge process, were identified and edited using ArcGIS geodatabase topology rules.The resulting draft “Land Use 2010” feature class was joined with the Office of Property Assessment (OPA), formerly BRT, real estate database (2009). The PCPC used OPA building description values from the real estate table as the basis for land use categorization. All features were attributed to the 2-digit level. PCPC staff checked and corrected these categorizations using the following resources: PhilaShops retail properties database (2003); Philadelphia Industrial Development Corporation’s Industrial Market and Landuse Strategy report (2009), and Philadelphia Parks and Recreation (PPR) parks land and facilities database (2010). Under the Philadelphia2035 District Planning process, this feature class will undergo field verification as each Planning District project is completed. A total of 18 Planning Districts will be surveyed from 2011 to 2016. Field verification results in corrections to land use attributes and population of the 3-digit land use codes, which cannot otherwise cannot be determined without field inspection. Revisions to this land use feature class will be posted as survey work and evaluation for each Planning District is fully completed. Thematic MappingFor thematic mapping, use the c_dig2 or c_Dig2Desc fields. The c_Dig2Desc field maintains the full text description of the 2-digit land use codes (e.g., 11 = Residential Low Density). An ESRI ArcGIS layer file (.lyr) with pre-set symbology is available from the PCPC. Symbol RGB Values11 - Residential Low : 255, 255, 20412 - Residential Medium : 245, 255, 1813 - Residential High : 255, 170, 021 - Commercial Consumer : 230, 0, 022 - Commercial Business/Professional : 168, 0, 023 -Mixed Commercial/Residential : 232, 149, 12131 - Industrial : 140, 0, 25541 - Civic/Institution: 0, 112, 25551 - Transportation : 204, 204, 20461 - Culture/Recreation : 0, 255, 23062 - Active Recreation: 155,204,179; 99, 204, 071 - Park/Open Space : 99, 204, 072 - Cemetery : 99, 204, 0; 107, 126, 14781 - Water : 191, 232, 25591 - Vacant: 168, 112, 092 - Other/Unknown: 107, 126, 174; 210, 210, 210

Copyright Text: Created by Mark Wheeler, GISP Maintained by PCPC GIS Divison Darshna Patel, GISP, GIS Manager at PCPC 1515 Arch Street, 13th Floor Philadelphia PA 19102 Darshna.patel@phila.gov 215-683-4611

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -75.28415128126424
YMin: 39.86173421807715
XMax: -74.95403893745981
YMax: 40.14379711484675
Spatial Reference: 4269  (4269)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [0, 0, 0, 0]
Outline:
Style: esriSLSSolid
Color: [0, 0, 0, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• C_DIG1 ( type: esriFieldTypeSmallInteger, alias: C_DIG1 )
• C_DIG1DESC ( type: esriFieldTypeString, alias: C_DIG1DESC, length: 50 )
• C_DIG2 ( type: esriFieldTypeSmallInteger, alias: C_DIG2 )
• C_DIG2DESC ( type: esriFieldTypeString, alias: C_DIG2DESC, length: 50 )
• C_DIG3 ( type: esriFieldTypeSmallInteger, alias: C_DIG3 )
• C_DIG3DESC ( type: esriFieldTypeString, alias: C_DIG3DESC, length: 250 )
• VACBLDG ( type: esriFieldTypeString, alias: VACBLDG, length: 5 )
• YEAR ( type: esriFieldTypeSmallInteger, alias: YEAR )
• SHAPE_Leng ( type: esriFieldTypeDouble, alias: SHAPE_Leng )
• Shape_Length ( type: esriFieldTypeDouble, alias: Shape_Length )
• Shape_Area ( type: esriFieldTypeDouble, alias: Shape_Area )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata