A. SUMMARY This is an open data set of all known City domains with associated registrar, department, and owner information. The City and County of San Francisco (City) seeks to serve the public with trustworthy, consistent, reliable and safe websites, regardless of department or service. To accomplish this goal, the Domain Registration and Management Policy standardizes and unifies the internet domain process. B. HOW THE DATASET IS CREATED Digital Services audited all city-owned websites and compiled this data in coordination with department stakeholders. C. UPDATE PROCESS This dataset will update daily. D. HOW TO USE THIS DATASET This dataset can be used to track the status of city-owned websites. E. KNOWN USES This dataset is essential for Department of Technology and Digital Services to create a plan for City-owned websites and email to move to the SF.gov domain or a subdomain by June 30, 2026. In compliance with AB1637 and the Domain Registration and Management Policy, all San Francisco government websites must migrate to a .gov domain by January 1, 2028.

Summary The City and County of San Francisco contracts with hundreds of nonprofit organizations to provide services for San Franciscans. These services include healthcare, legal aid, shelter, children’s programming, and more. This dataset contains all payments issued to nonprofit organizations by City departments since FY2019. This dataset will be updated at the close of each fiscal year. The underlying data is pulled from Supplier Payments on SF OpenBook. Please use SF OpenBook to find current-year data. The data in this dataset are presented in easy-to-read dashboards on our website. View the dashboards here: https://www.sf.gov/data/san-francisco-nonprofit-contracts-and-spending. How the dataset is created The Controller’s Office performs several significant data cleaning steps before uploading this dataset to the SF Open Data Portal. Please read the cleaning steps below: Cleaning Steps 1. SF OpenBook provides a filter labeled “Non-Profits Only” (Yes, No), and resulting datasets exported from SF OpenBook include a “Non Profit” column to indicate whether the supplier is a nonprofit (Yes, Blank). However, this field is not always accurate and excludes about 150 known nonprofits that are not labeled as a nonprofit in the City’s financial system. To ensure a complete dataset, we exported a full list of supplier payment data from SF OpenBook with the “Non-Profits Only” field filtered to “No” which provides a list of all supplier payments regardless of nonprofit status. We cleaned this data by adding a new “Nonprofit” column within the dataset and used this column to note a nonprofit status of “Yes” for approximately 150 known nonprofit suppliers without this indicator flagged in the financial system in addition to any nonprofits already accurately flagged in the system. We then filtered the full dataset using the new nonprofit column and used the filtered data for all of the dashboards on the webpage linked above. The list of excluded nonprofits may change over time as information gets updated in the City’s data system. Download the cleaned and updated dataset on the City’s Open Data Portal, which includes all of the known nonprofits. 2. While the University of California, San Francisco (UCSF) is technically not-for-profit, a university’s financial management is very different from traditional nonprofit service providers, and the City’s agreement with UCSF includes hospital staffing in addition to contracted services to the public. As such, the Controller's Office created a nonprofit column to be able to exclude payments to UCSF when reporting on overall spending. There are divisions of UCSF that provide more traditional contracted services, but these cannot be clearly identified in the data. Note that filtering out this data may reflect an underrepresentation of overall spending. 3. The Controller's Office also excludes several specific contracts that are predominately “pass through” payments where the nonprofit provider receives funds that they disperse to other agencies, such as for childcare or workforce subsidies. These types of contracts are substantially different from contracts where the nonprofit is providing direct services to San Franciscans. Update process This dataset will be manually updated after year-end financial processing is complete, typically in September. There may be a delay between the end of the fiscal year and the publication of this dataset.

A. SUMMARY The Municipal Natural Gas Equipment Inventory serves to catalog natural gas-fueled equipment used in municipally owned buildings. This inventory, implemented by the SF Environment Department, aims to establish an understanding of the scope of work needed to electrify municipal buildings and inform an effective and collaborative planning process. This effort was identified as an action in Section BO-2.4 of the 2021 Climate Action Plan and is included in the Environment Code Chapter 7 (Municipal Green Building Requirements). B. HOW THE DATASET IS CREATED The list of buildings required to report data for the Municipal Natural Gas Equipment Inventory was compiled by cross-referencing the City’s Facility Systems of Record and the 2020 municipal benchmarking report to identify all city-owned buildings with non-zero carbon emissions. Numerous municipal buildings are exempt from these reporting requirements, including facilities of the Port of San Francisco and buildings with a primary purpose of providing collection, storage, treatment, delivery, distribution, and/or transmission of water, wastewater, and/or power utilities. Each department received an inventory template, provided by the Environment Department, to submit high level building data and detailed information on each piece of natural gas equipment in use in these buildings. Departments were asked to self-report the required building and equipment data over the course of a 6-month data collection period in 2023 and are asked to keep this inventory up to date in the following years as equipment is replaced. C. UPDATE PROCESS The inventory will be regularly updated by department representatives via the inventory PowerApp. When a gas-powered equipment item is retired or replaced, departments are asked to mark it as no longer in use and provide information on any electric replacement equipment, if applicable. While departments have the flexibility to update the inventory at any time, they are encouraged to do so at 6 month intervals at the minimum. Updated inventory data will be automatically reflected in this dataset. D. HOW TO USE THIS DATASET It is important to note that this dataset does not include facilities of the Port of San Francisco and buildings with a primary purpose of providing collection, storage, treatment, delivery, distribution, and/or transmission of water, wastewater, and/or power utilities, in accordance with Environment Code Chapter 7 exemptions.

