Please review this brief video for a better understanding of how these data are created: https://www.youtube.com/watch?v=lvTCjVHxpAU

This data represents police response activity. Each row is a record of a Call for Service (CfS) logged with the Seattle Police Department (SPD) Communications Center. Calls originated from the community and range from in progress or active emergencies to requests for problem solving. Additionally, officers will log calls from their observations of the field.

Previous versions of this data set have withheld approximately 40% of calls. This updated process will release more than 95% of all calls but we will no longer provide latitude and longitude specific location data. In an effort to safeguard the privacy of our community, calls will only be located to the “beat” level. Beats are the most granular unit of management used for patrol deployment. To learn more about patrol deployment, please visit: https://www.seattle.gov/police/about-us/about-policing/precinct-and-patrol-boundaries.

As with any data, certain conditions and qualifications apply:

1) These data are queried from the Data Analytics Platform (DAP), and updated incrementally on a daily basis. A full refresh will occur twice a year and is intended to reconcile minor changes.

2) This data set only contains records of police response. If a call is queued in the system but cleared before an officer can respond, it will not be included.

3) These data contain administrative call types. Use the “Initial” and “Final” call type to identify the calls you wish to include in your analysis.

We invite you to engage these data, ask questions and explore.

The dataset includes total incoming calls, both emergency (9-1-1) and non-emergency, and outgoing non-emergency. Emergency calls are broken down by type of call, whether from a cell phone, landline, etc.

Spreadsheet for 911 statistics _DEMO DATA

All incident segments for each of the first responding agencies (PD, FD and EMS) that contribute to the end-to-end response times. This data set provides call volumes broken down by incident type for each Week Start time period as well as the timestamps and average response times (in seconds) for each segment of the call. For the Incident Type Definitions please refer to this link.

All 911 police emergency response calls for service in the City of Detroit since September 20, 2016 are included in this dataset. Emergency response calls are the result of people calling 911 to request police services, calls reported through the non-emergency DPD Telephone Crime Reporting (TCR) line that require emergency response, and ShotSpotter incidents. This dataset does not include requests for emergency response that occur through other channels (e.g. walk-ins, officer-initiated items). A DPD webpage provides recommendations for reporting different types of crime.Each row in the dataset represents a call for service and includes details such as when the call was received, its nature and assigned priority level, DPD response precinct or detail, and dispatch, travel, and total response times. Locations of incidents associated with each call are reported based on the nearest intersection to protect the privacy of individuals.This dataset replaces the previous 911 Calls for Service dataset, which is now deprecated. The current dataset does not include records for officer-initiated calls, and therefore has fewer records than the previous dataset. Officer-initiated call records through July 17th, 2024 are available in the deprecated dataset.Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or CrimeIntelligenceBureau@detroitmi.gov.

Calls for Service to NYPD's 911 system This dataset documents entries into the NYPD 911 system, ICAD. The data is collected from the ICAD system which call takers and dispatchers use to communicate with callers and the NYPD. Each record represents an entry into the system. The data includes entries generated by members of the public as well as self-initiated entries by NYPD Members of Service. The data can be used for issues being responded to by the NYPD.

Data Description: This dataset captures all Cincinnati Police Department Calls for Service. The City of Cincinnati's Computer Aided Dispatch (CAD) system records police incident response activity, which includes all calls for service to emergency operators, 911, alarms, police radio and non-emergency calls. CAD records all dispatch information, which is used by dispatchers, field supervisors, and on-scene officers to determine the priority, severity, and response needs surrounding the incident. Once an officer responds to a call, he/she updates the disposition to reflect findings on-scene. This dataset includes both proactive and reactive police incident data.

Data Creation: This data is created through the City’s computer-aided dispatch (CAD) system.

Data Created By: The source of this data is the Cincinnati Police Department.

Refresh Frequency: This data is updated daily.

CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/xw7t-5phj

Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.

Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).

Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad

Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

The data available here identifies and describes a sampling of publicly available datasets about the 911 emergency response system. This list of datasets is a resource for researchers, civic technologists, activists, and journalists seeking to learn more about the 911 emergency response system. The list helps to identify relevant datasets that could be used to understand various types of 911 activity.

