| Date | Title | Provider |
| 2025 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Datum of 1983
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
PhillyRising’s 19 active neighborhoods as of FY15. These areas were identified in partnership with the Police Department for their high rates of violent crime and quality of life issues, including poverty. PhillyRising strives to advance City services and community partnerships within these neighborhoods.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
The Choice Neighborhoods program is administered by the U.S. Department of Housing and Urban Development (HUD). It supports locally driven strategies to address struggling neighborhoods with distressed public or HUD-assisted housing through a comprehensive approach to neighborhood transformation.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
boat launches along the two major bodies of water, the Schuylkill River and the Delaware River. These boat launched have direct access into either one of these bodies of water.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
The points of pools owned and managed by Philadelphia Parks and Recreation. This layer was created to be used for the Philadelphia Parks and Recreation website.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
The points of spraygounds owned and managed by Philadelphia Parks and Recreation. This layer was created to be used for the Philadelphia Parks and Recreation website.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Displays the locations of adult exercise equipment located within or are maintained by Philadelphia Parks and Recreation (PPR).
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Footprints of buildings and structures located on Philadelphia Parks and Recreation (PPR) properties or utilized directly by PPR.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Point representations of Philadelphia Parks and Recreation (PPR) help locators. These are virtual points representing signage locations and their vehicular access points.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Displays the locations of playgrounds within PPR Boundaries. Playgrounds designated as similar age range equipment within a definable distance (not each piece of equipment).
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Point location feature for all PPR Program Sites. This includes all recreation centers, playgrounds, older adult centers, swimming pools, and environmental education centers.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Location and boundaries of lands that Philadelphia Parks and Recreation is responsible or has a distinct role in maintaining or managing.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Displays the locations of outdoor tennis courts located within Philadelphia Parks and Recreation boundaries.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2023 |
Locations of trees that Philadelphia Parks and Recreation (PPR) inventories within the limits of the City of Philadelphia. This dataset is a snapshot in time.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2004 |
Planimetric Coverage containing the delineation of topographic contours at ten foot intervals. Annotation of Contour Line elevations exists. Annotation viewable at 1" = 200'. The city-wide contour download file is approximately 250 megabytes.
Metadata
|
Download
|
Preview
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2004 |
Planimetric Coverage containing the delineation of topographic contours at two foot intervals. Annotation of Contour Line elevations exists. Annotation viewable at 1" = 200'. The city-wide contour download file is approximately 250 megabytes.
Metadata
|
Download
|
Preview
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2008 |
LiDAR and LAS data was gathered for the City of Philadelphia in April 2008. DEMs were generated from the raw data.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2010 |
LiDAR and LAS data was gathered for the City of Philadelphia in April 2010. DEMs were generated from the raw data.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2015 |
Classified LiDAR LAS and Derivative Products - This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. The dataset consists of 1024 lidar point cloud LAS files. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. The data was collected at a nominal point spacing of 0.70m using Pictometry's Riegl LMS-Q680i LiDAR system over 4 mission days on April 18th, 19th, 22nd, and 25th, 2015. At the time of capture ground condiitons were leaf-off, snow free, and water was at normal levels.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2015 |
Classified LiDAR LAS and Derivative Products - This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. The dataset consists of 1024 lidar point cloud LAS files. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. The data was collected at a nominal point spacing of 0.70m using Pictometry's Riegl LMS-Q680i LiDAR system over 4 mission days on April 18th, 19th, 22nd, and 25th, 2015. At the time of capture ground condiitons were leaf-off, snow free, and water was at normal levels.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2015 |
The lidar dataset was collected to be utilized for the creation of a digital elevation model and 1ft contours. Other uses expected. The GIS Services Group at OIT generated these 10ft Contours for the 2015 1ft Contours.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2015 |
The lidar dataset was collected to be utilized for the creation of a digital elevation model and 1ft contours. Other uses expected. Lidar Data Products for the Philadelphia, PA collection area including a 5ft Digital Elevation Model (DEM), and tiled1ft Contours.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2015 |
The lidar dataset was collected to be utilized for the creation of a digital elevation model and 1ft contours. Other uses expected. The GIS Services Group at OIT generated these 2ft Contours from the 2015 1ft Contours.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2018 |
DEM/Hillshade - LiDAR and LAS data was gathered for the City of Philadelphia in April 2018. DEMs were generated from the raw data. Classified LiDAR LAS and Derivative Products - This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. The dataset consists of 1024 lidar point cloud LAS files. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. The data was collected at a nominal point spacing of 0.70m using Pictometry's Riegl LMS-Q680i LiDAR system over 4 mission days on April 18th, 19th, 22nd, and 25th, 2015. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2018 |
DEM/Hillshade - LiDAR and LAS data was gathered for the City of Philadelphia in April 2018. DEM/Hillshade was generated from the raw data. Classified LiDAR LAS and Derivative Products - This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. The dataset consists of 1024 lidar point cloud LAS files. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. The data was collected at a nominal point spacing of 0.70m using Pictometry's Riegl LMS-Q680i LiDAR system over 4 mission days on April 18th, 19th, 22nd, and 25th, 2015. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2018 |
Planimetric Coverage containing the delineation of topographic contours at ten foot intervals. Annotation of Contour Line elevations exists. LiDAR and LAS data was gathered for the City of Philadelphia in April 2018. DEMs were generated from the raw data. This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 239 sq miles total. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels
Metadata
|
Download
| More Options...
| City of Philadelphia |
| 2018 |
Planimetric Coverage containing the delineation of topographic contours at two foot intervals. Annotation of Contour Line elevations exists. LiDAR and LAS data was gathered for the City of Philadelphia in April 2018. DEMs were generated from the raw data. This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 239 sq miles total. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels.
Metadata
|
Download
| More Options...
| City of Philadelphia |
| 2022 |
Contours 10ft - LiDAR and LAS data was gathered for the City of Philadelphia in April 2022. DEMs were generated from the raw data. Classified LiDAR LAS and Derivative Products - This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels. For Additional Information see: https://www.pasda.psu.edu/download/phillyLiDAR/2022/Metadata_and_Reports/Lidar_Report/65221207_Philadelphia_Mapping_Report.pdf
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2022 |
DEM - LiDAR and LAS data was gathered for the City of Philadelphia in April 2022. DEMs were generated from the raw data. Classified LiDAR LAS and Derivative Products - This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels. For Additional Information see: https://www.pasda.psu.edu/download/phillyLiDAR/2022/Metadata_and_Reports/Lidar_Report/65221207_Philadelphia_Mapping_Report.pdf
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2022 |
Hillshade - LiDAR and LAS data was gathered for the City of Philadelphia in April 2022. DEMs were generated from the raw data. Classified LiDAR LAS and Derivative Products - This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels. For Additional Information see: https://www.pasda.psu.edu/download/phillyLiDAR/2022/Metadata_and_Reports/Lidar_Report/65221207_Philadelphia_Mapping_Report.pdf
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2022 |
Topographic Contours 1ft - Planimetric Coverage containing the delineation of topographic contours at one foot intervals. Annotation of Contour Line elevations exists. LiDAR and LAS data was gathered for the City of Philadelphia in April 2022. DEMs were generated from the raw data. This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 239 sq miles total. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels. For Additional Information see: https://www.pasda.psu.edu/download/phillyLiDAR/2022/Metadata_and_Reports/Lidar_Report/65221207_Philadelphia_Mapping_Report.pdf
Metadata
|
Download
| More Options...
| City of Philadelphia |
| 1996 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 1996 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2000 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2000 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2004 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2004 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2005 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2005 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2008 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2008 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2009 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2009 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2010 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2010 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2011 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2011 |
Philadelphia aerial photography - Leaf On
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2011 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2011 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2012 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2012 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2014 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2014 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2015 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2015 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2016 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2016 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2016 |
Philadelphia aerial photography
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2016 |
Philadelphia aerial photography 3 inch pixels tile index. The dataset consists of tiled orthogonal imagery produced from nadir images captured by Pictometry International.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2017 |
Philadelphia aerial photography city wide mosaic. The dataset consists of tiled orthogonal imagery produced from nadir images captured by Pictometry International.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2017 |
Philadelphia aerial photography 1 meter pixels. The dataset consists of tiled orthogonal imagery produced from nadir images captured by Pictometry International.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2017 |
Philadelphia aerial photography 1 meter pixels tile index. The dataset consists of tiled orthogonal imagery produced from nadir images captured by Pictometry International.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2017 |
Philadelphia aerial photography 3 inch pixels. The dataset consists of tiled orthogonal imagery produced from nadir images captured by Pictometry International.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2017 |
Philadelphia aerial photography 3 inch pixels tile index. The dataset consists of tiled orthogonal imagery produced from nadir images captured by Pictometry International.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2018 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2018 |
Tile Index - Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2019 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2019 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2020 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2020 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2022 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2022 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2023 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2023 |
Tile Index - Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2024 |
Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2024 |
Tile Index - Color Citywide digital orthophotography with a ground resolution of at various resolutions, georeferenced to the Pennsylvania State Plane Coordinate System, and delivered as individual and mosaicked raster images. The dataset consists of tiled orthogonal imagery produced from nadir images captured by various contractors during the months of April and May.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2012 |
Philadelphia bike network and supporting datasets is an experimental dataset that combines various City of Philadelphia departments' datasets to support bike network routing. These datasets are in an experimental stage and are not yet approved for wide use. Use with caution is recommended. Datasets include Bike Network, Connector Streets, Regional Routes, and Trails and Side paths. For source, date, limitations and additional data for each supporting dataset, please see metadata.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2012 |
This dataset is a combination of both bike racks installed in 2008 as a result of Adopt-a-rack program and racks installed by converting parking meters by the Philadelphia Parking Authority.
Those racks installed in 2008 as part of the City's first Adopt-a-rack program were requested by civic and business associations who "adopted" them and promised to clear abandoned bikes, remove graffiti and maintain them if they were damaged. These bike racks are in the style of 'staple' or 'hoop' racks.
The PPA racks are those mounted to the former parking meter posts. They are the green discs that have been installed through Center City and parts of University City.
The PROJECT field defines the associated project of installation, either Adopt-a-rack or PPA.
The STAND_ADD field is most appropriate for address locating or geocoding purposes.
Please note the field NUM_RACKS represents the number of racks at a given address. Each record may represent more than one bike rack.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2008 |
Files used to comprise a 3D building model of the City of Philadelphia
Metadata
|
Download
| More Options...
| City of Philadelphia |
| 2010 |
Files used to comprise a 3D building model of the City of Philadelphia
Metadata
|
Download
| More Options...
| City of Philadelphia |
| 2015 |
Files used to comprise a 3D building model of the City of Philadelphia
Metadata
|
Download
| More Options...
| City of Philadelphia |
| 2017 |
Planimetric Coverage containing the delineation of buildings or related structure outlines that represent the footprints of buildings within the City of Philadelphia.
Outlines are based on imagery captured in early 2015.
FEATURES DELINEATED:
-Residential, commercial and industrial buildings
-Isolated garages, mobile homes, sheds
-Greenhouses and silos
-Buildings under construction that at least have walls
-Trailer boxes with windows or doors
Data was captured from AccuPLUS Orthomosaic tiles created off PAPHIL15-LEAF-OFF imagery, flown by Pictometry.
Metadata
|
Download
|
Preview
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2010 |
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
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
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
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
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
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2000 |
Census bureau statistical units. Most commonly used statistical unit. This version, released January 2004 contains a fix, replacing tract 172 which was omitted from previous versions.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2010 |
Census tracts are small, relatively permanent statistical subdivisions of a county delineated by local participants as part of the U.S. Census Bureau's Participant Statistical Areas Program. The U.S. Census Bureau delineated census tracts in situations where no local participant existed or where 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 decennial census data. Census tracts generally have between 1,500 and 8,000 people, with an optimum size of 4,000 people. Counties with fewer people have a single census tract.) When first delineated, census tracts are 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. Census tract boundaries are delineated with the intention of being maintained over many decades so that statistical comparisons can be made from decennial census to decennial census. However, physical changes in street patterns caused by highway construction, new developments, and so forth, may require occasional boundary revisions. In addition, census tracts occasionally are split due to population growth or combined as a result of substantial population decline.Census tracts are identified by a four-digit basic number and may have a two-digit numeric suffix; or example, 6059.02. The decimal point separating the four-digit basic tract number from the two-digit suffix is shown in the printed reports and on census maps. In computer-readable files, the decimal point is implied. Many census tracts do not have a suffix; in such cases, the suffix field is either left blank or is zero-filled. Leading zeros in a census tract number (for example, 002502) are shown only in computer-readable files. Census tract suffixes may range from .01 to .98. For the 1990 census, the .99 suffix was reserved for census tracts/block numbering areas (BNAs) that contained only crews-of-vessels population; for Census 2000, the crews-of-vessels population is part of the related census tract.Census tract numbers range from 1 to 9999 and are unique within a county or statistically equivalent entity. The U.S. Census Bureau reserves the basic census tract numbers 9400 to 9499 for census tracts delineated within or to encompass American Indian reservations and off-reservation trust lands that exist in multiple states or counties. The number 0000 in computer-readable files identifies a census tract delineated to provide complete coverage of water area in territorial seas and the Great Lakes. Projection: Lambert Conformal ConicXY Coordinate System: NAD 1983 StatePlane Pennsylvania South FIPS 3702 (US Feet)Datum: NAD 1983Units of Measurement: Foot_US
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Census tracts are small, relatively permanent statistical subdivisions of a county delineated by local participants as part of the U.S. Census Bureau's Participant Statistical Areas Program. The U.S. Census Bureau delineated census tracts in situations where no local participant existed or where 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 decennial census data. Census tracts generally have between 1,500 and 8,000 people, with an optimum size of 4,000 people. Counties with fewer people have a single census tract.) When first delineated, census tracts are 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. Census tract boundaries are delineated with the intention of being maintained over many decades so that statistical comparisons can be made from decennial census to decennial census. However, physical changes in street patterns caused by highway construction, new developments, and so forth, may require occasional boundary revisions. In addition, census tracts occasionally are split due to population growth or combined as a result of substantial population decline.Census tracts are identified by a four-digit basic number and may have a two-digit numeric suffix; or example, 6059.02. The decimal point separating the four-digit basic tract number from the two-digit suffix is shown in the printed reports and on census maps. In computer-readable files, the decimal point is implied. Many census tracts do not have a suffix; in such cases, the suffix field is either left blank or is zero-filled. Leading zeros in a census tract number (for example, 002502) are shown only in computer-readable files. Census tract suffixes may range from .01 to .98. For the 1990 census, the .99 suffix was reserved for census tracts/block numbering areas (BNAs) that contained only crews-of-vessels population; for Census 2000, the crews-of-vessels population is part of the related census tract.Census tract numbers range from 1 to 9999 and are unique within a county or statistically equivalent entity. The U.S. Census Bureau reserves the basic census tract numbers 9400 to 9499 for census tracts delineated within or to encompass American Indian reservations and off-reservation trust lands that exist in multiple states or counties. The number 0000 in computer-readable files identifies a census tract delineated to provide complete coverage of water area in territorial seas and the Great Lakes. Projection: Lambert Conformal ConicXY Coordinate System: NAD 1983 StatePlane Pennsylvania South FIPS 3702 (US Feet)Datum: NAD 1983Units of Measurement: Foot_US
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This polygon layer represents the Market Areas for each representative from the Department of Commerce Office of Business Services (OBS). All polygons (nearly all of which correspond to zip codes) associated with an OBS representative’s name comprise that representative’s Market Area.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This data set reflects the recipients, award amounts, and project sites for grant money disbursed by the Philadelphia Commerce Department for the Storefront Improvement Program whereby businesses are provided the funds to improve the exterior of their storefront and beautify the commercial corridor on which they operate.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
correctional facility points in the City, administered by the Philadelphia Prisons System
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 1990 |
District boundaries of municipal legislators.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2000 |
District Boundaries of Municipal Legislators
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2024 |
This map data layer represents the city council districts for the City of Philadelphia, PA. The city council districts data layer was determined by the boundaries of the Philadelphia County voting precincts and the City Ordinance that established the districts based on the precincts.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2024 |
This dataset is composed of the entire City of Philadelphia's parcels based on their legal descriptions.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2012 |
Commercial/industrial zones with special amenities.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2012 |
Commercial/industrial zones with special amenities
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Philadelphia Fire Department Fire Station Locations.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Polygon boundaries of geographic market areas in the city of Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Point geometric features representing planned and complete Green Stormwater Infrastructure (GSI).
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Philadelphia Green stormwater infrastructure public projects on parcels for the Big Green Map
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2013 |
Green City, Clean Waters is Philadelphia's 25-year plan to protect and enhance our watersheds by managing stormwater with green infrastructure. This feature class represents Green Stormwater Infrastructure (GSI) locations that are currently in the design phase or have been constructed.
Features updated: 01/25/2013
Attributes updated: 01/25/2013
Metadata updated 01/25/2013
Update Frequency - monthly
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2015 |
Planimetric Coverage containing the delineation of impervious surfaces for studying and calculating drainage runoff. This coverage shows surface features that are visible on the aerial photography, and is sometimes referred to as the landbase.
Metadata
|
Download
|
Preview
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2008 |
High resolution land cover dataset for Philadelphia. Seven land cover classes were mapped: (1) tree canopy, (2) grass/shrub, (3) bare earth, (4) water, (5) buildings, (6) roads, and (7) other paved surfaces. The minimum mapping unit for the delineation of features was set at ten square feet. The primary sources used to derive this land cover layer were 2008 Orthophotography and 2008 LiDAR LAS data. Ancillary data sources included GIS data (building footprints, road polygons, and hydrography) provided by City of Philadelphia. This land cover dataset is considered current as of 2008. Object-based image analysis techniques (OBIA) were employed to extract land cover information using the best available remotely sensed and vector GIS datasets. OBIA systems work by grouping pixels into meaningful objects based on their spectral and spatial properties, while taking into account boundaries imposed by existing vector datasets. Within the OBIA environment a rule-based expert system was designed to effectively mimic the process of manual image analysis by incorporating the elements of image interpretation (color/tone, texture, pattern, location, size, and shape) into the classification process. A series of morphological procedures were employed to insure that the end product is both accurate and cartographically pleasing. No accuracy assessment was conducted, but the dataset was subject to a thorough manual quality control. More than 30700 corrections were made to the classification.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2018 |
High resolution land cover dataset for Philadelphia,Pennsylvania. Seven land cover classes were mapped: (1) tree canopy, (2) grass/shrub, (3) bare earth, (4) water, (5) buildings, (6) roads, and (7) other paved surfaces. The primary sources used to derive this land cover layer were 2018 LiDAR data and 2017 NAIP imagery. Ancillary data sources included GIS data provided by Philadelphia,Pennsylvania or created by the UVM Spatial Analysis Laboratory. Object-based image analysis techniques (OBIA) were employed to extract land cover information using the best available remotely sensed and vector GIS datasets. OBIA systems work by grouping pixels into meaningful objects based on their spectral and spatial properties, while taking into account boundaries imposed by existing vector datasets. Within the OBIA environment a rule-based expert system was designed to effectively mimic the process of manual image analysis by incorporating the elements of image interpretation (color/tone, texture, pattern, location, size, and shape) into the classification process. A series of morphological procedures were employed to insure that the end product is both accurate and cartographically pleasing. Following the automated OBIA mapping a detailed manual review of the dataset was carried out at a scale of 1:3500 and all observable errors were corrected.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2012 |
Free Library of Philadelphia locations (branches and Central) are represented as point features. Feature Update Date: 05-2012
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2008 |
LiDAR data collection performed over the City of Philadelphia, PA in April of 2008. Products generated include Breaklines, 10ft DEM and 5ft DEM.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2010 |
LiDAR data collection performed over the City of Philadelphia, PA in April of 2010. Products generated include Breaklines, 10ft DEM and 5ft DEM.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2015 |
This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. The dataset consists of 1024 lidar point cloud LAS files. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. The data was collected at a nominal point spacing of 0.70m using Pictometry's Riegl LMS-Q680i LiDAR system over 4 mission days on April 18th, 19th, 22nd, and 25th, 2015. At the time of capture ground condiitons were leaf-off, snow free, and water was at normal levels.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2018 |
2018 LiDAR – 8ppm – Classified. LiDAR and LAS data was gathered for the City of Philadelphia in April 2018. DEMs were generated from the raw data. This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 239 sq miles total. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels. Key attribute field names and descriptions: LiDAR Classification Categories: 0 Created Not Classified 1 Unclassified 2 Ground 3 Low vegetation 4 Vegetation 5 High vegetation 6 Building 9 Water 17 Bridge Deck
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| City of Philadelphia |
| 2022 |
LiDAR and LAS data was gathered for the City of Philadelphia in April 2022. DEMs were generated from the raw data. This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 239 sq miles total. Each LAS file contains LiDAR point information, which has been calibrated, controlled, and classified. At the time of capture ground conditions were leaf-off, snow free, and water was at normal levels. For Additional Information see: https://www.pasda.psu.edu/download/phillyLiDAR/2022/Metadata_and_Reports/Lidar_Report/65221207_Philadelphia_Mapping_Report.pdf
Metadata
|
Download
| More Options...
| City of Philadelphia |
| 2015 |
Classified LiDAR LAS and Derivative Products - This dataset is lidar point cloud data covering the City of Philadelphia, PA, approximately 196 sq miles total. The dataset consists of 1024 lidar point cloud LAS files. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. The data was collected at a nominal point spacing of 0.70m using Pictometry's Riegl LMS-Q680i LiDAR system over 4 mission days on April 18th, 19th, 22nd, and 25th, 2015. At the time of capture ground condiitons were leaf-off, snow free, and water was at normal levels.
Metadata
|
Download
| More Options...
| City of Philadelphia |
| 2025 |
The Litter Index is used to compare the relative cleanliness of different areas of the city of Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
This file features polylines representing the major trails in the Philadelphia Parks & Recreation (PPR) system. It is not comprehensive of all trails thoughout the system. Other minor and rogue trails do exist and are not represented here. Data Development:Data were created by PP&R staff using historic information from the Fairmount Park Commission and Department of Recreation data archives. The data was primarily sourced using GPS technology. In certain cases data were created through orthophotography, georeferenced civil plans, and hard copy mapsTrail data is updated on a regular basis to indicate new trails, closed trails, and trails undergoing restoration or expansion.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2000 |
District boundaries of municipal legislators.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
This feature class is the administrative boundaries for the Philadelphia Police Department's districts.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
This feature class is the administrative boundaries for the Philadelphia Police Department's divisions. Divisions are subdivided into districts.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
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.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
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.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer displays their policing boundary for the Center City District (CCD) business improvement district.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This feature class contains polygons that illustrate 10 correctional facilities in the City, adminstered by Philadelphia Prisons System.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This feature class contains points that represent 10 correctional facilities in the City, administered by Philadelphia Prisons System.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Point data of all First Judicial District of PA courts.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This data was developed for cartographic use -- specifically, as reference information for the Police Athletic League.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Point locations of the Police District Headquarters in Philadelphia
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
The shapefile is the administrative boundaries for Police Sectors. Sectors are the logical
means by which police districts are subdivided. Each district is made up of 12-30 sectors.
In theory, a police patrol car is assigned to each sector and a supervisor for each 3-4 sectors.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Political subdivisions. Feature Update Date: 09-2012
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Polygon boundaries of PPR's operational districts as established by PPR's GIS staff and reviewed, revised, and approved by PPR's executive staff.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2009 |
This is a boundary file identifying Philadelphia development certified areas
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2012 |
Historic Sites on the National Register. Updated by the Planning Commission in Fall, 2010.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2012 |
Historic Sites on the Philadelphia Register. Updated by the Planning Commission in Fall, 2010.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
The location of schools in the City of Philadelphia with attribute information for address, grade level, type, and status indicating whether the school is open, proposed for closure or closed. The status field is intended to provide up to date information on school facility management conducted by all institution types.KEY ATTRIBUTE FIELDSGradeLevel – generalized description of grade levels as elementary, middle or high schoolGradeOrg – Grade Organizational Levels - estimate of grade levels range at the school, e.g., K-5Instit_Type – Institutional Type - public, private, parochial or charterActive – The current designation as active, closed or closing with expected closure date. Feature Update Date: 03-2012
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Inventory of fixed assets owned or leased by the City of Philadelphia including buildings, structures, piers, and properties (not including surplus properties). Also known as the Master Facilities database. Critical infrastructure omitted from public version.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer contains the railroad line capture from 2004 orthophotography. Sanborn’s methods for capturing railroad lines included aerial imagery and the 2004 DEM.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2004 |
This layer contains the railroad line capture from 2004 orthophotography. Sanborn’s methods for capturing railroad lines included aerial imagery and the 2004 DEM. This is one of the planimetric coverages developed as part of the aerial survey project of 1996 and updated using new aerial photography collected between 25 March 2004 and 23 April 2004.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
information on solar technology installations across Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Network of streets within City of Philadelphia with bike lanes and/or bike-friendly markings.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer was developed to aid the Bridge Division in maintaining and referencing the bridges of the City of Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer identifies the point locations of the city owned bridges that are maintained by the Bridge Division of the City of Philadelphia Streets Department.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer identifies the 286 city plan boundaries for the Surveys Division of the City of Philadelphia Streets Department.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Edge of drivable pavement, or travelway for all drivable pavement citywide, including the edge of traffic flow islands and drivable pavement within parks
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Polygons representing the area of drivable pavement citywide, as well as interior non-street polygons.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Just internal polygons with "FCODE = 9999" representing the area of drivable pavement citywide, as well as interior non-street polygons.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer delineates the six districts of the Highway Division of the City of Philadelphia Streets Department.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer delineates the six districts of the Highway Division of the City of Philadelphia Streets Department.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer delineates the fifty-six sections of the Highway Division of the City of Philadelphia Streets Department. Sections can be aggregated into districts and subdivided into subsections.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer delineates the 703 subsections of the Highway Division of the City of Philadelphia Streets Department.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer delineates the Arcs of the Polygons of the 703 subsections of the Highway Division of the City of Philadelphia Streets Department. Subsections can be aggregated into sections and districts.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Street segments listed on the Philadelphia Register of Historic Places as part of the Historic Street Paving Thematic District, as amended by the Historical Commission December 12th, 2014.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Polygons for street segments listed on the Philadelphia Register of Historic Places as part of the Historic Street Paving Thematic District, as amended by the Historical Commission December 12th, 2014.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer identifies the active intersection controls for the Street Lighting and Traffic Engineering Divisions of the City of Philadelphia Streets Department.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer identifies boundaries for City Leaf Collection Services.
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. Contact the Streets GIS unit for public consumption of the corresponding arc layer.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
To define the boundaries for Leaf Collection within the City of Philadelphia
The arc layer contains street name attributes for labeling the outside of the polygons. 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. Contact the Streets GIS unit for public consumption.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer identifies boundaries for City Leaf Collection Services.
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. Contact the Streets GIS unit for public consumption of the corresponding arc layer.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
The Litter Index is used to compare the relative cleanliness of different areas of the city of Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
To map streets with no through trucks in the City of Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
City of Philadelphia paving plan for 2015
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
The Recycling Diversion Rate is the rubbish collection tonage divided by the recycling collection tonnage by sanitation on collection day.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
The data is used to determine the day of collection 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. Contact the Streets GIS unit for public consumption of the corresponding arc layer.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Coverage of all the sanitation areas containing line, point, and polygon data used by the City of Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Coverage of all the sanitation districts containing line, point, and polygon data used by the City.
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. Contact the Streets GIS unit for public consumption of the corresponding arc layer.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Coverage of all the sanitation districts containing line, point, and polygon data used by the City.
The arc layer contains 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. Contact the Streets GIS unit for public consumption.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Used citywide as base layer for many purposes/applications. The street centerline is available for reference purposes only and does not represent exact engineering specifiactions. The Philadelphia Streets Department makes no guarantees as to the accuracy of the layer.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Created to show the City of Philadelphia's street lighting route districts.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
The street nodes layer was developed for use by agencies citywide including PWD, PCPC, Police, BRT, Health, etc.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
This layer was developed to aid the Street Lighting Division in planning, referencing, and maintaining the active street poles within the City of Philadelphia. Examples include: providing information regarding group replacement projects and any individual edits, using tables from layer for billing, and aiding cityworks.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
The Arterial layer was developed to aid various city agencies with planning, organizing, and maintaining the streets of the City of Philadelphia. These agencies include PWD, PCPC, Police, BRT, Health, etc.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer was developed to aid the Traffic Division in planning, organizing, and maintaining traffic flow within the City of Philadelphia. Examples include: the maintenance and placing of stop signs and signals and monitoring street travel direction.
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. Contact the Streets GIS unit for public consumption of the corresponding arc layer.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This is the arc file of the Traffic Districts layer. It was developed to aid the Traffic Division in planning, organizing, and maintaining traffic flow within the City of Philadelphia. Examples include: the maintenance and placing of stop signs and signals and monitoring street travel direction.
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. Contact the Streets GIS unit for public consumption.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer was developed to aid the Traffic Division in planning, organizing, and maintaining traffic flow within the City of Philadelphia. Examples include: the maintenance and placing of stop signs and signals and monitoring street travel direction.
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. Contact the Streets GIS unit for public consumption of the corresponding arc layer.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
This layer was developed to aid the Traffic Division in planning, organizing, and maintaining traffic flow within the City of Philadelphia. Examples include: the maintenance and placing of stop signs and signals and monitoring street travel direction.
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. Contact the Streets GIS unit for public consumption.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Big Belly brand waste baskets maintained/collected by the City of Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Non Big Belly waste baskets maintained/collected by the City of Philadelphia
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
The purpose of this dataset is to represent the Zip Code areas for the City of Philadelphia. The edges of Zip Codes are slightly modified for logical and cartographic purposes.
The arc layer contains 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. Contact the Streets GIS unit for public consumption.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Philadelphia. The edges of Zip Codes are slightly modified for logical and cartographic purposes.
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. Contact the Streets GIS unit for public consumption of the corresponding arc layer.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 1996 |
Planimetric Coverage containing the delineation of topographic contours. Annotation of Contour Line elevations exists. Annotation viewable at 1" = 200?
Metadata
|
Download
|
Preview
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2004 |
This dataset is composed of the entire City of Philadelphia's transparcels based on their legal descriptions. Feature update 2004
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
This point layer represents dams. The Purpose of this data is to describe the asset both locationally and via its attributes which are extensive for a GIS dataset and which are maintained. This data will serve as a platform for planning, analysis and research at PWD.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
This layer represents Green Stormwater Infrastructure Stormwater Management Practice types. Integrating Green Stormwater Infrastructure (GSI) into a highly developed area such as Philadelphia requires a decentralized and creative approach to planning and design. Various tools can be implemented to accomplish this, including stormwater planters, rain gardens and green roofs. All of these tools help to reduce runoff volume and filter pollutants by intercepting stormwater runoff before it enters the City's combined sewer system. The Purpose of this data is to describe the asset both locationally and via its attributes which are extensive for a GIS dataset and which are maintained. This data will serve as a platform for planning, analysis and research at PWD.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
This point layer contains all the wastewater and stormwater inlet locations. The Purpose of this data is to describe the asset both locationally and via its attributes which are extensive for a GIS dataset and which are maintained. This data will serve as a platform for planning, analysis and research at PWD.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
This point layer contains all the stormwater outfalls. The Purpose of this data is to describe the asset both locationally and via its attributes which are extensive for a GIS dataset and which are maintained. This data will serve as a platform for planning, analysis and research at PWD.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
The primary purpose of PWD_PARCEL layer is to calculate parcel-based stormwater charges for PWD customers under the new parcel-based stormwater billing program. The layer was created from the DOR_PARCELS layer in 2005 after it was decided that none of the other City parcel layers could meet the needs of PWD's stormwater billing program. Those needs are generally that the parcel delineations match up to what people actually own, that there is an accurate assessment of the impervious area on the parcel, and that there is owner information associated with the parcel. Over the past 5 years, PWD has made corrections based off deeds on file with DOR, BRT information, and other City records. PWD also matched up each DOR parcel to a corresponding BRT record that contained the owner information for that parcel.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
The purpose of this data is to describe the Rain Gauges both locationally and via their attributes.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Combined Sewer Service area within Philadelphia
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Green City, Clean Waters is Philadelphia's 25-year plan to protect and enhance our watersheds by managing stormwater with green infrastructure. This feature class represents Green Stormwater Infrastructure (GSI) locations that are currently in the design phase or have been constructed.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
District planning areas for Green City, Clean Waters stormwater management strategic planning.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Point geometric features representing land development projects in compliance with PWD’s Stormwater Regulations.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Philadelphia streams as mapped by Charles Ellet in 1842 and Previous study of historic streams conducted by PWD.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Philadelphia shoreline of Delaware River and Schuylkill River, digitized as mapped by Charles Ellet in 1842. Data is digitized from georeferenced map scans.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Polyline geometric features representing the center flow line of all waterways in Philadelphia's five major watersheds.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Polygon geometric features representing the waterways and impoundments in Philadelphia's five major watersheds.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Polygon feature class representing major watersheds in the Philadelphia and Region.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
Polygon feature class represtenting major watersheds in the Philadelphia Region.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Rain Barrel installation locations prior to RainCheck.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2025 |
RainCheck program installation sites
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Hydrographic polygon features included in Philadelphia Hydrology Map. This map was officially adopted by City Council as the official map of Philadelphia Watercoures Designated for Protection on September 13th, 2012. The geographic data depicts watercourses within Philadelphia County as they appear on the map and will not be edited or updated.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
Hydrographic polygon features included in Philadelphia Hydrology Map. This map was officially adopted by City Council as the official map of Philadelphia Watercoures Designated for Protection on September 13th, 2012. The geographic data depicts watercourses within Philadelphia County as they appear on the map and will not be edited or updated.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2016 |
The Zoning Code establishes a registry of community organizations to be managed by the Philadelphia City Planning Commission. The RCO system is designed to improve community notification of proposed developments and make community involvement more predictable across the city. RCOs became effective on August 22, 2012. Polygon boundaries of Registered Community Organizations (RCO) as established under Section 14-303 (12) of the City of Philadelphia Zoning Code enacted December 15, 2011 and made effective August 22, 2012. RCO’s register annually with the City Planning Commission and are notified of projects requiring Zoning Board approval or Civic Design Review. RCO boundaries may overlap as permitted by the Zoning Code.KEY ATTRIBUTE FIELDS:RCO Name: Name of Registered Community OrganizationType: Type of RCO.Expire Date: Date RCO registration with PCPC expiresExpire Year: Year RCO registration with PCPC expires Philadelphia Zoning-Related Websites:Registered Community Organizations -- http://www.phila.gov/CityPlanning/projectreviews/Pages/RegisteredCommunityOrganizationsZoning Code -- http://www.amlegal.com/library/pa/philadelphia.shtml and navigate to Title 14Zonng Map -- http://www.phila.gov/map On pop-up menu scroll down to 'Zoning'Zoning Administration Manual -- http://www.phila.gov/CityPlanning/projectreviews/Pages/Zoning.aspxDATA DEVELOPMENT:Features produced in ArcGIS Desktop using PA South Stateplane coordinates, NAD83, US Foot. Boundaries were constructed by PCPC using self-reported geographic descriptions by the RCO. Feature Update Date: 01-2013
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| City of Philadelphia |
| 2005 |
Mosaic - An orthoimage is remotely sensed image data in which displacement of features in the image caused by terrain relief and sensor orientation have been mathematically removed. Orthoimagery combines the image characteristics of a photograph with the geometric qualities of a map. This project consists of the creation of 3-band, 24 bit color digital orthophoto tiles for the 5-county, Pennsylvania portion DVRPC?s region utilizing a Leica ADS40 digital imaging system. The tiles were delivered in both GeoTIFF and MrSID MG3 formats. A GeoTIFF is a TIFF file which has geographic (or cartographic) data embedded as tags within the TIFF file. The geographic data can then be used to position the image in the correct location and geometry within a geographic information system (GIS) display. MrSID (Multi-resolution Seamless Image Database) is a proprietary, wavelet-based, image compression file format (*.sid) developed and patented by LizardTech, Inc. A 20:1 compression ratio was used for the MrSIDs. The complete data set contains 1,540 full ortho tiles in Pennsylvania State Plane South coordinate system, NAD83. The individual tiles measure 5,055' x 8,745' at a 1.0' pixel size. There is no image overlap between adjacent tiles. Counties include: Bucks, Chester, Delaware, Montgomery, and Philadelphia.
Metadata
|
Download
| More Options...
| Delaware Valley Regional Planning Commission |
| 2005 |
An elevation or topgraphic contour is a line that connects a series of points of equal elevation and is used to illustrate topography, or relief, on a map. It shows the height of ground above Mean Sea Level (M.S.L.). Numerous contour lines that are close together indicate hilly or mountainous terrain; when far apart, they represent a gentler slope. This layer consists of contours at a five foot interval for DVRPC's 9-county region and was generated from an aerial topographic survey in 2005.The Delaware Valley Regional Planning Commission's (DVRPC) 9-county region is made up of the following: Bucks, Chester, Delaware, Montgomery, and Philadelphia counties in Pennsylvania; and Burlington, Camden, Gloucester, and Mercer counties in New Jersey.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| Delaware Valley Regional Planning Commission |
| 2005 |
A spot elevation is an elevation measurement taken at a single location. It shows the height of ground above Mean Sea Level (M.S.L.). This layer consists of spot elevations for DVRPC's 9-county region and was generated from an aerial topographic survey in 2005.The Delaware Valley Regional Planning Commission's (DVRPC) 9-county region is made up of the following: Bucks, Chester, Delaware, Montgomery, and Philadelphia counties in Pennsylvania; and Burlington, Camden, Gloucester, and Mercer counties in New Jersey.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| Delaware Valley Regional Planning Commission |
| 2010 |
Mosaic - An orthoimage is remotely sensed image data in which displacement of features in the image caused by terrain relief and sensor orientation have been mathematically removed. Orthoimagery combines the image characteristics of a photograph with the geometric qualities of a map. This project consists of the creation of 3-band, 24 bit color digital orthophoto tiles for the 5-county, Pennsylvania portion DVRPC?s region utilizing a Leica ADS40 digital imaging system. The tiles were delivered in both GeoTIFF and MrSID MG3 formats. A GeoTIFF is a TIFF file which has geographic (or cartographic) data embedded as tags within the TIFF file. The geographic data can then be used to position the image in the correct location and geometry within a geographic information system (GIS) display. MrSID (Multi-resolution Seamless Image Database) is a proprietary, wavelet-based, image compression file format (*.sid) developed and patented by LizardTech, Inc. A 20:1 compression ratio was used for the MrSIDs. The complete data set contains 1,540 full ortho tiles in Pennsylvania State Plane South coordinate system, NAD83. The individual tiles measure 5,055' x 8,745' at a 1.0' pixel size. There is no image overlap between adjacent tiles. Counties include: Bucks, Chester, Delaware, Montgomery, and Philadelphia.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| Delaware Valley Regional Planning Commission |
| 2020 |
This orthoimagery consists of 1-foot pixel resolution, 3-band, natural color county mosaics in JPEG 2000 format covering the Delaware Valley Regional Planning Commission’s (DVRPC) 9-county region (Bucks, Chester, Delaware, Montgomery, and Philadelphia counties in Pennsylvania; and Burlington, Camden, Gloucester, and Mercer counties in New Jersey). This orthoimagery was acquired in the late winter/early spring of 2020. An orthoimage is remotely sensed image data in which displacement of features in the image caused by terrain relief and sensor orientation have been mathematically removed. Orthoimagery combines the image characteristics of a photograph with the geometric qualities of a map.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| Delaware Valley Regional Planning Commission |
| 1959 - 1995 |
Prior to the year 2000, DVRPC’s aerial imagery consisted of mylar aerial photo
enlargements or “atlas sheets”. These atlas sheets were produced from 9x9" aerial
photos. The imagery dates from the years 1959, 1965, 1970, 1975, 1980, 1985, 1990,
& 1995. The 1959s and 1965s primarily cover the urbanized portion of
the DVRPC region (the DVRPC region is made up of nine counties: Bucks, Chester,
Delaware, Montgomery, and Philadelphia in Pennsylvania; Burlington, Camden,
Gloucester, and Mercer in New Jersey). Subsequent years provide full coverage of the
region, minus the occasional missing scan.
In order to increase the efficiency of using the historical aerial imagery, the sheets were
scanned into TIFF (Tagged Image File Format) files. Each TIFF file ranges between 35-
40MB in size. Unlike DVRPC’s more recent aerial imagery (2000 and later), the
historical aerials are not “orthorectified” or “orthocorrected”. In other words, they are
simply aerial images with no spatial reference or uniform scale. Through the process of
georeferencing, the scanned images can be assigned a spatial reference which will
enable them to be used more readily in a GIS environment. That said, georeferencing is
not orthorectifying or orthocorrecting. What it does allow is for the scan to be displayed
relative to other spatially referenced GIS layers. A georeferenced scan does not have
the properties of an actual orthoimage. Whereas an orthoimage can be used for making
accurate measurements, a georeferenced image cannot, as it does not have the spatial
accuracy and uniform scale of an orthoimage.
ftp://ftp.pasda.psu.edu/pub/pasda/dvrpc/DVRPC_Historical_Aerials/Indexes/DVRPC_Historical_Aerial_Index_Maps.pdf
https://www.dvrpc.org/webmaps/TileIndex/
Metadata
|
Download
| More Options...
| Delaware Valley Regional Planning Commission |
| 2020 |
A 1% Annual Chance Flood Depth Grid represents the height of a 100 year flood surface elevation above ground or bottom of a stream channel measured in feet. The values are captured per cell of a defined area. The cell size for 1% Annual Chance Flood Depth Grids is variable. It is calculated by subtracting the height of the ground surface elevation from the surface height of the 1% annual chance flood. A Flood Depth Grid can assist a community in understanding, communicating, and relaying the variability and severity of flooding in a mapped floodplain.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| Federal Emergency Management Agency |
| 2025 |
The FIRM is the basis for floodplain management, mitigation, and insurance activities for the National Flood Insurance Program (NFIP). Insurance applications include enforcement of the mandatory purchase requirement of the Flood Disaster Protection Act, which "... requires the purchase of flood insurance by property owners who are being assisted by Federal programs or by Federally supervised, regulated or insured agencies or institutions in the acquisition or improvement of land facilities located or to be located in identified areas having special flood hazards," Section 2 (b) (4) of the Flood Disaster Protection Act of 1973. In addition to the identification of Special Flood Hazard Areas (SFHAs), the risk zones shown on the FIRMs are the basis for the establishment of premium rates for flood coverage offered through the NFIP. The DFIRM Database presents the flood risk information depicted on the FIRM in a digital format suitable for use in electronic mapping applications. The DFIRM database is a subset of the Digital FIS database that serves to archive the information collected during the FIS. The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting
data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance
flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM
Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps
(FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data,
where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA).
The file is georeferenced to earth's surface using the UTM projection and coordinate system.The
specifications for the horizontal control of DFIRM data files are consistent with those required for
mapping at a scale of 1:12,000.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
| More Options...
| Federal Emergency Management Agency |
| 2005 |
various layers clipped to counties - The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting
data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance
flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The DFIRM
Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps
(FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data,
where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA).
The file is georeferenced to earth's surface using the UTM projection and coordinate system. The
specifications for the horizontal control of DFIRM data files are consistent with those required for
mapping at a scale of 1:12,000.
Metadata
|
Download
| More Options...
| Federal Emergency Management Agency |
| 2019 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2024 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2017 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2015 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2016 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2023 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2021 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2014 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2021 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2014 |
The National Flood Hazard Layer (NFHL) data incorporates all Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters Of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis. The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual-chance flood event, and areas of minimal flood risk. The FIRM Database is derived from Flood Insurance Studies (FISs), previously published FIRMs, flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by FEMA. The NFHL is available as State or US Territory data sets. Each State or Territory data set consists of all FIRM Databases and corresponding LOMRs available on the publication date of the data set. The specification for the horizontal control of FIRM Databases is consistent with those required for mapping at a scale of 1:12,000. This file is georeferenced to the Earth's surface using the Geographic Coordinate System (GCS) and North American Dataum of 1983 (NSRS-2007).
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Federal Emergency Management Agency |
| 2012 |
During 2011 - 2012, the Pennsylvania Department of Environmental Protection (PA DEP), as part of the Coastal Zone Management (CZM) Program and Pennsylvania Stream ReLeaf, funded Heritage Conservancy to develop a rapid assessment method to identify and map sections of stream lacking riparian forest buffers. Montgomery County Planning Commission provided in-kind funding for the project as well as completing the assessment portion in Montgomery Count. Heritage Conservancy completed the assessment for the areas in Bucks County and Philadelphia County. Both organizations then mapped waterways lacking riparian forest buffers. The assessment included the main stem, tributaries and small headwater streams. The 1' pixel resolution 2010 aerials from DVRPC served as the basis for the riparian conditions along the waterways. The forest buffer conditions were classified and digitized into a Geographic Information System (GIS). This dataset is an assessment of the same area completed back in 200-2004. The same methodology of creating 50 foot buffers from the edge of water to assess the tree cover in this area was used. The stream centerline is used to represent the classification of whether one side, both sides, or neither side has tree cover. In addition to the three categories from the previous assessment, the category of culvert was added to incorporate areas where there was not an opportunity for tree cover.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Heritage Conservancy |
| 2016 |
Natural Lands Trust works proactively to protect the natural heritage of the Philadelphia region for today and generations to come. This file contains various
layers and maps for Schuylkill Action Network - Land Prioritization Strategy Model Included maps are:
Composite Resource Protection Prioritization, Composite Resource Protection Prioritization 3 color, DVRPC Future Development Year 2020-2030, Future Development on High Priority CRP Areas, NLT SC Conservation Resource Prioritization, PWD Source Water Model.
Also included are the GIS data layers that support these maps.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Natural Lands Trust |
| 2007 |
Natural Lands Trust works proactively to protect the natural heritage of the Philadelphia region for today and generations to come. This file contains various
layers and maps for Schuylkill Action Network - Land Prioritization Strategy Model Included maps are:
Composite Resource Protection Prioritization, Composite Resource Protection Prioritization 3 color, DVRPC Future Development Year 2020-2030, Future Development on High Priority CRP Areas, NLT SC Conservation Resource Prioritization, PWD Source Water Model.
Also included are the GIS data layers that support these maps.
Metadata
|
Download
| More Options...
| Natural Lands Trust |
| 2021 |
Counties include: Adams, Berks, Bucks, Carbon, Chester, Columbia, Cumberland, Dauphin, Delaware, Franklin, Lackawanna, Lancaster, Lebanon, Lehigh, Monroe, Montgomery, Northampton, Northumberland, Perry, Philadelphia, Pike, Schuylkill, Susquehanna, Wayne, Wyoming, York. Product: This orthoimagery data set includes 0.5 foot 8-bit 4-band (RGBN) digital orthoimage mosaics in GeoTIFF, Mr. SID, and JPEG 2000 (JP2) format. Dataset Description: The PEMA 2020-2021 0.5-Foot Orthoimagery project called for the planning, acquisition, processing, and derivative products of imagery data to be collected at a ground sample distance (GSD) of 0.5 foot. Project specifications are based on the American Society of Photogrammetry and Remote Sensing (ASPRS) standards. The data were developed based on a horizontal projection/datum of NAD 1983 HARN StatePlane Pennsylvania Feet, Foot US.. Ground Conditions: Imagery was collected in winter 2020 and 2021, while no snow was on the ground and rivers were at or below normal levels. In order to post process the imagery data to meet task order specifications and meet ASPRS horizontal accuracy guidelines, NV5 Geospatial utilized a total of 496 ground control points to assess the horizontal accuracy of the data.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| Pennsylvania Emergency Management Agency |
| 2021 |
Counties include: Adams, Berks, Bucks, Carbon, Chester, Columbia, Cumberland, Dauphin, Delaware, Franklin, Lackawanna, Lancaster, Lebanon, Lehigh, Monroe, Montgomery, Northampton, Northumberland, Perry, Philadelphia, Pike, Schuylkill, Susquehanna, Wayne, Wyoming, York. Product: This orthoimagery data set includes 0.5 foot 8-bit 4-band (RGBN) digital orthoimage mosaics in GeoTIFF, Mr. SID, and JPEG 2000 (JP2) format. Dataset Description: The PEMA 2020-2021 0.5-Foot Orthoimagery project called for the planning, acquisition, processing, and derivative products of imagery data to be collected at a ground sample distance (GSD) of 0.5 foot. Project specifications are based on the American Society of Photogrammetry and Remote Sensing (ASPRS) standards. The data were developed based on a horizontal projection/datum of NAD 1983 HARN StatePlane Pennsylvania Feet, Foot US.. Ground Conditions: Imagery was collected in winter 2020 and 2021, while no snow was on the ground and rivers were at or below normal levels. In order to post process the imagery data to meet task order specifications and meet ASPRS horizontal accuracy guidelines, NV5 Geospatial utilized a total of 496 ground control points to assess the horizontal accuracy of the data.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| Pennsylvania Emergency Management Agency |
| 2021 |
Counties include: Adams, Berks, Bucks, Carbon, Chester, Columbia, Cumberland, Dauphin, Delaware, Franklin, Lackawanna, Lancaster, Lebanon, Lehigh, Monroe, Montgomery, Northampton, Northumberland, Perry, Philadelphia, Pike, Schuylkill, Susquehanna, Wayne, Wyoming, York. Product: This orthoimagery data set includes 0.5 foot 8-bit 4-band (RGBN) digital orthoimage mosaics in GeoTIFF, Mr. SID, and JPEG 2000 (JP2) format. Dataset Description: The PEMA 2020-2021 0.5-Foot Orthoimagery project called for the planning, acquisition, processing, and derivative products of imagery data to be collected at a ground sample distance (GSD) of 0.5 foot. Project specifications are based on the American Society of Photogrammetry and Remote Sensing (ASPRS) standards. The data were developed based on a horizontal projection/datum of NAD 1983 HARN StatePlane Pennsylvania Feet, Foot US.. Ground Conditions: Imagery was collected in winter 2020 and 2021, while no snow was on the ground and rivers were at or below normal levels. In order to post process the imagery data to meet task order specifications and meet ASPRS horizontal accuracy guidelines, NV5 Geospatial utilized a total of 496 ground control points to assess the horizontal accuracy of the data.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| Pennsylvania Emergency Management Agency |
| 2021 |
Counties include: Adams, Berks, Bucks, Carbon, Chester, Columbia, Cumberland, Dauphin, Delaware, Franklin, Lackawanna, Lancaster, Lebanon, Lehigh, Monroe, Montgomery, Northampton, Northumberland, Perry, Philadelphia, Pike, Schuylkill, Susquehanna, Wayne, Wyoming, York. Product: This orthoimagery data set includes 0.5 foot 8-bit 4-band (RGBN) digital orthoimage mosaics in GeoTIFF, Mr. SID, and JPEG 2000 (JP2) format. Dataset Description: The PEMA 2020-2021 0.5-Foot Orthoimagery project called for the planning, acquisition, processing, and derivative products of imagery data to be collected at a ground sample distance (GSD) of 0.5 foot. Project specifications are based on the American Society of Photogrammetry and Remote Sensing (ASPRS) standards. The data were developed based on a horizontal projection/datum of NAD 1983 HARN StatePlane Pennsylvania Feet, Foot US.. Ground Conditions: Imagery was collected in winter 2020 and 2021, while no snow was on the ground and rivers were at or below normal levels. In order to post process the imagery data to meet task order specifications and meet ASPRS horizontal accuracy guidelines, NV5 Geospatial utilized a total of 496 ground control points to assess the horizontal accuracy of the data.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| Pennsylvania Emergency Management Agency |
| 2021 |
Counties include: Adams, Berks, Bucks, Carbon, Chester, Columbia, Cumberland, Dauphin, Delaware, Franklin, Lackawanna, Lancaster, Lebanon, Lehigh, Monroe, Montgomery, Northampton, Northumberland, Perry, Philadelphia, Pike, Schuylkill, Susquehanna, Wayne, Wyoming, York. Product: This orthoimagery data set includes 0.5 foot 8-bit 4-band (RGBN) digital orthoimage mosaics in GeoTIFF, Mr. SID, and JPEG 2000 (JP2) format. Dataset Description: The PEMA 2020-2021 0.5-Foot Orthoimagery project called for the planning, acquisition, processing, and derivative products of imagery data to be collected at a ground sample distance (GSD) of 0.5 foot. Project specifications are based on the American Society of Photogrammetry and Remote Sensing (ASPRS) standards. The data were developed based on a horizontal projection/datum of NAD 1983 HARN StatePlane Pennsylvania Feet, Foot US.. Ground Conditions: Imagery was collected in winter 2020 and 2021, while no snow was on the ground and rivers were at or below normal levels. In order to post process the imagery data to meet task order specifications and meet ASPRS horizontal accuracy guidelines, NV5 Geospatial utilized a total of 496 ground control points to assess the horizontal accuracy of the data.
Metadata
|
Download
|
Preview
|
KMZ
|
Add to ArcMap:
Image
| More Options...
| Pennsylvania Emergency Management Agency |
| 2021 |
Special regulation areas - are counties that may limit the type of arms and ammunition permitted to be used for hunting in these areas. Special Regulation Areas include:In western Pennsylvania, all of Allegheny County.In Southeastern Pennsylvania, all of Bucks, Chester, Delaware, Montgomery and Philadelphia counties, and also during special controlled hunts at Ridley Creek and Tyler state parks.
Metadata
|
Download
|
Preview
|
KMZ
|
Spreadsheet
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| Pennsylvania Game Commission |
| 2018 |
Building Footprints from Individual Counties for the State of Pennsylvania. This dataset is incomplete and Building Footprints will be added as available. Building Footprints Include: Allegheny, Lancaster, Philadelphia
Metadata
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| The Pennsylvania State University |
| 2024 |
This data set is a digital soil survey and generally is the most
detailed level of soil geographic data developed by the National
Cooperative Soil Survey. The information was prepared by digitizing
maps, by compiling information onto a planimetric correct base
and digitizing, or by revising digitized maps using remotely
sensed and other information.
This data set consists of georeferenced digital map data and
computerized attribute data. The map data are in a soil survey area
extent format and include a detailed, field verified inventory
of soils and miscellaneous areas that normally occur in a repeatable
pattern on the landscape and that can be cartographically shown at
the scale mapped. A special soil features layer (point and line
features) is optional. This layer displays the location of features
too small to delineate at the mapping scale, but they are large
enough and contrasting enough to significantly influence use and
management. The soil map units are linked to attributes in the
National Soil Information System relational database, which gives
the proportionate extent of the component soils and their properties.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| U S Department of Agriculture |
| 2024 |
This data set is a digital soil survey and generally is the most
detailed level of soil geographic data developed by the National
Cooperative Soil Survey. The information was prepared by digitizing
maps, by compiling information onto a planimetric correct base
and digitizing, or by revising digitized maps using remotely
sensed and other information.
This data set consists of georeferenced digital map data and
computerized attribute data. The map data are in a soil survey area
extent format and include a detailed, field verified inventory
of soils and miscellaneous areas that normally occur in a repeatable
pattern on the landscape and that can be cartographically shown at
the scale mapped. A special soil features layer (point and line
features) is optional. This layer displays the location of features
too small to delineate at the mapping scale, but they are large
enough and contrasting enough to significantly influence use and
management. The soil map units are linked to attributes in the
National Soil Information System relational database, which gives
the proportionate extent of the component soils and their properties.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| U S Department of Agriculture |
| 2024 |
This data set is a digital soil survey and generally is the most
detailed level of soil geographic data developed by the National
Cooperative Soil Survey. The information was prepared by digitizing
maps, by compiling information onto a planimetric correct base
and digitizing, or by revising digitized maps using remotely
sensed and other information.
This data set consists of georeferenced digital map data and
computerized attribute data. The map data are in a soil survey area
extent format and include a detailed, field verified inventory
of soils and miscellaneous areas that normally occur in a repeatable
pattern on the landscape and that can be cartographically shown at
the scale mapped. A special soil features layer (point and line
features) is optional. This layer displays the location of features
too small to delineate at the mapping scale, but they are large
enough and contrasting enough to significantly influence use and
management. The soil map units are linked to attributes in the
National Soil Information System relational database, which gives
the proportionate extent of the component soils and their properties.
Metadata
|
Download
|
Preview
|
KMZ
|
GeoJSON
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| U S Department of Agriculture |
| 2000 |
A scope of work was developed in response to a request by the U. S. Army Corps
of Engineers, Philadelphia District. The request was to perform a topographic
change grid analysis for the Frankford 7.5-minute quadrangle, 1:24,000-scale
topographic map, which includes the Wissinoming neighborhood, and the Germantown 7.5-minute quadrangle, which includes the Logan and Feltonville neighborhoods of the City of Philadelphia. The following tasks were performed under this scope of work: A GPS-corrected GIS grid analysis for each quadrangle was completed and is accompanied by documentation that describes procedures and provides metadata of the informational content of the GIS. A high-resolution global positioning system (GPS) survey was conducted for each topographic quadrangle in order to evaluate and correct systematic discrepancies in elevation between the modern and historic surveys. Prior to release, the fully documented GPS-corrected GIS grid analysis for each quadrangle was reviewed for (1) com-pleteness of documentation and for (2) appropriate analysis and discussion of uncertainties.
The following report is in fulfillment of the tasks outlined in this scope of work and was performed by the U. S. Geological Survey for the U. S. Army Corps of Engineers, Philadelphia District under MIPR agreement number: W25PHS93358288.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| U S Geological Survey |
| 2000 |
A scope of work was developed in response to a request by the U. S. Army Corps
of Engineers, Philadelphia District. The request was to perform a topographic
change grid analysis for the Frankford 7.5-minute quadrangle, 1:24,000-scale
topographic map, which includes the Wissinoming neighborhood, and the Germantown 7.5-minute quadrangle, which includes the Logan and Feltonville neighborhoods of the City of Philadelphia. The following tasks were performed under this scope of work: A GPS-corrected GIS grid analysis for each quadrangle was completed and is accompanied by documentation that describes procedures and provides metadata of the informational content of the GIS. A high-resolution global positioning system (GPS) survey was conducted for each topographic quadrangle in order to evaluate and correct systematic discrepancies in elevation between the modern and historic surveys. Prior to release, the fully documented GPS-corrected GIS grid analysis for each quadrangle was reviewed for (1) com-pleteness of documentation and for (2) appropriate analysis and discussion of uncertainties.
The following report is in fulfillment of the tasks outlined in this scope of work and was performed by the U. S. Geological Survey for the U. S. Army Corps of Engineers, Philadelphia District under MIPR agreement number: W25PHS93358288.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| U S Geological Survey |
| 2000 |
A scope of work was developed in response to a request by the U. S. Army Corps
of Engineers, Philadelphia District. The request was to perform a topographic
change grid analysis for the Frankford 7.5-minute quadrangle, 1:24,000-scale
topographic map, which includes the Wissinoming neighborhood, and the Germantown 7.5-minute quadrangle, which includes the Logan and Feltonville neighborhoods of the City of Philadelphia. The following tasks were performed under this scope of work: A GPS-corrected GIS grid analysis for each quadrangle was completed and is accompanied by documentation that describes procedures and provides metadata of the informational content of the GIS. A high-resolution global positioning system (GPS) survey was conducted for each topographic quadrangle in order to evaluate and correct systematic discrepancies in elevation between the modern and historic surveys. Prior to release, the fully documented GPS-corrected GIS grid analysis for each quadrangle was reviewed for (1) com-pleteness of documentation and for (2) appropriate analysis and discussion of uncertainties.
The following report is in fulfillment of the tasks outlined in this scope of work and was performed by the U. S. Geological Survey for the U. S. Army Corps of Engineers, Philadelphia District under MIPR agreement number: W25PHS93358288.
Metadata
|
Download
|
Preview
|
Add to ArcMap:
Image
or
Feature
|
Add to ArcGIS Pro
| More Options...
| U S Geological Survey |