Philadelphia Police Part One Crime Incidents

Crime Data from 2006 to the present

Organization
Division
Release Date
Dec. 12, 2012
Data Types
ArcGIS REST, CSV
Categories
Description
From the metadata: "The layer holds Part I crime for the City of Philadelphia beginning January 1, 2006. Part I crime includes, Homicides, Rapes, Robberies, Aggravated Assaults, Thefts. The data displayed is generalized by the crime type and the block location." The data is updated daily. Metadata is included in the zipfile.
Crime Incident Data
Crime Incident Data
Organization
Division
Release Date
Dec. 12, 2012
Data Types
ArcGIS REST, CSV
Categories
Usage
Public Use; Free
Description
From the metadata: "The layer holds Part I crime for the City of Philadelphia beginning January 1, 2006. Part I crime includes, Homicides, Rapes, Robberies, Aggravated Assaults, Thefts. The data displayed is generalized by the crime type and the block location." The data is updated daily. Metadata is included in the zipfile.
Update Frequency
Daily
Coordinate Systems
3857, Web Mercator WGS84, meters
Contact Email
Contact Url
Date Added
Dec. 12, 2012, 9:45 a.m.
Last Update
Jan. 27, 2014, 7:57 a.m.
Crime Incident Data
Crime Incident Data

Average Rating

5 Votes
Please login to add comments
Comments
jimRsmiley
12/22/2012
I pulled down the csv file. The SECTOR column changes from sector ids to what looks like PSA ids around September 2009. I'm looking to thematic map crime changes over time by sectors.
rcheetham
12/24/2012
The metadata lists the coordinate system as "WGS84 Web Mercator" but the data is in latitude/longitude. It should probably be "WGS84 decimal degrees".
jchoffmann913
01/01/2013
The breadth of this data is great, though I wish it were linked to Court system in some way to track defendants. I initially had some trouble loading visualizing this data as a map in Google Fusion -- it was not automatically georeferencing -- but I was able to fix that by importing into Carto DB and exporting as a new .csv.
jchoffmann913
01/01/2013
This entry is coming up in Ohio because the longitude is off, and it's not clear what the exact address is: 6 1 2011-12-01 18:06:00 2011-12-01 18:06:00 18 Confidential 679\2 N 13TH ST 200 195178 Rape 195178 -84.69369121 39.1207947
PLRfromGENA
01/08/2013
Still studying the data and working out how to combine searches in a ruby app, but so far useful and easy to work with
jeffreymealo
04/08/2013
Thanks for this invaluable data. During analysis, I found that 2,020 of the latitudes and longitudes provided are not inside Philadelphia. Some had the latitude and the longitude reversed; others were in Ohio (as stated by jchoffmann913). The latter were not a simple number swaps, something seems to have gone awry.
jeffreymealo
11/12/2013
Attention System/Network Administrator(s): All traffic originating from 192.0.0.0/8 to gis.phila.gov (170.115.248.48) is being dropped on your end. Traffic originating from 76.0.0.0/8 is allowed. This means as many as 16,711,680 IPs are being blocked erroneously. The traffic is able to get as far as 170.115.109.6 before it is filtered. A rule to block all traffic from 192.0.0.0/8 is likely the culprit. To block spoofed LAN traffic on the WAN only the following should be blocked: 192.168.0.0/16 172.16.0.0/12 10.0.0.0/8 169.254.0.0/16 The following networks have been allocated by the IANA for public use and should not be blocked: 192.0.0.0/9 192.128.0.0/11 192.160.0.0/13 192.169.0.0/16 192.170.0.0/15 192.172.0.0/14 192.176.0.0/12 192.192.0.0/10