Incidents based on initial police reports taken by officers when responding to calls for service. Data is modified for public use. Address and Location are not exact locations of incidents and have been rounded to nearest hundred block. Lat/Long are approximations only based on rounded hundred block. Incidents reported in this dataset may not correlate with 911 Events datasets and calls for Police service.

The City of Mesa does not disclose information that is inflammatory in nature that impacts our citizens. Crimes reported in this data set have not been adjudicated in a court of law for final determination.

Although sensitive crimes are included, the approximate address are NOT included. Therefore aggregate totals of crimes are accurate, without providing sensitive information. Addresses are not included for: sexual abuse, sexual assault, suicide, incest, molestation of a child or homicide.

Similar information is also provided through the Communitycrimemap.com website, a 3rd party service that visually reviews crime data for Mesa and outlining areas.

Some of the data fields provided are used to report to the Federal Bureau of Investigation. For a listing of data fields and description please see their UCR Program Data Collections page. Alternatively, please see the Bureau of Justice Statistics NIBRS website for a listing of data fields.

For current events see Police Dispatch Events 2021-present. Calls for service dispatched to Mesa Police Patrol Officers through Computer Aided Dispatch (CAD) system for the period 1/1/2017 - 12/31/2020. Calls are modified for public use, obfuscating the address number through rounding it to the 100 block. Note that these are calls for service and may not necessarily correspond to the data located in the Police Incidents dataset. Crimes reported in this data set have not been adjudicated in a court of law for final determination.

Sensitive crimes are listed but the address of their occurrence will NOT be included. In this way aggregate totals of crimes will be accurate, without providing sensitive information. Addresses where the following crime types occur will NOT be captured: Sexual abuse, Sexual assault, Suicide, Incest, Molestation of a child and Homicide.

Priority One (P1) Call: Life threatening or confrontations which may threaten life or safety of a person.

Priority Two (P2) Call: In progress crime that could result in a threat to injure or possible major property loss or immediate apprehension of a suspect. Accidents with injury or other traffic incidents that create a traffic hazard.

Priority Three (P3) Call: Minor in-progress/just occurred calls, where there is no threat of injury or major property loss.

Priority Four (P4) Call: Nuisance calls, civil standbys, delayed reports where reporting party (RP) is at public location.

Priority Five (P5) Call: Calls where a delay will not result in a crime occurring or the loss of an apprehension or an injured person not receiving aid.

Public view of calls for service dispatched to Mesa Police Patrol Officers through Computer Aided Dispatch (CAD) system beginning 1/1/2021-present day. See also Police CAD Events 2017-2020. The Location and Geolocation values are approximated and do not represent actual call locations. Dispatched call Location is modified by rounding street number to the 100 block. Geolocation is a modified point on a street segment centerline based on the rounded 100 block street number. This public version redacts Location and Geolocation where the Initial Call Type or Final Call Type is considered sensitive: Sexual Assault, Homicide, Molesting, Dead Body, Suicide, Completed Suicide, Behavioral Health, Behavioral Health Transfer/Transport.

Note that these are dispatched calls for service and may not necessarily correspond to the data located in Police Incidents dataset. Crimes reported in this data set have not been adjudicated in a court of law for final determination.

Total incidents aggregated by 1/16 mile hexagon; areas with fewest # incidents unshaded (see legend). Locations rounded to nearest hundred block.

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

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

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

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

Incidents based on initial police reports taken by officers when responding to calls for service. Data is modified for public use. Address and Location are not exact locations of incidents and have been rounded to nearest hundred block. Lat/Long are approximations only based on rounded hundred block. Incidents reported in this dataset may not correlate with 911 Events datasets and calls for Police service.

The City of Mesa does not disclose information that is inflammatory in nature that impacts our citizens. Crimes reported in this data set have not been adjudicated in a court of law for final determination.

Although sensitive crimes are included, the approximate address are NOT included. Therefore aggregate totals of crimes are accurate, without providing sensitive information. Addresses are not included for: sexual abuse, sexual assault, suicide, incest, molestation of a child or homicide.

Similar information is also provided through the Communitycrimemap.com website, a 3rd party service that visually reviews crime data for Mesa and outlining areas.

Some of the data fields provided are used to report to the Federal Bureau of Investigation. For a listing of data fields and description please see their UCR Program Data Collections page. Alternatively, please see the Bureau of Justice Statistics NIBRS website for a listing of data fields.

Historical staffing counts of employees in police department by calendar year. Typically Full Time Equivalent (FTE) count is approved annually by City Council as part of the city's budget process.

Police incidents reported as crimes against person or property, formerly known as Part 1 or Part 2 crimes. See "Criminal Activity" PDF in the dataset attachments section (About this Dataset) for list of the 15 offenses included. Filtered view to include only if the incident involved one or more of the 15 listed offenses.

**Updates to this dataset are paused due to technical difficulties in Police**
Misdemeanor jail inmate housing (incidents by location, month, fiscal year) beginning from fiscal year 2011/2012, and includes information relating to those individuals housed at CoreCivic beginning July 2017. No individually identifiable information is included in this data extract.

This data will be posted one month behind when the period closes due to the data collection process.