Serious violent crimes consist of Part 1 offenses as defined by the U.S. Department of Justice’s Uniform Reporting Statistics. These include murders, nonnegligent homicides, rapes (legacy and revised), robberies, and aggravated assaults. LAPD data were used for City of Los Angeles, LASD data were used for unincorporated areas and cities that contract with LASD for law enforcement services, and CA Attorney General data were used for all other cities with local police departments. This indicator is based on location of residence. Single-year data are only available for Los Angeles County overall, Service Planning Areas, Supervisorial Districts, City of Los Angeles overall, and City of Los Angeles Council Districts.Neighborhood violence and crime can have a harmful impact on all members of a community. Living in communities with high rates of violence and crime not only exposes residents to a greater personal risk of injury or death, but it can also render individuals more susceptible to many adverse health outcomes. People who are regularly exposed to violence and crime are more likely to suffer from chronic stress, depression, anxiety, and other mental health conditions. They are also less likely to be able to use their parks and neighborhoods for recreation and physical activity.For more information about the Community Health Profiles Data Initiative, please see the initiative homepage.

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.

Retirement Notice: This item is in mature support as of June 2023 and will be retired in December 2025. A replacement item has not been identified at this time. Esri recommends updating your maps and apps to phase out use of this item.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 indices Permitted use of this data is covered in the DATA section of the EsriMaster Agreement (E204CW) and these supplemental terms.

This dataset aggregates Seattle Police Department crime statistics with spatial ZIP code boundaries and US Census data to determine the property crime rate per 1,000 residents. The following sources were used to create this dataset:

King County ZIP Code Boundaries

Source: https://data-seattlecitygis.opendata.arcgis.com/datasets/SeattleCityGIS::zip-codes/explore

King County provides approximate ZIP code boundaries, updated quarterly and published by the city of Seattle.

SPD Crime Data: 2008-Present

Source: https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5

The Seattle Police Department publishes data for reported crimes from 2008 to the present, refreshed daily. This data includes whether the crime is classified as against a person, against property, or against society.

2020 ACS 5-year estimates for population

Source: https://data.census.gov/cedsci/table?q=population%20seattle&g=0400000US53%248600000&tid=ACSDP5Y2020.DP05

The US Census Department American Community Survey (ACS) publishes 5-year estimates of population by a variety of geographies, including ZIP Code Tabulation Areas (ZCTAs), geographic approximations of each ZIP code.

Data Processing

Using the pandas and geopandas libraries within python, the following processing steps were followed to prepare this dataset: - Converted the date and time reported field in the SPD dataset to a datetime object and extracted the year - Filtered to crimes reported between 2008 and 2021 - Filtered to only crimes against property - Dropped rows with null values for year, crime against category, longitude, or latitude - Performed a spatial join using the latitude and longitude for each report in the SPD data to append a ZIP code from the King County ZIP Code boundary shapefile - Summarized to calculate a count of property crimes reported for each combination of year and ZIP code - Summarized by ZIP code to calculate the count of years with at least one crime reported and the total number of property crimes reported - Calculated the average number of property crimes reported per year in each ZIP code - Merged with the ACS population estimates - Calculated the number of property crimes reported per year per 1,000 population for each zip code

Photo by Justus Hayes: https://www.pexels.com/photo/a-bicycle-chained-to-a-metal-post-6355944/

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 Name

Field Description

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 Occurred

the date the incident actually occurred

Badge ID

Badge ID of responding Officer

Offense Classification

NIBRS Reporting category for the criminal act committed

Offense Code Name

NIBRS Reporting code for the criminal act committed

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

NIBRS Group

hierarchy that follows the guidelines of the FBI National Incident Based Reporting System

Was Offense Completed

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

Location Category

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

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

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

Much research has examined how crime rates vary across urban neighborhoods, focusing particularly on community-level demographic and social characteristics. A parallel line of work has treated crime at the individual level as an expression of certain behavioral patterns (e.g., impulsivity). Little work has considered, however, whether the prevalence of such behavioral patterns in a neighborhood might be predictive of local crime, in large part because such measures are hard to come by and often subjective. The Facebook Advertising API offers a special opportunity to examine this question as it provides an extensive list of “interests” that can be tabulated at various geographic scales. Here we conduct an analysis of the association between the prevalence of interests among the Facebook population of a ZIP code and the local rate of assaults, burglaries, and robberies across 9 highly populated cities in the US. We fit various regression models to predict crime rates as a function of the Facebook and census demographic variables. In general, models using the variables for the interests of the whole adult population on Facebook perform better than those using data on specific demographic groups (such as Males 18-34). In terms of predictive performance, models combining Facebook data with demographic data generally have lower error rates than models using only demographic data. We find that interests associated with media consumption and mating competition are predictive of crime rates above and beyond demographic factors. We discuss how this might integrate with existing criminological theory.

