The Existing Buildings Energy Performance Ordinance (Environment Code Chapter 20) requires that each non-residential building with at least 10,000 square feet of conditioned (heated or cooled) space and each residential building with at least 50,000 square feet of conditioned space must be benchmarked using Energy Star Portfolio Manager annually. Each non-residential building specified above is also required to undergo an energy audit or retrocommissioning at least once every 5 years. More information: www.sfenvironment.org/ebo. This dataset lists compliance status for private-sector (non-municipal) properties where the owner has been notified a building is subject to the ordinance. Fields reported have expand as of early October 2015 to include energy use intensity, the 1-100 Portfolio Manager rating, and estimated greenhouse gas emissions from annual energy consumption.
A. SUMMARY A list of testing locations including address and coordinates for mapping.
B. HOW THE DATASET IS CREATED Dataset is manually compiled by staff from the various testing providers.
C. UPDATE PROCESS Data is updated as needed. If you have a site you'd like added to the dataset and map, please email DPH.DOC.Ops.Testing@sfdph.org.
D. HOW TO USE THIS DATASET Dataset can be used to map locations of test sites and understand which require insurance and which do not. It is the base data used to power the user-facing map of testing locations at https://datasf.org/covid19-testing-locations
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.
A. SUMMARY Medical provider confirmed COVID-19 cases and confirmed COVID-19 related deaths in San Francisco, CA aggregated by several different geographic areas and normalized by 2018 American Community Survey (ACS) 5-year estimates for population data to calculate rate per 10,000 residents.
Cases and deaths are both mapped to the residence of the individual, not to where they were infected or died. For example, if one was infected in San Francisco at work but lives in the East Bay, those are not counted as SF Cases or if one dies in Zuckerberg San Francisco General but is from another county, that is also not counted in this dataset.
Dataset is cumulative and covers cases going back to March 2nd, 2020 when testing began. It is updated daily.
B. HOW THE DATASET IS CREATED Addresses from medical 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. The 2018 ACS estimates for population provided by the Census are used to create a rate which is equal to ([count] / [acs_population]) * 10000) representing the number of cases per 10,000 residents.
C. UPDATE PROCESS Geographic analysis is scripted by SFDPH staff and synced to this dataset each day.
D. HOW TO USE THIS DATASET Privacy rules in effect To protect privacy, certain rules are in effect:
1. Case counts greater than 0 and less than 10 are dropped - these will be null (blank) values
2. Death counts greater than 0 and less than 10 are dropped - these will be null (blank) values
3. Cases and deaths dropped altogether for areas where acs_population < 1000
Rate suppression in effect where counts lower than 20 Rates are not calculated unless the 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.
Row included for Citywide case counts, incidence rate, and deaths A single row is included that has the Citywide case counts and incidence rate. This can be used for comparisons. Citywide will capture all cases regardless of address quality. While some cases cannot be mapped to sub-areas like Census Tracts, ongoing data quality efforts result in improved mapping on a rolling bases.
Snapshot of San Francisco Development Pipeline. Tracking of construction and entitlement activity based on data from Dept of Building Inspection's Permit Tracking and the Planning Department's Case Tracking enterprise databases, processed quarterly.
Neighborhood notification boundaries created by the Department of City Planning. These boundaries are designed solely for the Planning Department's neighborhood notifications where neighborhood groups are notified about certain types of developments in their area. An Excel spreadsheet of Neighborhood Groups contact details can be downloaded from this page: http://sf-planning.org/index.aspx?page=1654 There are alternative neighborhood boundaries available (which include a larger number of neighborhoods) here (Mayors Office): https://data.sfgov.org/d/pty2-tcw4 and here (Realtors): https://data.sfgov.org/d/5gzd-g9ns
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.