Retirement Notice: This item is in mature support as of June 2023 and will be retired in December 2025. A replacement item has not been identified at this time. Esri recommends updating your maps and apps to phase out use of this item.This map shows the total crime index in the U.S. in 2022 in a multi-scale map (by state, county, ZIP Code, tract, and block group). The layer uses 2020 Census boundaries. The pop-up is configured to include the following information for each geography level:Total crime indexPersonal and Property crime indices Sub-categories of personal and property crime indices Permitted use of this data is covered in the DATA section of the EsriMaster Agreement (E204CW) and these supplemental terms.

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.

The following datasets contain the crime rate for cities in the United States. The four datasets are separated based on population ranges.

FILE DESCRIPTION

File names: - 'crime_40 _60.csv': dataset for population ranging from 40,000 to 60,000. - 'crime_60 _100.csv': dataset for population ranging from 60,000 to 100,000. - 'crime_100 _250.csv': dataset for population ranging from 100,000 to 250,000. - 'crime_250 _plus.csv': dataset for population greater than 250,000.

COLUMN DESCRIPTION

For file: crime_40 _60.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'violent_crime': violent crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ The following datasets contain the crime rate for cities in the United States. The four datasets are separated based on population ranges.

FILE DESCRIPTION

File names: - 'crime_40 _60.csv': dataset for population ranging from 40,000 to 60,000. - 'crime_60 _100.csv': dataset for population ranging from 60,000 to 100,000. - 'crime_100 _250.csv': dataset for population ranging from 100,000 to 250,000. - 'crime_250 _plus.csv': dataset for population greater than 250,000.

COLUMN DESCRIPTION

For file: crime_40 _60.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'violent_crime': violent crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ assault': agrv_ assault - 'prop_crime': property crime - 'burglary': burglary - 'larceny': larceny theft - 'vehicle_theft': motor vehicle theft

crime_60 _100.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'violent_crime': violent crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ assault': agrv_ assault - 'prop_crime': property crime - 'burglary': burglary - 'larceny': larceny theft - 'vehicle_theft': motor vehicle theft

crime_100 _250.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'violent_crime': violent crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ assault': agrv_ assault - 'prop_crime': property crime - 'burglary': burglary - 'larceny': larceny theft - 'vehicle_theft': motor vehicle theft

crime_250 _plus.csv: - 'states': name of the state - 'cities': name of the city - 'population': population of the city - 'total_crime': total crime - 'murder': murder and nonnegligent manslaughter - 'rape': forcible rape - 'robbery': robbery - 'agrv_ assault': agrv_ assault - 'total_violent _crime': total violent crime - 'prop_crime': property crime - 'burglary': burglary - 'larceny': larceny theft - 'vehicle_theft': motor vehicle theft - 'tot_prop _crime': total property crime - 'arson': arson

Photo by David von Diemar on Unsplash

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

This dataset aggregates Seattle Police Department crime statistics with spatial ZIP code boundaries and US Census data to determine the property crime rate per 1,000 residents. The following sources were used to create this dataset:

King County ZIP Code Boundaries

Source: https://data-seattlecitygis.opendata.arcgis.com/datasets/SeattleCityGIS::zip-codes/explore

King County provides approximate ZIP code boundaries, updated quarterly and published by the city of Seattle.

SPD Crime Data: 2008-Present

Source: https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5

The Seattle Police Department publishes data for reported crimes from 2008 to the present, refreshed daily. This data includes whether the crime is classified as against a person, against property, or against society.

2020 ACS 5-year estimates for population

Source: https://data.census.gov/cedsci/table?q=population%20seattle&g=0400000US53%248600000&tid=ACSDP5Y2020.DP05

The US Census Department American Community Survey (ACS) publishes 5-year estimates of population by a variety of geographies, including ZIP Code Tabulation Areas (ZCTAs), geographic approximations of each ZIP code.

Data Processing

