Newly created and updated datasets for data.sf.gov

Filtered View Updated: Map of Fire Inspections

opendata@sfgov.org — Fri, 23 Oct 2026 09:29:37 +0000

Filterable on Inspection type and date performed

Filtered View Updated: SF Air Traffic Passenger Stats

opendata@sfgov.org — Thu, 22 Oct 2026 22:08:23 +0000

A. SUMMARY San Francisco International Airport Report on Monthly Passenger Traffic Statistics by Airline. B. HOW THE DATASET IS CREATED Data is self-reported by airlines and is only available at a monthly level C. UPDATE PROCESS Data updated quarterly D. HOW TO USE THIS DATASET Airport data is seasonal in nature, therefore any comparative analyses should be done on a period-over-period basis (i.e. January 2010 vs. January 2009) as opposed to period-to-period (i.e. January 2010 vs. February 2010). It is also important to note that fact and attribute field relationships are not always 1-to-1. For example, Passenger Counts belonging to United Airlines will appear in multiple attribute fields and are additive, which provides flexibility for the user to derive categorical Passenger Counts as desired.

Filtered View Updated: Dataset Ownership (Data Steward)

instrumentationresource@tylertech.onmicrosoft.com — Thu, 22 Oct 2026 19:07:11 +0000

This dataset is derived from the Data Asset Catalog and can be used to help data coordinators identify data stewards (or dataset owners) for the inventory process.

Filtered View Updated: SF Illegal lodging - Police Reports

opendata@sfgov.org — Thu, 22 Oct 2026 17:05:25 +0000

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 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.

Filtered View Updated: Shoplifting Reports at 4th St. and Minna St.

opendata@sfgov.org — Thu, 22 Oct 2026 17:05:25 +0000

Filtered View Updated: this years violations

opendata@sfgov.org — Thu, 22 Oct 2026 12:51:08 +0000

These records indicate the actual violations and comments by the inspector found during the inspection. The data should be sorted on the Complaint Number field and the Item Sequence Number field. The user should be able to link this file with the Building Complaints dataset (https://data.sfgov.org/d/gm2e-bten) to get a more accurate picture of the violations.

Filtered View Updated: violations by address

opendata@sfgov.org — Thu, 22 Oct 2026 12:51:08 +0000

Filtered View Updated: complaints by neighborhood

opendata@sfgov.org — Thu, 22 Oct 2026 12:51:08 +0000

Filtered View Updated: complaints by address/block+lot

opendata@sfgov.org — Thu, 22 Oct 2026 12:46:02 +0000

These are complaints from Housing, Building, Electrical, Plumbing, and Code Enforcement divisions within the Department of Building Inspection. Routine and non-routine inspections from the housing division are tracked using complaints only if violations are found during the inspections. The NOVTYPE field can be used to determine the source of the complaint.

Filtered View Updated: this years complaints

opendata@sfgov.org — Thu, 22 Oct 2026 12:46:02 +0000

Filtered View Updated: Eviction Heat Map

opendata@sfgov.org — Thu, 22 Oct 2026 12:22:58 +0000

Note 2/27/2024: There was a previous issue with this dataset that created duplicate rows for each record. This issue has been fixed. Data includes eviction notices filed with the San Francisco Rent Board per San Francisco Administrative Code 37.9(c). A notice of eviction does not necessarily indicate that the tenant was eventually evicted, so the notices below may differ from actual evictions. Notices are published since January 1, 1997.

Filtered View Updated: Osean

opendata@sfgov.org — Thu, 22 Oct 2026 11:25:24 +0000

Note 1/25/2024: The pipeline for this dataset was recently updated. If you see any issues please email support@datasf.org. Some changes you may see:
Change in formatting for unique_identifier, naics_codes, and lic_codes
Shifting in geospatial fields, e.g. neighborhood and business_corridor
SUMMARY This dataset includes the locations of businesses that pay taxes to the City and County of San Francisco. Each registered business may have multiple locations and each location is a single row. The Treasurer & Tax Collector’s Office collects this data through business registration applications, account update/closure forms, and taxpayer filings. Business locations marked as “Administratively Closed” have not filed or communicated with TTX for 3 years, or were marked as closed following a notification from another City and County Department. The data is collected to help enforce the Business and Tax Regulations Code including, but not limited to: Article 6, Article 12, Article 12-A, and Article 12-A-1. http://sftreasurer.org/registration. To learn more about using this dataset watch this video. To update your listing or look up your BAN see this FAQ: https://support.datasf.org/help/registered-business-faqs

Dataset Updated: category_tiles

system.publisher-l@socrata.com — Wed, 16 Sep 2026 23:42:15 +0000

Filtered View Updated: SFPD Traffic Stops over time

opendata@sfgov.org — Wed, 29 Jul 2026 22:15:39 +0000

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 Look up table for other coded data fields

Dataset Updated: wallpaper_banner

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:59:10 +0000

Dataset Updated: section_headers

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:59:06 +0000

Dataset Updated: sections

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:59:03 +0000

Dataset Updated: featured_stories

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:58:59 +0000

Dataset Updated: cityscape_resource_tiles

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:58:54 +0000

Dataset Updated: announcement_category_tile

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:58:47 +0000

Filtered View Created: Map of Fire Inspections

opendata@sfgov.org — Thu, 09 Apr 2026 23:58:29 +0000

Filterable on Inspection type and date performed

Dataset Created: wallpaper_banner

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:59:08 +0000

Dataset Created: section_headers

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:59:05 +0000

Dataset Created: sections

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:59:01 +0000

Dataset Created: featured_stories

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:58:56 +0000

Dataset Created: cityscape_resource_tiles

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:58:53 +0000

Dataset Created: category_tiles

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:58:49 +0000

Dataset Created: announcement_category_tile

system.publisher-l@socrata.com — Tue, 01 Jul 2025 22:58:46 +0000

Filtered View Created: SF Illegal lodging - Police Reports

opendata@sfgov.org — Tue, 10 Sep 2024 21:27:56 +0000

Filtered View Created: Shoplifting Reports at 4th St. and Minna St.

opendata@sfgov.org — Mon, 24 Jun 2024 03:15:47 +0000

Filtered View Created: Eviction Heat Map

opendata@sfgov.org — Wed, 15 May 2024 18:03:22 +0000

Filtered View Created: SFPD Traffic Stops over time

opendata@sfgov.org — Thu, 02 May 2024 21:54:03 +0000

Filtered View Created: SF Air Traffic Passenger Stats

opendata@sfgov.org — Sat, 17 Feb 2024 20:40:02 +0000

Filtered View Created: Osean

opendata@sfgov.org — Thu, 08 Feb 2024 01:21:12 +0000

Filtered View Created: this years complaints

opendata@sfgov.org — Tue, 21 Nov 2023 00:26:48 +0000

Filtered View Created: complaints by address/block+lot

opendata@sfgov.org — Sat, 11 Nov 2023 23:29:50 +0000

Filtered View Created: violations by address

opendata@sfgov.org — Sat, 11 Nov 2023 21:15:04 +0000

Filtered View Created: complaints by neighborhood

opendata@sfgov.org — Sat, 11 Nov 2023 21:05:37 +0000

Filtered View Created: this years violations

opendata@sfgov.org — Sat, 11 Nov 2023 20:59:52 +0000

Filtered View Created: Dataset Ownership (Data Steward)

instrumentationresource@tylertech.onmicrosoft.com — Tue, 25 Apr 2023 17:02:03 +0000

This dataset is derived from the Data Asset Catalog and can be used to help data coordinators identify data stewards (or dataset owners) for the inventory process.