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

***Starting on March 7th, 2024, the Los Angeles Police Department (LAPD) will adopt a new Records Management System for reporting crimes and arrests. This new system is being implemented to comply with the FBI's mandate to collect NIBRS-only data (NIBRS — FBI - https://www.fbi.gov/how-we-can-help-you/more-fbi-services-and-information/ucr/nibrs). During this transition, users will temporarily see only incidents reported in the retiring system. However, the LAPD is actively working on generating new NIBRS datasets to ensure a smoother and more efficient reporting system. *** **Update 1/18/2024 - LAPD is facing issues with posting the Crime data, but we are taking immediate action to resolve the problem. We understand the importance of providing reliable and up-to-date information and are committed to delivering it. As we work through the issues, we have temporarily reduced our updates from weekly to bi-weekly to ensure that we provide accurate information. Our team is actively working to identify and resolve these issues promptly. We apologize for any inconvenience this may cause and appreciate your understanding. Rest assured, we are doing everything we can to fix the problem and get back to providing weekly updates as soon as possible. ** This dataset reflects incidents of crime in the City of Los Angeles dating back to 2020. This data is transcribed from original crime reports that are typed on paper and therefore there may be some inaccuracies within the data. Some location fields with missing data are noted as (0°, 0°). Address fields are only provided to the nearest hundred block in order to maintain privacy. This data is as accurate as the data in the database. Please note questions or concerns in the comments.

This map shows the total crime index in the U.S. in 2020 in a multi-scale map (by state, county, ZIP Code, tract, and block group). The pop-up is configured to include the following information for each geography level:Total crime indexPersonal and Property crime indices Sub-categories of personal and property crime indicesThe values are all referenced by an index value. The index values for the US level are 100, representing average crime for the country. A value of more than 100 represents higher crime than the national average, and a value of less than 100 represents lower crime than the national average. For example, an index of 120 implies that crime in the area is 20 percent higher than the US average; an index of 80 implies that crime is 20 percent lower than the US average.Additional Esri Resources:Esri DemographicsU.S. 2020/2025 Esri Updated DemographicsEssential demographic vocabularyEsri's arcgis.com demographic map layersPermitted use of this data is covered in the DATA section of the Esri Master Agreement (E204CW) and these supplemental terms.

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

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

Important Note: This item is in mature support as of June 2023 and will be retired in December 2025.This map shows the total crime index in the U.S. in 2022 in a multi-scale map (by state, county, ZIP Code, tract, and block group). The layer uses 2020 Census boundaries.The pop-up is configured to include the following information for each geography level:Total crime indexPersonal and Property crime indices Sub-categories of personal and property crime indicesPermitted use of this data is covered in the DATA section of the EsriMaster Agreement (E204CW) and these supplemental terms.

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

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

SANDAG provides an annual report on crime in the San Diego region. This dataset contains data from the 2009 through 2022 editions of the report. Data for 2023 is converted from California Incident Based Reporting System (CIBRS) data provided by SANDAG. Additional data comes from Arjis and DOJ OpenJustice. Some data for previous years reports is updated with new editions. "San Diego County" includes all cities and unincorporated areas in San Diego County. "Sheriff - Total" includes the contract cities and the unincorporated area served by the San Diego County Sheriff's Department. California and United States data come from the FBI's Annual Crime Reports.

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

Important Note: This item is in mature support as of July 2022 and will be retired in December 2025. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. This layer uses 2010 Census geographies. This layer shows the total crime index in the U.S. in 2021 in a multi-scale map (by state, county, ZIP Code, tract, and block group). The pop-up is configured to include the following information for each geography level:Personal and Property crime indices Sub-categories of personal and property crime indicesPermitted use of this data is covered in the DATA section of the EsriMaster Agreement (E204CW) and these supplemental terms.

