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

FILE DESCRIPTION

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

COLUMN DESCRIPTION

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

FILE DESCRIPTION

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

COLUMN DESCRIPTION

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

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

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

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

Photo by David von Diemar on Unsplash

The data provided in this dataset is preliminary in nature and may have not been investigated by a detective at the time of download. The data is therefore subject to change after a complete investigation. This data represents only calls for police service where a police incident report was taken. Due to the variations in local laws and ordinances involving crimes across the nation, whether another agency utilizes Uniform Crime Report (UCR) or National Incident Based Reporting System (NIBRS) guidelines, and the results learned after an official investigation, comparisons should not be made between the statistics generated with this dataset to any other official police reports. Totals in the database may vary considerably from official totals following the investigation and final categorization of a crime. Therefore, the data should not be used for comparisons with Uniform Crime Report or other summary statistics.Data is broken out by year into separate CSV files. Note the file grouping by year is based on the crime's Date Reported (not the Date Occurred).Older cases found in the 2003 data are indicative of cold case research. Older cases are entered into the Police database system and tracked but dates and times of the original case are maintained.Data may also be viewed off-site in map form for just the last 6 months on communitycrimemap.comData Dictionary:Field NameField DescriptionIncident Numberthe number associated with either the incident or used as reference to store the items in our evidence roomsDate Reportedthe date the incident was reported to LMPDDate Occurredthe date the incident actually occurredBadge IDBadge ID of responding OfficerOffense ClassificationNIBRS Reporting category for the criminal act committedOffense Code NameNIBRS Reporting code for the criminal act committedNIBRS_CODEthe code that follows the guidelines of the National Incident Based Reporting System. For more details visit https://ucr.fbi.gov/nibrs/2011/resources/nibrs-offense-codes/viewNIBRS Grouphierarchy that follows the guidelines of the FBI National Incident Based Reporting SystemWas Offense CompletedStatus indicating whether the incident was an attempted crime or a completed crime.LMPD Divisionthe LMPD division in which the incident actually occurredLMPD Beatthe LMPD beat in which the incident actually occurredLocation Categorythe type of location in which the incident occurred (e.g. Restaurant)Block Addressthe location the incident occurredCitythe city associated to the incident block locationZip Codethe zip code associated to the incident block locationContact:LMPD Open Records lmpdopenrecords@louisvilleky.gov

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

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 dataset contains county-level totals for the years 2002-2014 for eight types of crime: murder, rape, robbery, aggravated assault, burglary, larceny, motor vehicle theft, and arson. These crimes are classed as Part I criminal offenses by the United States Federal Bureau of Investigations (FBI) in their Uniform Crime Reporting (UCR) program. Each record in the dataset represents the total of each type of criminal offense reported in (or, in the case of missing data, attributed to) the county in a given year.

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