This map 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: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.For more information about the AGS Crime Indices, click here. Additional Esri Resources:Esri DemographicsU.S. 2021/2026 Esri Updated DemographicsEssential demographic vocabularyEsri's arcgis.com demographic map layersPermitted 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.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

Crime severity index (violent, non-violent, youth) and weighted clearance rates (violent, non-violent), Canada, provinces, territories and Census Metropolitan Areas, 1998 to 2024.

This table contains data on the rate of violent crime (crimes per 1,000 population) for California, its regions, counties, cities and towns. Crime and population data are from the Federal Bureau of Investigations, Uniform Crime Reports. Rates above the city/town level include data from city, university and college, county, state, tribal, and federal law enforcement agencies. The table is part of a series of indicators in the Healthy Communities Data and Indicators Project of the Office of Health Equity. Ten percent of all deaths in young California adults aged 15-44 years are related to assault and homicide. In 2010, California law enforcement agencies reported 1,809 murders, 8,331 rapes, and over 95,000 aggravated assaults. African Americans in California are 11 times more likely to die of assault and homicide than Whites. More information about the data table and a data dictionary can be found in the About/Attachments section.

This interactive map symbolizes the population of total homeless individuals with small to large blue circles in each zip code. Additional homeless population demographics available by pop-up.

This map shows the total crime index in the U.S. in 2018 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. 2018/2023 Esri Updated DemographicsEssential demographic vocabularyEsri's arcgis.com demographic map layers

This dataset consists of gun violence within Jefferson county that may fall within LMPDs radar, including non-fatal shootings, homicides, as well as shot-spotter data. The mapping data points where there are victims have been obfuscated to maintain privacy, while still being accurate enough to be placed in its correct boundaries, particularly around, neighborhoods, ZIP Codes, Council districts, and police divisions. The data also excludes any victim information that could be used to identify any individual. this data is used to make the public aware of what is going on in their communities. The data consists of only criminal incidents, excluding any cases that are deemed non-criminal.Field NameField DescriptionCase numberPolice report number. For ShotSpotter detections, it is the ShotSpotter ID.DateTimeDate and time in which the original incident occurred. Time is rounded down.AddressAddress rounded down to the one hundred block of where the initial incident occured. Unless it is an intersection.NeighborhoodNeighborhood in which the original incident occurred.Council DistrictCouncil district in which the original incident occurred.LatitudeLatitude coordinate used to map the incidentLongitudeLongitude coordinate used to map the incidentZIP CodeZIP Code in which the original incident occurred.Crime Typea distinction between incidents, whether it is a non-fatal shooting, homicide, or a ShotSpotter detection.CauseUsed to differentiate on the cause of death for homicide victims.SexGender of the victim of the initial incident.RaceRace/Ethnicity of the victim in a given incident.Age GroupCategorized age groups used to anonymize victim information.Division NamePolice division or department where the initial incident occurred.Crime report data is provided for Louisville Metro Police Divisions only; crime data does not include smaller class cities, unless LMPD becomes involved in smaller agency incident.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.Contact:Ivan Benitez, Ph.D.Gun Violence Data FellowOffice for Safe and Healthy Neighborhoodsivan.benitez@louisvilleky.gov

Retirement Notice: 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 USA property 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 indices Permitted use of this data is covered in the DATA section of the EsriMaster Agreement (E204CW) and these supplemental terms.

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

The .csv file can be found here -- scroll down to "Additional Datasets" and then click the "Hate Crime" link and then download the zip file. The zip file will contain the .csv file and a .pdf file that contains more information regarding the scope and limitations of the data collected.

Please keep in mind, given what is communicated in the methodology file from the .zip file, be wary about drawing particular conclusions from this data.

I have not made any changes to this file. All preprocessing was done after creating a dataframe via the Pandas library.

There are 28 columns in the dataset. There are 219,073 entries in this data. There are no duplicate values in this data. The following eight columns have null values (PUB_AGENCY_UNIT, ADULT_VICTIM_COUNT, JUVENILE_VICTIM_COUNT, ADULT_OFFENDER_COUNT, JUVENILE_OFFENDER_COUNT, OFFENDER_RACE, OFFENDER_ETHNICITY, and TOTAL_INDIVIDUAL_VICTIMS).

