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.

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.

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.

This hosted feature layer has been published in RI State Plane Feet NAD 83.Representative locations of structures and sites throughout Rhode Island. These data include addressed and unaddressed locations as well as occupied and unoccupied structures. These data were originally designed and developed for Rhode Island E 9-1-1 Uniform Emergency Telephone System (RI E 9-1-1) purposes. This dataset continues to be maintained to provide an accurate spatial reference for RI E 9-1-1 telecommunicators. Portions of this dataset were collected as early as 2001. Inaccuracies do exist in these data and are therefore under constant revision. Any discrepancies, inaccuracies or inconsistencies recognized in these data should be reported to the pertinent municipality who should alert RI E-911. Users are also encouraged to email ri911gis@akassociates911.com with any suggested updates for this actively maintained dataset.

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.

Collect and aggregate information from state level reporting entities that can be used to measure the progress of 9 1-1 authorities across the country in enhancing their existing operations and migrating to more advanced - Internet-Protocol-enabled emergency networks. The data will be maintained in a "National 9-1-1 Profile Database." One of the objectives of the National 9-1-1 Program is to develop, collect, and disseminate information concerning practices, procedures, and technology used in the implementation of E9 1 1 services and to support 9-1-1 Public Safety Answering Points (PSAPs) and related state and local public safety agencies for 9 1 1 deployment and operations. The National 9-1-1 profile database can be used to follow the progress of 9-1-1 authorities in enhancing their existing systems and implementing next-generation networks for more advanced systems.

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.

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

description: 911 Public Safety Answering Point (PSAP) service area boundaries in Arkansas 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.; abstract: 911 Public Safety Answering Point (PSAP) service area boundaries in Arkansas 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.

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 are the events captured in an agency’s Computer-Aided Dispatch (CAD) system used to facilitate incident response.

This dataset includes both proactive and reactive police incident data.

The source of this data is the City of Cincinnati's computer-aided dispatch (CAD) database.

This data is updated daily.

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.

911 Addressing Data for Sullivan County, NY. Includes:

Roads Address Points Master Street Name table

This data is open data and can be downloaded from the Sullivan County Geoportal.

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.

Updated as of February 26, 2019. The FCC’s 911 Master PSAP Registry (PSAP Registry) lists Public Safety Answering Points (PSAPs) by an FCC assigned identification number (PSAP ID), PSAP name, state, county, city, and provides information on any type of record change and the reason for updating the record. The Commission updates the Registry periodically as it receives additional information. For further information concerning the FCC's PSAP Registry, or to notify the Commission of changes to the PSAP Registry, contact Kim Anderson and John A. Evanoff, Public Safety and Homeland Security Bureau at fccpsapregistryupdate@fcc.gov.

The Next-Generation 911 file geodatabase is a comprehensive dataset that contains various Geographic Information Systems (GIS) data layers benefiting public safety agencies within state, regional, and local government. The core layers in this product are the Site & Structure Address Points, Road Centerlines, and Emergency Service Zones. These core layers form the foundation for The State of Tennessee's Next-Generation 911 Telephone System. Click Here For Detailed Information About the Product

This data set provides counts and percent/average response times for the categories of incidents outlined in Local Law 119 of 2013: The Ariel Russo Emergency 9-1-1 Response Time Reporting Act. For Local Law 119 Compliance Category Definitions please refer to this link.

Data Description: In July 2018, the City of Cincinnati launched an emergency communication tool, Smart911, that provides 9-1-1 call takers and first responders with additional critical information about participating residents. This technology helps reduce response times and provide first responders with vital information that can help improve incident outcomes. Through Smart911, residents can create a secure “Safety Profile” that will automatically display to emergency call takers immediately upon placing a 9-1-1 call. When a call comes in, a call taker will see a user’s Safety Profile as well as a Facility Profile about their current location. For more information on Smart911 please visit: https://www.cincinnati-oh.gov/cityofcincinnati/news/smart911-tech-now-available-in-cincinnati/ This data set contains the total amount of enrollments in Hamilton County from July 2018 to present. This data allows users to view total enrollment by web site, application or overall. Additionally, the data can be filtered to show enrollment by zip code or by week.

Data Creation: This data is created when individuals create a “Safety Profile” through Smart911.

Data Created By: The source of this data is Rave Mobile Safety and ECC.

Refresh Frequency: This data set is updated weekly.

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

This hosted view feature layer has been published in RI State Plane Feet NAD 83.For complete metadata record - https://www.rigis.org/datasets/edc::e-911-sites/aboutRepresentative locations of structures and sites coded as P7 Site type throughout Rhode Island. These data include addressed and unaddressed locations as well as occupied and unoccupied structures. These data were originally designed and developed for Rhode Island E 9-1-1 Uniform Emergency Telephone System (RI E 9-1-1) purposes. This dataset continues to be maintained to provide an accurate spatial reference for RI E 9-1-1 telecommunicators. Portions of this dataset were collected as early as 2001. Inaccuracies do exist in these data and are therefore under constant revision. Any discrepancies, inaccuracies or inconsistencies recognized in these data should be reported to the pertinent municipality who should alert RI E-911. Users are also encouraged to email ri911gis@akassociates911.com with any suggested updates for this actively maintained dataset.