A. SUMMARY This data is an annual snapshot of existing land use as of March of the indicated year for every parcel in the City and County of San Francisco. This year's 2023 data was produced from the Land Use 2020, updated for residential properties using the Planning Department's permit database and current 2023 Assessor-Recorder data. The commercial data was not updated; the commercial data will be updated in next year's 2024 release. Each row of data corresponds to a parcel with 16 columns (fields or attributes) of information about each parcel, as described below. B. HOW THE DATASET IS CREATED The dataset is assembled from a range of City and commercial databases, including Assessor’s office and Dun & Bradstreet for commercial land uses. C. UPDATE PROCESS A new dataset will be added annually without updating previous years’ data. D. HOW TO USE THIS DATASET Review this document to understand the data (fields and their categories): Land Use Database 2023 Summary Limitations: Although every attempt is made to provide accurate data, the volume of data and parcels does not allow the Department to guarantee accuracy. Should errors be found, or questions arise, please email rebecca.latto@sfgov.org. E. RELATED DATASETS San Francisco Land Use - 2020

A. SUMMARY This dataset includes data on a variety of substance use services funded by the San Francisco Department of Public Health (SFDPH). This dataset only includes Drug MediCal-certified residential treatment, withdrawal management, and methadone treatment. Other private non-Drug Medi-Cal treatment providers may operate in the city. Withdrawal management discharges are inclusive of anyone who left withdrawal management after admission and may include someone who left before completing withdrawal management. This dataset also includes naloxone distribution from the SFDPH Behavioral Health Services Naloxone Clearinghouse and the SFDPH-funded Drug Overdose Prevention and Education program. Both programs distribute naloxone to various community-based organizations who then distribute naloxone to their program participants. Programs may also receive naloxone from other sources. Data from these other sources is not included in this dataset. Finally, this dataset includes the number of clients on medications for opioid use disorder (MOUD). The number of people who were treated with methadone at a Drug Medi-Cal certified Opioid Treatment Program (OTP) by year is populated by the San Francisco Department of Public Health (SFDPH) Behavioral Health Services Quality Management (BHSQM) program. OTPs in San Francisco are required to submit patient billing data in an electronic medical record system called Avatar. BHSQM calculates the number of people who received methadone annually based on Avatar data. Data only from Drug MediCal certified OTPs were included in this dataset. The number of people who receive buprenorphine by year is populated from the Controlled Substance Utilization Review and Evaluation System (CURES), administered by the California Department of Justice. All licensed prescribers in California are required to document controlled substance prescriptions in CURES. The Center on Substance Use and Health calculates the total number of people who received a buprenorphine prescription annually based on CURES data. Formulations of buprenorphine that are prescribed only for pain management are excluded. People may receive buprenorphine and methadone in the same year, so you cannot add the Buprenorphine Clients by Year, and Methadone Clients by Year data together to get the total number of unique people receiving medications for opioid use disorder. For more information on where to find treatment in San Francisco, visit findtreatment-sf.org.  B. HOW THE DATASET IS CREATED This dataset is created by copying the data into this dataset from the SFDPH Behavioral Health Services Quality Management Program, the California Controlled Substance Utilization Review and Evaluation System (CURES), and the Office of Overdose Prevention. C. UPDATE PROCESS Residential Substance Use Treatment, Withdrawal Management, Methadone, and Naloxone data are updated quarterly with a 45-day delay. Buprenorphine data are updated quarterly and when the state makes this data available, usually at a 5-month delay. D. HOW TO USE THIS DATASET Throughout the year this dataset may include partial year data for methadone and buprenorphine treatment. As both methadone and buprenorphine are used as long-term treatments for opioid use disorder, many people on treatment at the end of one calendar year will continue into the next. For this reason, doubling (methadone), or quadrupling (buprenorphine) partial year data will not accurately project year-end totals. E. RELATED DATASETS Overdose-Related 911 Responses by Emergency Medical Services Unintentional Overdose Death Rates by Race/Ethnicity Preliminary Unintentional Drug Overdose Deaths

