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.

The crime rate in London was 106.4 crime offences per thousand people for the 2024/25 reporting year, compared with 105.8 in the previous year. Between 2015/16 and 2019/20, the crime rate in the UK capital increased in every reporting year. The sudden drop in 2019/20 was due to the COVID-19 pandemic causing a sharp reduction in certain types of crime, such as robbery and theft. Crime patterns in the capital Overall there were 951,803 crimes reported by the police in London in 2024/25, compared with 938,020 in the previous reporting year. Types of crime that have increased recently include violent crimes, shoplifting, and theft from the person offences. One positive is that the number of homicide offences in London has fallen to much lower levels than seen in the late 2010s. Additionally, the Metropolitan Police force area has a lower crime rate than many of the UK's other major police forces, such as West Yorkshire, Greater Manchester, and South Yorkshire. Police recruitment drive ends era of cuts  The rise in crime in London happened alongside a decline in both personnel and funding for the London Metropolitan Police. Compared with 2010 for example, there were around 3,000 fewer police officers in 2018, while annual funding was reduced to around 3.3 billion pounds between 2013/14 and 2018/19, compared with 3.62 billion in 2012/13. These cuts were due to the policy of austerity that was implemented by the UK government during that time period, but this has recently been replaced by pledges to increase spending and to recruit more police. In 2024/25, the budget for the Metropolitan Police was over five billion pounds, while the number of officers in 2024 increased to around 35,310.

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

Numbers of recorded offences, and rates of offences per thousand population, by broad crime grouping, by financial year and borough. Rate is given as per thousand population, and are calculated using mid-year population from the first part of the financial year eg For Financial year 2008-09, mid-year estimates for 2008 are used. Offences: These are confirmed reports of crimes being committed. All data relates to "notifiable offences" - which are designated categories of crimes that all police forces in England and Wales are required to report to the Home Office Crime rates are not available for Heathrow due to no population figures There were changes to the police recorded crime classifications from April 2012. Therefore caution should be used when comparing sub-groups of crime figures from 2012/13 with earlier years. Action Fraud have taken over the recording of fraud offences on behalf of individual police forces. This process began in April 2011 and was rolled out to all police forces by March 2013. Due to this change caution should be applied when comparing data over this transitional period and with earlier years. Link to data on Met Police website. Crime stats on ONS website

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

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.

There were ******* crimes recorded by the Metropolitan Police in London in 2024/25, the most of any police force area in England and Wales. Greater Manchester Police reported ******* crimes, while West Midlands police recorded *******, making these police forces the second and third-highest in terms of crime recorded.

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.

There were ******* violent crime offences recorded by the Metropolitan Police and City of London Police Forces in London in 2024/25, a decrease when compared with the previous reporting year. From a low of ******* violent crimes in 2015/16, violent crime has increased almost every year. This reflects a pattern of increasing violent crime replicated across England and Wales as a whole, with a peak of *** million offences reported in 2022/23. Overall offences also rising The overall crime figures for London also show a trend of increasing crime in the UK capital. In 2015/16 for example, there were ******* crimes recorded in London, compared to ******* in 2024/25. This follows a similar pattern seen in England and Wales, which has witnessed an uptick in crime after reaching historic lows in the mid-2010s. In 2013/14 for example, there were approximately ** crimes per 100,000 people in England and Wales, compared with *****in 2024/25. By contrast, in Scotland, and in Northern Ireland, crimes rates have remained broadly similar to the mid-2010s. Police budgets rising again Due to the austerity policies enacted by UK governments in the 2010s, the amount the UK government spent on the police was effectively frozen between 2013/14 and 2016/17. This policy has since been reversed, with the overall UK police budget reaching **** billion pounds in 2024/25, compared with 16.4 billion in 2016/17. The amount budgeted for the Metropolitan Police by the Mayor of London for 2025/26 was **** billion British pounds, a significant increase on the **** billion budgeted in 2018/19, but slightly lower than in 2024/25.

