Narcan/Naloxone deployment count represents the number of incident reports in which an incident code 51050 (Aided Case, Naloxone Deployment) is included. Counts may not capture if there was more than one deployment for an individual, or one deployment each for several individuals, or any combination thereof.

Disclaimer: The San Francisco Police Department does not guarantee the accuracy, completeness, timeliness or correct sequencing of the information as the data is subject to change as modifications and updates are completed.

A. SUMMARY
Read the detailed overview of this dataset.

This dataset includes incident reports that have been filed as of January 1, 2018. These reports are filed by officers or self-reported by members of the public using SFPD’s online reporting system. The reports are categorized into the following groups based on how the report was received and the type of incident:

Initial Reports: the first report filed for an incident
Coplogic Reports: incident reports filed by members of the public using SFPD’s online reporting system
Vehicle Reports: any incident reports related to stolen and/or recovered vehicles

Disclaimer: The San Francisco Police Department does not guarantee the accuracy, completeness, timeliness or correct sequencing of the information as the data is subject to change as modifications and updates are completed.

B. HOW THE DATASET IS CREATED
Data is added to open data once incident reports have been reviewed and approved by a supervising Sergeant or Lieutenant. Incident reports may be removed from the dataset if in compliance with court orders to seal records or for administrative purposes such as active internal affair investigations and/or criminal investigations.

Read more about how incident reports are created and approved in the detailed overview of this dataset.

C. UPDATE PROCESS
Updated automatically daily by 10:00 Pacific

D. HOW TO USE THIS DATASET
Read more about how to appropriately use identifiers, interpret different kinds of records, and limitations of analysis related to active privacy controls.

A. SUMMARY
Dispatched Calls-For-Service – Closed Calls includes all calls for service which generate a record in the Department of Emergency Management's Computer Aided Dispatch (CAD) System, and typically have a law enforcement unit dispatched to the location. Calls originate from the public via calls to the 911 call center or from law enforcement officers in the field upon viewing an incident (‘On-View’). The Closed Calls dataset includes only calls for service that have been closed, and is updated every 24 hours, to include the initial call type, final call type and call disposition. Not all Calls for Service generate a Police Incident Report, so data does not directly correlate to the Police Incidents Report dataset. All relevant time intervals are also included. Dataset contains calls handled by law enforcement which can include Police, MTA parking enforcement, the Sheriff’s Office, and others. Some Calls for Service data is suppressed, due to the nature of the call and privacy concerns related to the incident.

Please refer to the 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 daily at 2:00am with previous days data.

D. HOW TO USE THIS DATASET
Please refer Dispatched Calls for Service Explainer for full documentation

E. KEY RELATED DATASETS
Datasets:
Law Enforcement Dispatched Calls for Service: Real-time
Police Department Incident Reports: 2018 to Present
Fire Department Calls for Service

Geographic Boundaries:
Current Police Districts
Analysis Neighborhoods
Supervisor Districts

These department codes are maintained in the City's financial system of record. Department Groups, Divisions, Sections, Units, Sub Units and Departments are nested in the dataset from left to right. Each nested unit has both a code and an associated name.

The dataset represents a flattened tree (hierarchy) so that each leaf on the tree has it's own row. Thus certain rows will have repeated codes across columns.

Data changes as needed.