This dataset contains aggregate data on violent index victimizations at the quarter level of each year (i.e., January – March, April – June, July – September, October – December), from 2001 to the present (1991 to present for Homicides), with a focus on those related to gun violence. Index crimes are 10 crime types selected by the FBI (codes 1-4) for special focus due to their seriousness and frequency. This dataset includes only those index crimes that involve bodily harm or the threat of bodily harm and are reported to the Chicago Police Department (CPD). Each row is aggregated up to victimization type, age group, sex, race, and whether the victimization was domestic-related. Aggregating at the quarter level provides large enough blocks of incidents to protect anonymity while allowing the end user to observe inter-year and intra-year variation. Any row where there were fewer than three incidents during a given quarter has been deleted to help prevent re-identification of victims. For example, if there were three domestic criminal sexual assaults during January to March 2020, all victims associated with those incidents have been removed from this dataset. Human trafficking victimizations have been aggregated separately due to the extremely small number of victimizations.

This dataset includes a " GUNSHOT_INJURY_I " column to indicate whether the victimization involved a shooting, showing either Yes ("Y"), No ("N"), or Unknown ("UKNOWN.") For homicides, injury descriptions are available dating back to 1991, so the "shooting" column will read either "Y" or "N" to indicate whether the homicide was a fatal shooting or not. For non-fatal shootings, data is only available as of 2010. As a result, for any non-fatal shootings that occurred from 2010 to the present, the shooting column will read as “Y.” Non-fatal shooting victims will not be included in this dataset prior to 2010; they will be included in the authorized dataset, but with "UNKNOWN" in the shooting column.

The dataset is refreshed daily, but excludes the most recent complete day to allow CPD time to gather the best available information. Each time the dataset is refreshed, records can change as CPD learns more about each victimization, especially those victimizations that are most recent. The data on the Mayor's Office Violence Reduction Dashboard is updated daily with an approximately 48-hour lag. As cases are passed from the initial reporting officer to the investigating detectives, some recorded data about incidents and victimizations may change once additional information arises. Regularly updated datasets on the City's public portal may change to reflect new or corrected information.

How does this dataset classify victims?

The methodology by which this dataset classifies victims of violent crime differs by victimization type:

Homicide and non-fatal shooting victims: A victimization is considered a homicide victimization or non-fatal shooting victimization depending on its presence in CPD's homicide victims data table or its shooting victims data table. A victimization is considered a homicide only if it is present in CPD's homicide data table, while a victimization is considered a non-fatal shooting only if it is present in CPD's shooting data tables and absent from CPD's homicide data table.

To determine the IUCR code of homicide and non-fatal shooting victimizations, we defer to the incident IUCR code available in CPD's Crimes, 2001-present dataset (available on the City's open data portal). If the IUCR code in CPD's Crimes dataset is inconsistent with the homicide/non-fatal shooting categorization, we defer to CPD's Victims dataset.

For a criminal homicide, the only sensible IUCR codes are 0110 (first-degree murder) or 0130 (second-degree murder). For a non-fatal shooting, a sensible IUCR code must signify a criminal sexual assault, a robbery, or, most commonly, an aggravated battery. In rare instances, the IUCR code in CPD's Crimes and Victims dataset do not align with the homicide/non-fatal shooting categorization:

1. In instances where a homicide victimization does not correspond to an IUCR code 0110 or 0130, we set the IUCR code to "01XX" to indicate that the victimization was a homicide but we do not know whether it was a first-degree murder (IUCR code = 0110) or a second-degree murder (IUCR code = 0130).
2. When a non-fatal shooting victimization does not correspond to an IUCR code that signifies a criminal sexual assault, robbery, or aggravated battery, we enter “UNK” in the IUCR column, “YES” in the GUNSHOT_I column, and “NON-FATAL” in the PRIMARY column to indicate that the victim was non-fatally shot, but the precise IUCR code is unknown.

Other violent crime victims: For other violent crime types, we refer to the IUCR classification that exists in CPD's victim table, with only one exception:

1. When there is an incident that is associated with no victim with a matching IUCR code, we assume that this is an error. Every crime should have at least 1 victim with a matching IUCR code. In these cases, we change the IUCR code to reflect the incident IUCR code because CPD's incident table is considered to be more reliable than the victim table.

Note: All businesses identified as victims in CPD data have been removed from this dataset.

Note: The definition of “homicide” (shooting or otherwise) does not include justifiable homicide or involuntary manslaughter. This dataset also excludes any cases that CPD considers to be “unfounded” or “noncriminal.”

