This dataset represents the Police Emergency and Non-Emergency calls to 911

recordId: Record number
callKey: 'callKey' is a unique reference number on every record
callDateTime: date of record (year/month/day hour:minute)
priority: The importance of the service that is expected to be taken
district: Name of the specific district within the state.
description: name of illegal activity
callNumber: Phone number (Encrypted)
incidentLocation: location where incident is occurred
location: The exact location of the reporter
Neighborhood: The name of the neighborhood
PoliceDistrict: geographical area patrolled by a police force.
PolicePost:
CouncilDistrict: type of local government division
SheriffDistricts: Local government has divided the state into several sheriff's office so that they can better service
Community_Statistical_Areas: Community Statistical Areas are clusters of neighborhoods developed by the City's Planning Department based on recognizable city neighborhoods.
Census_Tracts: Uniquely numbered in each county with a numeric code.
ZIPCode: The postal code of the location
NeedsSync: refers to the process of ensuring that the data on two or more devices is consistent and up to date.(It is used in ArcGIS)
ESRI_OID: It is used in ArcGIS

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.

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.

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

As of March 12, 2020 the government of Ecuador imposed a nationwide lockdown due to the coronavirus (COVID-19) pandemic. From that date until October 31, over ** thousand domestic violence incidents were dealt with through calls to the emergency hotline Ecu 911. Nearly ****** emergency calls were due to incidents relating to domestic violence, ****** of them related to psychological violence. During nationwide lockdowns there has been a growth in domestic violence and sexual abuse reports in Latin America.

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.

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.

The Allegheny County 911 center answers and dispatches 911 calls for 111 out of 130 municipalities in Allegheny County. Agencies are dispatched via a computer aided dispatch (CAD) system. This dataset contains dispatched EMS and Fire events from the CAD and includes details about the nature of the emergency.

To protect the privacy of callers and prevent sensitive health or other identifying information being revealed, the following steps were taken:

• Aggregated event location to census block groups.
• Aggregated call date/time to quarter and year.
• Shortened call types to remove potentially identifying information.
• Flagged certain call types as containing sensitive health information, such as mental health issues, overdose, etc.
• Checked frequency of calls with sensitive health information:
  • If the number of calls (in a particular category related to sensitive health information) for a certain quarter/year and census block group was greater than or equal to 5, the call description was included.
  • If less than 5, the call description was redacted.

Events requiring EMS and Fire services will appear in both datasets with a different Call ID. Events requiring two agencies of the same service (e.g. two or more different fire companies responded to a major fire) will only list the primary responder.

The call descriptions are based on information provided by the caller. The calls are not later updated with a disposition or correction if the original description was inaccurate. For example, if EMS is dispatched to the scene of a stroke, but the person actually had a heart attack, that record would not be updated later with the correct description.

A small subset of the CAD data had no call type recorded. These records are preserved with a "null" in the Description_Short field. Redacted call types are listed as "Removed".

The 19 municipalities that dispatch their own EMS, Fire, and/or Police services are called "ringdown municipalities". These are subject to change. The list can be found in the Ringdown Municipalities 2019 resource.

Due to the size of these tables, you may experience 504 Gateway Timeout errors when trying to download the first two resources below. Use the following links instead.

To download the 911 EMS Dispatches table, click on this link: https://tools.wprdc.org/downstream/ff33ca18-2e0c-4cb5-bdcd-60a5dc3c0418

To download the 911 Fire Dispatches table, click on this link: https://tools.wprdc.org/downstream/b6340d98-69a0-4965-a9b4-3480cea1182b

Support for Health Equity datasets and tools provided by Amazon Web Services (AWS) through their Health Equity Initiative.

This dataset represents the Police Emergency and Non-Emergency calls to 911. Data is updated at least weekly. Data updated as of January 07, 2022 at 15:08:43

