Visit the interactive Crime Mapping Tool and prepare your own tailored crime report showing the latest maps, graphs and data on crimes, victims and offenders in NSW LGAs, suburbs or postcodes.

*Note: prior to June 2021 there were three additional crime tools available providing data for Local Government Areas on crime trends, crimes by premises and LGA crime rankings. These tools are no longer supported; this information is available in the Crime Mapping Tool.

CrimeMapping.com allows citizens to query and map recent crimes and incidents within the City’s borders. Crime data is extracted on a regular basis from each department's records system so that the information being viewed through a Web browser is the most current available.

This dataset reflects reported incidents of crime that have occurred in the City of Chicago over the past year, minus the most recent seven days of data. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at 312.745.6071 or RandD@chicagopolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited.

The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. Any use of the information for commercial purposes is strictly prohibited. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data is updated daily.

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.

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

In 2023, the District of Columbia had the highest reported violent crime rate in the United States, with 1,150.9 violent crimes per 100,000 of the population. Maine had the lowest reported violent crime rate, with 102.5 offenses per 100,000 of the population. Life in the District The District of Columbia has seen a fluctuating population over the past few decades. Its population decreased throughout the 1990s, when its crime rate was at its peak, but has been steadily recovering since then. While unemployment in the District has also been falling, it still has had a high poverty rate in recent years. The gentrification of certain areas within Washington, D.C. over the past few years has made the contrast between rich and poor even greater and is also pushing crime out into the Maryland and Virginia suburbs around the District. Law enforcement in the U.S. Crime in the U.S. is trending downwards compared to years past, despite Americans feeling that crime is a problem in their country. In addition, the number of full-time law enforcement officers in the U.S. has increased recently, who, in keeping with the lower rate of crime, have also made fewer arrests than in years past.

This dataset reflects reported incidents of crime (with the exception of murders where data exists for each victim) that occurred in the City of Chicago from 2001 to present, minus the most recent seven days. Data is extracted from the Chicago Police Department's CLEAR (Citizen Law Enforcement Analysis and Reporting) system. In order to protect the privacy of crime victims, addresses are shown at the block level only and specific locations are not identified. Should you have questions about this dataset, you may contact the Research & Development Division of the Chicago Police Department at 312.745.6071 or RandD@chicagopolice.org. Disclaimer: These crimes may be based upon preliminary information supplied to the Police Department by the reporting parties that have not been verified. The preliminary crime classifications may be changed at a later date based upon additional investigation and there is always the possibility of mechanical or human error. Therefore, the Chicago Police Department does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information and the information should not be used for comparison purposes over time. The Chicago Police Department will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. All data visualizations on maps should be considered approximate and attempts to derive specific addresses are strictly prohibited. The Chicago Police Department is not responsible for the content of any off-site pages that are referenced by or that reference this web page other than an official City of Chicago or Chicago Police Department web page. The user specifically acknowledges that the Chicago Police Department is not responsible for any defamatory, offensive, misleading, or illegal conduct of other users, links, or third parties and that the risk of injury from the foregoing rests entirely with the user. The unauthorized use of the words "Chicago Police Department," "Chicago Police," or any colorable imitation of these words or the unauthorized use of the Chicago Police Department logo is unlawful. This web page does not, in any way, authorize such use. Data is updated daily Tuesday through Sunday. The dataset contains more than 65,000 records/rows of data and cannot be viewed in full in Microsoft Excel. Therefore, when downloading the file, select CSV from the Export menu. Open the file in an ASCII text editor, such as Wordpad, to view and search. To access a list of Chicago Police Department - Illinois Uniform Crime Reporting (IUCR) codes, go to http://data.cityofchicago.org/Public-Safety/Chicago-Police-Department-Illinois-Uniform-Crime-R/c7ck-438e

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

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

This study was designed to develop crime forecasting as an application area for police in support of tactical deployment of resources. Data on crime offense reports and computer aided dispatch (CAD) drug calls and shots fired calls were collected from the Pittsburgh, Pennsylvania Bureau of Police for the years 1990 through 2001. Data on crime offense reports were collected from the Rochester, New York Police Department from January 1991 through December 2001. The Rochester CAD drug calls and shots fired calls were collected from January 1993 through May 2001. A total of 1,643,828 records (769,293 crime offense and 874,535 CAD) were collected from Pittsburgh, while 538,893 records (530,050 crime offense and 8,843 CAD) were collected from Rochester. ArcView 3.3 and GDT Dynamap 2000 Street centerline maps were used to address match the data, with some of the Pittsburgh data being cleaned to fix obvious errors and increase address match percentages. A SAS program was used to eliminate duplicate CAD calls based on time and location of the calls. For the 1990 through 1999 Pittsburgh crime offense data, the address match rate was 91 percent. The match rate for the 2000 through 2001 Pittsburgh crime offense data was 72 percent. The Pittsburgh CAD data address match rate for 1990 through 1999 was 85 percent, while for 2000 through 2001 the match rate was 100 percent because the new CAD system supplied incident coordinates. The address match rates for the Rochester crime offenses data was 96 percent, and 95 percent for the CAD data. Spatial overlay in ArcView was used to add geographic area identifiers for each data point: precinct, car beat, car beat plus, and 1990 Census tract. The crimes included for both Pittsburgh and Rochester were aggravated assault, arson, burglary, criminal mischief, misconduct, family violence, gambling, larceny, liquor law violations, motor vehicle theft, murder/manslaughter, prostitution, public drunkenness, rape, robbery, simple assaults, trespassing, vandalism, weapons, CAD drugs, and CAD shots fired.

