A. SUMMARY
San Francisco's local Emergency Medical Service Agency (EMSA) publishes information on the time it takes for emergency response vehicles to arrive at the scene of a medical incident after it is dispatched. This dataset is used to calculate the response times published in these dashboards. The dashboards are available here.
This dataset is derived from Fire Department Calls for Service dataset and includes responses to 911 calls for service from the city’s Computer-Aided Dispatch (CAD) system. Please refer to that dataset for details on the underlying data.

B. HOW THE DATASET IS CREATED
This dataset applies additional validation steps to the Fire Department Calls for Service data. This data excludes any responses that meet the following criteria:

• Response to a non-medical event
• Response missing the time stamps necessary to calculate the response time
• Response with negative response time
• Response where the interval between when the vehicle arrives on scene and when the vehicle transports the patient is <1 minute
• Response where the response time is >120 minutes

C. UPDATE PROCESS
This dataset updates daily via automated data pipeline.

D. HOW TO USE THIS DATASET
This dataset is used to populate the Response Times dashboard. Please note that the incident_number column is not a unique identifier as several emergency medical service units may respond to the same call or incident.

A. SUMMARY Fire Calls-For-Service includes all fire units' responses to 911 calls from the city's Computer-Aided Dispatch (“CAD”) system. This includes responses to Medical Incidents requiring EMS staff. Each record includes the call number, incident number, address, unit identifier, call type, and disposition. All relevant time intervals are also included. Because this dataset is based on responses, and since most calls involve multiple units, there are multiple records for each call number. Addresses are associated with an intersection or call box, not a specific address. B. HOW THE DATASET IS CREATED This dataset is an extract from the Department of Emergency Management’s computer-aided dispatch system. The dataset is enhanced with fire-department specific information before being uploaded to the open data portal. C. UPDATE PROCESS This dataset updates daily via automated data pipeline. D. HOW TO USE THIS DATASET This dataset is based on responses, and since most calls involve multiple units, there are multiple records for each call number. The most common call types are Medical Incidents, Alarms, Structure Fires, and Traffic Collisions. E. RELATED DATASETS Fire Incidents

A. SUMMARY This dataset is derived from the Fire Department Calls for Service dataset. It includes summary data for the last 30 days. Summaries are presented by station area. The summary data includes number of calls and average response time (in minutes). Calls are further divided into emergency calls (Code 3) and non-emergency calls (Code 2). B. HOW THE DATASET IS CREATED Filters are applied to the raw data by selecting only the calls for the last 30 full days. The last day included in the dataset is the day before the day the dataset is extracted. C. UPDATE PROCESS Data is updated every day. D. HOW TO USE THIS DATASET This dataset is just a summary of the existing Calls For Service Data. It is provided as a simple way for a user to collect this information.

BackgroundPrior literature suggests that mass gathering events pose challenges to an emergency medical services (EMS) system. We aimed to investigate whether events influence EMS call rates.Materials and methodsThis study is a retrospective review of all primary response ambulance calls in Rhode Island (US) between January 1st, 2018 and August 31st, 2022. The number of EMS calls per day was taken from the state’s EMS registry. Event data was collected using a Google (Google LLC, Mountain View, CA) search. We used separate Poisson regression models with the number of ambulance calls as the dependent and the social event categories sports, agricultural, music events, and public exhibitions as independent variables. All models controlled for the population at risk and the period of the COVID−19 pandemic. Results are presented as increases or decreases in calls per 100,000 inhabitants from the mean over the study period.ResultsThe mean number of daily EMS calls was 38 ± 4 per 100,000 inhabitants. EMS encountered significantly more missions on days with music events (+3, 95% CI [2; 3]) and public exhibitions (+2, 95% CI [1; 2]). In contrast, days with agricultural events were associated with fewer calls (−1, 95% CI [−1; 0]). We did not find any effect of sports events on call rates.ConclusionIncreased ambulance call volumes are observed on days with music events and public exhibitions. Days with agricultural events are associated with fewer EMS calls.

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 shows all calls processed by emergency communications personnel in Norfolk, VA. The Emergency Communications Center is where calls are received from the public and then dispatched to public safety personnel (police, fire-rescue). The dataset shows daily (24-hour period of operations) calls and texts processed by emergency communications personnel. This dataset will be updated daily.

Please note: Data from April 5, 2023 to May 23, 2023 is not available due to equipment upgrades during this timeframe. To view the most updated version of the dataset, please click here: https://data.norfolk.gov/Public-Safety/Emergency-Communications-24-Hour-Call-Volume/nj5u-a2dj/about_data

Norfolk Fire-Rescue (NFR) responds to a wide range of emergency situations throughout the city, including medical emergencies, fires, rescues, and other critical incidents. Operating 24/7, NFR is committed to protecting the safety and well-being of Norfolk residents through timely and professional service.

This dataset provides a daily summary of NFR calls for service, grouped by the date the call was received, the geographic fire station zone, and the type of event. It includes data from January 1, 2014 to the present and is updated daily. The dataset does not contain any personally identifiable information or specific addresses associated with the 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.

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.

