By Bob Gourley
CTOlabs.com, a subsidiary of the technology research, consulting and services firm Crucial Point LLC and a peer site of CTOvision.com, has just announced a white paper on the use of Big Data for Predictive Policing
In this paper we review the evolution of law enforcement use of Big Data and capture some key lessons learned. We also provide tips for getting started which should help any organization get moving on a predictive policing Big Data activity.
From the paper:
Law enforcement methodology has evolved tremendously in the past few decades to embrace quantitative analysis and statistics with the rise of data-driven policing. Now, law enforcement strategy is poised to take another leap forward with Big Data and predictive policing. Already, departments facing rising crime but falling budgets have turned to Big Data analytics to supplement the instincts of their officers and make patrols more proactive rather than reactive. Though much work remains to be done, advances in predictive policing have the potential to let law enforcement agencies do more with less and prevent crime rather than simply respond to it.
Patrol is the backbone of law enforcement, the largest use of department personnel and resources as well as the source of the majority of officer interactions with the community and hence has the greatest potential to reduce crime. Despite the perception of the old-fashioned “beat cop,” patrol has repeatedly been redefined through new technology. The introduction of 911, police cars, and radios first marginalized foot patrol and, especially in more active departments, made patrol primarily responsive, driven by calls for service. When officers did get the chance to patrol freely, working to reduce crime rather than respond to it, their “beats” would be determined by administrative divisions, areas they could reasonably cover, and, at best, “primal policing” based on experience and instinct.
Download the paper at: Big Data for Predictive Policing
![](http://img.zemanta.com/pixy.gif?x-id=e0a72b0a-730e-4f39-8f56-c9eb702a15b5)
Leave a Reply
You must be logged in to post a comment.