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.

For up to date data starting in 2018, please go to the new dataset at: https://data.sfgov.org/d/wg3w-h783

As of May 2018, the feed from the legacy mainframe CABLE was discontinued. It was extremely prone to issues and caused many delays in data accessibility. The new dataset linked above comes from the Crime Data Warehouse, a more reliable data system maintained by the Police Department.

This data will undergo a minor update to conform more closely to the schema of the new dataset. We will post a change notice when that work is planned. This change will not include adding new fields or backfilling data. It is provided as is. We are keeping data from the two systems separate to make it transparent to data users that there were fundamental changes.

A. SUMMARY
These data represent hate crimes reported by the SFPD to the California Department of Justice. Read the detailed overview of this dataset here.

What is a Hate Crime?
A hate crime is a crime against a person, group, or property motivated by the victim's real or perceived protected social group. An individual may be the victim of a hate crime if they have been targeted because of their actual or perceived: (1) disability, (2) gender, (3) nationality, (4) race or ethnicity, (5) religion, (6) sexual orientation, and/or (7) association with a person or group with one or more of these actual or perceived characteristics. Hate crimes are serious crimes that may result in imprisonment or jail time.

B. HOW THE DATASET IS CREATED
How is a Hate Crime Processed?
Not all prejudice incidents including the utterance of hate speech rise to the level of a hate crime. The U.S. Constitution allows hate speech if it does not interfere with the civil rights of others. While these acts are certainly hurtful, they do not rise to the level of criminal violations and thus may not be prosecuted. When a prejudice incident is reported, the reporting officer conducts a preliminary investigation and writes a crime or incident report. Bigotry must be the central motivation for an incident to be determined to be a hate crime. In that report, all facts such as verbatims or statements that occurred before or after the incident and characteristics such as the race, ethnicity, sex, religion, or sexual orientations of the victim and suspect (if known) are included. To classify a prejudice incident, the San Francisco Police Department’s Hate Crimes Unit of the Special Investigations Division conducts an analysis of the incident report to determine if the incident falls under the definition of a “hate crime” as defined by state law.
California Penal Code 422.55 - Hate Crime Definition

C. UPDATE PROCESS
These data are updated monthly.

D. HOW TO USE THIS DATASET
This dataset includes the following information about each incident: the hate crime offense, bias type, location/time, and the number of hate crime victims and suspects. The data presented mirrors data published by the California Department of Justice, albeit at a higher frequency. The publishing of these data meet requirements set forth in PC 13023.

E. RELATED DATASETS
California Department of Justice - Hate Crimes Info
California Department of Justice - Hate Crimes Data

A. SUMMARY
The San Francisco Police Department (SFPD) Stop Data was designed to capture information to comply with the Racial and Identity Profiling Act (RIPA), or California Assembly Bill (AB)953. SFPD officers collect specific information on each stop, including elements of the stop, circumstances and the perceived identity characteristics of the individual(s) stopped. The information obtained by officers is reported to the California Department of Justice. This dataset includes data on stops starting on July 1st, 2018, which is when the data collection program went into effect. Read the detailed overview for this dataset here.

B. HOW THE DATASET IS CREATED
By the end of each shift, officers enter all stop data into the Stop Data Collection System, which is automatically submitted to the California Department of Justice (CA DOJ). Once a quarter the Department receives a stops data file from CA DOJ. The SFPD conducts several transformations of this data to ensure privacy, accuracy and compliance with State law and regulation. For increased usability, text descriptions have also been added for several data fields which include numeric codes (including traffic, suspicion, citation, and custodial arrest offense codes, and actions taken as a result of a stop). See the data dictionaries below for explanations of all coded data fields. Read more about the data collection, and transformation, including geocoding and PII cleaning processes, in the detailed overview of this dataset.

C. UPDATE PROCESS
Information is updated on a quarterly basis.

D. HOW TO USE THIS DATASET
This dataset includes information about police stops that occurred, including some details about the person(s) stopped, and what happened during the stop. Each row is a person stopped with a record identifier for the stop and a unique identifier for the person. A single stop may involve multiple people and may produce more than one associated unique identifier for the same record identifier. A certain percentage of stops have stop information that can’t be geocoded. This may be due to errors in data input at the officer level (typos in entry or providing an address that doesn't exist). More often, this is due to officers providing a level of detail that isn't codable to a geographic coordinate - most often at the Airport (ie: Terminal 3, door 22.) In these cases, the location of the stops is coded as unknown.

E. DATA DICTIONARIES
CJIS Offense Codes data look up table