Traditionally, criminal research on a national scale has relied primarily on the FBI's Uniform Crime Reports (UCR), a tool with several weaknesses: (1) it contains no unique personal identifiers, precluding analysis of re-offense rates, (2) it lacks detail about individual crimes and their outcomes (e.g., number of charges, plea bargains, dispositions, fines, jail sentences), (3) reporting to the UCR is highly variable, so the aggregate statistics cannot be read as a comprehensive picture of crime. An alternative approach to crime record analysis can be pursued by the study of individual court records, housed in hundreds of counties across the United States. However, each jurisdiction employs local laws and sparse, idiosyncratic information management systems, making it prohibitively difficult to compare detailed crime records across time and place.To overcome all these limitations, we have developed the NeuLaw Criminal Record Database (CRD), a rich and growing collection of tens of millions of crime records. The CRD provides an unprecedented level of detail about individual offenders, their crimes, and their interactions with the criminal justice system; additionally, it translates court records into a common framework for cross-jurisdiction comparison. In particular, the database includes anonymized identifiers to enable large-scale exploration of criminal re-offense (recidivism). The CRD is growing monthly; as of this writing it contains 22.5 million records from 1977 to 2014 from Harris County in Texas, New York City, Miami-Dade County in Florida, and the state of New Mexico. The database can enable or enhance many types of research—for example, identification of high-risk offenders, measurement of changes in policing strategies, and quantification of legislative efficacy—thus giving policy makers the best data upon which to base law enforcement decisions.

Updated daily postings on Montgomery County’s open data website, dataMontgomery, provide the public with direct access to crime statistic databases - including raw data and search functions – of reported County crime. The data presented is derived from reported crimes classified according to the National Incident-Based Reporting System (NIBRS) of the Criminal Justice Information Services (CJIS) Division Uniform Crime Reporting (UCR) Program and documented by approved police incident reports. The data is compiled by “EJustice”, a respected law enforcement records-management system used by the Montgomery County Police Department and many other law enforcement agencies. To protect victims’ privacy, no names or other personal information are released. All data is refreshed on a quarterly basis to reflect any changes in status due to on-going police investigation. dataMontgomery allows the public to query the Montgomery County Police Department's database of founded crime. The information contained herein includes all founded crimes reported after July 1st 2016 and entered to-date utilizing Uniform Crime Reporting (UCR) rules. Please note that under UCR rules multiple offenses may appear as part of a single founded reported incident, and each offense may have multiple victims. Please note that these crime reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the crime data available on this web page may reflect: -Information not yet verified by further investigation -Information that may include attempted and reported crime -Preliminary crime classifications that may be changed at a later date based upon further investigation -Information that may include mechanical or human error -Arrest information [Note: all arrested persons are presumed innocent until proven guilty in a court of law.] Update Frequency: Daily

Police Records Management System Market Outlook

The global police records management system market size was valued at approximately USD 2.5 billion in 2023 and is projected to reach around USD 5.3 billion by 2032, growing at a compound annual growth rate (CAGR) of 8.8% from 2024 to 2032. This dynamic growth is primarily driven by advancements in digital technology, increased focus on public safety, and the growing demand for efficient management of police records. The significant rise in criminal activities globally has necessitated the adoption of sophisticated records management systems by law enforcement agencies to streamline operations and improve response times. Furthermore, the integration of advanced technologies such as artificial intelligence and big data analytics into these systems is expected to further propel the market growth over the forecast period.

The increasing focus on public safety and security is one of the primary growth factors fueling the expansion of the police records management system market. With the rise in crime rates and the complexity of modern crimes, law enforcement agencies are compelled to adopt more effective and efficient systems for managing and analyzing records. These systems enable better coordination and faster decision-making, which are crucial in combating crime and ensuring public safety. Governments across the world are investing heavily in modernizing their police infrastructure, which includes the deployment of robust records management systems. This investment is expected to continue, driven by the need for more sophisticated solutions that can handle the growing volume and complexity of data involved in law enforcement operations.

