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.

Interactive dashboard for open data portal. Displays crimes by zip code.

***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.

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.

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 Name

Field Description

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 Occurred

the date the incident actually occurred

Badge ID

Badge ID of responding Officer

Offense Classification

NIBRS Reporting category for the criminal act committed

Offense Code Name

NIBRS Reporting code for the criminal act committed

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

NIBRS Group

hierarchy that follows the guidelines of the FBI National Incident Based Reporting System

Was Offense Completed

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

Location Category

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

Contact:LMPD Open Records lmpdopenrecords@louisvilleky.gov

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

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).

Content

Data is a culmination of separate csv files found at https://data.louisvilleky.gov/dataset/crime-data

Each row represents a reported crime

The following description is from https://data.louisvilleky.gov/dataset/crime-data:

DATE_REPORTED - the date the incident was reported to LMPD

DATE_OCCURED - the date the incident actually occurred

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

Acknowledgements

Thank you to Louisville OPEN DATA!

https://data.louisvilleky.gov/dataset/crime-data

Inspiration

Which crimes are most common? In which zip codes is crime more likely to occur? Is there a trend of some crimes increasing and other decreasing in number? Which crimes take longest to report? Which beats handle the most homicides?

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 dataset is a filtered view of LASD-published year-to-date crime data for the City of West Hollywood, updated monthly. It is presented in its raw format and is completely unaltered.

Please contact the Los Angeles Sheriff's Department with any questions regarding the underlying data.

Incident Date = Date the crime incident occurred Incident Reported Date = Date the crime was reported to LASD Category = Incident crime category Stat = A three digit numerical coding system to identify the primary crime category for an incident Stat Desc = The definition of the statistical code number Address (last two digits of # rounded to 00) = The street number, street name, state and zip where the incident occurred Street (last two digits of # rounded to 00) = The street number and street name where the incident occurred City = The city where the incident occurred Zip = The zip code of the location where the incident occurred Incident ID = The URN #, or Uniform Report Number, is a unique # assigned to every criminal and noncriminal incident Reporting District = A geographical area defined by LASD which is within a city or unincorporated area where the incident occurred Seq = Each incident for each station is issued a unique sequence # within a given year Gang Related = Indicates if the crime incident was gang related (column added 08/02/2012) Unit ID = ORI # is a number issued by the FBI for every law enforcement agency Unit Name = Station Name Longitude (truncated to 3 decimals, equivalent to half-block rounding) (column added 01/04/2021) Latitude (truncated to 3 decimals, equivalent to half-block rounding) (column added 01/04/2021) Part Category = Part I Crime or Part II Crime indicator (replaced DELETED column 01/04/2021)

This map shows the total crime index in the U.S. in 2020 in a multi-scale map (by state, county, ZIP Code, tract, and block group). 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 indicesThe values are all referenced by an index value. The index values for the US level are 100, representing average crime for the country. A value of more than 100 represents higher crime than the national average, and a value of less than 100 represents lower crime than the national average. For example, an index of 120 implies that crime in the area is 20 percent higher than the US average; an index of 80 implies that crime is 20 percent lower than the US average.Additional Esri Resources:Esri DemographicsU.S. 2020/2025 Esri Updated DemographicsEssential demographic vocabularyEsri's arcgis.com demographic map layersPermitted use of this data is covered in the DATA section of the Esri Master Agreement (E204CW) and these supplemental terms.

Esri's Crime Indexes data incorporates information from the AGS national CrimeRisk database that is based on an extensive analysis of several years of crime incidents reported by most US law enforcement jurisdictions. The Crime Indexes database includes standardized indexes for a range of serious crimes against both persons and property. The data vintage is 2019. All attributes are available at the following geography levels: State, County, Tract, Block Group, ZIP Code, Place, CBSA and DMA. Attributes include total crime index, personal crime index, and other indexes for serious crimes. To view ArcGIS Online items using this service, including the terms of use, visit http://goto.arcgisonline.com/demographics5/USA_Crime.

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

The Division of Criminal Justice Services (DCJS) collects crime reports from more than 500 New York State police and sheriffs' departments. DCJS compiles these reports as New York's official crime statistics and submits them to the FBI under the National Uniform Crime Reporting (UCR) Program. UCR uses standard offense definitions to count crime in localities across America regardless of variations in crime laws from state to state. In New York State, law enforcement agencies use the UCR system to report their monthly crime totals to DCJS. The UCR reporting system collects information on seven crimes classified as Index offenses which are most commonly used to gauge overall crime volume. These include the violent crimes of murder/non-negligent manslaughter, forcible rape, robbery, and aggravated assault; and the property crimes of burglary, larceny, and motor vehicle theft. Police agencies may experience reporting problems that preclude accurate or complete reporting. The counts represent only crimes reported to the police but not total crimes that occurred. DCJS posts preliminary data in the spring and final data in the fall.

Web app displaying 2021-YTD NIBRS crime data. Data is included for all areas that the St. Louis County Police Department and the St. Louis County Park Rangers patrol. Additionally, data is included for the following police departments in St. Louis County: Ballwin, Bel Nor, Bel Ridge, Bella Villa, Bellefontaine Neighbors, Breckenridge Hills, Brentwood, Bridgeton, Country Club Hills, Chesterfield, Clayton, Crestwood, Creve Coeur, Des Peres, Ellisville, Eureka, Frontenac, Hillsdale, Kirkwood, Ladue, Lakeshire, Moline Acres, Maplewood, Normandy, Olivette, Overland, Pagedale, Riverview, Richmond Heights, Rock Hill, Saint Louis County, Shrewsbury, St. John, Sunset Hills, Town & Country, Velda City, Webster Groves, and Woodson Terrace.The data in this map should not be compared to previous UCR Part 1 crime data provided by the department. NIBRS data is counted differently, and comparisons made between the data will not be accurate.

The data are provided are the Maryland Statistical Analysis Center (MSAC), within the Governor's Office of Crime Control and Prevention (GOCCP). MSAC, in turn, receives these data from the Maryland State Police's annual Uniform Crime Reports.

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

Much research has examined how crime rates vary across urban neighborhoods, focusing particularly on community-level demographic and social characteristics. A parallel line of work has treated crime at the individual level as an expression of certain behavioral patterns (e.g., impulsivity). Little work has considered, however, whether the prevalence of such behavioral patterns in a neighborhood might be predictive of local crime, in large part because such measures are hard to come by and often subjective. The Facebook Advertising API offers a special opportunity to examine this question as it provides an extensive list of “interests” that can be tabulated at various geographic scales. Here we conduct an analysis of the association between the prevalence of interests among the Facebook population of a ZIP code and the local rate of assaults, burglaries, and robberies across 9 highly populated cities in the US. We fit various regression models to predict crime rates as a function of the Facebook and census demographic variables. In general, models using the variables for the interests of the whole adult population on Facebook perform better than those using data on specific demographic groups (such as Males 18-34). In terms of predictive performance, models combining Facebook data with demographic data generally have lower error rates than models using only demographic data. We find that interests associated with media consumption and mating competition are predictive of crime rates above and beyond demographic factors. We discuss how this might integrate with existing criminological theory.

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