Using the pandas and geopandas libraries within python, the following processing steps were followed to prepare this dataset: - Converted the date and time reported field in the SPD dataset to a datetime object and extracted the year - Filtered to crimes reported between 2008 and 2021 - Filtered to only crimes against property - Dropped rows with null values for year, crime against category, longitude, or latitude - Performed a spatial join using the latitude and longitude for each report in the SPD data to append a ZIP code from the King County ZIP Code boundary shapefile - Summarized to calculate a count of property crimes reported for each combination of year and ZIP code - Summarized by ZIP code to calculate the count of years with at least one crime reported and the total number of property crimes reported - Calculated the average number of property crimes reported per year in each ZIP code - Merged with the ACS population estimates - Calculated the number of property crimes reported per year per 1,000 population for each zip code

Photo by Justus Hayes: https://www.pexels.com/photo/a-bicycle-chained-to-a-metal-post-6355944/

Crime severity index (violent, non-violent, youth) and weighted clearance rates (violent, non-violent), Canada, provinces, territories and Census Metropolitan Areas, 1998 to 2024.

This table contains data on the rate of violent crime (crimes per 1,000 population) for California, its regions, counties, cities and towns. Crime and population data are from the Federal Bureau of Investigations, Uniform Crime Reports. Rates above the city/town level include data from city, university and college, county, state, tribal, and federal law enforcement agencies. The table is part of a series of indicators in the Healthy Communities Data and Indicators Project of the Office of Health Equity. Ten percent of all deaths in young California adults aged 15-44 years are related to assault and homicide. In 2010, California law enforcement agencies reported 1,809 murders, 8,331 rapes, and over 95,000 aggravated assaults. African Americans in California are 11 times more likely to die of assault and homicide than Whites. More information about the data table and a data dictionary can be found in the About/Attachments section.

Update Frequency: Daily

Current year to date. The data included in this dataset has been reviewed and approved by a Milwaukee Police Department supervisor and the Milwaukee Police Department’s Records Management Division. This approval process can take a few weeks from the reported date of the crime. For preliminary crime data, please visit the Milwaukee Police Department’s Crime Maps and Statistics dashboard at https://city.milwaukee.gov/police/Information-Services/Crime-Maps-and-Statistics.

Wisconsin Incident Based Report (WIBR) Group A Offenses.

The Crime Data represents incident level data defined by Wisconsin Incident Based Reporting System (WIBRS) codes. WIBRS reporting is a crime reporting standard and can not be compared to any previous UCR report. Therefore, the Crime Data may reflect:

• Information not yet verified by further investigation
• Preliminary crime classifications that may be changed at a later date based upon further investigation
• Information that may include mechanical or human error

Neither the City of Milwaukee nor the Milwaukee Police Department guarantee (either express or implied) the accuracy, completeness, timeliness, or correct sequencing of the Crime Data. The City of Milwaukee and the Milwaukee Police Department shall have no liability for any error or omission, or for the use of, or the results obtained from the use of the Crime Data. In addition, the City of Milwaukee and the Milwaukee Police Department caution against using the Crime Data to make decisions/comparisons regarding the safety of or the amount of crime occurring in a particular area. When reviewing the Crime Data, the site user should consider that:

• The information represents only police services where a report was made and does not include other calls for police service
• The information does not reflect or certify "safe" or "unsafe" areas
• The information will sometimes reflect where the crime was reported versus where the crime occurred

This data is not intended to represent a total number/sum of crimes, rather 1 = True and 0 = False.

The use of the Crime Data indicates the site user's unconditional acceptance of all risks associated with the use of the Crime Data.

To download XML and JSON files, click the CSV option below and click the down arrow next to the Download button in the upper right on its page. XY fields in data is in projection Wisconsin State Plane South NAD27 (WKID 32054).

Note: Due to a system migration, this data will cease to update on March 14th, 2023. The current projection is to restart the updates on or around July 17th, 2023.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

Data for violent crimes per Police Incident Data taken from the records managment sysmte

This is the most current information as of the date of upload. This provides the user the ability to view the most current crime information within Kansas City, Missouri. The displayed information is the most current information from the data source as of the date of upload. The data source is dynamic and therefore constantly changing. Changes to the information may occur, as incident information is refined. While the Board of Police Commissioners of Kansas City, Missouri (Board) makes every effort to maintain and distribute accurate information, no warranties and/or representations of any kind are made regarding information, data or services provided. The Board is not responsible for misinterpretation of this information and makes no inference or judgment as to the relative safety to any particular area or neighborhood. In no event shall the Board be liable in any way to the users of this data. Users of this data shall hold the Board harmless in all matters and accounts arising from the use and/or accuracy of this data.

