Trouble downloading or have questions about this City dataset? Visit the OpenDataPhilly Discussion Group
Data is from 2015 and does not currently receive any updates.
This dataset combines data from various City of Philadelphia departments in order to create a set of supporting documentation for bike network routing. Datasets include Bike Network, Connector Streets, Regional Routes, and Trails and Side paths. Each dataset has its own parameters, dates, and sources, and individuals are encouraged to view the metadata associated with this data. This dataset is experimental and remains a work in progress. Please use with caution.
Line data includes the network of both streets with bike lanes and streets considered bicycle-friendly. Also known as the bicycle network.
This is a point dataset of bus transit shelters installed and maintained by the City of Philadelphia, in partnership with Intersection Media.
Map of the existing and planning segments of the regional trail network
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.
This dataset includes checks and ACH (direct deposit) payments made by the City during the fiscal year, which runs from July 1st 2016 through June 31st 2017.
Please see full metadata to learn more detail about important notes to this data, such as:
The Complete Streets Layer combines the Street Types developed by the City Planning Commission’s Pedestrian and Bicycle Plan, with the Complete Streets Handbook of the Mayor’s Office of Transportation and Utilities. It allows developers, planners, engineers and community groups to easily identify their street type and associated pedestrian, bicycle and other travel priorities to be included during the planning of new streets or large developments.
This data includes curb edges with cartways and curb edges without cartways to represent travelways within the City of Philadelphia and it aids in placement of street centerline.
Polygon description of use rights for ingress/egress, driveways, alleyways, utilities, drainage and subsurface areas.
Traffic Count Viewer is an online mapping application, which users can use to explore traffic count reports in different locations within the Delaware Valley, including Philadelphia. Users search by location (address, city, zip code, or place name) to view point features on the interactive mapping visualization of traffic records. Clicking on a point of interest or grouping multiple points on the map yields traffic count information tables, which includes: Date of Counnt ; DVRPC File # ; Type ; Annual Average Daily Traffic (AADT) ; Municipality ; Route Number ; Road Name ; Count Direction ; and From/To Locations, as well as a link to the detailed (hourly) report. Data tables are exportable as .CSV and detailed reports are available for export in multiple formats (including basic .doc and .rtf outputs.) Traffic count data is collected by the Delaware Valley Regional Planning Commission and other agencies.
Choices & Voices version 2.1 allows you to participate in developing a vision for growth and development in Greater Philadelphia between now and 2040. Identify your preferred development pattern, and then select regional funding levels and major transportation projects that you would like to see happen over the next 27 years. This application is crowdsourced, so you’ll be able to compare your scenario to the vision created by all other participants.
This version of Choices & Voices has been updated to correspond with the recently amended Connections 2040 Plan for Greater Philadelphia. This amendment reflects transportation increased funding levels in Pennsylvania from the passage of Act 89 of 2013.
Choices & Voices was a winner of the U.S. DOT 2014 Data Innovation Challenge.
Contains an inventory of all know road bikeable trails in Philadelphia, as compiled for the 2013 Philadelphia Trail Master Plan. This feature class was used to create maps, graphics, and inform analysis as part of the Philadelphia Trail Master Plan, adopted by the Planning Commission in July 2013. Please refer to the Philadelphia Trail Master Plan for further detail on the descriptions of the attributes described in the metadata. Inventory includes both existing trails and existing sidepaths, as defined in the metadata. Sidepaths are designated by the Streets Department with advisory approval from the Planning Commission, with the exception of side paths on Philadelphia Parks and Recreation property.
Please note that the dataset below is a snapshot of data captured at one time and does not receive regular updates.
The Highway Districts dataset shows the boundaries of highway districts used for managing maintenance of roads.
To map older streets with historical value in the City of Philadelphia.
Data relating to the Indego BikeShare program, including station locations and the number of available bikes. More information about the program is available at: https://www.rideindego.com/about/data/
Data relating to the Indego BikeShare program, including station locations and the number of available bikes. More information about the program is available at: https://www.rideindego.com/about/data/
The Indego bikeshare service offers an API but it only shows current stations and usage; historical data is not published. Randy Olson has developed a longitudinal data set that is updated hourly since June 30, 2015. Data columns include: capture_datetime, name, kioskID, coordinates (lat/long), address, zip code, bikes available, docks available, total docks, public status, and others.
To map streets with no through trucks in the City of Philadelphia.
Explore Philadelphia’s most popular open geographic data in one easy to use mapping tool. This tool was built by the City’s Office of Innovation and Technology’s CityGeo team.
Locations of Pennsylvania At-Grade Intersections as maintained by the PA Dept of Transportation
Bridge locations within Pennsylvania
Locations and attributes of drainage pipe structures that intersect with a state route
Point locations of Pennsylvania Interstate mile markers
Public roads, including those not maintained by the PA Dept. of Transportation.
Boundaries of municipalities within Pennsylvania as delineated for the PennDOT Type 10 general highway maps. Additional information comes from the Pennsylvania Bureau of Municipal Services. This layer contains all classifications of municipality including first and second class townships, boroughs, cities and the town.
Rails Lines within Pennsylvania
Pennsylvania Railroad Crossing Points of Intersection
School districts as defined by Pennsylvania Department of Transportation, Bureau of Planning and Research, Cartographic Information Division
State-owned and maintained public roads within Pennsylvania as extracted from the PENNDOT Roadway Management System (RMS). Includes fields describing pavement type, traffic volumes and other information. The Administrative version is used for reporting purposeslike the federal aid system and federal functional classification.
Traffic volumes; measured and calculated amounts of vehicle traffic that travel the sections of road.
PennDOT Transportation Improvement Projects as derived from the Multi-Modal Project Management System (MPMS).
An online parking facility information and look-up tool developed by the Philadelphia Parking Authority (PPA) for the Center City and University City areas. Users browse preselected popular destinations/neighborhoods or enter an address in either areas to explore corresponding parking entries, represented as different feature points on a map. Specific parking information includes PPA facilities, private facilities, and popular destination markers. Clicking on each location-point, yields information about different rates, type of facility (garage/lot), total spaces, distance to entered destination, and operator name.
Please note that this is a very large dataset. To see all violations, download all datasets for all years.
If you are comfortable with APIs, you can also use the API links to access this data. You can learn more about how to use the API at Carto’s SQL API site and in the Carto guide in the section on making calls to the API.
City of Philadelphia paving plan for 2015 that displays paving project funding, City - Local Funding, City - Federal Funding, and State Funding.
Reported crashes in the city of Philadelphia from 2008-2012. Original data source is PennDOT, the data was geocoded and flag table merged with crash locations to provide a more complete dataset with incident information.
Freight Data Portal for the Delaware Valley.
The Delaware Valley is a premier freight transportation gateway. It possesses one of the world’s busiest freshwater ports; rail freight service from two large Class I railroads and 12 smaller short lines; an airport with expanding international cargo services; an excellent highway and connector network; and numerous rail and port intermodal terminals.
The performance of this extraordinary network helps promote and support a thriving economy. PhillyFreightFinder is a resource for exploring and tracking the Philadelphia-Camden-Trenton regional freight network.
Open Freight App is a project by the Delaware Valley Regional Planning Commission (DVRPC) to share with regional and national transportation planning partners the framework that is the basis for the PhillyFreightFinder web mapping and data application. Through this effort, DVRPC hopes that county planning agencies, metropolitan planning organizations and state departments of transportation, and economic development agencies can leverage this framework to further their efforts in making freight transportation data public. By utilizing the Open Freight App framework, rather than building from scratch, planning agencies can focus their time and resources on the development of data sets that can serve to improve the access to information on freight facilities and their role in economic development and transportation across the country. Open Freight App would serve as a self-hosted solution to offer these datasets to other planners, economic developers, public officials, decision-makers and the general public.
PhillyHistory.org is an online database of historic photographs and maps from the Philadelphia City Archives and four additional area institutions. A project of the City of Philadelphia Department of Records, the database contains images dating back to the 1850s and can be searched by geographic criteria such as address, intersection, place name, and neighborhood as well as keyword, date, collection, topics, and other criteria. Images and maps are associated with a location using the database’s geocoding feature. Users can create a free account to save images, bookmark searches, and submit error reports.
The City of Philadelphia’s ArcGIS Online organization that hosts references to open data releases as feature services and AGO map applications shared with the public. Maintained by the City’s Office of Innovation and Technology’s CityGeo team.
The purpose of this dataset is to report inefficiencies in SEPTA’s regional rail train scheduling for use by SEPTA employees and casual train riders. It also documents late trains, which you can use to excuse work lateness.
Boat launches across the city are places where boats (kayaks, canoes, and or motorboats) can be launched onto the Schuylkill River or Delaware River. This dataset identifies the boat launches/ramps located on PPR property or boat launches PPR administers directly.
Trouble downloading or have questions about this City dataset? Visit the OpenDataPhilly Discussion Group
Provides access to SEPTA travel alerts via an API. All travel alerts can be viewed at https://www3.septa.org/api/Alerts/.
To retrieve travel alerts for a specific route or line, add the parameter: route/line name to the URL.
Example: https://www3.septa.org/api/Alerts/index.php?routes=bus_route_33
The API endpoint at get_alert_data.php provides more verbose messages for either the whole system or a single route
Example: https://www3.septa.org/api/Alerts/get_alert_data.php?route_id=bus_route_33
Provides access to current SEPTA bus detours via an API. All detours for all routes can be accessed at https://www3.septa.org/api/BusDetours/.
To specify detours for a specific route, add the parameter: route number to the URL.
Example: https://www3.septa.org/api/BusDetours/23
Visual dashboards that describe ridership and performance metrics.
Returns a list of all elevator outages. The API does not require any paramters.
SEPTA publishes real-time alerts, updates, and vehicle positions as GTFS-RT data feeds in protocol buffer (protobuf) format. A human-readable version is available from each end-point using /print.php but will only have the most recent 5 records.
SEPTA schedule and location information in GTFS format. Additional informatoion can be found on GitHub (https://github.com/septadev/GTFS/) or Google group (https://groups.google.com/forum/#!forum/septadev)
The SEPTA Real-time Map combines the results of several APIs, including bus, trolley and regional rail locations and alerts.
The TrainView API returns information on all current regional rail trains.
The NextToArrive API returns departure and arrival times between two different stations. Please refer to the Regional Rail Inputs page (see below) to see all valid inputs. <ul> <li>req1 is the starting Regional Rail station</li> <li>req2 is the ending Regional Rail station</li> <li>req3 is an integer with the number of results to show</li> </ul>
The Arrival/Departure API returns a list/queue of regional rail trains to arrive at a station in two/both directions. The direction is demarcated as either Northbound or Southbound. The directions are obviously not geographical references, but rather a reference to the old Reading and Pennsy Railroads. The key to understanding the direction is by using Suburban Station as a starting point: Any trains that move eastbound towards Market East are all considered Northbound; trains going from suburban t o 30th St are all Southbound. The path field describes more accurately the path of travel along various branches. Every regional stop is a valid parameter. Please refer to the Regional Rail Inputs page (see below) to see all valid inputs.
Stop summary files represent average daily ridership at the stop level over the course of the relevant period. Trolley ridership data was generated using automatic passenger counters (APCs). Bus data is calculated from a variety of sources depending on the route and year. The bus data files represent average daily fall ridership from 2014 – present. Accurate weekend bus data was not available until 2017 at which point SEPTA had more widespread APC coverage. No bus data is available for Fall 2020 due to a malware attack. APC bus data was also not available for articulated vehicles and the Boulevard Direct from August 2020 through February 2022 due to the malware attack.
Geographic data for SEPTA routes, stops, and locations is available from both APIs and GIS data.
Provides API access to SEPTA regional rail, bus, and trolley schedules.
Regional rail schedules are accessed by train number. Train numbers are in the GTFS files or the route stop API.
Example: https://www3.septa.org/api/RRSchedules/index.php?req1=458 returns rail schedule for the Aiport Line.
Bus and trolley schedules are accessed by stop ID.
Example: https://www3.septa.org/api/BusSchedules/index.php?stop_id=12345
returns scheduled stops for Ridge Av & Walnut Ln
SEPTA SMS Transit enables users to request scheduled trip information via text message. Users subscribe to the service via text. After setting up an account, users can receive schedule information by texting the Stop ID number for a bus, trolley, or subway stop to 41411. They will receive a return text with information on the four next scheduled trips from that stop. Users can include the specific route designation in the text to receive information on a certain route if the stop serves multiple routes. In addition to using the SMS, there is also a simulator which people can use to experiment at no cost.
Finally, the SMS data can be accessed from an API. The data returned by the API is currently text format, separated. The API can be accessed in the format: https://www3.septa.org/sms/var1/var2/var3/var4/var5
[var1] = stop id
[var2] = route id OR i/o for inbound/outbound
[var3] = i/o for inbound/outbound only if route id is supplied
[var4] = returns schedule times on or after specified date, format: MM/DD/YYYY. Defaults to current day.
[var5] = returns schedule times on or after specified time, format: HH:mm:ss. Defaults to current time.
Stops fall into one of three categories, here is an explanation with some sample links:
TransitView provides real-time information about SEPTA buses and trolleys. TransitViewAll returns all current bus and trolley locations. TrnasitView accepts a route number and retuns locations for all vehicles on that route.
Example: https://www3.septa.org/api/TransitView/index.php?route=33 returns all vehicles on bus route 33
Trip planner for finding SEPTA routes and times between an origin and destination.
The SEPTA Real Time Locator on Skookul Philadelphia provides real time access to data on the current location of SEPTA buses, trains, and trolleys. Data can be accessed via mobile, desktop, and laptop devices. Users can bookmark specific data requests such as a bus route (http://skookul.com/transportation/#bus-9) or train route (http://skookul.com/transportation/#train-airport).
This dataset contains a modified version of street centerlines used for spatial analysis to derive the High Injury Network (HIN). This version has been arrived at, using steps described in the methodology for High Injury Network. See the Metadata link for an attached PDF describing the methodology.
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. Associated tables can be found here: https://www.opendataphilly.org/datasets/street-place-names
https://www.opendataphilly.org/datasets/street-name-alias-list
This is an API for querying street lane closures made by PGW for maintenance and repair of the gas network. There are two methods on the SOAP endpoint, one for retrieving a list of historical closures for a period of dates (earliest time period is December 2009) and one for returning details about specific current closures. Both methods return data for the Project Number, Address, EUN Number, Construction Start/End date, reason for the work, degree of closure, and contact information for the responsible party at PGW.
Street Centerline Arcs with link to legal cards, which are a collection of cards containing the official record of the legal description and drawings of city streets.
The street nodes layer was developed for use by agencies citywide including PWD, PCPC, Police, BRT, Health, etc.
A listing of “places” and their corresponding addresses to be used for geocoding.
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.
This interactive mapping application displays current/future street closures, trash/recycling days, street sweeping plans, snow plowing info (during a snow event) and paving plans.
Street segments containing train tracks.
Point-based dataset showing the approximate locations where Traffic Calming Devices exist in the street to reduce speeding of motor vehicles. Traffic Calming Devices examples are speed cushions, speed humps, and speed tables. These devices could be made of asphalt or rubber materials.
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 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.
This data set contains crash data for the years 2007-2020 from the Pennsylvania Department of Transportation (Penn DOT). This is a subset of the annual Crash Data compiled and released by Penn DOT for the entire state.
This data contains the High Injury Network. It is derived using spatial data analysis of crash data for years 2012-2016 from Pennsylvania Department of Transportation.
An online application, which enables users to view calculated walkability ranks and related neighborhood metrics, such as proximity of nearby businesses, service providers, and recreational/outdoor spaces. Users can select geographic parameters (neighborhood names), or search for specific locations (addresses), to access mobility data, which is also visualized on a heat map tool with marked features. In addition to walkability, the application also gauges biking and transit scores, which measure the convenience/proximity to bikability and public transit opportunities. Users can also access walking, biking, and transit score through an API. More information about the Walk Score is available through Redfin.