Attributes/demographics of FBI Uniform Crime Reporting Part I violent crime victims and offenders, updated monthly, aggregated to the CMPD jurisdiction, Neighborhood Profile Area (NPA), and Violent Crime Hotspot (focus areas for the City's violence reduction initiative). Monthly counts cover the time frame Jan-2015 to present. Crime categories comprising violent crime include homicide, rape, robbery, and aggravated assault. Attributes of violent crime victims include counts of domestic violence (DV and Non-DV), age group, gender, and race/ethnicity. Attributes of violent crime offenders include counts of age group, gender, and race/ethnicity.

Dataset highlighting crimes reported to the Albany Police Department for the past year to date geocoded by Neighborhood. It is the same data as Patrol Zone.

For purposes of crime statistics, the FBI Uniform Crime Report Hierarchy Rule requires when more than one offense occurs in an incident the highest priority crime is selected as the primary offense.

Abstract: 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.Purpose: 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. This change was not applied to datasets pre-2020.Supplemental Information: All statistics presented in Crime Cards are based on preliminary DC criminal code offense definitions. The data do not represent official statistics submitted to the FBI under the Uniform Crime Reporting program (UCR) or National Incident Based Reporting System (NIBRS). All preliminary offenses are coded based on DC criminal code and not the FBI offense classifications. Please understand that any comparisons between MPD preliminary data as published on this website and the official crime statistics published by the FBI under the Uniform Crime Reporting Program (UCR) are inaccurate and misleading. The MPD does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information. The MPD will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. Please note that changes to MPD's PSA and police district boundaries occasionally occur. The statistics provided through DC Crime Mapping Application are based on current police boundaries as of January 3, 2017. Sex Assault Data Availability: In an effort to provide more clear information about the most serious sex assaults that are most closely aligned with the public's perception of rape and attempted rape, the most serious sex abuse categories are included in the reports of DC Code Index Violent Crimes: Sex Assault. The figures reported in this category include First Degree Sex Abuse, Second Degree Sex Abuse, Attempted First Degree Sex Abuse and Assault with Intent to Commit First Degree Sex Abuse against adults. Data in this format is available online from 2011. Similar to the other offense data, the sex assault statistics are subject to change due to a variety of reasons, such as a change in classification, the determination that certain offense reports were unfounded, or late reporting. Please understand that any comparisons between MPD preliminary data as published on this website and the official crime statistics published by the FBI under the Uniform Crime Reporting Program (UCR) are inaccurate and misleading. Please also be aware that on Sunday, August 23, 2015, the MPD implemented a new records management system called Cobalt. The offense categories presented within this application have remained the same; however, all statistics are subject to change due to a variety of reasons, such as a change in classification, the determination that certain offense reports were unfounded, or late reporting. All statistics presented in Crime Cards are based on preliminary DC Index crime data reported from 2009 up to a second before midnight today (that's 11:59:59 pm yesterday) . They are compiled based on the date the offense was reported ( Report Date) to the police department. The date and time window of the crime’s occurrence is provided in the See a det

This map shows a comparable measure of crime in the United States. The crime index compares the average local crime level to that of the United States as a whole. An index of 100 is average. A crime index of 120 indicates that crime in that area is 20 percent above the national average.The crime data is provided by Applied Geographic Solutions, Inc. (AGS). AGS created models using the FBI Uniform Crime Report databases as the primary data source and using an initial range of about 65 socio-economic characteristics taken from the 2000 Census and AGS’ current year estimates. The crimes included in the models include murder, rape, robbery, assault, burglary, theft, and motor vehicle theft. The total crime index incorporates all crimes and provides a useful measure of the relative “overall” crime rate in an area. However, these are unweighted indexes, meaning that a murder is weighted no more heavily than a purse snatching in the computations. The geography depicts states, counties, Census tracts and Census block groups. An urban/rural "mask" layer helps you identify crime patterns in rural and urban settings. The Census tracts and block groups help identify neighborhood-level variation in the crime data.------------------------The Civic Analytics Network collaborates on shared projects that advance the use of data visualization and predictive analytics in solving important urban problems related to economic opportunity, poverty reduction, and addressing the root causes of social problems of equity and opportunity. For more information see About the Civil Analytics Network.

All BPD data on Open Baltimore is preliminary data and subject to change. The information presented through Open Baltimore represents Part I victim based crime data. The data do not represent statistics submitted to the FBI's Uniform Crime Report (UCR); therefore any comparisons are strictly prohibited. For further clarification of UCR data, please visit http://www.fbi.gov/about-us/cjis/ucr/ucr. Please note that this data is preliminary and subject to change. Prior month data is likely to show changes when it is refreshed on a monthly basis. All data is geocoded to the approximate latitude/longitude location of the incident and excludes those records for which an address could not be geocoded. Any attempt to match the approximate location of the incident to an exact address is strictly prohibited.

This map shows a comparable measure of crime in the United States. The crime index compares the average local crime level to that of the United States as a whole. An index of 100 is average. A crime index of 120 indicates that crime in that area is 20 percent above the national average.The crime data is provided by Applied Geographic Solutions, Inc. (AGS). AGS created models using the FBI Uniform Crime Report databases as the primary data source and using an initial range of about 65 socio-economic characteristics taken from the 2000 Census and AGS’ current year estimates. The crimes included in the models include murder, rape, robbery, assault, burglary, theft, and motor vehicle theft. The total crime index incorporates all crimes and provides a useful measure of the relative “overall” crime rate in an area. However, these are unweighted indexes, meaning that a murder is weighted no more heavily than a purse snatching in the computations. The geography depicts states, counties, Census tracts and Census block groups. An urban/rural "mask" layer helps you identify crime patterns in rural and urban settings. The Census tracts and block groups help identify neighborhood-level variation in the crime data.------------------------The Civic Analytics Network collaborates on shared projects that advance the use of data visualization and predictive analytics in solving important urban problems related to economic opportunity, poverty reduction, and addressing the root causes of social problems of equity and opportunity. For more information see About the Civil Analytics Network.

All BPD data on Open Baltimore is preliminary data and subject to change. The information presented through Open Baltimore represents Part I victim based crime data. The data do not represent statistics submitted to the FBI's Uniform Crime Report (UCR); therefore any comparisons are strictly prohibited. For further clarification of UCR data, please visit http://www.fbi.gov/about-us/cjis/ucr/ucr. Please note that this data is preliminary and subject to change. Prior month data is likely to show changes when it is refreshed on a monthly basis. All data is geocoded to the approximate latitude/longitude location of the incident and excludes those records for which an address could not be geocoded. Any attempt to match the approximate location of the incident to an exact address is strictly prohibited.

Dataset highlighting arrests by Albany PD Officers for the past year to date GeoCoded by Neighborhood. It is the same data as Arrests by Patrol Zone

For purposes of crime statistics, the FBI Uniform Crime Report Hierarchy Rule requires when more than one offense occurs in an incident the highest priority crime is selected as the primary offense.

🇺🇸 United States English 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

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

Abstract: 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.Purpose: 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. This change was not applied to datasets pre-2020.Supplemental Information: All statistics presented in Crime Cards are based on preliminary DC criminal code offense definitions. The data do not represent official statistics submitted to the FBI under the Uniform Crime Reporting program (UCR) or National Incident Based Reporting System (NIBRS). All preliminary offenses are coded based on DC criminal code and not the FBI offense classifications. Please understand that any comparisons between MPD preliminary data as published on this website and the official crime statistics published by the FBI under the Uniform Crime Reporting Program (UCR) are inaccurate and misleading. The MPD does not guarantee (either expressed or implied) the accuracy, completeness, timeliness, or correct sequencing of the information. The MPD will not be responsible for any error or omission, or for the use of, or the results obtained from the use of this information. Please note that changes to MPD's PSA and police district boundaries occasionally occur. The statistics provided through DC Crime Mapping Application are based on current police boundaries as of January 3, 2017. Sex Assault Data Availability: In an effort to provide more clear information about the most serious sex assaults that are most closely aligned with the public's perception of rape and attempted rape, the most serious sex abuse categories are included in the reports of DC Code Index Violent Crimes: Sex Assault. The figures reported in this category include First Degree Sex Abuse, Second Degree Sex Abuse, Attempted First Degree Sex Abuse and Assault with Intent to Commit First Degree Sex Abuse against adults. Data in this format is available online from 2011. Similar to the other offense data, the sex assault statistics are subject to change due to a variety of reasons, such as a change in classification, the determination that certain offense reports were unfounded, or late reporting. Please understand that any comparisons between MPD preliminary data as published on this website and the official crime statistics published by the FBI under the Uniform Crime Reporting Program (UCR) are inaccurate and misleading. Please also be aware that on Sunday, August 23, 2015, the MPD implemented a new records management system called Cobalt. The offense categories presented within this application have remained the same; however, all statistics are subject to change due to a variety of reasons, such as a change in classification, the determination that certain offense reports were unfounded, or late reporting. All statistics presented in Crime Cards are based on preliminary DC Index crime data reported from 2009 up to a second before midnight today (that's 11:59:59 pm yesterday) . They are compiled based on the date the offense was reported ( Report Date) to the police department. The date and time window of the crime’s occurrence is provided in the See a det

All BPD data on Open Baltimore is preliminary data and subject to change. The information presented through Open Baltimore represents Part I victim based crime data. The data do not represent statistics submitted to the FBI's Uniform Crime Report (UCR); therefore any comparisons are strictly prohibited. For further clarification of UCR data, please visit http://www.fbi.gov/about-us/cjis/ucr/ucr. Please note that this data is preliminary and subject to change. Prior month data is likely to show changes when it is refreshed on a monthly basis. All data is geocoded to the approximate latitude/longitude location of the incident and excludes those records for which an address could not be geocoded. Any attempt to match the approximate location of the incident to an exact address is strictly prohibited.

Portland Crime Data

Accessed directly from Portland Police Bureau's Open Data initiative; compiled from 2015-2023.

Column Info:

Address: Address of reported incident at the 100 block level (e.g.: 1111 SW 2nd Ave would be 1100 Block SW 2nd Ave).

Case Number: The case year and number for the reported incident (YY-######).

Crime Against: Crime against category (Person, Property, or Society).

Neighborhood: Neighborhood where incident occurred. If the neighborhood name is missing, the incident occurred outside of the boundaries of the Portland neighborhoods or at a location that could not be assigned to a specific address in the system. (e.g., Portland, near Washington Park, on the streetcar, etc.).

Occur Date: Date the incident occurred. The exact occur date is sometimes unknown. In most situations, the first possible date the crime could have occurred is used as the occur date. (For example, victims return home from a week-long vacation to find their home burglarized. The burglary could have occurred at any point during the week. The first date of their vacation would be listed as the occur date.)

Occur Time: Time the incident occurred. The exact occur time is sometimes unknown. In most situations, the first possible time the crime could have occurred is used as the occur time. The time is reported in the 24-hour clock format, with the first two digits representing hour (ranges from 00 to 23) and the second two digits representing minutes (ranges from 00 to 59).

Offense Category: Category of offense (for example, Assault Offenses).

Offense Type: Type of offense (for example, Aggravated Assault). Note: The statistic for Homicide Offenses has been updated in the Group A Crimes report to align with the 2019 FBI NIBRS definitions. The statistic for Homicide Offenses includes (09A) Murder & Non-negligent Manslaughter and (09B) Negligent Manslaughter. As of January 1, 2019, the FBI expanded the definition of negligent manslaughter to include traffic fatalities that result in an arrest for driving under the influence, distracted driving, or reckless driving. The change in definition impacts the 2019 homicide offenses statistic and the comparability of 2019 homicide statistics to prior year.

Open Data Lat/Lon: Generalized Latitude / Longitude of the reported incident. For offenses that occurred at a specific address, the point is mapped to the block's midpoint. Offenses that occurred at an intersection is mapped to the intersection centroid.

Open Data X/Y: Generalized XY point of the reported incident. For offenses that occurred at a specific address, the point is mapped to the block's midpoint. Offenses that occurred at an intersection is mapped to the intersection centroid. To protect the identity of victims and other privacy concerns, the points of certain case types are not released. XY points use the Oregon State Plane North (3601), NAD83 HARN, US International Feet coordinate system.

Offense Count: Number of offenses per incident. Offenses (i.e. this field) are summed for counting purposes.

This data represents crime reported to the Seattle Police Department (SPD). Each row contains the record of a unique event where at least one criminal offense was reported by a member of the community or detected by an officer in the field. This data is the same data used in meetings such as SeaStat (https://www.seattle.gov/police/information-and-data/seastat) for strategic planning, accountability and performance management.

These data contain offenses and offense categorization coded to simulate the standard reported to the FBI under the National Incident Based Reporting System (NIBRS) and used to generate Uniform Crime Report (UCR) summary statistics. As these records evolve, daily and are continually refreshed, they will not match official UCR statistics. They represent a more accurate state of the record.

Previous versions of this data set have withheld approximately 40% of crimes. This updated process includes all records of crime reports logged in the Departments Records Management System (RMS) since 2008, which are tracked as part of the SeaStat process. In an effort to safeguard the privacy of our community, offense reports will only be located to the “beat” level. Location specific coordinates will no longer be provided.

Beats are the most granular unit of management used for patrol deployment. To learn more about patrol deployment, please visit: https://www.seattle.gov/police/about-us/about-policing/precinct-and-patrol-boundaries. In addition to the Departments patrol deployment areas, these data contain the “Neighborhood” where the crime occurred, if available. This coding is used to align crime data with the Micro Community Policing Plan (MCPP). For more information see: https://www.seattle.gov/police/community-policing/about-mcpp.

As with any data, certain condition and qualifications apply: 1) These data are refreshed, daily and represent the most accurate, evolved state of the record.

2) Due to quality control processes, these data will lag between 2 and 6 weeks. Most changes will occur within that record and reports logged in the last 2 weeks should be treated as volatile. Analysts may wish to remove these records from their analysis.

3) Not all offenses are reported here, only the primary offense as determined by the “Hierarchy Rule.” For more information on NIBRS and UCR, see the FBI (https://ucr.fbi.gov/nibrs-overview).

4) This dataset contains records of offenses that occurred prior to “go-live” of the existing RMS. Records are queried based on the full population of data and are not constrained by “Occurred Date.”

We invite you to engage these data, ask questions and explore.