Crime Rates of offences per thousand population, by broad crime grouping, by financial year for wards. Offences: These are confirmed reports of crimes being committed. All data relates to "notifiable offences" - which are designated categories of crimes that all police forces in England and Wales are required to report to the Home Office. Ward data should not be aggregated to give a borough or London total. This is because a small percentage (less than 5%) of crimes in this dataset have not been geocoded to a ward. Therefore total numbers and rates are indicative only, and are not an exact measure at ward level. The rate is calculated using ward GLA 2012-based (SHLAA) population projections, and population data calculated and constrained to 2012 Borough (SHLAA) projections. The London figure only includes the Met Police area, not the City of London. The London total includes all offences in the Met Police Area including those that could not be geocoded. Therefore the London total will not equal the sum of the wards. Some ward boundaries changed in 2014. From 2013/14 the data shown is for the new boundaries. This only affects Hackney, Kensington and Chelsea, and Tower Hamlets. From 2013/14, the numbers and rates for 2013 ward boundaries in Hackney, K&C and Tower Hamlets, have all been modelled based on the proportion of population living in each area at the 2011 Census. Action Fraud have taken over the recording of fraud offences on behalf of individual police forces. This process began in April 2011 and was rolled out to all police forces by March 2013. Due to this change caution should be applied when comparing data over this transitional period and with earlier years. Data by detailed crime group and month are available from the MPS website .

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

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

As part of the quarterly release of Crime data and trends by the Office for National Statistics, data is released aggregated at police force level for the most recent rolling 12 months. The below interactive infographic allows you to click through the key crime indicators assessed to see how London (the Metropolitan Police Service) is performing compared to the rest of the country (using the same data from 12 months previously). Also included are the key performing London boroughs in each indicator during the period covered.

***In January 2020, as part of implementing a new citywide police incident reporting system the City began moving away from reporting crime to the FBI Unified Crime Reporting (UCR) Program and instead to the new National Incident-Based Reporting System (NIBRS) format. For this reason, 2020 UCR data may have inconsistencies and/or inaccuracies. A filtered view of UCR data is available for 2011-2019 at https://citydata.mesaaz.gov/Police/Crime-Reporting-Statistics-Uniform-Crime-Reporting/bfen-qa5d

As of January 1, 2021, the National Incident-Based Reporting System (NIBRS) became the national crime data collection program. NIBRS was implemented to improve the overall quality of crime data collected by law enforcement, by capturing details on each single crime incident, as well as on separate offenses within the same incident. The historic Summary Reporting System (SRS) data collection, which collects more limited information than the more robust NIBRS, was phased out to make Uniform Crime Reporting (UCR) a NIBRS-only data collection.

Coming soon, look for a new dataset based on NIBRS, which will provide more complete and comprehensive data for law enforcement, researchers, and the public.

The Uniform Crime Reporting Program collects statistics on the number of offenses known to City of Mesa Police Department. Address and Location data are not exact location of incidents and have been rounded to nearest hundred block. Lat/Long are approximations only based on rounded hundred block. Part 1 offenses are reported monthly and are chosen by the Federal Bureau of Investigation (FBI) because they are serious crimes, they occur with regularity in all areas of the country, and they are likely to be reported to police. Part I offenses are defined as: Criminal homicide, Forcible Rape, Robbery, Aggravated Assault, Burglary (breaking or entering), Larceny-theft (except motor vehicle theft), Motor vehicle theft and Arson.

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

• Knife Crime (and SDR) - Knife Crime with Injury - Gun Crime (and SDR) - Gun Crime with firearm discharged - Gang violence indicator - Dog Attacks (and SDR) - Homicide - Sexual Offences - Burglary (all) - Burglary (residential) - Robbery (all) - Theft & Handling - Theft from Person* - Theft of Motor Vehicle* - Theft from Motor Vehicle* - Criminal Damage* - Domestic Offences - Homophobic Hate Victims

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