San Francisco Data

Author: OpenData
Description: Note: All incident locations are mapped to nearby intersections to ensure anonymity. The locations of incidents reported before April 24, 2024 are currently mapped to a slightly different set of intersections than those reported on or after April 24. This may result in slight reporting irregularities for analyses that span this date. We will harmonize all historical data and resolve this as soon as possible. A. SUMMARY Read the <a href="https://sfdigitalservices.gitbook.io/dataset-explainers/sfpd-incident-report-2018-to-present">detailed overview of this dataset</a>. 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. <a href="https://support.datasf.org/help/police-department-incident-reports-2018-to-present-overview">Read more about how incident reports are created and approved in the detailed overview of this dataset</a>. C. UPDATE PROCESS Updated automatically daily by 10:00 Pacific D. HOW TO USE THIS DATASET <a href="https://sfdigitalservices.gitbook.io/dataset-explainers/sfpd-incident-report-2018-to-present">Read more about</a> how to appropriately use identifiers, interpret different kinds of records, and limitations of analysis related to active privacy controls.
Category: Public Safety
Tags: crime, crime reports, sfpd, police department
Rating: Current value: 0 out of 5
Data Provided By: Police Department
Source Link: https://www.sanfranciscopolice.org/
License: Public Domain Dedication and License

Police Department Incident Reports: 2018 to PresentNote: All incident locations are mapped to nearby intersections to ensure anonymity. The locations of incidents reported before April 24, 2024 are currently mapped to a slightly different set of intersections than those reported on or after April 24. This may result in slight reporting irregularities for analyses that span this date. We will harmonize all historical data and resolve this as soon as possible. A. SUMMARY Read the <a href="https://sfdigitalservices.gitbook.io/dataset-explainers/sfpd-incident-report-2018-to-present">detailed overview of this dataset</a>. 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. <a href="https://support.datasf.org/help/police-department-incident-reports-2018-to-present-overview">Read more about how incident reports are created and approved in the detailed overview of this dataset</a>. C. UPDATE PROCESS Updated automatically daily by 10:00 Pacific D. HOW TO USE THIS DATASET <a href="https://sfdigitalservices.gitbook.io/dataset-explainers/sfpd-incident-report-2018-to-present">Read more about</a> how to appropriately use identifiers, interpret different kinds of records, and limitations of analysis related to active privacy controls.Visit the full page to view this data.

This view cannot be displayed

Embed this Dataset

      <div><iframe width="_width_px" title="Police Department Incident Reports: 2018 to Present" height="_height_px" src="https://data.sfgov.org/w/wg3w-h783/ikek-yizv?cur=FAr3JZ9Er_B&from=T3d03JWb8bx" frameborder="0"scrolling="no"><a href="https://data.sfgov.org/Public-Safety/Police-Department-Incident-Reports-2018-to-Present/wg3w-h783" title="Police Department Incident Reports: 2018 to Present" target="_blank">Police Department Incident Reports: 2018 to Present</a></iframe><p><a href="http://www.socrata.com/" target="_blank">Powered by Tyler Technologies</a></p></div>

Size

500x425
760x646
950x808

Custom Size

425x425 is the minimum size

Width

Height

The Socrata Open Data API (SODA) provides programmatic access to this dataset including the ability to filter, query, and aggregate data. For more more information, view the API docs for this dataset or visit our developer portal

API Endpoint:

Field Names:

Incident Datetime: incident_datetime
Incident Date: incident_date
Incident Time: incident_time
Incident Year: incident_year
Incident Day of Week: incident_day_of_week
Report Datetime: report_datetime
Row ID: row_id
Incident ID: incident_id
Incident Number: incident_number
CAD Number: cad_number
Report Type Code: report_type_code
Report Type Description: report_type_description
Filed Online: filed_online
Incident Code: incident_code
Incident Category: incident_category
Incident Subcategory: incident_subcategory
Incident Description: incident_description
Resolution: resolution
Intersection: intersection
CNN: cnn
Police District: police_district
Analysis Neighborhood: analysis_neighborhood
Supervisor District: supervisor_district
Supervisor District 2012: supervisor_district_2012
Latitude: latitude
Longitude: longitude
Point: point
Neighborhoods: :@computed_region_jwn9_ihcz
ESNCAG - Boundary File: :@computed_region_jg9y_a9du
Central Market/Tenderloin Boundary Polygon - Updated: :@computed_region_h4ep_8xdi
Civic Center Harm Reduction Project Boundary: :@computed_region_n4xg_c4py
HSOC Zones as of 2018-06-05: :@computed_region_nqbw_i6c3
Invest In Neighborhoods (IIN) Areas: :@computed_region_viu7_rrfi
Current Supervisor Districts: :@computed_region_26cr_cadq
Current Police Districts: :@computed_region_qgnn_b9vv

Use OData to open the dataset in tools like Excel or Tableau. This provides a direct connection to the data that can be refreshed on-demand within the connected application.

Socrata OData documentation

Tableau users should select the OData v2 endpoint option.

San Francisco Data

API Endpoint:

Field Names:

OData V4 Endpoint:

OData V2 Endpoint:

Want to leave a comment?

You are leaving data.sfgov.org.

Notice