Note: In some instances, the police department's raw incident-level data and victim-level data that were inputs into this dataset do not align on the type of crime that occurred. In those instances, this dataset attempts to correct mismatches between incident and victim specific crime types. When it is not possible to determine which victims are associated with the most recent crime determination, the dataset will show empty cells in the respective demographic fields (age, sex, race, etc.).

Note: The initial reporting officer usually asks victims to report demographic data. If victims are unable to recall, the reporting officer will use their best judgment. “Unknown” can be reported if it is truly unknown.

!!!WARNING~~~This dataset has a large number of flaws and is unable to properly answer many questions that people generally use it to answer, such as whether national hate crimes are changing (or at least they use the data so improperly that they get the wrong answer). A large number of people using this data (academics, advocates, reporting, US Congress) do so inappropriately and get the wrong answer to their questions as a result. Indeed, many published papers using this data should be retracted. Before using this data I highly recommend that you thoroughly read my book on UCR data, particularly the chapter on hate crimes (https://ucrbook.com/hate-crimes.html) as well as the FBI's own manual on this data. The questions you could potentially answer well are relatively narrow and generally exclude any causal relationships. ~~~WARNING!!!For a comprehensive guide to this data and other UCR data, please see my book at ucrbook.comVersion 9 release notes:Adds 2021 data.Version 8 release notes:Adds 2019 and 2020 data. Please note that the FBI has retired UCR data ending in 2020 data so this will be the last UCR hate crime data they release. Changes .rda file to .rds.Version 7 release notes:Changes release notes description, does not change data.Version 6 release notes:Adds 2018 dataVersion 5 release notes:Adds data in the following formats: SPSS, SAS, and Excel.Changes project name to avoid confusing this data for the ones done by NACJD.Adds data for 1991.Fixes bug where bias motivation "anti-lesbian, gay, bisexual, or transgender, mixed group (lgbt)" was labeled "anti-homosexual (gay and lesbian)" prior to 2013 causing there to be two columns and zero values for years with the wrong label.All data is now directly from the FBI, not NACJD. The data initially comes as ASCII+SPSS Setup files and read into R using the package asciiSetupReader. All work to clean the data and save it in various file formats was also done in R. Version 4 release notes: Adds data for 2017.Adds rows that submitted a zero-report (i.e. that agency reported no hate crimes in the year). This is for all years 1992-2017. Made changes to categorical variables (e.g. bias motivation columns) to make categories consistent over time. Different years had slightly different names (e.g. 'anti-am indian' and 'anti-american indian') which I made consistent. Made the 'population' column which is the total population in that agency. Version 3 release notes: Adds data for 2016.Order rows by year (descending) and ORI.Version 2 release notes: Fix bug where Philadelphia Police Department had incorrect FIPS county code. The Hate Crime data is an FBI data set that is part of the annual Uniform Crime Reporting (UCR) Program data. This data contains information about hate crimes reported in the United States. Please note that the files are quite large and may take some time to open.Each row indicates a hate crime incident for an agency in a given year. I have made a unique ID column ("unique_id") by combining the year, agency ORI9 (the 9 character Originating Identifier code), and incident number columns together. Each column is a variable related to that incident or to the reporting agency. Some of the important columns are the incident date, what crime occurred (up to 10 crimes), the number of victims for each of these crimes, the bias motivation for each of these crimes, and the location of each crime. It also includes the total number of victims, total number of offenders, and race of offenders (as a group). Finally, it has a number of columns indicating if the victim for each offense was a certain type of victim or not (e.g. individual victim, business victim religious victim, etc.). The only changes I made to the data are the following. Minor changes to column names to make all column names 32 characters or fewer (so it can be saved in a Stata format), made all character values lower case, reordered columns. I also generated incident month, weekday, and month-day variables from the incident date variable included in the original data.

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

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

Latvia crime rate per 100K population for 2021 was 3.04, a 17.57% decline from 2020.

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

<li>Latvia crime rate per 100K population for 2020 was <strong>3.69</strong>, a <strong>8.8% increase</strong> from 2019.</li>
<li>Latvia crime rate per 100K population for 2019 was <strong>3.39</strong>, a <strong>21.85% decline</strong> from 2018.</li>
<li>Latvia crime rate per 100K population for 2018 was <strong>4.34</strong>, a <strong>4.73% 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.

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

This 2021 crime data is the list of crimes that the Syracuse Police Department responded to in 2021. These records does not include rape offenses as well as any crimes that have been sealed by the court. Crimes are reported to the FBI in two major categories under the Uniform Crime Reports specification: Part 1 and Part 2 crimes. Part 1 crimes include criminal homicide, forcible rape, robbery, aggravated assault, burglary, larceny-theft, and motor vehicle theft. In these records, rape offenses have been excluded due to victim privacy concerns.Part 2 crimes include all other offenses. A more detailed guide to Part 1 crimes is listed below. More details about Part 2 Crimes is listed in the Part 2 Crimes Dataset.When using the data, the date and time provided are when the crime was actually reported. This means that though a larceny might be reported at noon, the actual crime could have happened at 8am, but was not realized until someone noticed hours later. Similarly, if a home break-in happens during a holiday weekend when the owners are out of town, the crime report may not come in until they return home and notice the crime took place previously. The address in the dataset is where the crime occurred. The location is also anonymized to the block level, so a crime that occurred at 123 Main St. will appear as occurring on the 100 block of Main St. This is to protect the privacy of all involved. Finally, information about crimes is fluid, and details about the crime could change.Data DictionaryDR Number - Department Report (DR) number is a unique number assigned by the Records Management System, the first two numbers identify the year in which the incident was reported.Time start and time end - Listed in military time (2400) - Burglaries and larcenies are often a time frame. Address - Where the crime occurred. All addresses are in the 100’s because the Syracuse Police Department allows privacy for residents and only lists the block number.Code Defined - Offense names are listed as crime categories group for ease of understanding. There may have been other offenses also, but the one displayed is the highest Unified Crime Reporting (UCR) category.Arrest - Means that there was an arrest, but not necessarily for that crime.Larceny Code - Indicates the type of larceny (Example: From Building or From Motor Vehicle).DisclaimerData derived from the Syracuse Police Department record management system, any data not listed is not currently available.Part I Crime DefinitionsCriminal homicide—a.) Murder and non-negligent manslaughter: the willful (non-negligent) killing of one human being by another. Deaths caused by negligence, attempts to kill, assaults to kill, suicides, and accidental deaths are excluded. The program classifies justifiable homicides separately and limits the definition to: (1) the killing of a felon by a law enforcement officer in the line of duty; or (2) the killing of a felon, during the commission of a felony, by a private citizen. b.) Manslaughter by negligence: the killing of another person through gross negligence. Deaths of persons due to their own negligence, accidental deaths not resulting from gross negligence, and traffic fatalities are not included in the category Manslaughter by Negligence. Robbery—The taking or attempting to take anything of value from the care, custody, or control of a person or persons by force or threat of force or violence and/or by putting the victim in fear. Aggravated assault—An unlawful attack by one person upon another for the purpose of inflicting severe or aggravated bodily injury. This type of assault usually is accompanied by the use of a weapon or by means likely to produce death or great bodily harm. Simple assaults are excluded. Burglary (breaking or entering)—The unlawful entry of a structure to commit a felony or a theft. Attempted forcible entry is included. Larceny-theft (except motor vehicle theft)—The unlawful taking, carrying, leading, or riding away of property from the possession or constructive possession of another. Examples are thefts of bicycles, motor vehicle parts and accessories, shoplifting, pocket picking, or the stealing of any property or article that is not taken by force and violence or by fraud. Attempted larcenies are included. Embezzlement, confidence games, forgery, check fraud, etc., are excluded. Motor vehicle theft—The theft or attempted theft of a motor vehicle. A motor vehicle is self-propelled and runs on land surface and not on rails. Motorboats, construction equipment, airplanes, and farming equipment are specifically excluded from this category.

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

This data set is no longer compiled by the Ministry of the Solicitor General. Violent crimes under the Criminal Code include: * homicide * attempted murder * sexual assault (levels 1-3) * assault * robbery * criminal harassment * uttering threats * other violent violations The data can be accessed from Statistics Canada.

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

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

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