- API
Police Incidents
citydata.mesaaz.gov | Last Updated 2024-06-17T23:57:06.000ZIncidents 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.
- API
Energy Resources Gas Emergency Response (PUBLIC)
citydata.mesaaz.gov | Last Updated 2024-07-02T14:22:17.000ZThis version redacts all sensitive information including who the case was submitted to, who was dispatched, actual location of the incident, and the geocoded location of the incident. The data documented in the table below is the information related to each emergency call that is received by Energy Resources. The data serves as the official record for each call and is used for various things such as determining response time, tracking call volume and ultimately serving as the official record of a response if any questions should arise about how Energy Resources handled an emergency call.
- API
Fire and Medical Incidents Dispatched in City of Mesa - Public View
citydata.mesaaz.gov | Last Updated 2024-07-07T18:24:56.000ZThis redacted view dataset removes HIPAA protected information for medical calls and unique locations of incidents. Information about incidents dispatched by Fire & Medical for service within the City of Mesa. All dispatch and response times are based on calls received and dispatched by Mesa Regional Dispatch Center (MRDC) only. Calls to 911 are routed by a 911 Control Office to a primary public safety answering point (PSAP). The primary PSAP for emergency calls in the City of Mesa is Police 911 dispatch. Fire and Medical calls are transferred to the MRDC, a secondary PSAP for dispatch. Call handling and response times in this dataset do not include primary PSAP receive, handle and transfer times. NOTE: An incident's Reason Code and Category here may differ from how the call was originally dispatched by 911 CAD. Visit https://www.fcc.gov/general/9-1-1-and-e9-1-1-services and http://www.mesaaz.gov/residents/fire-medical/divisions-sections/dispatch-deployment for more information. Also see http://www.mesaaz.gov/residents/police/divisions/communications/how-does-911-work for additional information about using 911.
- API
PRCF - Parks Ranger Reports
citydata.mesaaz.gov | Last Updated 2024-07-07T11:19:07.000ZThe Park Rangers report monthly on the number of warnings or citations given, the total number of parks visited for the month, and the total number of warnings or citations that were related to the population of homeless. This data populates directly from a SharePoint form.
- API
Crime Reporting Statistics
citydata.mesaaz.gov | Last Updated 2024-07-01T14:40:17.000Z***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.
- API
Code Enforcement
citydata.mesaaz.gov | Last Updated 2024-07-03T14:48:38.000ZFull dataset containing information about Code Enforcement. Note that in this dataset a code case may be represented by multiple rows as workflow status changes. To learn more about code enforcement in the City of Mesa, visit the <b><a href="https://www.mesaaz.gov/residents/code-compliance" target="_blank" rel="noopener noreferrer">Code Compliance Office</b></a>. For distinct code cases showing only the most recent status, see <b> <a href="https://data.mesaaz.gov/Code-Compliance/Code-Enforcement-Distinct-Cases/2fkz-4tb7" target="_blank" rel="noopener noreferrer">Distinct Code Enforcement Cases</a></b>. See also the following related datasets: <b> <a href="https://data.mesaaz.gov/Code-Compliance/Code-Enforcement-Case-Turn-Around-Time-TAT-/k9hp-cy2s" target="_blank" rel="noopener noreferrer">Code Enforcement Case Turn Around Time</a></b>, <b><a href="https://data.mesaaz.gov/Code-Compliance/Code-Cases-by-Officer/akj6-u9kt" target="_blank" rel="noopener noreferrer">Code Cases by Officer</a></b>, and <b><a href="https://data.mesaaz.gov/Code-Compliance/Code-Compliance-Investigation-Response/8t34-hz58" target="_blank" rel="noopener noreferrer">Code Compliance Investigation Response</a></b>.
- API
Fire and Medical Incidents
citydata.mesaaz.gov | Last Updated 2024-07-07T18:24:56.000ZNumber of incidents responded to in Mesa Fire and Medical's jurisdiction by Type, Calendar Year
- API
Water Resources Work Orders - Public View
citydata.mesaaz.gov | Last Updated 2024-07-07T14:08:58.000ZInformation about work performed on Water Resources assets such as valves and hydrants. This view redacts sensitive information including the work order location.
- API
Water Service Interruptions - Work Orders (Public)
citydata.mesaaz.gov | Last Updated 2024-07-07T14:08:58.000ZInformation about water services work orders where a service disruption resulted. Filtered view where service disruption was at least 4 hours in duration.
- API
Police Dispatched (CAD) Events by Month
citydata.mesaaz.gov | Last Updated 2024-01-16T16:08:40.000ZNumber of police calls for service dispatched by month. 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.<br /><br />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.<br /><br />Emergency (E) Calls: Life threatening or confrontations which may threaten life or safety of a person. <br /><br />Priority One 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.<br /><br />Priority Two Calls: Minor in-progress/just occurred calls, where there is no threat of injury or major property loss.<br /><br />Priority Three Calls: Nuisance calls, civil standbys, delayed reports where reporting party (RP) is at public location. <br /><br />Priority Four Calls: Calls where a delay will not result in a crime occurring or the loss of an apprehension or an injured person not receiving aid. <br /><br />Priority Five Calls: Calls with no time requirement for dispatch. Calls where a delay will not result in a crime occurring or the loss of an apprehension or an injured person not receiving aid where the priority is approved by a supervisor.<br /><br />Priority Six Calls: On-view calls. An officer on view or officer initiated case.