Important Note: This item is in mature support as of June 2023 and will be retired in December 2025.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 indicesPermitted use of this data is covered in the DATA section of the EsriMaster Agreement (E204CW) and these supplemental terms.

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

The RAIDS Online system maps crime locations for Lee's Summit, MO. The information can be filtered by date and type of crime.BAIR's public crime map, RAIDS Online, connects law enforcement with the community to reduce crime and improve public safety. Crime mapping helps the public get a better idea of the crime activity in their area so they can make more informed decisions about how to stay safe.RAIDS Online goes beyond crime mapping by automatically alerting the public about recent crime activity and by improving communication between the public and law enforcement through anonymous tips. RAIDS Online empowers the public to make better decisions about crime by putting the same technology used by law enforcement to analyze and interpret crime activity into the hands of the public.

The City of Ferndale uses the service CrimeMapping.com to provide near-live mapping of local crimes, sorted by category. Our goal in providing this information is to reduce crime through a better-informed citizenry. Crime reports older than 180 days can be accessed in this data set. For near-live crime data, go to crimemapping.com. this is a subset of this historic data that has been geocoded to allow for easy analysis and mapping in a different data set. It contains all easily geocoded addresses. A complete CSV file covering all crime reports from 5/2011 to 5/2017 is also available.

Web-Map & App Specifications: Application Name: Crime Mapping - Public ViewerApplication URL: https://arcgis.com/apps/webappviewer/index.html?id=cd5b990f2132430bb2bda1da366f175cWeb-Map Name: Crime Mapping Public Viewer -Web-Map Web Map ID#: id=c5088710b69e40bc89c335e4d4101bbeApp Template: Web-app Builder - Foldable ThemeAudience: External Use - Public ViewersFound on halifax.ca - https://www.halifax.ca/fire-police/police/crime-mappingFind ART, map symbols, logos and splash screen write up at this location. R:\ICT\ICT BIDS\Mapping Services\ArcGIS_Online\Published - Interactive Maps\Crime Mapping

The RMS Crime Incidents dataset consists of crime reports from the Detroit Police Department Records Management System (RMS). This data reflects reported criminal offenses that have occurred in the City of Detroit. Incident-based offense data is extracted from the Detroit Police Department's records management system hourly. This data set contains the most recent data available and is updated anytime DPD sends official crime records contributing to the Michigan Incident Crime Reporting (MICR) or the National Incident Based Reporting systems (reflected by the IBR Date field). It should be noted that some incidents involve the commission of multiple offenses, such as a domestic assault where property was also vandalized. In such cases, there is a row in the dataset for each offense, and the related offenses share a common Crime ID and Report Number.

CrimeStat III is a spatial statistics program for the analysis of crime incident locations, developed by Ned Levine and Associates under the direction of Ned Levine, PhD, that was funded by grants from the National Institute of Justice (grants 1997-IJ-CX-0040, 1999-IJ-CX-0044, 2002-IJ-CX-0007, and 2005-IJ-CX-K037). The program is Windows-based and interfaces with most desktop GIS programs. The purpose is to provide supplemental statistical tools to aid law enforcement agencies and criminal justice researchers in their crime mapping efforts. CrimeStat is being used by many police departments around the country as well as by criminal justice and other researchers. The program inputs incident locations (e.g., robbery locations) in 'dbf', 'shp', ASCII or ODBC-compliant formats using either spherical or projected coordinates. It calculates various spatial statistics and writes graphical objects to ArcGIS, MapInfo, Surfer for Windows, and other GIS packages. CrimeStat is organized into five sections: Data Setup Primary file - this is a file of incident or point locations with X and Y coordinates. The coordinate system can be either spherical (lat/lon) or projected. Intensity and weight values are allowed. Each incident can have an associated time value. Secondary file - this is an associated file of incident or point locations with X and Y coordinates. The coordinate system has to be the same as the primary file. Intensity and weight values are allowed. The secondary file is used for comparison with the primary file in the risk-adjusted nearest neighbor clustering routine and the duel kernel interpolation. Reference file - this is a grid file that overlays the study area. Normally, it is a regular grid though irregular ones can be imported. CrimeStat can generate the grid if given the X and Y coordinates for the lower-left and upper-right corners. Measurement parameters - This page identifies the type of distance measurement (direct, indirect or network) to be used and specifies parameters for the area of the study region and the length of the street network. CrimeStat III has the ability to utilize a network for linking points. Each segment can be weighted by travel time, travel speed, travel cost or simple distance. This allows the interaction between points to be estimated more realistically. Spatial Description Spatial distribution - statistics for describing the spatial distribution of incidents, such as the mean center, center of minimum distance, standard deviational ellipse, the convex hull, or directional mean. Spatial autocorrelation - statistics for describing the amount of spatial autocorrelation between zones, including general spatial autocorrelation indices - Moran's I , Geary's C, and the Getis-Ord General G, and correlograms that calculate spatial autocorrelation for different distance separations - the Moran, Geary, Getis-Ord correlograms. Several of these routines can simulate confidence intervals with a Monte Carlo simulation. Distance analysis I - statistics for describing properties of distances between incidents including nearest neighbor analysis, linear nearest neighbor analysis, and Ripley's K statistic. There is also a routine that assigns the primary points to the secondary points, either on the basis of nearest neighbor or point-in-polygon, and then sums the results by the secondary point values. Distance analysis II - calculates matrices representing the distance between points for the primary file, for the distance between the primary and secondary points, and for the distance between either the primary or secondary file and the grid. 'Hot spot' analysis I - routines for conducting 'hot spot' analysis including the mode, the fuzzy mode, hierarchical nearest neighbor clustering, and risk-adjusted nearest neighbor hierarchical clustering. The hierarchical nearest neighbor hot spots can be output as ellipses or convex hulls. 'Hot spot' analysis II - more routines for conducting hot spot analysis including the Spatial and Temporal Analysis of Crime (STAC), K-means clustering, Anselin's local Moran, and the Getis-Ord local G statistics. The STAC and K-means hot spots can be output as ellipses or convex hulls. All of these routines can simulate confidence intervals with a Monte Carlo simulation. Spatial Modeling Interpolation I - a single-variable kernel density estimation routine for producin

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 https://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.

