Police recorded crime figures by Police Force Area and Community Safety Partnership areas (which equate in the majority of instances, to local authorities).

The dataset contains a subset of locations and attributes of incidents reported in the ASAP (Analytical Services Application) crime report database by the District of Columbia Metropolitan Police Department (MPD). Visit crimecards.dc.gov for more information. This data is shared via an automated process where addresses are geocoded to the District's Master Address Repository and assigned to the appropriate street block. Block locations for some crime points could not be automatically assigned resulting in 0,0 for x,y coordinates. These can be interactively assigned using the MAR Geocoder.On February 1 2020, the methodology of geography assignments of crime data was modified to increase accuracy. From January 1 2020 going forward, all crime data will have Ward, ANC, SMD, BID, Neighborhood Cluster, Voting Precinct, Block Group and Census Tract values calculated prior to, rather than after, anonymization to the block level. This change impacts approximately one percent of Ward assignments.

Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates within 30 days of the system migration, on or around April 13th, 2023Crime 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.com Data Dictionary: INCIDENT_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence rooms DATE_REPORTED - the date the incident was reported to LMPD DATE_OCCURED - the date the incident actually occurred BADGE_ID - UOR_DESC - Uniform Offense Reporting code for the criminal act committed CRIME_TYPE - the crime type category NIBRS_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/view UCR_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 occurred LMPD_BEAT - the LMPD beat in which the incident actually occurred PREMISE_TYPE - the type of location in which the incident occurred (e.g. Restaurant) BLOCK_ADDRESS - the location the incident occurred CITY - the city associated to the incident block location ZIP_CODE - the zip code associated to the incident block location ID - Unique identifier for internal database Contact: Crime Information Center CrimeInfoCenterDL@louisvilleky.gov

We will build you a custom US crime dataset based on your needs. Data points may include date, time, location, crime type, crime description, victim demographics, offender demographics, arrest records, charges filed, court outcomes, police department response time, incident outcome, weapon used, property stolen or damaged, crime location type, and other related data.

Use our US crime datasets for a range of applications to enhance public safety and policy effectiveness. Analyzing these datasets can help organizations understand crime patterns and trends across different regions of the United States, enabling them to tailor their strategies and interventions accordingly. Depending on your needs, you may access the entire dataset or a customized subset.

Popular use cases include: improving public safety measures, designing targeted crime prevention programs, resource allocation for law enforcement, and more.

Serious violent crimes consist of Part 1 offenses as defined by the U.S. Department of Justice’s Uniform Reporting Statistics. These include murders, nonnegligent homicides, rapes (legacy and revised), robberies, and aggravated assaults. LAPD data were used for City of Los Angeles, LASD data were used for unincorporated areas and cities that contract with LASD for law enforcement services, and CA Attorney General data were used for all other cities with local police departments. This indicator is based on location of residence. Single-year data are only available for Los Angeles County overall, Service Planning Areas, Supervisorial Districts, City of Los Angeles overall, and City of Los Angeles Council Districts.Neighborhood violence and crime can have a harmful impact on all members of a community. Living in communities with high rates of violence and crime not only exposes residents to a greater personal risk of injury or death, but it can also render individuals more susceptible to many adverse health outcomes. People who are regularly exposed to violence and crime are more likely to suffer from chronic stress, depression, anxiety, and other mental health conditions. They are also less likely to be able to use their parks and neighborhoods for recreation and physical activity.For more information about the Community Health Profiles Data Initiative, please see the initiative homepage.

"Crime Statistics" is a comprehensive collection of datasets focused on various dimensions of crime within a region, state, and district provided by the National Crime Records Bureau (NCRB). This dataset collection is invaluable for researchers, policymakers, law enforcement agencies, and social welfare organizations. It provides a multifaceted view of crime, covering different victim groups and crime types, ranging from crimes against specific social groups to cybercrimes and missing person cases. The datasets included help analyze trends, formulate targeted policies, and implement crime prevention strategies.

This dataset includes all valid felony, misdemeanor, and violation crimes reported to the New York City Police Department (NYPD) for all complete quarters so far this year (2017). For additional details, please see the attached data dictionary in the ‘About’ section.