Crime data from years prior to the current one. 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

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

In 2023, the state with the highest crime rate in the United States per 100,000 inhabitants was New Mexico. That year, the crime rate was ******** crimes per 100,000 people. In comparison, New Hampshire had the lowest crime rate at ****** crimes per 100,000 people. Crime rate The crime rate in the United States has generally decreased over time. There are several factors attributed to the decrease in the crime rate across the United States. An increase in the number of police officers and an increase in income are some of the reasons for a decrease in the crime rate. Unfortunately, people of color have been disproportionately affected by crime rates, as they are more likely to be arrested for a crime versus a white person. Crime rates regionally The District of Columbia had the highest rate of reported violent crimes in the United States in 2023 per 100,000 inhabitants. The most common crime clearance type in metropolitan counties in the United States in 2020 was murder and non-negligent manslaughter. The second most dangerous city in the country in 2020 was Detroit. Detroit has faced severe levels of economic and demographic declines in the past years. Not only has the population decreased, the city has filed for bankruptcy. Despite the median household income increasing, the city still struggles financially.

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

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

Description Crime incidents starting with those reported in 2016. The data provided is the latest available information and is updated regularly as statistics change. For access to comprehensive reports, kindly submit a public record request here.Note: Crimes that occurred before 2016 are included if the date reported was in 2016 or later.

Disclaimer: The City strives to provide the highest-quality information on this platform. The content on this website is provided as a public service, on an ‘as is’ basis. The City makes no warranty, representation, or guarantee of any type as to the content, accuracy, timeliness, completeness, or fitness for any particular purpose or use of any public data provided on this portal; nor shall any such warranty be implied, including, without limitation, the implied warranties of merchantability and fitness for a particular purpose. The City assumes no liability by making data available to the public or other departments.This dataset is featured in the following app(s): Cleveland Division of Police Crime DashboardCrime Incidents MapData GlossarySee the Attributes section below for details about each column in this dataset.Update Frequency Daily around 8 AM EST

Contacts

 City of Cleveland, Division of Police

The URL provided here links to the LexisNexis Community Crime Map viewer. This is an external website not produced by the City of Vancouver; crime data is submitted by the Vancouver Police Department and other local area law enforcement agencies and is meant for public information.NOTE: This product and the information shown is provided "AS IS" and exists for informational purposes only. The City of Vancouver (COV) makes no warranties regarding the accuracy of such data. This product and information is not prepared, nor is suitable, for legal, engineering, or surveying purposes. Any sale, reproduction or distribution of this information, or products derived therefrom, in any format is expressly prohibited. Data are provided by multiple sources and subject to change without notice.

Disclaimer: Crime Responses is provided by the Gainesville Police Department (GPD) to document initial details surrounding an incident to which GPD officers respond. This dataset contains crime incidents from 2011 to present and includes a reduced set of fields focused on capturing the type of incident as well when and where an incident occurred. The Incident location addresses have been rounded off and are not the exact location due to the constitutional amendment known as "Marsy's Law".

In 2021, Florida reporting of crime data began a transition from Summary Reporting System (SRS) to National Incident-Based Reporting System (NIBRS), causing an effect on crime statistics reported by Law Enforcement Agencies such as the Gainesville Police Department who made this transition on November 16, 2021. The effect would be an increase in crime due to the elimination of the SRS Hierarchy Rule which collected only the most serious offense in an incident while NIBRS will now capture up to 10 offenses per incident and specifies more offense categories than SRS. The inclusion of these crimes, particularly property crimes, will reflect an increase in crime when switching from SRS reporting to NIBRS' reporting. The apparent increase (usually not greater than 2.7%) is simply due to the difference between how crimes are counted in NIBRS versus the SRS and its application of the Hierarchy Rule. More information regarding NIBRS effect on crime statistics can be found on the following link: https://ucr.fbi.gov/nibrs/2014/resource-pages/effects_of_nibrs_on_crime_statistics_final.pdf.

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.

Colombia crime rate per 100K population for 2021 was 27.48, a 13.37% increase from 2020.

<ul style='margin-top:20px;'>

<li>Colombia crime rate per 100K population for 2020 was <strong>24.24</strong>, a <strong>5.87% decline</strong> from 2019.</li>
<li>Colombia crime rate per 100K population for 2019 was <strong>25.75</strong>, a <strong>1.82% decline</strong> from 2018.</li>
<li>Colombia crime rate per 100K population for 2018 was <strong>26.23</strong>, a <strong>3.13% increase</strong> from 2017.</li>
</ul>Intentional homicides are estimates of unlawful homicides purposely inflicted as a result of domestic disputes, interpersonal violence, violent conflicts over land resources, intergang violence over turf or control, and predatory violence and killing by armed groups. Intentional homicide does not include all intentional killing; the difference is usually in the organization of the killing. Individuals or small groups usually commit homicide, whereas killing in armed conflict is usually committed by fairly cohesive groups of up to several hundred members and is thus usually excluded.