During the first quarter of 2021, the R911 NAT created a list of priority cities including the top 100 cities by population, all state capitals, and the 82 cities that are home to Code for America Brigades. The team then conducted internet searches for each city using terms like “911 calls for service” and “open 911 data.” The dataset and a codebook defining each of these fields are provided as .csv files within a zip file.

Note: this file does not contain the actual 911 datasets, which often number in the millions of records. The data_link field contains the URL of the site where each dataset is publicly available.

See also: The Reimagine 911 knowledge base at: https://reimagine-911.gitbook.io/knowledge-base

Contributors: This open data review was performed by the Code for America Reimagine 911 National Action Team. Contributing team members include: Aleks Hatfield, Brandon Bolton, Chizo Nwagwu, Dan Stormont, Elaine Chow, Em Spalti, Erica Pauls, Gio Sce, Gregory Janesch, Iva Momcheva, Ivelina Momcheva, Jamie Klenetsky Fay, Jason Trout, Jaya Prasad Jayakumar, Jennifer Miller, Jim Grenadier, Joanna Smith, Jonathan Melvin, Katlyn McGraw, Margaret Fine, Mariah Lynch, Micah Mutrux, Michelle Hoogenhout, Patina Herring, Peter Zeglen, Sarah Graham, Sebastian Barajas

Data Description: Emergency Communications Center Calls are records captured for each call. The call data does not contain the nature of the emergency or dispatched resources. For dispatch data reference Police Calls for Service (CAD) or Cincinnati Fire Incidents (CAD).

Data Creation: This dataset includes both emergency (911) and administrative calls to the center. To obtain just emergency (911) calls filter for Call Type ID = 911 CALLS.

Data Created By: The source of this data is the City of Cincinnati's Call System provided by West Communications.

Refresh Frequency: This dataset updates weekly on Fridays.

CincyInsights: The City of Cincinnati maintains an interactive dashboard portal, CincyInsights in addition to our Open Data in an effort to increase access and usage of city data. This data set has an associated dashboard available here: https://insights.cincinnati-oh.gov/stories/s/snnn-n6ic

Data Dictionary: A data dictionary providing definitions of columns and attributes is available as an attachment to this dataset.

Processing: The City of Cincinnati is committed to providing the most granular and accurate data possible. In that pursuit the Office of Performance and Data Analytics facilitates standard processing to most raw data prior to publication. Processing includes but is not limited: address verification, geocoding, decoding attributes, and addition of administrative areas (i.e. Census, neighborhoods, police districts, etc.).

Data Usage: For directions on downloading and using open data please visit our How-to Guide: https://data.cincinnati-oh.gov/dataset/Open-Data-How-To-Guide/gdr9-g3ad

Disclaimer: In compliance with privacy laws, all Public Safety datasets are anonymized and appropriately redacted prior to publication on the City of Cincinnati’s Open Data Portal. This means that for all public safety datasets: (1) the last two digits of all addresses have been replaced with “XX,” and in cases where there is a single digit street address, the entire address number is replaced with "X"; and (2) Latitude and Longitude have been randomly skewed to represent values within the same block area (but not the exact location) of the incident.

Calls for Service to NYPD's 911 system
This dataset documents entries into the NYPD 911 system, ICAD. The data is collected from the ICAD system which call takers and dispatchers use to communicate with callers and the NYPD. Each record represents an entry into the system. The data includes entries generated by members of the public as well as self-initiated entries by NYPD Members of Service. The data can be used for issues being responded to by the NYPD.

Data from City of Cleveland Public Safety's Computer-aided Dispatch (CAD) system on calls for Cleveland Division of Police service. Dashboard includes information on 911 and non-emergency Police calls including insights on time of day and day of week, breakouts by call priority, and more.Data starts with calls from 2021. The data provided is the latest available information and is updated regularly as statistics change.Update FrequencyDaily by 8:30AM EasternRelated data item(s):Police Calls for Service DatasetPolice Calls for Service Map ViewerContactsFor more info or requests, please see the City of Cleveland, Division of Police webpage.How to Use the DashboardUse the filters on the left side of the dashboard to filter the data included in the dashboard.Use the "Click to Reset Filters" button to remove all filters.Modify the data range in the top right corner of the dashboard.Use the tabs at the bottom of the dashboard to navigate to different pages.Click a section of a chart to highlight it. Click it again to undo.