The "2019 Crimes Data" dataset contains information about reported crimes in various regions through the year 2000-2019. This dataset aims to provide insights into crime trends, patterns, and rates for analysis and predictive modeling. The data can be used for exploratory data analysis (EDA), trend identification, and forecasting future crime activities and rates. The dataset is particularly valuable for law enforcement agencies, researchers, and analysts interested in understanding crime dynamics. ***Source of Data*:** The data was collected from official crime statistics sources, police department records, and news articles from reputable sources. All efforts were made to ensure accuracy and reliability in data collection.

Usage: This dataset is suitable for a wide range of analyses, including exploratory data analysis, trend visualization, and predictive modeling. Analysts and researchers can use this data to uncover crime patterns, identify hotspots, and develop models for predicting crime rates in upcoming years. Law enforcement agencies, such as the FBI, can benefit from insights gained through this dataset to improve crime prevention and resource allocation strategies.

In 2023, the violent crime rate in the United States was 363.8 cases per 100,000 of the population. Even though the violent crime rate has been decreasing since 1990, the United States tops the ranking of countries with the most prisoners. In addition, due to the FBI's transition to a new crime reporting system in which law enforcement agencies voluntarily submit crime reports, data may not accurately reflect the total number of crimes committed in recent years. Reported violent crime rate in the United States The United States Federal Bureau of Investigation tracks the rate of reported violent crimes per 100,000 U.S. inhabitants. In the timeline above, rates are shown starting in 1990. The rate of reported violent crime has fallen since a high of 758.20 reported crimes in 1991 to a low of 363.6 reported violent crimes in 2014. In 2023, there were around 1.22 million violent crimes reported to the FBI in the United States. This number can be compared to the total number of property crimes, roughly 6.41 million that year. Of violent crimes in 2023, aggravated assaults were the most common offenses in the United States, while homicide offenses were the least common. Law enforcement officers and crime clearance Though the violent crime rate was down in 2013, the number of law enforcement officers also fell. Between 2005 and 2009, the number of law enforcement officers in the United States rose from around 673,100 to 708,800. However, since 2009, the number of officers fell to a low of 626,900 officers in 2013. The number of law enforcement officers has since grown, reaching 720,652 in 2023. In 2023, the crime clearance rate in the U.S. was highest for murder and non-negligent manslaughter charges, with around 57.8 percent of murders being solved by investigators and a suspect being charged with the crime. Additionally, roughly 46.1 percent of aggravated assaults were cleared in that year. A statistics report on violent crime in the U.S. can be found here.

The Tempe Police Department prides itself in its continued efforts to reduce harm within the community and is providing this dataset on hate crime incidents that occur in Tempe.The Tempe Police Department documents the type of bias that motivated a hate crime according to those categories established by the FBI. These include crimes motivated by biases based on race and ethnicity, religion, sexual orientation, disability, gender and gender identity.The Bias Type categories provided in the data come from the Bias Motivation Categories as defined in the Federal Bureau of Investigation (FBI) National Incident-Based Reporting System (NIBRS) manual, version 2020.1 dated 4/15/2021. The FBI NIBRS manual can be found at https://www.fbi.gov/file-repository/ucr/ucr-2019-1-nibrs-user-manua-093020.pdf with the Bias Motivation Categories found on pages 78-79.Although data is updated monthly, there is a delay by one month to allow for data validation and submission.Information about Tempe Police Department's collection and reporting process for possible hate crimes is included in https://storymaps.arcgis.com/stories/a963e97ca3494bfc8cd66d593eebabaf.Additional InformationSource: Data are from the Law Enforcement Records Management System (RMS)Contact: Angelique BeltranContact E-Mail: angelique_beltran@tempe.govData Source Type: TabularPreparation Method: Data from the Law Enforcement Records Management System (RMS) are entered by the Tempe Police Department into a GIS mapping system, which automatically publishes to open data.Publish Frequency: MonthlyPublish Method: New data entries are automatically published to open data. Data Dictionary

Recorded crime figures for Community Safety Partnerships which equates in the majority of instances to local authorities . The data are rolling 12 month totals, with data points shown at the end of each financial year between year ending March 2003 and year ending March 2007 and at the end of each quarter from June 2007. The data cover local authority boundaries from April 2009 onwards and local authority area names correspond to Community Safety Partnership areas.