A. SUMMARY In compliance with CA Government Code 6270.5 (passed via SB 272), the City must publish a catalog of enterprise systems that collect data about the public. There are certain exceptions to this detailed in the Government Code. The code is available here. B. HOW THE DATASET IS CREATED This dataset is collated through 2 ways: 1. Ongoing updates are made throughout the year to reflect new or retired systems, this process involves DataSF staff reconciling records at the request of departments 2. Annual bulk updates - departments review their inventories and identify changes and updates and submit those to DataSF for a once a year bulk update - not all departments will have changes or their changes will have been captured over the course of the prior year already as ongoing updates C. UPDATE PROCESS The dataset changes infrequently and is uploaded manually as needed by DataSF staff D. HOW TO USE THIS DATASET Companion dataset inventory dataset A companion dataset of inventoried and published datasets can be accessed online as well.

A. SUMMARY This is a dataset containing points representing the midpoint of each block in the City of San Francisco. This dataset is used for geomasking (e.g. removing an exact address and replacing it with a nearby anonymized point) and other anonymization tasks. B. HOW THE DATASET IS CREATED This dataset was created by calculating the midpoint of each the street segment in the city (see Streets - Active and Retired) then returning the latitude and longitude of that midpoint. A street segment is a line between two intersections. Street midpoints are calculated for each side of the block. C. UPDATE PROCESS This dataset is updated weekly. D. HOW TO USE THIS DATASET Use this dataset for geomasking and other anonymization workflows. E. RELATED DATASETS - Streets - Active and Retired

A. SUMMARY This data represents the boundaries of City-owned lands maintained in the City's Facility System of Record (FSR). Note: Not all lands are within the City and County proper. The City owns properties outside of its boundaries, including lands managed by SF Recreation and Parks, SF Public Utilities Commission, and other agencies. Certain lands are managed by following agencies which are not directly part of the City and County of San Francisco, but are included here for reference: San Francisco Housing Authority (SFHA), San Francisco Office of Community Investment and Infrastructure (OCII), and City College of San Francisco. B. HOW THE DATASET IS CREATED The Enterprise GIS program in the Department of Technology is the technical custodian of the FSR. This team creates and maintains this dataset in conjunction with the Real Estate Division and the Capital Planning Program of the City Administrator’s Office, who act as the primary business data stewards for this data. C. UPDATE PROCESS There are a handful of events that may trigger changes to this dataset: 1. The sale of a property 2. The leasing of a property 3. The purchase of a property 4. The change in jurisdiction of a property (e.g. from MTA to DPW) 5. The removal or improvement of the property Each of these changes triggers a workflow that updates the FSR. The Real Estate Division and Capital Planning make updates on an ongoing basis. The full dataset is reviewed quarterly to ensure nothing is missing or needs to be corrected. Updates to the data, once approved, are immediately reflected in the internal system and are updated here in the open dataset on a monthly basis. D. HOW TO USE THIS DATASET See here for an interactive map of all the City lands in this dataset. To track the facilities on City lands, join this dataset to the City Facilities dataset using the land_id field. If you see an error in the data, you can submit a change request with the relevant information to dtis.helpdesk@sfgov.org. Please be as specific about the error as you can (including relevant land_id(s)). E. RELATED DATASETS City Facilities

The purpose of the San Francisco Communitywide Greenhouse Gas Inventory is to measure and track greenhouse gas emissions to determine progress towards meeting the City's climate action goals. The Department of the Environment collects this data from various sources and calculates the emissions per current greenhouse gas protocols. This data supports San Francisco's climate change planning and mitigation strategies. Note: Greenhouse gas emissions were calculated based on the ICLEI 2012 U.S. Community Protocol Version 1.0. San Francisco inventories are completed in accordance with the ICLEI U.S. Community Protocol (USCP) for Accounting and Reporting of Greenhouse Gas Emissions. The methodology and sectors tracked were third party verified in inventory year 2012. The subsequent inventories are completed according to the guidance of the verifiers. The third-party verification memo for 2010 is available at http://sfenvironment.org/download/2010-community-greenhouse-gas-inventory-3rd-party-verification-memo-march-2013 and for 2012 at http://sfenvironment.org/download/2012-community-greenhouse-gas-inventory-3rd-party-verification-memo-january-2015. In 2015, the City began reporting its emissions to C40 to improve its GHG emissions inventory by using a newer protocol to estimate emissions referred to as the Global Protocol for Community-Scale Greenhouse Gas Emissions Inventories (GPC). GPC is a framework unifying emissions inventories globally while incorporating new categories to track. San Francisco has been tracking its emissions since 1990; hence, it continues to use the ICLEI USCP. Today, San Francisco continues to disclose emissions under the GPC framework for reporting purposes to and compliance with the Global Covenant of Mayors (GCOM).

A. SUMMARY The San Francisco Controller's Office maintains a database of the salary and benefits paid to City employees since fiscal year 2013. B. HOW THE DATASET IS CREATED This data is summarized and presented on the Employee Compensation report hosted at http://openbook.sfgov.org, and is also available in this dataset in CSV format. C. UPDATE PROCESS New data is added on a bi-annual basis when available for each fiscal and calendar year. D. HOW TO USE THIS DATASET Before using please first review the following two resources: