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.

In 2023, approximately **** million emergency calls were received by police departments across Japan. With over *** million calls, Tokyo Prefecture, the country's capital and most populous prefecture, accounted for the highest number of incoming emergency calls.

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.

A CSV file which is updated daily by 11am available for each year, starting from November 1st, 2015, with the current year being updated daily through 7 days prior to today's posting date. All citizen-generated dispatched calls for police service are included. Officer self-initiated calls and non dispatched calls such as calls for general information or calls that are transferred to other departments such as FIRE for response are not included.

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.

How many calls does the police in Sweden receive? In 2020, the Swedish Police received about *** thousand emergency calls. That was the highest number of calls in the past couple of years. The number of calls peaked, however, in 2017 with over ***** thousand.

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.

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

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.

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.

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.

2017 EMS Annual Report - Stories - Answering 911 Calls

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.

Emergency - 911 Calls Montgomery County, PA Reference: https://www.kaggle.com/mchirico/montcoalert

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.

911 Public Safety Answering Point (PSAP) service area boundaries in the United States 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 a 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 day / 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 other cases, 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 plus the homes and businesses along a road which is partly in another county. At the request of NGA, text fields in this dataset have been set to all upper case to facilitate consistent database engine search results. At the request of NGA, 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.Homeland Security Use Cases: Use cases describe how the data may be used and help to define and clarify requirements. 1) A disaster has struck, or is predicted for, a locality. The PSAP that may be affected must be identified and verified to be operational. 2) In the event that the local PSAP is inoperable, adjacent PSAP locations could be identified and utilized.