Monthly volume of E911 calls received by Cook County ETSB 911. Counts are broken up by call type and Remote Site location. The Cook County ETSB provides 9-1-1 services for all Unincorporated Cook County and the municipalities of Dixmoor, Ford Heights, Golf, Northlake, Phoenix, Robbins, and Stone Park. Incoming Call Volume by Type: Statistics gathered by the caller class of service and by caller trunk number. Remote Site Transfer Call Volume: Transferred Call Volume of each Cook County ETSB remote site for the month.

This dataset is for Police Serviced 911 calls for 2018. For the comprehensive dataset which includes all records please refer to the Police Serviced 911 Calls dataset. Emergency response calls are the result of people calling 911 to request police services, calls reported through the non-emergency DPD Telephone Crime Reporting (TCR) line that require emergency response, and ShotSpotter incidents. This dataset does not include requests for emergency response that occur through other channels (e.g. walk-ins, officer-initiated items). A DPD webpage provides recommendations for reporting different types of crime.Each row in the dataset represents a call for service and includes details such as when the call was received, its nature and assigned priority level, DPD response precinct or detail, and dispatch, travel, and total response times. Locations of incidents associated with each call are reported based on the nearest intersection to protect the privacy of individuals.Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or CrimeIntelligenceBureau@detroitmi.gov.

The selected police-reported crime statistics during the COVID-19 pandemic special survey collects timely monthly aggregate information on the types of police-reported activity, including criminal incidents and other calls for service, which occurred during the months of the COVID-19 pandemic.

This table shows all 911 police emergency response and officer-initiated calls for service in the City of Detroit in the last 30 days. Emergency response calls are the result of people calling 911 to request police services. Officer-initiated calls include traffic stops, street investigations and other policing activities (such as observing crimes in progress) where police officers initiate the response. The table includes all calls taken, dispatch, travel, and total response times for those calls serviced by a police agency. The data also include the responding agency, unit, call type and category of each call. Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Intelligence Unit at 313-596-2250 or CrimeIntelligenceBureau@detroitmi.gov.

DATASET DESCRIPTION: This dataset is a filtered view of the APD Computer Aided Dispatch (CAD) Incidents dataset and contains information only on incidents which came in through 911 calls. Additionally, it is filtered to limit data from January 1, 2019 through the most recent month of data. This dataset is visualized in the dashboard APD 911 Calls for Service.

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 COMPUTER AIDED DISPATCH INCIDENTS 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.

1. 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.

2. 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 Last Updated

The District’s 911 call center is one of the busiest in the country, historically ranking as the 4th busiest center behind those of New York City, Chicago, and Los Angeles. The goal of this tool is to help track this progress and provide insight into the daily operations of DC’s 911 call takers and dispatchers, work that happens behind the scenes but is critical to building a safer, stronger DC. This is a beta site with continuous testing and improvements. Expect updates to the dashboard as Office of Unified Communications (OUC) receives feedback on this first-of-its-kind tool.

This dataset is for Police Serviced 911 calls from January 1st, 2025 to present day, or until the end of the calendar year 2025 - whatever comes first. For the comprehensive dataset which includes all records please refer to the Police Serviced 911 Calls dataset. Emergency response calls are the result of people calling 911 to request police services, calls reported through the non-emergency DPD Telephone Crime Reporting (TCR) line that require emergency response, and ShotSpotter incidents. This dataset does not include requests for emergency response that occur through other channels (e.g. walk-ins, officer-initiated items). A DPD webpage provides recommendations for reporting different types of crime.Each row in the dataset represents a call for service and includes details such as when the call was received, its nature and assigned priority level, DPD response precinct or detail, and dispatch, travel, and total response times. Locations of incidents associated with each call are reported based on the nearest intersection to protect the privacy of individuals.Should you have questions about this dataset, you may contact the Commanding Officer of the Detroit Police Department's Crime Data Analytics at 313-596-2250 or CrimeIntelligenceBureau@detroitmi.gov.