Comment on page
SFPD Incident Report: 2018 to Present
The San Francisco Police Department’s (SFPD) Incident Report Datatset is one of the most used datasets on DataSF. The dataset compiles data from the department’s Crime Data Warehouse (CDW) to provide information on incident reports filed by the SFPD in CDW, or filed by the public with the SFPD.
The incident report dataset is good at providing counts of incident reports, by type, date, time and location. This information can be used to help understand the number, location, and nature, of incidents of crime that are reported to or reported by the SFPD. Geographic information is anonymized and provided to help understand incident reports across neighborhoods, police districts and supervisorial districts. Provision of date information allows for analysis of data trends over time.
No. While incident reports may serve as the basis for official crime statistics, official crime statistics are governed by the FBI’s UCR and NIBRS program. The most recent official UCR/NIBRS statistical release from the SFPD can be found via the California Department of Justice’s Open Justice portal.
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 types based on how the report was received and the type of incident:
- 1.Initial Reports: the first report filed for an incident
- 2.Supplemental Reports: a follow up report to an initial, Coplogic or vehicle report.
- 3.Coplogic Reports: incident reports filed by members of the public using SFPD’s online reporting system
- 4.Vehicle Reports: any incident reports related to stolen and/or recovered vehicles
All incident reports must be approved by a supervising Sergeant or Lieutenant. Once a supervising officer has provided approval via electronic signature, no further changes can be made to the initial report. If changes or additional information is required or discovered during an investigation, a supplemental report may be generated to capture updates.
For example, a supplemental report may be issued to show an arrest was made, a missing person was found, or to provide additional details of property taken in a theft. To differentiate between the initial and supplemental reports, a filter can be applied to the “Report Type Description” field. Failing to filter between the initial and supplemental report can lead to double counting of incidents.
The department uses a Secure File Transfer Protocol (SFTP) feed to share incident data with DataSF daily.
Incident reports can have one or more associated Incident Codes. For example, an officer may have a warrant for an arrest and while making the arrest, discovers narcotics in the individual’s possession. The officer would record two Incident Codes: (1) for the warrant and (2) for the discovery of narcotics.
When multiple Incident Codes exist, the Incident ID, Incident Number and CAD Numbers remain the same and the Row ID field can be used as a unique identifier for each row of data. An example is provided below.
Incident reports do not necessarily capture all data surrounding policing and crime. This dataset does not capture citations (unless an associated incident report was written with the citation.) For example, a routine speeding ticket would generally not require an incident report, however, a speeding ticket that reveals a driver with a felony warrant leading to an arrest would require an incident report.
This dataset does not include any identifiable information of any person (suspect, victim, reporting party, officer, witness, etc). This dataset may not capture other law enforcement agency incidents within San Francisco (BART PD, US Park Police, for example), or reports not filed with the SFPD.
The release of this data must balance the need for disclosure to the public against the risk of violating the privacy of those individuals present within the dataset. As such, the dataset is subject to several privacy controls to ensure anonymity for all persons within the data.
- 1.All incident locations are shown at the intersection level only.
- 2.Records involving juveniles have been withheld from this dataset.
- 3.All records coded as confidential have been withheld from this dataset.
Incident reports may be removed from the dataset in compliance with court orders to seal records or for administrative purposes such as active internal affairs investigations and/or criminal investigations. The data shared does not include personally identifiable information on any person within the dataset (suspect, victim, reporting party, officer, witness, etc).
Coordinates associated with incident locations provided within the dataset are anonymized and reflect the nearest intersection of each occurrence. Intersections used in the masking are associated with either 0 or greater than 11 premise addresses. A premise address is a specific place of work or residence. Some coordinates may be omitted for the following reasons:
- 1.Invalid addresses - addresses submitted by officer’s pass-through validation, however, the online submission does not validate addresses on entry. While best efforts are made to match those to valid addresses when loading to the Crime Data Warehouse, there are still technical limitations to fixing all poorly formed addresses.
- 2.Addresses for incidents outside of SF - some cases are referred from outside SFPD districts. These will be marked as “Out of SF” in the Police District column and do not have associated geographic information.
Per California Government Code (GC) § 6254 and California Welfare and Institutions Code § 827, incidents identifying juvenile information will not be available in this dataset. All incidents with a resolution of “Cite or Arrest Juvenile” and/or “Exceptional Juvenile” have been removed from this dataset. In addition, the following juvenile related Incident Codes have been removed from this dataset:
The removal of juvenile related data in 2020 resulted in the retention of 3,581 records, or about 2.82% of the unredacted 2020 dataset.
Juvenile Records Retained, by Crime Category - 2020
The SFPD routinely codifies certain incident reports as confidential for various reasons. These reasons include at the request of the reporting party, due to the sensitivity of the investigation, or at the request of the investigator or chain of command.
In 2020, 7,414 confidential flagged reports were retained by the department, or about 5.8% of the unredacted dataset. Of the 7,414 reports, 53% were also flagged as domestic violence reports.