This dataset has the Apache 2.0 license.

Some questions that I have about the data: 

Why are there so many columns with large amounts of NaN values? Could this be related to inconsistences in reporting?

For the columns related to race and ethnicity, why is the largest category "Unknown"? Could it be that information was not gathered during the time the hate crime was initially recorded?

How can this data, especially when worked on by data analysts and data scientists, help law enforcement agencies in better understanding and ultimately reducing hate crimes in the US?

This layer shows the personal crime index in the U.S. in 2017 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 crime indexSub-categories of the personal crime indexThe 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.For more information about the AGS Crime Indices, click here. Additional Esri Resources:Esri DemographicsU.S. 2017/2022 Esri Updated DemographicsEssential demographic vocabularyEsri's arcgis.com demographic map layers

This study examined spatial and temporal features of crime guns in Pittsburgh, Pennsylvania, in order to ascertain how gun availability affected criminal behavior among youth, whether the effects differed between young adults and juveniles, and whether that relationship changed over time. Rather than investigating the general prevalence of guns, this study focused only on those firearms used in the commission of crimes. Crime guns were defined specifically as those used in murders, assaults, robberies, weapons offenses, and drug offenses. The emphasis of the project was on the attributes of crime guns and those who possess them, the geographic sources of those guns, the distribution of crime guns over neighborhoods in a city, and the relationship between the prevalence of crime guns and the incidence of homicide. Data for Part 1, Traced Guns Data, came from the City of Pittsburgh Bureau of Police. Gun trace data provided a detailed view of crime guns recovered by police during a two-year period, from 1995 to 1997. These data identified the original source of each crime gun (first sale to a non-FFL, i.e., a person not holding a Federal Firearms License) as well as attributes of the gun and the person possessing the gun at the time of the precipitating crime, and the ZIP-code _location where the gun was recovered. For Part 2, Crime Laboratory Data, data were gathered from the local county crime laboratory on guns submitted by Pittsburgh police for forensic testing. These data were from 1993 to 1998 and provided a longer time series for examining changes in crime guns over time than the data in Part 1. In Parts 3 and 4, Stolen Guns by ZIP-Code Data and Stolen Guns by Census Tract Data, data on stolen guns came from the local police. These data included the attributes of the guns and residential neighborhoods of owners. Part 3 contains data from 1987 to 1996 organized by ZIP code, whereas Part 4 contains data from 1993 to 1996 organized by census tract. Part 5, Shots Fired Data, contains the final indicator of crime gun prevalence for this study, which was 911 calls of incidents involving shots fired. These data provided vital information on both the geographic _location and timing of these incidents. Shots-fired incidents not only captured varying levels of access to crime guns, but also variations in the willingness to actually use crime guns in a criminal manner. Part 6, Homicide Data, contains homicide data for the city of Pittsburgh from 1990 to 1995. These data were used to examine the relationship between varying levels of crime gun prevalence and levels of homicide, especially youth homicide, in the same city. Part 7, Pilot Mapping Application, is a pilot application illustrating the potential uses of mapping tools in police investigations of crime guns traced back to original point of sale. NTC. It consists of two ArcView 3.1 project files and 90 supporting data and mapping files. Variables in Part 1 include date of manufacture and sale of the crime gun, weapon type, gun model, caliber, firing mechanism, dealer _location (ZIP code and state), recovery date and _location (ZIP code and state), age and state of residence of purchaser and possessor, and possessor role. Part 2 also contains gun type and model, as well as gun make, precipitating offense, police zone submitting the gun, and year the gun was submitted to the crime lab. Variables in Parts 3 and 4 include month and year the gun was stolen, gun type, make, and caliber, and owner residence. Residence locations are limited to owner ZIP code in Part 3, and 1990 Census tract number and neighborhood name in Part 4. Part 5 contains the date, time, census tract and police zone of 911 calls relating to shots fired. Part 6 contains the date and census tract of the homicide incident, drug involvement, gang involvement, weapon, and victim and offender ages. Data in Part 7 include state, county, and ZIP code of traced guns, population figures, and counts of crime guns recovered at various geographic locations (states, counties, and ZIP codes) where the traced guns first originated in sales by an FFL to a non-FFL individual. Data for individual guns are not provided in Part 7.