This statistic shows the crime severity index value of metropolitan areas in Canada in 2023. As of 2023, the crime severity index in Saskatoon, Saskatchewan, stood at 116.31.

***Starting on March 7th, 2024, the Los Angeles Police Department (LAPD) will adopt a new Records Management System for reporting crimes and arrests. This new system is being implemented to comply with the FBI's mandate to collect NIBRS-only data (NIBRS — FBI - https://www.fbi.gov/how-we-can-help-you/more-fbi-services-and-information/ucr/nibrs). During this transition, users will temporarily see only incidents reported in the retiring system. However, the LAPD is actively working on generating new NIBRS datasets to ensure a smoother and more efficient reporting system. *** **Update 1/18/2024 - LAPD is facing issues with posting the Crime data, but we are taking immediate action to resolve the problem. We understand the importance of providing reliable and up-to-date information and are committed to delivering it. As we work through the issues, we have temporarily reduced our updates from weekly to bi-weekly to ensure that we provide accurate information. Our team is actively working to identify and resolve these issues promptly. We apologize for any inconvenience this may cause and appreciate your understanding. Rest assured, we are doing everything we can to fix the problem and get back to providing weekly updates as soon as possible. ** This dataset reflects incidents of crime in the City of Los Angeles dating back to 2020. This data is transcribed from original crime reports that are typed on paper and therefore there may be some inaccuracies within the data. Some location fields with missing data are noted as (0°, 0°). Address fields are only provided to the nearest hundred block in order to maintain privacy. This data is as accurate as the data in the database. Please note questions or concerns in the comments.

Incident-based crime statistics (actual incidents, rate per 100,000 population, percentage change in rate, unfounded incidents, percent unfounded, total cleared, cleared by charge, cleared otherwise, persons charged, adults charged, youth charged / not charged), by detailed violations (violent, property, traffic, drugs, other Federal Statutes), police services in Ontario, 1998 to 2024.

Incident-based crime statistics (actual incidents, rate per 100,000 population, percentage change in rate, unfounded incidents, percent unfounded, total cleared, cleared by charge, cleared otherwise, persons charged, adults charged, youth charged / not charged), by detailed violations (violent, property, traffic, drugs, other Federal Statutes), Canada, provinces, territories, Census Metropolitan Areas and Canadian Forces Military Police, 1998 to 2024.

This dataset consists of gun violence within Jefferson county that may fall within LMPDs radar, including non-fatal shootings, homicides, as well as shot-spotter data. The mapping data points where there are victims have been obfuscated to maintain privacy, while still being accurate enough to be placed in its correct boundaries, particularly around, neighborhoods, ZIP Codes, Council districts, and police divisions. The data also excludes any victim information that could be used to identify any individual. this data is used to make the public aware of what is going on in their communities. The data consists of only criminal incidents, excluding any cases that are deemed non-criminal.Field NameField DescriptionCase numberPolice report number. For ShotSpotter detections, it is the ShotSpotter ID.DateTimeDate and time in which the original incident occurred. Time is rounded down.AddressAddress rounded down to the one hundred block of where the initial incident occured. Unless it is an intersection.NeighborhoodNeighborhood in which the original incident occurred.Council DistrictCouncil district in which the original incident occurred.LatitudeLatitude coordinate used to map the incidentLongitudeLongitude coordinate used to map the incidentZIP CodeZIP Code in which the original incident occurred.Crime Typea distinction between incidents, whether it is a non-fatal shooting, homicide, or a ShotSpotter detection.CauseUsed to differentiate on the cause of death for homicide victims.SexGender of the victim of the initial incident.RaceRace/Ethnicity of the victim in a given incident.Age GroupCategorized age groups used to anonymize victim information.Division NamePolice division or department where the initial incident occurred.Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities, unless LMPD becomes involved in smaller agency incident.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.Contact:Ivan Benitez, Ph.D.Gun Violence Data FellowOffice for Safe and Healthy Neighborhoodsivan.benitez@louisvilleky.gov

