DATASET DESCRIPTION This dataset contains information on both 911 calls (usually referred to as Calls for Service or Dispatched Incidents) and officer-initiated incidents recorded in the Computer Aided Dispatch (CAD) system. These are differentiated by the Incident Type field, defined below. This data excludes records that were cancelled after being identified as duplicates of the same incident, such as when two 911 calls are made for the same incident. It also excludes records that were cancelled because they were handled by another agency such as Austin Fire or Austin-Travis County Emergency Medical Services or because they were found to not require a police response. GENERAL ORDERS RELATING TO THIS DATA: The Department has a responsibility to protect life and property and to provide service to the residents of Austin. To fulfill this obligation it must provide an appropriate response to calls. AUSTIN POLICE DEPARTMENT DATA DISCLAIMER 1. The data provided is for informational use only and may differ from official Austin Police Department crime data. 2. The Austin Police Department’s databases are continuously updated, and changes can be made due to a variety of investigative factors including but not limited to offense reclassification and dates. 3. Reports run at different times may produce different results. Care should be taken when comparing against other reports as different data collection methods and different systems of record may have been used. 4.The Austin Police Department does not assume any liability for any decision made or action taken or not taken by the recipient in reliance upon any information or data provided. City of Austin Open Data Terms of Use - https://data.austintexas.gov/stories/s/ranj-cccq
This dataset has the following 27 columns:
| Column Name | API Column Name | Data Type | Description | Sample Values |
|---|---|---|---|---|
| Incident Number | incident_number | text | An unique integer identifying a computer-aided dispatch incident, consisting of a two-digit year number, three-digit day-of-year and four-digit incident-count number. | 152052135 241321558 241831655 222661541 140732331 view top 100 |
| Incident Type | incident_type | text | A flag indicating whether a given incident was dispatched or officer-initiated. Dispatched incidents are received via 911 calls while officer-initiated incidents are created by officers in the field. | Dispatched Incident Officer-Initiated Incident view top 100 |
| Council District | council_district | text | The council district where the offense occurred. | 9 0 3 4 2 view top 100 |
| Mental Health Flag | mental_health_flag | text | A flag indicating whether a given incident was mental-health related or not. A given incident may be flagged as mental-health-related due to the initial problem description, the final problem description, the call disposition, because a crisis counselor was assigned to the call, because the caller asked for mental health services, because a 911 call taker assessed mental health played a role in the call or because the subject of a use of force related to the incident displayed "Emotionally Disturbed Person" conduct. Please note that multiple of the preceding conditions are often true for mental-health related calls. Problem descriptions related to mental health may indicate the call is related to an "Emotionally Disturbed Person" or an attempted suicide. Call dispositions that indicate a call is mental-health-related will contain an "MH" in the call disposition description and indicate that a responding officer assessed that mental health had a role in the incident. | Not Mental Health Incident Mental Health Incident view top 100 |
| Priority Level | priority_level | text | The priority level assigned to the incident at the time of the first officer's arrival. Priority levels range between 0 and 4, with 0 being the highest priority and 4 being the lowest priority. | Priority 3 Priority 2 Priority 1 Priority 0 view top 100 |
| Response Datetime | response_datetime | calendar_date | The date and time that the 911 call-takers Emergency Call Taker (ECT) screen opened following the 911 call being answered in the case of dispatched incidents. In the case of officer-initiated incidents, this field indicates the time the incident was created and sent to the incident queue if it was created via the officer's onboard computer or the time the dispatcher opened their ECT screen and created the incident if the officer created the incident through dispatch. | 2019-01-01T00:00:01.000 2018-10-30T16:50:37.000 2015-03-31T09:55:05.000 2014-06-30T16:31:19.000 2023-10-24T01:38:13.000 view top 100 |
| Response Year | response_year | number | Year incident occurred. | 2014 2016 2015 2017 2018 view top 100 |
| Response Month | response_month | text | Month incident occurred. | Mar May Aug Jul Jun view top 100 |
| Response Day of Week | response_day_of_week | text | The three-character day of week of the Response Datetime. | Fri Thu Wed Tue Mon view top 100 |
| Response Hour | response_hour | number | An integer representing the hour of day of the Response Datetime | 22 21 17 18 23 view top 100 |
| First Unit Arrived Datetime | first_unit_arrived_datetime | calendar_date | The date and time that the first APD unit arrived on scene to the incident. This is the endpoint for response time calculations. Multiple units may arrive on a single incident, while individual units may be made up of one or more officers. | 2020-05-21T00:44:11.000 2016-09-06T17:43:07.000 2014-03-28T23:46:49.000 2015-01-03T22:01:20.000 2019-06-05T13:35:54.000 view top 100 |
| Call Closed Datetime | call_closed_datetime | calendar_date | The date and time that the incident was closed, indicating that all units have left the scene and it is no longer active. | 2019-05-12T21:20:12.000 2018-04-09T06:27:49.000 2019-02-13T06:11:26.000 2019-05-13T06:24:14.000 2019-07-29T06:56:07.000 view top 100 |
| Sector | sector | text | The Austin Police Department patrol sector where the incident occurred. | David Edward Baker Frank Adam view top 100 |
| Initial Problem Description | initial_problem_description | text | A preliminary description of the problem meant to be addressed by the CAD incident based on either the information given to the 911 call taker in the case of dispatched incidents, or information collected by officers in the case of officer-initiated incidents. Initial problem descriptions may differ from final problem descriptions based on additional information that comes to light during the call-taking and response processes. | Traffic Stop Disturbance Other Alarm Burglar On Site Incident Check Welfare Urgent view top 100 |
| Initial Problem Category | initial_problem_category | text | A general category describing the problem that the CAD incident was meant to address based on the Initial Problem Description value. | Traffic Stop/Hazard Other Disturbance Administrative Welfare Check view top 100 |
| Final Problem Description | final_problem_description | text | A description of the ultimate issue that was meant to be addressed by the CAD incident. This may differ from the initial problem description based on additional information that comes to light during the call-taking and response processes. Certain final problem descriptions may describe specific criminal offenses from the Texas Penal Code. | Traffic Stop Disturbance Other Suspicious Person Doc / C.o. Violation False Burglar Alarm view top 100 |
| Final Problem Category | final_problem_category | text | A general category describing the problem that the CAD incident was meant to address based on the Final Problem Description value. | Traffic Stop/Hazard Administrative Disturbance Other Welfare Check view top 100 |
| Number of Units Arrived | number_of_units_arrived | number | A count of the number of APD units that arrived on scene in response to the CAD incident. Please note that some units may consist of more than one APD officer, while certain units may also include civilian personnel such as crime scene technicians. Moreover, this count may include a variety of type of personnel including patrol officers, investigators, supervisors and public information officers if such personnel are required for the incident response. | 1 2 3 4 5 view top 100 |
| Unit Time on Scene | unit_time_on_scene | number | The total amount of time spent on scene by all APD units in seconds. | 4 3 5 6 2 view top 100 |
| Call Disposition Description | call_disposition_description | text | A description of the outcome of the call. | No Report Report Written Unable To Locate 10/8 From Traffic False Alarm view top 100 |
| Report Written Flag | report_written_flag | text | A flag indicating that a responding unit wrote a report in the Records Management System based on this CAD incident. Note that a report being written does not necessarily mean that a criminal offense took place. | No Yes view top 100 |
| Response Time | response_time | number | The amount of time between when the 911 call was answered when the first officer arrived on scene in seconds. Please note that this field is not applicable to officer-initiated incidents and is left blank for such incidents. | 1 0 363 297 316 view top 100 |
| Officer Injured/Killed Count | officer_injured_killed_count | number | A count of officers seriously injured or killed in a use of force related to this CAD incident where the subject of the use of force was a person with mental illness. | 0 1 view top 100 |
| Subject Injured/Killed Count | subject_injured_killed_count | number | A count of the subjects of a use of force who were seriously injured or killed in a use of force related to this CAD incident where those subjects had a mental illness. | 0 1 view top 100 |
| Other Injured/Killed Count | other_injured_killed_count | number | The number of persons seriously injured or killed in an incident related to this CAD incident where there was also a use of force against an individual with mental illness where either the subject of that use of force or the officer involved in that use of force were seriously injured or killed. | 0 view top 100 |
| Geo ID | geoid | number | A Census Block Group identifier; a concatenation of the current state FIPS code, county FIPS code, census tract code, and block group number. | 484539800001 484530011011 484530011032 484530007001 484530009024 view top 100 |
| Census Block Group | blkgpnm | number | Shortened Block Group Name based on the Census Bureau's Geo ID. State digits have been removed due to system limitations. | 4539800001 4530011011 4530011032 4530007001 4530009024 view top 100 |