Note: As of April 16, 2021, this dataset will update daily with a five-day data lag.
A. SUMMARY This dataset contains COVID-19 positive confirmed cases aggregated by several different geographic areas and by day. COVID-19 cases are mapped to the residence of the individual and shown on the date the positive test was collected. In addition, 2019 American Community Survey (ACS) 5-year population estimates are included to calculate the cumulative rate per 10,000 residents.
Dataset covers cases going back to March 2nd, 2020 when testing began. This data may not be immediately available for recently reported cases and data will change to reflect as information becomes available. Data updated daily.
B. HOW THE DATASET IS CREATED Addresses from the COVID-19 case data are geocoded by the San Francisco Department of Public Health (SFDPH). Those addresses are spatially joined to the geographic areas. Counts are generated based on the number of address points that match each geographic area for a given date.
The 2019 ACS estimates for population provided by the Census are used to create a cumulative rate which is equal to ([cumulative count up to that date] / [acs_population]) * 10000) representing the number of total cases per 10,000 residents (as of the specified date).
COVID-19 case data undergo quality assurance and other data verification processes and are continually updated to maximize completeness and accuracy of information. This means data may change for previous days as information is updated.
C. UPDATE PROCESS Geographic analysis is scripted by SFDPH staff and synced to this dataset daily at 05:00 Pacific Time.
D. HOW TO USE THIS DATASET This dataset can be used to track the spread of COVID-19 throughout the city, in a variety of geographic areas. Note that the new cases column in the data represents the number of new cases confirmed in a certain area on the specified day, while the cumulative cases column is the cumulative total of cases in a certain area as of the specified date.
Privacy rules in effect To protect privacy, certain rules are in effect:
1. Any area with a cumulative case count less than 10 are dropped for all days the cumulative count was less than 10. These will be null values.
2. Once an area has a cumulative case count of 10 or greater, that area will have a new row of case data every day following.
3. Cases are dropped altogether for areas where acs_population < 1000
4. Deaths data are not included in this dataset for privacy reasons. The low COVID-19 death rate in San Francisco, along with other publicly available information on deaths, means that deaths data by geography and day is too granular and potentially risky. Read more in our privacy guidelines
Rate suppression in effect where counts lower than 20 Rates are not calculated unless the cumulative case count is greater than or equal to 20. Rates are generally unstable at small numbers, so we avoid calculating them directly. We advise you to apply the same approach as this is best practice in epidemiology.
A note on Census ZIP Code Tabulation Areas (ZCTAs) ZIP Code Tabulation Areas are special boundaries created by the U.S. Census based on ZIP Codes developed by the USPS. They are not, however, the same thing. ZCTAs are areal representations of routes. Read how the Census develops ZCTAs on their website.
Privately-owned public open spaces (POPOS) are publicly accessible spaces in forms of plazas, terraces, atriums, small parks, and even snippets which are provided and maintained by private developers. In San Francisco, POPOS mostly appear in the Downtown office district area. Prior to 1985, developers provided POPOS under three general circumstances: voluntarily, in exchange for a density bonus, or as a condition of approval. The 1985 Downtown Plan created the first systemic requirements for developers to provide publicly accessible open space as a part of projects in C-3 Districts. The goal was to “provide in the downtown quality open space in sufficient quantity and variety to meet the needs of downtown workers, residents and visitors.” (See Planning Code Section 138 for regulations). Since then, project sponsors for residential projects may provide POPOS instead of their required open spaces in the Downtown Residential (DTR) and Eastern Neighborhoods (Section 135 of the Planning Code). Learn more at http://sf-planning.org/privately-owned-public-open-space-and-public-art-popos
The Department of Public Health and the Mayor’s Office of Housing and Community Development, with support from the Planning Department, created 41 neighborhoods by grouping 2010 Census tracts, using common real estate and residents’ definitions for the purpose of providing consistency in the analysis and reporting of socio-economic, demographic, and environmental data, and data on City-funded programs and services. They are not codified in Planning Code nor Administrative Code.
This dataset is produced by assigning Census tracts to neighborhoods based on existing neighborhood definitions used by Planning and MOHCD. A qualitative assessment is made to identify the appropriate neighborhood for a given tract based on an understanding of population distribution and significant landmarks. Once all tracts have been assigned a neighborhood, the tracts are combined to produce Analysis Neighborhoods which is available at https://data.sfgov.org/d/p5b7-5n3h
The San Francisco Controller's Office maintains a database of payments made to vendors from fiscal year 2007 forward. This data is presented on the Vendor Payments report hosted at http://openbook.sfgov.org, and is also available in this dataset in CSV format, which represents summary data by purchase order. We have removed sensitive information from this data – this is intended to show payments made to entities providing goods and services to the City and County and to protect individuals. For example, we have removed payments to employees (reimbursements, garnishments) and jury members, revenue refunds, payments for judgments and claims, witnesses, relocation and rehousing, and a variety of human services payments. New data is added on a weekly basis.
Supplier payments represent payments to City contractors and vendors that provide goods and/or services to the City. Certain other non-supplier payee payments, which are made to parties other than traditional City contractors and vendors, are also included in this dataset, These include payments made for tax and fee refunds, rebates, settlements, etc.
San Francisco Campaign and Governmental Conduct Code ("S.F. C&GC Code") sections 1.143(c), 1.152(a)(3), 1.161(b), 1.161.5, and 1.160.5 require persons who make any independent expenditure, electioneering communication, or member communication that clearly identifies a candidate for City elective office or who authorizes, administers or pays for a persuasion poll to file disclosure statements with the Ethics Commission. For detailed instructions, please see Third Party Disclosure Form Regarding Candidates.
Annual Inventory Update Notice We have updated the inventory with provisional update as of July 1, 2020 based on an initial cleanup and reconciliation of records. DataSF staff are delayed on a full update because of the ongoing COVID-19 response but are working with departments to complete that annual update by end of July.
A. SUMMARY The dataset inventory provides a list of data maintained by departments that are candidates for open data publishing or have already been published and is collected in accordance with Chapter 22D of the Administrative Code. The inventory will be used in conjunction with department publishing plans to track progress toward meeting plan goals for each department. Department publishing plans are available at https://datasf.org/publishing/plans
B. HOW THE DATASET IS CREATED This dataset is collated through 2 ways:
1. Ongoing updates are made throughout the year to reflect new datasets, this process involves DataSF staff reconciling publishing records after datasets are published
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 is synced automatically daily, but the underlying data changes manually throughout the year as needed
D. HOW TO USE THIS DATASET Interpreting dates in this dataset This dataset has 3 dates:
1. Date Added - when the dataset was added to the inventory itself
2. First Published - when the dataset was initially published on the platform
3. Date Created on Platform - the open data portal automatically captures the date the dataset was first created, this is that system generated date
Note that in certain cases we may have published a dataset prior to it being added to the inventory. We do our best to have an accurate accounting of when something was added to this inventory and when it was published. In most cases the inventory addition will happen prior to publishing, but in certain cases it will be published and we will have missed updating the inventory as this is a manual process.
First published will give an accounting of when it was actually available on the open data catalog and date added when it was added to this list.
Date Created on Platform will show when a dataset was initially created. Because datasets are created and re-created as underlying systems changed, this date can be after the first published date if, for example, there was a new dataset published as an improvement over a previous one. Additionally, for new datasets, this date is often prior to the first published date as it is created, reviewed, QA'd and prepared for release.