This dataset contains a list of Police Dispatched Incidents records. Update Frequency : 4 Times Daily

This data set encompasses calls for service from 2017 to present from the City of Somerville's Computer Aided Dispatch (CAD) system. It excludes routine or administrative tasks (like vehicle refueling), community engagement efforts, and other non-call-related activities.,Certain sensitive incidents, such as potential homicides or those requiring investigative follow-up, are omitted. Additionally, some incidents deemed sensitive statutorily or by SPD are included in the data set but stripped of temporal or geographic information in order to protect the privacy of victims.,This data set is refreshed daily with data appearing with a one-month delay (e.g. CAD calls for service from 1/1 will appear on 2/1). If a daily update does not refresh, please email data@somervillema.gov.

DATASET DESCRIPTION: This Dataset includes the average response time by Call Priority across days of the week and hours of the day. Response Times reflect the same information contained in the APD 911 Calls for Service 2019-2024 dataset. AUSTIN POLICE DEPARTMENT DATA DISCLAIMER 1. The data provided is for informational use only and may differ from official Austin Police Department data. 2. 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. 3. 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

AUSTIN POLICE DEPARTMENT DATA DISCLAIMER Please read and understand the following information. This dataset contains a record of incidents that the Austin Police Department responded to and wrote a report. Please note one incident may have several offenses associated with it, but this dataset only depicts the highest level offense of that incident. Data is from 2003 to present. This dataset is updated weekly. Understanding the following conditions will allow you to get the most out of the data provided. Due to the methodological differences in data collection, different data sources may produce different results. This database is updated weekly, and a similar or same search done on different dates can produce different results. Comparisons should not be made between numbers generated with this database to any other official police reports. Data provided represents only calls for police service where a report was written. Totals in the database may vary considerably from official totals following investigation and final categorization. Therefore, the data should not be used for comparisons with Uniform Crime Report statistics. 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. Pursuant to section 552.301 (c) of the Government Code, the City of Austin has designated certain addresses to receive requests for public information sent by electronic mail. For requests seeking public records held by the Austin Police Department, please submit by utilizing the following link: https://apd-austintx.govqa.us/WEBAPP/_rs/(S(0auyup1oiorznxkwim1a1vpj))/supporthome.aspx

Guide for APD 911 Calls for Service 2019-2024 Dataset

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.

A. SUMMARY This dataset comes from the San Francisco Emergency Medical Services Agency and includes all opioid overdose-related 911 calls responded to by emergency medical services (ambulances). The purpose of this dataset is to show how many opioid overdose-related 911 calls the San Francisco Fire Department and other ambulance companies respond to each week. This dataset is based on ambulance patient care records and not 911 calls for service data. B. HOW THE DATASET IS CREATED The San Francisco Fire Department and other ambulance companies send electronic patient care reports to the California Emergency Medical Services Agency for all 911 calls they respond to. The San Francisco Emergency Medical Services Agency (SF EMSA) has access to the state database that includes all reports for 911 calls in San Francisco County. In order to identify overdose-related calls that resulted in an emergency medical service (or ambulance) response, SF EMSA filters the patient care reports based on set criteria used in other jurisdictions called The Rhode Island Criteria. These criteria filter calls to only include those calls where EMS documented that an opioid overdose was involved and/or naloxone (Narcan) was administered. Calls that do not involve an opioid overdose are filtered out of the dataset. Calls that result in a patient death on scene are also filtered out of the dataset. This dataset is created by copying the total number of calls each week when the state makes this data available. C. UPDATE PROCESS Data is generally available with a 24-hour lag on a weekly frequency but the exact lag and update frequency is based on when the State makes this data available. D. HOW TO USE THIS DATASET This dataset includes the total number of calls a week. The week starts on a Sunday and ends on the following Saturday. This dataset will not match the Fire Department Calls for Service dataset, as this dataset has been filtered to include only opioid overdose-related 911 calls based on electronic patient care report data. Additionally, the Fire Department Calls for Service data are primarily based on 911 call data (i.e. calls triaged and recorded by San Francisco’s 911 call center) and not the finalized electronic patient care reports recorded by Fire Department paramedics. E. RELATED DATASETS Fire Department Calls for Service San Francisco Department of Public Health Substance Use Services Unintentional Overdose Death Rates by Race/Ethnicity Preliminary Unintentional Drug Overdose Deaths F. CHANGE LOG

The EMS Incident Dispatch Data file contains data that is generated by the EMS Computer Aided Dispatch System. The data spans from the time the incident is created in the system to the time the incident is closed in the system. It covers information about the incident as it relates to the assignment of resources and the Fire Department’s response to the emergency. To protect personal identifying information in accordance with the Health Insurance Portability and Accountability Act (HIPAA), specific locations of incidents are not included and have been aggregated to a higher level of detail.

DATASET DESCRIPTION: This dataset provides the case report number, the date the incident occurred, subject race and gender at the time of the interaction and the lead charge. This dataset contains only instances where a warning was issued to the subject of the interaction for a violation. GENERAL ORDERS RELATING TO TRAFFIC ENFORCEMENT: After stopping the violator, officers shall exercise good judgment in deciding what enforcement action should be taken (e.g., warning, citation, arrest). Additionally, field release citations and warnings shall be completed as outlined in General Order 308, which permits law enforcement agencies to use citation release procedures in lieu of arrest for specified Class A or B misdemeanor offenses, and all Class C misdemeanor offenses with certain exceptions. AUSTIN POLICE DEPARTMENT DATA DISCLAIMER: 1. The data provided is for informational use only and may differ from official Austin Police Department crime data. 2. 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. 3. 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