Version 4 release notes:I am retiring this dataset - please do not use it. The reason that I made this dataset is that I had seen a lot of recent articles using the NACJD version of the data and had several requests that I make a concatenated version myself. This data is heavily flawed as noted in the excellent Maltz & Targonski's (2002) paper (see PDF available to download here and important paragraph from that article below) and I was worried that people were using the data without considering these flaws. So the data available here had the warning below this section (originally at the top of these notes so it was the most prominent thing) and had the Maltz & Targonski PDF included in the zip file so people were aware of it. There are two reasons that I am retiring it. First, I see papers and other non-peer reviewed reports still published using this data without addressing the main flaws noted by Maltz and Targonski. I don't want to have my work contribute to research that I think is fundamentally flawed. Second, this data is actually more flawed that I originally understood. The imputation process to replace missing data is based off of a bad design, and Maltz and Targonski talk about this in detail so I won't discuss it too much. The additional problem is that the variable that determines whether an agency has missing data is fatally flawed. That variable is the "number_of_months_reported" variable which is actually just the last month reported. So if you only report in December it'll have 12 months reported instead of 1. So even a good imputation process will be based on such a flawed measure of missingness that it will be wrong. How big of an issue is this? At the moment I haven't looked into it in enough detail to be sure but it's enough of a problem that I no longer want to release this kind of data (within the UCR data there are variables that you can use to try to determine the actual number of months reported but that stopped being useful due to a change in the data in 2018 by the FBI. And even that measure is not always accurate for years before 2018.).!!! Important Note: There are a number of flaws in the imputation process to make these county-level files. Included as one of the files to download (and also in every zip file) is Maltz & Targonski's 2002 paper on these flaws and why they are such an issue. I very strongly recommend that you read this paper in its entirety before working on this data. I am only publishing this data because people do use county-level data anyways and I want them to know of the risks. Important Note !!!The following paragraph is the abstract to Maltz & Targonski's paper: County-level crime data have major gaps, and the imputation schemes for filling in the gaps are inadequate and inconsistent. Such data were used in a recent study of guns and crime without considering the errors resulting from imputation. This note describes the errors and how they may have affected this study. Until improved methods of imputing county-level crime data are developed, tested, and implemented, they should not be used, especially in policy studies.Version 3 release notes: Adds a variable to all data sets indicating the "coverage" which is the proportion of the agencies in that county-year that report complete data (i.e. that aren't imputed, 100 = no imputation, 0 = all agencies imputed for all months in that year.). Thanks to Dr. Monica Deza for the suggestion. The following is directly from NACJD's codebook for county data and is an excellent explainer of this variable.The Coverage Indicator variable represents the proportion of county data that is reported for a given year. The indicator ranges from 0 to 100. A value of 0 indicates that no data for the county were reported and all data have been imputed. A value of 100 indicates that all ORIs in the county reported for all 12 months in the year. Coverage Indicator is calculated as follows: CI_x = 100 * ( 1 - SUM_i { [ORIPOP_i/COUNTYPOP] * [ (12 - MONTHSREPORTED_i)/12 ] } ) where CI = Coverage Indicator x = county i = ORI within countyReorders data so it's sorted by year then county rather than vice versa as before.Version 2 release notes: Fixes bug where Butler University (ORI = IN04940) had wrong FIPS state and FIPS state+county codes from the LEAIC crosswa

Basic Metadata Note: Assault deaths are also known as Homicides.

*Rates per 100,000 population. Age-adjusted rates per 100,000 2000 US standard population.

**Blank Cells: Rates not calculated for fewer than 5 events. Rates not calculated in cases where zip code is unknown.

***API: Asian/Pacific Islander. ***AIAN: American Indian/Alaska Native.

Prepared by: County of San Diego, Health & Human Services Agency, Public Health Services, Community Health Statistics Unit, 2019.

Code Source: ICD-9CM - AHRQ HCUP CCS v2015. ICD-10CM - AHRQ HCUP CCS v2018. ICD-10 Mortality - California Department of Public Health, Group Cause of Death Codes 2013; NHCS ICD-10 2e-v1 2017.

Data Guide, Dictionary, and Codebook: https://www.sandiegocounty.gov/content/dam/sdc/hhsa/programs/phs/CHS/Community%20Profiles/Public%20Health%20Services%20Codebook_Data%20Guide_Metadata_10.2.19.xlsx