911 Public Safety Answering Point (PSAP) service area boundaries in New Mexico According to the National Emergency Number Association (NENA), a Public Safety Answering Point (PSAP) is a facility equipped and staffed to receive 9-1-1 calls. The service area is the geographic area within which a 911 call placed using a landline is answered at the associated PSAP. This dataset only includes primary PSAPs. Secondary PSAPs, backup PSAPs, and wireless PSAPs have been excluded from this dataset. Primary PSAPs receive calls directly, whereas secondary PSAPs receive calls that have been transferred by a primary PSAP. Backup PSAPs provide service in cases where another PSAP is inoperable. Most military bases have their own emergency telephone systems. To connect to such system from within a military base it may be necessary to dial a number other than 9 1 1. Due to the sensitive nature of military installations, TGS did not actively research these systems. If civilian authorities in surrounding areas volunteered information about these systems or if adding a military PSAP was necessary to fill a hole in civilian provided data, TGS included it in this dataset. Otherwise military installations are depicted as being covered by one or more adjoining civilian emergency telephone systems. In some cases areas are covered by more than one PSAP boundary. In these cases, any of the applicable PSAPs may take a 911 call. Where a specific call is routed may depend on how busy the applicable PSAPS are (i.e. load balancing), operational status (i.e. redundancy), or time of date / day of week. If an area does not have 911 service, TGS included that area in the dataset along with the address and phone number of their dispatch center. These are areas where someone must dial a 7 or 10 digit number to get emergency services. These records can be identified by a "Y" in the [NON911EMNO] field. This indicates that dialing 911 inside one of these areas does not connect one with emergency services. This dataset was constructed by gathering information about PSAPs from state level officials. In some cases this was geospatial information, in others it was tabular. This information was supplemented with a list of PSAPs from the Federal Communications Commission (FCC). Each PSAP was researched to verify its tabular information. In cases where the source data was not geospatial, each PSAP was researched to determine its service area in terms of existing boundaries (e.g. city and county boundaries). In some cases existing boundaries had to be modified to reflect coverage areas (e.g. "entire county north of Country Road 30"). However, there may be cases where minor deviations from existing boundaries are not reflected in this dataset, such as the case where a particular PSAPs coverage area includes an entire county, and the homes and businesses along a road which is partly in another county. Text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. All diacritics (e.g., the German umlaut or the Spanish tilde) have been replaced with their closest equivalent English character to facilitate use with database systems that may not support diacritics.

This dataset represents the Police Emergency and Non-Emergency calls to 911 in the 2021 calendar year. To leave feedback or ask a question about this dataset, please fill out the following form: 911 Calls for Service 2021 feedback form.

This a legacy dataset from the period of November 1, 2010 to April 21, 2014 showing daily counts of 911 dispatches by City of Boston public safety agencies. Agencies included are the Boston Police Department, Boston Fire Department, and Boston Emergency Medical Services.

This dataset outlines the emergency communications call volume by month and hour.

Revision Note (February 10, 2025): The data pipeline for "Law Enforcement Dispatched Calls for Service: Real-Time" has been updated. A spelling error with the column "priority_original" has been corrected. Column data types and formatting have been updated to reflect DataSF standards. Law Enforcement Dispatched Calls for Service: Closed Calls has also been updated as part of a larger effort to upgrade our Calls for Service pipelines. Email support@datasf.org with any questions or concerns. A. SUMMARY Law Enforcement Dispatched Calls for Service: Real-Time includes all calls for service that generate a record in the Department of Emergency Management's Computer Aided Dispatch (CAD) System and result in a law enforcement unit being dispatched to a location. Calls originate either from the public (via calls to the 911 call center) or from law enforcement officers in the field upon viewing an incident (‘On-View’). This dataset represents a rolling 48 hour window of calls for service. It contains both open and closed calls. It is both updated every 10 minutes and delayed by an additional 10 minutes. Open calls are defined as active calls that are unverified, but being worked by law enforcement. Closed calls are calls that law enforcement have indicated are resolved. Not all calls for service generate a police incident report, so data does not directly correlate to the Police Incident Reports dataset. The Real-time Calls dataset contains calls handled by law enforcement which can include Police, MTA parking enforcement, the Sheriff’s Office, and others. Some fields in the calls for service data are redacted due to the sensitive nature of the call and/or privacy concerns related to the incident. Please refer Law Enforcement Dispatched Calls for Service Explainer for full documentation. B. HOW THE DATASET IS CREATED Once a received 911 call is dispatched, a record (CAD#) is generated in the Department of Emergency Management's Computer Aided Dispatch (CAD) System. C. UPDATE PROCESS Updated every 10 minutes with the past 48hrs of open and closed calls that have been dispatched. D. HOW TO USE THIS DATASET Please refer Law Enforcement Dispatched Calls for Service Explainer for full documentation. Note: To find data for calls originating from the 311 Connected Worker app dispatched from the Healthy Streets Operations Center (HSOC), search for the value “HSOC” in the onview_flag column. E. KEY RELATED DATASETS Datasets: Law Enforcement Dispatched Calls for Service: Closed Calls Police Department Incident Reports: 2018 to Present Fire Department Calls for Service Geographic Boundaries: Current Police Districts Analysis Neighborhoods Supervisor Districts

This table is no longer updated or authoritative and is therefore deprecated. The Police Serviced 911 Calls dataset is the authoritative replacement.This table shows all 911 police emergency response and officer-initiated calls for service in the City of Detroit from September 20, 2016 through July 17, 2024. 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.

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.