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, 2023Incidents of Officers assaulted by individuals since 2010.Data Dictionary:ID - the row numberDATE_REPORTED - the date the incident was reported to LMPDDATE_OCCURED - the date the incident actually occurredCRIME_TYPE - the crime type category (assault or homicide)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/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 occurredUOR_DESC - Uniform Offense Reporting code for the criminal act committedLEOKA_APPLIES - whether or not the incident is reported to the Center for the Study of Law Enforcement Officers Killed and Assaulted (LEOKA). For more information visit https://leoka.org/OFFICER_KILLED - whether or not an officer was killed due to the incidentTYPE_OF_ASSIGNMENT - how the officer was assigned at the time of the incident (e.g. ONE-MAN VEHICLE ALONE (UNIFORMED OFFICER))TYPE_OF_ACTIVITY - the type of activity the officer was doing at the time of the incident (e.g. RESPONDING TO DISTURBANCE CALLS)OFFENSE_CITY - the city associated to the incident block locationOFFENSE_ZIP - the zip code associated to the incident block location