The COVID-19 pandemic has claimed over one million lives in the United States and has drastically changed how patients interact with the healthcare system. Emergency medical services (EMS) are essential for emergency response, disaster preparedness, and responding to everyday emergencies. We therefore examined differences in EMS utilization and call severity in 2020 compared to trends from 2015–2019 in a large, multi-state advanced life support EMS agency serving the U.S. Upper Midwest. Specifically, we analyzed all emergency calls made to Mayo Clinic Ambulance, the sole advanced life support EMS provider serving a large area in Minnesota and Wisconsin, and compared the number of emergency calls made in 2020 to the number of calls expected based on trends from 2015–2019. We similarly compared caller demographics, call severity, and proportions of calls made for overdose/intoxication, behavioral health, and motor vehicle accidents. Subgroup analyses were performed for rural vs. urban areas. We identified 262,232 emergent EMS calls during 2015–2019 and 53,909 calls in 2020, corresponding to a decrease of 28.7% in call volume during 2020. Caller demographics shifted slightly towards older patients (mean age 59.7 [SD, 23.0] vs. 59.1 [SD, 23.7] years; p

This file contains 11,738 records which summarize FRES daily emergency service call activity from 2011 - 2/29/2016, including the following fields: date of the call, type of call (Alarms, Structure Fire, Fuel Spill, etc.) and the total of each type per day.

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 September 2, 2025*. 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.

*Note: We want to inform our users that updates to this dataset is currently unavailable from September 3, 2025, forward. The city is actively working with our partners to restore regular data publishing and is committed to resuming daily updates as soon as possible. We appreciate your patience and understanding during this time. Our goal is to ensure the accuracy, consistency, and timeliness of the data we provide. Please check back for updates and thank you for your continued interest in open data.

⚠️Due to the City's transition to a new Computer-Aided Dispatch (CAD) system, the EMS Calls for Service data, dashboards and maps on this site currently include records only through 8/11/25. Regular updates are paused to align and unify old and new data models, but we aim to restore fully automated daily updates by the end of 2025.This transition does not impact Public Safety systems or operations. Data for the pause period (from 8/11/25 until integration completion) is still available upon request via the City’s public records portal. Thank you for your patience!DescriptionData from the City of Cleveland Public Safety's Computer-aided Dispatch (CAD) system on calls for Cleveland Division of EMS service. Includes information on priority, type, and location at the Census Tract level. Data begins with calls from 2021 onward and is updated daily. Call times are shown in your local time zone but are converted to UTC when downloaded.This dataset is used in the following app(s):EMS Calls for Service DashboardData GlossarySee the Attributes section below for details about each column in this dataset.Update FrequencyDaily around 8:30 AMContactsCity of Cleveland, Division of Emergency Medical Service

Context

DataSF seeks to transform the way that the City of San Francisco works -- through the use of data.

https://datasf.org/about/

Content

This dataset contains the following tables: ['311_service_requests', 'bikeshare_stations', 'bikeshare_status', 'bikeshare_trips', 'film_locations', 'sffd_service_calls', 'sfpd_incidents', 'street_trees']

• This data includes all San Francisco 311 service requests from July 2008 to the present, and is updated daily. 311 is a non-emergency number that provides access to non-emergency municipal services.
• This data includes fire unit responses to calls from April 2000 to present and is updated daily. Data contains the call number, incident number, address, unit identifier, call type, and disposition. Relevant time intervals are also included. Because this dataset is based on responses, and most calls involved multiple fire units, there are multiple records for each call number. Addresses are associated with a block number, intersection or call box.
• This data includes incidents from the San Francisco Police Department (SFPD) Crime Incident Reporting system, from January 2003 until the present (2 weeks ago from current date). The dataset is updated daily. Please note: the SFPD has implemented a new system for tracking crime. This dataset is still sourced from the old system, which is in the process of being retired (a multi-year process).
• This data includes a list of San Francisco Department of Public Works maintained street trees including: planting date, species, and location. Data includes 1955 to present.

This dataset is deprecated and not being updated.

Fork this kernel to get started with this dataset.

Acknowledgements

http://datasf.org/

• https://cloud.google.com/bigquery/public-data/sfo-311
• https://cloud.google.com/bigquery/public-data/sffd-service-calls
• https://cloud.google.com/bigquery/public-data/sfpd-reports
• https://cloud.google.com/bigquery/public-data/sfo-trees

Dataset Source: SF OpenData. This dataset is publicly available for anyone to use under the following terms provided by the Dataset Source - http://sfgov.org/ - and is provided "AS IS" without any warranty, express or implied, from Google. Google disclaims all liability for any damages, direct or indirect, resulting from the use of the dataset.

Banner Photo by @meric from Unplash.

Inspiration

Which neighborhoods have the highest proportion of offensive graffiti?

Which complaint is most likely to be made using Twitter and in which neighborhood?

What are the most complained about Muni stops in San Francisco?

What are the top 10 incident types that the San Francisco Fire Department responds to?

How many medical incidents and structure fires are there in each neighborhood?

What’s the average response time for each type of dispatched vehicle?

Which category of police incidents have historically been the most common in San Francisco?

What were the most common police incidents in the category of LARCENY/THEFT in 2016?

Which non-criminal incidents saw the biggest reporting change from 2015 to 2016?

What is the average tree diameter?

What is the highest number of a particular species of tree planted in a single year?

Which San Francisco locations feature the largest number of trees?

This dataset contains the daily incidents by FRS Statuion data indicating incident occurred in each fire station response area. The data is the incident records broken down by call type group for each fire station response area. Update Frequency: Daily

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). For officer-initiated records, please refer to the DPD CAD Initiated Records dataset. 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 DPDinformatics@detroitmi.gov. A DPD webpage provides recommendations for reporting different types of crime.

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.

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.