A map used in the Public Crime Map application.

Web map. Map for St. Louis County and Municipal Crime app.

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.

An ArcGIS Web AppBuilder app used by the public to explore recent crime conditions in their community and create reports for an area of interest.

An interactive public crime mapping application providing DC residents and visitors easy-to-understand data visualizations of crime locations, types and trends across all eight wards. Crime Cards was created by the DC Metropolitan Police Department (MPD) and Office of the Chief Technology Officer (OCTO). Special thanks to the community members who participated in reviews with MPD Officers and IT staff, and those who joined us for the #SaferStrongerSmarterDC roundtable design review. All statistics presented in Crime Cards are based on preliminary DC Index crime data reported from 2009 to midnight of today’s date. They are compiled based on the date the offense was reported (Report Date) to MPD. The application displays two main crime categories: Violent Crime and Property Crime. Violent Crimes include homicide, sex abuse, assault with a dangerous weapon (ADW), and robbery. Violent crimes can be further searched by the weapon used. Property Crimes include burglary, motor vehicle theft, theft from vehicle, theft (other), and arson.CrimeCards collaboration between the Metropolitan Police Department (MPD), the Office of the Chief Technology Officer (OCTO), and community members who participated at the #SafterStrongerSmarterDC roundtable design review.

Crimes & incidents within Sarpy County, NebraskaData current as of the last business day.

The Detroit Police Department provided property and violent crime location data for 2016. Data Driven Detroit aggregated the data up to a block level. Data was obtained for the health and Safety section of Little Caesar's Arena District Needs Assessment.Click here for metadata (descriptions of the fields).

ArcGIS Dashboard allows users to present maps and data in an interactive, dynamic, and intuitive way. It is integrated within the ArcGIS system, so you are ready to use maps and data from your organisation's ArcGIS online or Enterprise.

Locations for crime reporting and investigation in Los Angeles CountyThis dataset is maintained through the County of Los Angeles Location Management System. The Location Management System is used by the County of Los Angeles GIS Program to maintain a single, comprehensive geographic database of locations countywide. For more information on the Location Management System, visithttp://egis3.lacounty.gov/lms/.

This dataset is for RMS Crime Incidents for 2018. For the comprehensive dataset which includes all records please refer to the RMS Crime Incidents dataset. The RMS Crime Incidents dataset consists of crime reports from the Detroit Police Department Records Management System (RMS). This data reflects reported criminal offenses that have occurred in the City of Detroit. Incident-based offense data is extracted from the Detroit Police Department's records management system hourly. This data set contains the most recent data available and is updated anytime DPD sends official crime records contributing to the Michigan Incident Crime Reporting (MICR) or the National Incident Based Reporting systems (reflected by the IBR Date field). It should be noted that some incidents involve the commission of multiple offenses, such as a domestic assault where property was also vandalized. In such cases, there is a row in the dataset for each offense, and the related offenses share a common Crime ID and Report Number.

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

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