Crime data assembled by census block group for the MSA from the Applied Geographic Solutions' (AGS) 1999 and 2005 'CrimeRisk' databases distributed by the Tetrad Computer Applications Inc. CrimeRisk is the result of an extensive analysis of FBI crime statistics. Based on detailed modeling of the relationships between crime and demographics, CrimeRisk provides an accurate view of the relative risk of specific crime types at the block group level. Data from 1990 - 1996,1999, and 2004-2005 were used to compute the attributes, please refer to the 'Supplemental Information' section of the metadata for more details. Attributes are available for two categories of crimes, personal crimes and property crimes, along with total and personal crime indices. Attributes for personal crimes include murder, rape, robbery, and assault. Attributes for property crimes include burglary, larceny, and mother vehicle theft. 12 block groups have no attribute information. CrimeRisk is a block group and higher level geographic database consisting of a series of standardized indexes for a range of serious crimes against both persons and property. It is derived from an extensive analysis of several years of crime reports from the vast majority of law enforcement jurisdictions nationwide. The crimes included in the database are the "Part I" crimes and include murder, rape, robbery, assault, burglary, theft, and motor vehicle theft. These categories are the primary reporting categories used by the FBI in its Uniform Crime Report (UCR), with the exception of Arson, for which data is very inconsistently reported at the jurisdictional level. Part II crimes are not reported in the detail databases and are generally available only for selected areas or at high levels of geography. In accordance with the reporting procedures using in the UCR reports, aggregate indexes have been prepared for personal and property crimes separately, as well as a total index. While this provides a useful measure of the relative "overall" crime rate in an area, it must be recognized that these are unweighted indexes, in that a murder is weighted no more heavily than a purse snatching in the computation. For this reason, caution is advised when using any of the aggregate index values. The block group boundaries used in the dataset come from TeleAtlas's (formerly GDT) Dynamap data, and are consistent with all other block group boundaries in the BES geodatabase. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

*This dataset is updated nightly. Crime data represents the initial information that is provided by individuals calling for police assistance. Please note that the dataset only contains the last 5 years. Remaining information is often amended for accuracy after an Officer arrives and investigates the reported incident. Most often, the changes are made to more accurately reflect the official legal definition of the crimes reported. An example of this is for someone to report that they have been "robbed," when their home was broken into while they were away. The official definition of "robbery" is to take something by force. An unoccupied home being broken into, is actually defined as a "burglary," or a "breaking and entering." While there are mechanisms in place to make each initial call as accurate as possible, some events require evaluation upon arrival. Caution should be used when making assumptions based solely on the data provided, as they may not represent the official crime reports.

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

Context

From 1934 to 1963, San Francisco was infamous for housing some of the world's most notorious criminals on the inescapable island of Alcatraz. Today, the city is known more for its tech scene than its criminal past. But, with rising wealth inequality, housing shortages, and a proliferation of expensive digital toys riding BART to work, there is no scarcity of crime in the city by the bay. From Sunset to SOMA, and Marina to Excelsior, this dataset provides nearly 12 years of crime reports from across all of San Francisco's neighborhoods.

This dataset was featured in our completed playground competition entitled San Francisco Crime Classification. The goals of the competition were to:

• predict the category of crime that occurred, given the time and location

• visualize the city and crimes (see Mapping and Visualizing Violent Crime for inspiration)

Content

This dataset contains incidents derived from SFPD Crime Incident Reporting system. The data ranges from 1/1/2003 to 5/13/2015. The training set and test set rotate every week, meaning week 1,3,5,7... belong to test set, week 2,4,6,8 belong to training set. There are 9 variables:

• Dates - timestamp of the crime incident

• Category - category of the crime incident (only in train.csv).

• Descript - detailed description of the crime incident (only in train.csv)

• DayOfWeek - the day of the week

• PdDistrict - name of the Police Department District

• Resolution - how the crime incident was resolved (only in train.csv)

• Address - the approximate street address of the crime incident

• X - Longitude

• Y - Latitude

Acknowledgements

This dataset is part of our completed playground competition entitled San Francisco Crime Classification. Visit the competition page if you are interested in checking out past discussions, competition leaderboard, or more details regarding the competition. If you are curious to see how your results rank compared to others', you can still make a submission at the competition submission page!

The original dataset is from SF OpenData, the central clearinghouse for data published by the City and County of San Francisco.