Technological advancements play a critical role in the growth of the police records management system market. The introduction of technologies such as cloud computing, artificial intelligence, machine learning, and big data analytics into records management systems has revolutionized the way police records are processed, stored, and retrieved. These technologies enable real-time data analysis, predictive analytics, and enhanced data security, thereby improving the overall efficiency and effectiveness of law enforcement agencies. In addition, the shift towards cloud-based solutions offers scalability, flexibility, and cost-effectiveness, which are appealing to both small and large law enforcement agencies. The continuous innovation in this space is expected to drive further adoption and expansion of police records management systems globally.

Another significant driver for the market is the increasing collaboration and information sharing between law enforcement agencies across different regions and countries. The globalization of crime has necessitated a unified approach to law enforcement, with agencies working together to share critical information and insights. Police records management systems facilitate this cooperation by offering centralized platforms for data sharing and collaboration. As agencies continue to recognize the importance of inter-agency cooperation, the demand for robust and interoperable records management systems is expected to rise, contributing to the market's growth.

Policing Technologies have become an integral part of modern law enforcement strategies, significantly influencing the development and implementation of police records management systems. These technologies encompass a wide range of tools and solutions designed to enhance the capabilities of law enforcement agencies. From body-worn cameras and automated license plate readers to sophisticated data analytics platforms, policing technologies provide invaluable support in crime prevention, investigation, and community engagement. The integration of these technologies into records management systems allows for more comprehensive data collection and analysis, enabling agencies to make informed decisions and improve operational efficiency. As the demand for advanced policing technologies continues to grow, their role in shaping the future of police records management systems is expected to expand, offering new opportunities for innovation and collaboration in the field.

Regionally, North America holds a prominent position in the police records management system market, owing to the early adoption of advanced technologies and significant investments in law enforcement infrastructure. The presence of leading market players and the federal government's proactive approach towards public safety and security further bolster the market in this region. Europe f

Each record in this dataset shows information about an arrest executed by the Chicago Police Department (CPD). Source data comes from the CPD Automated Arrest application. This electronic application is part of the CPD CLEAR (Citizen Law Enforcement Analysis and Reporting) system, and is used to process arrests Department-wide.

A more-detailed version of this dataset is available to media by request. To make a request, please email dataportal@cityofchicago.org with the subject line: Arrests Access Request. Access will require an account on this site, which you may create at https://data.cityofchicago.org/signup. New data fields may be added to this public dataset in the future. Requests for individual arrest reports or any other related data other than access to the more-detailed dataset should be directed to CPD, through contact information on that site or a Freedom of Information Act (FOIA) request.

The data is limited to adult arrests, defined as any arrest where the arrestee was 18 years of age or older on the date of arrest. The data excludes arrest records expunged by CPD pursuant to the Illinois Criminal Identification Act (20 ILCS 2630/5.2).

Department members use charges that appear in Illinois Compiled Statutes or Municipal Code of Chicago. Arrestees may be charged with multiple offenses from these sources. Each record in the dataset includes up to four charges, ordered by severity and with CHARGE1 as the most severe charge. Severity is defined based on charge class and charge type, criteria that are routinely used by Illinois court systems to determine penalties for conviction. In case of a tie, charges are presented in the order that the arresting officer listed the charges on the arrest report. By policy, Department members are provided general instructions to emphasize seriousness of the offense when ordering charges on an arrest report.

Each record has an additional set of columns where a charge characteristic (statute, description, type, or class) for all four charges, or fewer if there were not four charges, is concatenated with the | character. These columns can be used with the Filter function's "Contains" operator to find all records where a value appears, without having to search four separate columns.