We will build you a custom India crime dataset based on your needs. Data points may include date, time, location, crime type, crime description, victim demographics, offender demographics, arrest records, charges filed, court outcomes, police department response time, incident outcome, weapon used, property stolen or damaged, crime location type, and other related data.

Use our India crime datasets for a range of applications to enhance public safety and policy effectiveness. Analyzing these datasets can help organizations understand crime patterns and trends across different regions of India, enabling them to tailor their strategies and interventions accordingly. Depending on your needs, you may access the entire dataset or a customized subset.

Popular use cases include: improving public safety measures, designing targeted crime prevention programs, resource allocation for law enforcement, and more.

Gain critical insights into crime trends, risk assessment, and public safety with our comprehensive Crime Dataset. Designed for law enforcement agencies, researchers, and analysts, this dataset provides structured and reliable crime data to support investigations, policy-making, and crime prevention strategies.

Dataset Features

Crime Reports: Access detailed records of reported crimes, including incident type, date, time, and location. Law Enforcement Data: Extract information on arrests, case statuses, and law enforcement responses. Geospatial Crime Mapping: Analyze crime distribution across different regions, cities, and neighborhoods. Trends & Patterns: Identify crime trends over time, including seasonal fluctuations and high-risk areas. Demographic Insights: Understand crime demographics, including offender and victim profiles.

Customizable Subsets for Specific Needs Our Crime Dataset is fully customizable, allowing you to filter data based on crime type, location, time period, or law enforcement jurisdiction. Whether you need broad coverage for national crime analysis or focused data for local risk assessment, we tailor the dataset to your needs.

Popular Use Cases

Crime Risk Assessment & Prevention: Identify high-crime areas, assess risk factors, and develop crime prevention strategies. Law Enforcement & Investigations: Support law enforcement agencies with structured crime data for case analysis and intelligence gathering. Urban Planning & Public Safety: Use crime data to inform city planning, improve public safety measures, and allocate resources effectively. AI & Predictive Analytics: Train AI models for crime forecasting, anomaly detection, and predictive policing. Policy & Legal Research: Analyze crime trends to support policy-making, legal studies, and criminal justice reforms.

Whether you're analyzing crime trends, supporting law enforcement, or developing predictive models, our Crime Dataset provides the structured data you need. Get started today and customize your dataset to fit your research and security objectives.

This dataset represents the location and characteristics of major (Group A) crime against persons such as homicide, shooting, robbery, aggravated assault etc. within the City of Baltimore. Data is updated weekly. This dataset contains crime data starting 1/1/2022 through present.Note: The way the Baltimore Police Department collects and reports data on crimes has changed, effective Jan. 1, 2025. The FBI has mandated that all law enforcement agencies across the country make the transition to the National Incident-Based Reporting System (NIBRS) to improve the overall quality, accuracy and timeliness of crime data collected.For more information, visit: https://www.baltimorepolice.org/nibrs If you have any questions or need to report an issue for this dataset, please use this feedback form to submit your response, and the Open Baltimore support team will contact you.DATA DICTIONARY:

    Field Name
    Description

  CCNumberUnique identifier for the record.
  CrimeDateTimeDate and time when the crime occurred.
  DescriptionType of crime incident reported.
  CrimeCodeCode assigned to categorize the crime type.
  WeaponIndicates if a weapon was involved in the crime incident.
  ShootingIndicates if a shooting of a firearm was involved in the crime incident.
  PostPolice post (sub-unit of geography under districts) under the current mapping scheme.
  GenderSex or gender of the victim.
  AgeAge of the victim.
  RaceRace of the victim.
  EthnicityEthnicity of the victim.
  Old_DistrictPolice district under the previous mapping scheme.
  New_DistrictPolice district under the current mapping scheme.
  Inside_OutsideIndicates whether the crime occurred indoors or outdoors.
  NeighborhoodNeighborhood where the incident occurred.
  LocationAddress or general location where the incident occurred.
  LongitudeLongitude of the incident's geographic location.
  LatitudeLatitude of the incident's geographic location.
  GeoLocationConcatenation of the Latitude and Longitude fields.
  PremiseTypeType of premise where the incident occurred (residence, business, vacant building).
  Total_IncidentsTotal number of incidents occurring for the reported crime.

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