Users interested in learning more about CPD arrest processes can review current directives, using the CPD Automated Directives system (http://directives.chicagopolice.org/directives/). Relevant directives include:

• Special Order S06-01-11 – CLEAR Automated Arrest System: describes the application used by Department members to enter arrest data. • Special Order S06-01-04 – Arrestee Identification Process: describes processes related to obtaining and using CB numbers. • Special Order S09-03-04 – Assignment and Processing of Records Division Numbers: describes processes related to obtaining and using RD numbers. • Special Order 06-01 – Processing Persons Under Department Control: describes required tasks associated with arrestee processing, include the requirement that Department members order charges based on severity.

This dataset contains Crime and Safety data from the Cary Police Department.

This data is extracted by the Town of Cary's Police Department's RMS application. The police incidents will provide data on the Part I crimes of arson, motor vehicle thefts, larcenies, burglaries, aggravated assaults, robberies and homicides. Sexual assaults and crimes involving juveniles will not appear to help protect the identities of victims.

This dataset includes criminal offenses in the Town of Cary for the previous 10 calendar years plus the current year. The data is based on the National Incident Based Reporting System (NIBRS) which includes all victims of person crimes and all crimes within an incident. The data is dynamic, which allows for additions, deletions and/or modifications at any time, resulting in more accurate information in the database. Due to continuous data entry, the number of records in subsequent extractions are subject to change. Crime data is updated daily however, incidents may be up to three days old before they first appear.

About Crime Data

The Cary Police Department strives to make crime data as accurate as possible, but there is no avoiding the introduction of errors into this process, which relies on data furnished by many people and that cannot always be verified. Data on this site are updated daily, adding new incidents and updating existing data with information gathered through the investigative process.

This dynamic nature of crime data means that content provided here today will probably differ from content provided a week from now. Additional, content provided on this site may differ somewhat from crime statistics published elsewhere by other media outlets, even though they draw from the same database.

Withheld Data

In accordance with legal restrictions against identifying sexual assault and child abuse victims and juvenile perpetrators, victims, and witnesses of certain crimes, this site includes the following precautionary measures: (a) Addresses of sexual assaults are not included. (b) Child abuse cases, and other crimes which by their nature involve juveniles, or which the reports indicate involve juveniles as victims, suspects, or witnesses, are not reported at all.

Certain crimes that are under current investigation may be omitted from the results in avoid comprising the investigative process.

Incidents five days old or newer may not be included until the internal audit process has been completed.

This data is updated daily.

The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on communitycrimemap.comData Dictionary:Field NameField DescriptionIncident Numberthe number associated with either the incident or used as reference to store the items in our evidence roomsDate Reportedthe date the incident was reported to LMPDDate Occurredthe date the incident actually occurredBadge IDBadge ID of responding OfficerOffense ClassificationNIBRS Reporting category for the criminal act committedOffense Code NameNIBRS Reporting code for the criminal act committedNIBRS_CODEthe code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://res1ucrd-o-tfbid-o-tgov.vcapture.xyz/nibrs/2011/resources/nibrs-offense-codes/viewNIBRS Grouphierarchy that follows the guidelines of the FBI National Incident Based Reporting SystemWas Offense CompletedStatus indicating whether the incident was an attempted crime or a completed crime.LMPD Divisionthe LMPD division in which the incident actually occurredLMPD Beatthe LMPD beat in which the incident actually occurredLocation Categorythe type of location in which the incident occurred (e.g. Restaurant)Block Addressthe location the incident occurredCitythe city associated to the incident block locationZip Codethe zip code associated to the incident block locationContact:LMPD Open Records lmpdopenrecords@louisvilleky.gov

Description: Pursuant to the Sex Offender and Child Murderer Community Notification Law, 730 ILCS 152/101,et seq., the Chicago Police Department maintains a list of sex offenders residing in the City of Chicago who are required to register under the Sex Offender Registration Act, 730 ILCS 150/2, et seq. To protect the privacy of the individuals, addresses are shown at the block level only and specific locations are not identified. The data are extracted from the CLEAR (Citizen Law Enforcement Analysis and Reporting) system developed by the Department. Although every effort is made to keep this list accurate and current, the city cannot guarantee the accuracy of this information. Offenders may have moved and failed to notify the Chicago Police Department as required by law. If any information presented in this web site is known to be outdated, please contact the Chicago Police Department at srwbmstr@chicagopolice.org, or mail to Sex Registration Unit, 3510 S Michigan Ave, Chicago, IL 60653. Disclaimer: This registry is based upon the legislature's decision to facilitate access to publicly available information about persons convicted of specific sexual offenses. The Chicago Police Department has not considered or assessed the specific risk of re-offense with regard to any individual prior to his or her inclusion within this registry, and has made no determination that any individual included within the registry is currently dangerous. Individuals included within this registry are included solely by virtue of their conviction record and Illinois law. The main purpose of providing this data on the internet is to make the information more available and accessible, not to warn about any specific individual.

Anyone who uses information contained in the Sex Offender Database to commit a criminal act against another person is subject to criminal prosecution. Data Owner: Chicago Police Department. Frequency: Data is updated daily. Related Applications: CLEARMAP (http://j.mp/lLluSa).

Market Research Intellect's Police Records Management System Market Report highlights a valuation of USD 1. 2 billion in 2024 and anticipates growth to USD 2. 5 billion by 2033, with a CAGR of 9. 3% from 2026–2033. Explore insights on demand dynamics, innovation pipelines, and competitive landscapes.

The primary table for all public data on complaints, including dates, locations and the outcomes of closed complaints received since the year 2000. The dataset is part of a database of all public police misconduct records the Civilian Complaint Review Board (CCRB) maintains on complaints against New York Police Department uniformed members of service received in CCRB's jurisdiction since the year 2000, when CCRB's database was first built. This data is published as four tables: Civilian Complaint Review Board: Police Officers Civilian Complaint Review Board: Complaints Against Police Officers Civilian Complaint Review Board: Allegations Against Police Officers Civilian Complaint Review Board: Penalties A single complaint can include multiple allegations, and those allegations may include multiple subject officers and multiple complainants. Public records exclude complaints and allegations that were closed as Mediated, Mediation Attempted, Administrative Closure, Conciliated (for some complaints prior to the year 2000), or closed as Other Possible Misconduct Noted. This database is inclusive of prior datasets held on Open Data (previously maintained as "Civilian Complaint Review Board (CCRB) - Complaints Received," "Civilian Complaint Review Board (CCRB) - Complaints Closed," and "Civilian Complaint Review Board (CCRB) - Allegations Closed") but includes information and records made public by the June 2020 repeal of New York Civil Rights law 50-a, which precipitated a full revision of what CCRB data could be considered public.

description: Please read and understand the following information. Understanding the following conditions will allow you to get the most out of the data provided. ??? Due to the methodological differences in data collection, different data sources may produce different results. ??? Our on-line database is continuously being updated. The data provided here represents a particular point in time. Searches may be accomplished using several geographic boundaries: Police area commands or districts, zip codes and census tracts. Additionally, a known case number may be entered. Updates to the police report database occur daily. Information is available from today???s date back 18 months. Due to several factors (once-a-day updates, offense reclassification, reported versus occurred dates, etc.) comparisons should not be made between numbers generated with this database to any other official police reports. Data provided represents only calls for police service where a report was written. Totals in the database may vary considerably from official totals following investigation and final categorization. Therefore, the data should not be used for comparisons with Uniform Crime Report statistics. The Austin Police Department does not assume any liability for any decision made or action taken or not taken by the recipient in reliance upon any information or data provided.; abstract: Please read and understand the following information. Understanding the following conditions will allow you to get the most out of the data provided. ??? Due to the methodological differences in data collection, different data sources may produce different results. ??? Our on-line database is continuously being updated. The data provided here represents a particular point in time. Searches may be accomplished using several geographic boundaries: Police area commands or districts, zip codes and census tracts. Additionally, a known case number may be entered. Updates to the police report database occur daily. Information is available from today???s date back 18 months. Due to several factors (once-a-day updates, offense reclassification, reported versus occurred dates, etc.) comparisons should not be made between numbers generated with this database to any other official police reports. Data provided represents only calls for police service where a report was written. Totals in the database may vary considerably from official totals following investigation and final categorization. Therefore, the data should not be used for comparisons with Uniform Crime Report statistics. The Austin Police Department does not assume any liability for any decision made or action taken or not taken by the recipient in reliance upon any information or data provided.

A list of all NYPD officers, as reported to CCRB by NYPD based on NYPD's roster, and a count of any complaints they have received since the year 2000. The dataset is part of a database of all public police misconduct records the Civilian Complaint Review Board (CCRB) maintains on complaints against New York Police Department uniformed members of service received in CCRB's jurisdiction since the year 2000, when CCRB's database was first built. This data is published as four tables: Civilian Complaint Review Board: Police Officers Civilian Complaint Review Board: Complaints Against Police Officers Civilian Complaint Review Board: Allegations Against Police Officers Civilian Complaint Review Board: Penalties A single complaint can include multiple allegations, and those allegations may include multiple subject officers and multiple complainants. Public records exclude complaints and allegations that were closed as Mediated, Mediation Attempted, Administrative Closure, Conciliated (for some complaints prior to the year 2000), or closed as Other Possible Misconduct Noted. This database is inclusive of prior datasets held on Open Data (previously maintained as "Civilian Complaint Review Board (CCRB) - Complaints Received," "Civilian Complaint Review Board (CCRB) - Complaints Closed," and "Civilian Complaint Review Board (CCRB) - Allegations Closed") but includes information and records made public by the June 2020 repeal of New York Civil Rights law 50-a, which precipitated a full revision of what CCRB data could be considered public.

Data Description and Disclaimer This dataset reflects incidents that have been reported to the New Orleans Police Department in 2013. Data is provided by Orleans Parish Communication District (OPCD), the administrative office of 9-1-1 for the City of New Orleans. In the OPCD system, NOPD may reclassify or change the signal type for up to 36 hours after the incident is marked up. For information about an incident after this time period, citizens may request police reports from the NOPD Public Records Division. In order to protect the privacy of victims, addresses are shown at the block level and the call types cruelty to juveniles, juvenile attachment and missing juvenile have been removed in accordance with the Louisiana Public Records Act, L.R.S. 44:1. Map coordinates (X,Y) have been removed for the following call types: Aggravated Rape, Aggravated Rape - MA, Crime Against Nature, Mental Patient, Oral Sexual Battery, Prostitution, Sexual Battery, Simple Rape, Simple Rape - Male V, and Soliciting for Prost. Disclaimer: These incidents may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the New Orleans Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The New Orleans Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The New Orleans Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of New Orleans or New Orleans Police Department web page. The user specifically acknowledges that the New Orleans Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. Any use of the information for commercial purposes is strictly prohibited. The unauthorized use of the words "New Orleans Police Department," "NOPD," or any colorable imitation of these words or the unauthorized use of the New Orleans Police Department logo is unlawful. This web page does not, in any way, authorize such use.

AUSTIN POLICE DEPARTMENT DATA DISCLAIMER Please read and understand the following information. This dataset contains a record of incidents that the Austin Police Department responded to and wrote a report. Please note one incident may have several offenses associated with it, but this dataset only depicts the highest level offense of that incident. Data is from 2003 to present. This dataset is updated weekly. Understanding the following conditions will allow you to get the most out of the data provided. Due to the methodological differences in data collection, different data sources may produce different results. This database is updated weekly, and a similar or same search done on different dates can produce different results. Comparisons should not be made between numbers generated with this database to any other official police reports. Data provided represents only calls for police service where a report was written. Totals in the database may vary considerably from official totals following investigation and final categorization. Therefore, the data should not be used for comparisons with Uniform Crime Report statistics. The Austin Police Department does not assume any liability for any decision made or action taken or not taken by the recipient in reliance upon any information or data provided. Pursuant to section 552.301 (c) of the Government Code, the City of Austin has designated certain addresses to receive requests for public information sent by electronic mail. For requests seeking public records held by the Austin Police Department, please submit by utilizing the following link: https://apd-austintx.govqa.us/WEBAPP/_rs/(S(0auyup1oiorznxkwim1a1vpj))/supporthome.aspx

The Seattle Police Department (SPD) replaced its Records Management System (RMS) in May 2019. To preserve data quality and continuity between systems (2008-Present), SPD relied on the National Incident-Based Reporting System (NIBRS). The standardization of crime classifications allows for comparison over time. For more information on definitions and classifications, please visit https://www.fbi.gov/services/cjis/ucr/nibrs.

Additional groupings are used to analyze crime in SPD’s Crime Dashboard. Violent and property crime categories align with best practices. For additional inquiries, we encourage the use of the underline data to align with the corresponding query.

Disclaimer: Only finalized (UCR approved) reports are released. Those in draft, awaiting approval, or completed after the update, will not appear until the subsequent day(s). Data is updated once every twenty-four hours. Records and classification changes will occur as a report makes its way through the approval and investigative process.

Global Police Records Management System is segmented by Application (Law Enforcement, Government, Criminal Justice, Security, Compliance), Type (Digital, Cloud-based, Automated, Integrated, Customizable) and Geography(North America, LATAM, West Europe, Central & Eastern Europe, Northern Europe, Southern Europe, East Asia, Southeast Asia, South Asia, Central Asia, Oceania, MEA)

The Regional Crime Analysis GIS (RCAGIS) is an Environmental Systems Research Institute (ESRI) MapObjects-based system that was developed by the United States Department of Justice Criminal Division Geographic Information Systems (GIS) Staff, in conjunction with the Baltimore County Police Department and the Regional Crime Analysis System (RCAS) group, to facilitate the analysis of crime on a regional basis. The RCAGIS system was designed specifically to assist in the analysis of crime incident data across jurisdictional boundaries. Features of the system include: (1) three modes, each designed for a specific level of analysis (simple queries, crime analysis, or reports), (2) wizard-driven (guided) incident database queries, (3) graphical tools for the creation, saving, and printing of map layout files, (4) an interface with CrimeStat spatial statistics software developed by Ned Levine and Associates for advanced analysis tools such as hot spot surfaces and ellipses, (5) tools for graphically viewing and analyzing historical crime trends in specific areas, and (6) linkage tools for drawing connections between vehicle theft and recovery locations, incident locations and suspects' homes, and between attributes in any two loaded shapefiles. RCAGIS also supports digital imagery, such as orthophotos and other raster data sources, and geographic source data in multiple projections. RCAGIS can be configured to support multiple incident database backends and varying database schemas using a field mapping utility.

Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities.The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on Crimemapping.comData Dictionary:INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence roomsDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedCRIME_TYPE - the crime type categoryNIBRS_CODE - the code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewUCR_HIERARCHY - hierarchy that follows the guidelines of the FBI Uniform Crime Reporting. For more details visit https://ucr.fbi.gov/ATT_COMP - Status indicating whether the incident was an attempted crime or a completed crime.LMPD_DIVISION - the LMPD division in which the incident actually occurredLMPD_BEAT - the LMPD beat in which the incident actually occurredPREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant)BLOCK_ADDRESS - the location the incident occurredCITY - the city associated to the incident block locationZIP_CODE - the zip code associated to the incident block locationID - Unique identifier for internal databaseContact:Crime Information CenterCrimeInfoCenterDL@louisvilleky.gov

Sadly, the trend of fatal police shootings in the United States seems to only be increasing, with a total 1,173 civilians having been shot, 248 of whom were Black, as of December 2024. In 2023, there were 1,164 fatal police shootings. Additionally, the rate of fatal police shootings among Black Americans was much higher than that for any other ethnicity, standing at 6.1 fatal shootings per million of the population per year between 2015 and 2024. Police brutality in the U.S. In recent years, particularly since the fatal shooting of Michael Brown in Ferguson, Missouri in 2014, police brutality has become a hot button issue in the United States. The number of homicides committed by police in the United States is often compared to those in countries such as England, where the number is significantly lower. Black Lives Matter The Black Lives Matter Movement, formed in 2013, has been a vocal part of the movement against police brutality in the U.S. by organizing “die-ins”, marches, and demonstrations in response to the killings of black men and women by police. While Black Lives Matter has become a controversial movement within the U.S., it has brought more attention to the number and frequency of police shootings of civilians.

The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on communitycrimemap.comData Dictionary:Field NameField DescriptionIncident Numberthe number associated with either the incident or used as reference to store the items in our evidence roomsDate Reportedthe date the incident was reported to LMPDDate Occurredthe date the incident actually occurredBadge IDBadge ID of responding OfficerOffense ClassificationNIBRS Reporting category for the criminal act committedOffense Code NameNIBRS Reporting code for the criminal act committedNIBRS_CODEthe code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewNIBRS Grouphierarchy that follows the guidelines of the FBI National Incident Based Reporting SystemWas Offense CompletedStatus indicating whether the incident was an attempted crime or a completed crime.LMPD Divisionthe LMPD division in which the incident actually occurredLMPD Beatthe LMPD beat in which the incident actually occurredLocation Categorythe type of location in which the incident occurred (e.g. Restaurant)Block Addressthe location the incident occurredCitythe city associated to the incident block locationZip Codethe zip code associated to the incident block locationContact:LMPD Open Records lmpdopenrecords@louisvilleky.gov