INTRODUCTION: As California’s homeless population continues to grow at an alarming rate, large metropolitan regions like the San Francisco Bay Area face unique challenges in coordinating efforts to track and improve homelessness. As an interconnected region of nine counties with diverse community needs, identifying homeless population trends across San Francisco Bay Area counties can help direct efforts more effectively throughout the region, and inform initiatives to improve homelessness at the city, county, and metropolitan level. OBJECTIVES: The primary objective of this research is to compare the annual Point-in-Time (PIT) counts of homelessness across San Francisco Bay Area counties between the years 2018-2022. The secondary objective of this research is to compare the annual Point-in-Time (PIT) counts of homelessness among different age groups in each of the nine San Francisco Bay Area counties between the years 2018-2022. METHODS: Two datasets were used to conduct research. The first dataset (Dataset 1) contains Point-in-Time (PIT) homeless counts published by the U.S. Department of Housing and Urban Development. Dataset 1 was cleaned using Microsoft Excel and uploaded to Tableau Desktop Public Edition 2022.4.1 as a CSV file. The second dataset (Dataset 2) was published by Data SF and contains shapefiles of geographic boundaries of San Francisco Bay Area counties. Both datasets were joined in Tableau Desktop Public Edition 2022.4 and all data analysis was conducted using Tableau visualizations in the form of bar charts, highlight tables, and maps. RESULTS: Alameda, San Francisco, and Santa Clara counties consistently reported the highest annual count of people experiencing homelessness across all 5 years between 2018-2022. Alameda, Napa, and San Mateo counties showed the largest increase in homelessness between 2018 and 2022. Alameda County showed a significant increase in homeless individuals under the age of 18. CONCLUSIONS: Results from this research reveal both stark and fluctuating differences in homeless counts among San Francisco Bay Area Counties over time, suggesting that a regional approach that focuses on collaboration across counties and coordination of services could prove beneficial for improving homelessness throughout the region. Results suggest that more immediate efforts to improve homelessness should focus on the counties of Alameda, San Francisco, Santa Clara, and San Mateo. Changes in homelessness during the COVID-19 pandemic years of 2020-2022 point to an urgent need to support Contra Costa County.

A log of dataset alerts open, monitored or resolved on the open data portal. Alerts can include issues as well as deprecation or discontinuation notices.

VITAL SIGNS INDICATOR Population (LU1)

FULL MEASURE NAME Population estimates

LAST UPDATED October 2019

DESCRIPTION Population is a measurement of the number of residents that live in a given geographical area, be it a neighborhood, city, county or region.

DATA SOURCES U.S Census Bureau: Decennial Census No link available (1960-1990) http://factfinder.census.gov (2000-2010)

California Department of Finance: Population and Housing Estimates Table E-6: County Population Estimates (1961-1969) Table E-4: Population Estimates for Counties and State (1971-1989) Table E-8: Historical Population and Housing Estimates (2001-2018) Table E-5: Population and Housing Estimates (2011-2019) http://www.dof.ca.gov/Forecasting/Demographics/Estimates/

U.S. Census Bureau: Decennial Census - via Longitudinal Tract Database Spatial Structures in the Social Sciences, Brown University Population Estimates (1970 - 2010) http://www.s4.brown.edu/us2010/index.htm

U.S. Census Bureau: American Community Survey 5-Year Population Estimates (2011-2017) http://factfinder.census.gov

U.S. Census Bureau: Intercensal Estimates Estimates of the Intercensal Population of Counties (1970-1979) Intercensal Estimates of the Resident Population (1980-1989) Population Estimates (1990-1999) Annual Estimates of the Population (2000-2009) Annual Estimates of the Population (2010-2017) No link available (1970-1989) http://www.census.gov/popest/data/metro/totals/1990s/tables/MA-99-03b.txt http://www.census.gov/popest/data/historical/2000s/vintage_2009/metro.html https://www.census.gov/data/datasets/time-series/demo/popest/2010s-total-metro-and-micro-statistical-areas.html

CONTACT INFORMATION vitalsigns.info@bayareametro.gov

METHODOLOGY NOTES (across all datasets for this indicator) All legal boundaries and names for Census geography (metropolitan statistical area, county, city, and tract) are as of January 1, 2010, released beginning November 30, 2010, by the U.S. Census Bureau. A Priority Development Area (PDA) is a locally-designated area with frequent transit service, where a jurisdiction has decided to concentrate most of its housing and jobs growth for development in the foreseeable future. PDA boundaries are current as of August 2019. For more information on PDA designation see http://gis.abag.ca.gov/website/PDAShowcase/.

Population estimates for Bay Area counties and cities are from the California Department of Finance, which are as of January 1st of each year. Population estimates for non-Bay Area regions are from the U.S. Census Bureau. Decennial Census years reflect population as of April 1st of each year whereas population estimates for intercensal estimates are as of July 1st of each year. Population estimates for Bay Area tracts are from the decennial Census (1970 -2010) and the American Community Survey (2008-2012 5-year rolling average; 2010-2014 5-year rolling average; 2013-2017 5-year rolling average). Estimates of population density for tracts use gross acres as the denominator.

Population estimates for Bay Area PDAs are from the decennial Census (1970 - 2010) and the American Community Survey (2006-2010 5 year rolling average; 2010-2014 5-year rolling average; 2013-2017 5-year rolling average). Population estimates for PDAs are derived from Census population counts at the tract level for 1970-1990 and at the block group level for 2000-2017. Population from either tracts or block groups are allocated to a PDA using an area ratio. For example, if a quarter of a Census block group lies with in a PDA, a quarter of its population will be allocated to that PDA. Tract-to-PDA and block group-to-PDA area ratios are calculated using gross acres. Estimates of population density for PDAs use gross acres as the denominator.

Annual population estimates for metropolitan areas outside the Bay Area are from the Census and are benchmarked to each decennial Census. The annual estimates in the 1990s were not updated to match the 2000 benchmark.

The following is a list of cities and towns by geographical area: Big Three: San Jose, San Francisco, Oakland Bayside: Alameda, Albany, Atherton, Belmont, Belvedere, Berkeley, Brisbane, Burlingame, Campbell, Colma, Corte Madera, Cupertino, Daly City, East Palo Alto, El Cerrito, Emeryville, Fairfax, Foster City, Fremont, Hayward, Hercules, Hillsborough, Larkspur, Los Altos, Los Altos Hills, Los Gatos, Menlo Park, Mill Valley, Millbrae, Milpitas, Monte Sereno, Mountain View, Newark, Pacifica, Palo Alto, Piedmont, Pinole, Portola Valley, Redwood City, Richmond, Ross, San Anselmo, San Bruno, San Carlos, San Leandro, San Mateo, San Pablo, San Rafael, Santa Clara, Saratoga, Sausalito, South San Francisco, Sunnyvale, Tiburon, Union City, Vallejo, Woodside Inland, Delta and Coastal: American Canyon, Antioch, Benicia, Brentwood, Calistoga, Clayton, Cloverdale, Concord, Cotati, Danville, Dixon, Dublin, Fairfield, Gilroy, Half Moon Bay, Healdsburg, Lafayette, Livermore, Martinez, Moraga, Morgan Hill, Napa, Novato, Oakley, Orinda, Petaluma, Pittsburg, Pleasant Hill, Pleasanton, Rio Vista, Rohnert Park, San Ramon, Santa Rosa, Sebastopol, Sonoma, St. Helena, Suisun City, Vacaville, Walnut Creek, Windsor, Yountville Unincorporated: all unincorporated towns

This raster dataset depicts the population denisty of the nine county San Francisco Bay Area Region, California produced with a Dasymetric Mapping Technique, which is used to depict quantitative areal data using boundaries that divide an area into zones of relative homogeneity with the purpose of better portraying the population distribution. The source data was then adjusted in order to get convert the units to persons per acre. This dataset is an accurate representation of population distribution within census boundaries and can be used in a number of ways, including as the Conservation Suitability layer for the Marxan inputs and the watershed integrity analysis.

VITAL SIGNS INDICATOR Population (LU1)

FULL MEASURE NAME
Population estimates

LAST UPDATED
February 2023

DESCRIPTION
Population is a measurement of the number of residents that live in a given geographical area, be it a neighborhood, city, county or region.

DATA SOURCE
California Department of Finance: Population and Housing Estimates - http://www.dof.ca.gov/Forecasting/Demographics/Estimates/
Table E-6: County Population Estimates (1960-1970)
Table E-4: Population Estimates for Counties and State (1970-2021)
Table E-8: Historical Population and Housing Estimates (1990-2010)
Table E-5: Population and Housing Estimates (2010-2021)

Bay Area Jurisdiction Centroids (2020) - https://data.bayareametro.gov/Boundaries/Bay-Area-Jurisdiction-Centroids-2020-/56ar-t6bs
Computed using 2020 US Census TIGER boundaries

U.S. Census Bureau: Decennial Census Population Estimates - http://www.s4.brown.edu/us2010/index.htm- via Longitudinal Tract Database Spatial Structures in the Social Sciences, Brown University
1970-2020

U.S. Census Bureau: American Community Survey (5-year rolling average; tract) - https://data.census.gov/
2011-2021
Form B01003

Priority Development Areas (Plan Bay Area 2050) - https://opendata.mtc.ca.gov/datasets/MTC::priority-development-areas-plan-bay-area-2050/about

CONTACT INFORMATION
vitalsigns.info@bayareametro.gov

METHODOLOGY NOTES (across all datasets for this indicator)
All historical data reported for Census geographies (metropolitan areas, county, city and tract) use current legal boundaries and names. A Priority Development Area (PDA) is a locally-designated area with frequent transit service, where a jurisdiction has decided to concentrate most of its housing and jobs growth for development in the foreseeable future. PDA boundaries are current as of December 2022.

Population estimates for Bay Area counties and cities are from the California Department of Finance, which are as of January 1st of each year. Population estimates for non-Bay Area regions are from the U.S. Census Bureau. Decennial Census years reflect population as of April 1st of each year whereas population estimates for intercensal estimates are as of July 1st of each year. Population estimates for Bay Area tracts are from the decennial Census (1970-2020) and the American Community Survey (2011-2021 5-year rolling average). Estimates of population density for tracts use gross acres as the denominator.

Population estimates for Bay Area tracts and PDAs are from the decennial Census (1970-2020) and the American Community Survey (2011-2021 5-year rolling average). Population estimates for PDAs are allocated from tract-level Census population counts using an area ratio. For example, if a quarter of a Census tract lies with in a PDA, a quarter of its population will be allocated to that PDA. Estimates of population density for PDAs use gross acres as the denominator. Note that the population densities between PDAs reported in previous iterations of Vital Signs are mostly not comparable due to minor differences and an updated set of PDAs (previous iterations reported Plan Bay Area 2040 PDAs, whereas current iterations report Plan Bay Area 2050 PDAs).

The following is a list of cities and towns by geographical area:

Big Three: San Jose, San Francisco, Oakland

Bayside: Alameda, Albany, Atherton, Belmont, Belvedere, Berkeley, Brisbane, Burlingame, Campbell, Colma, Corte Madera, Cupertino, Daly City, East Palo Alto, El Cerrito, Emeryville, Fairfax, Foster City, Fremont, Hayward, Hercules, Hillsborough, Larkspur, Los Altos, Los Altos Hills, Los Gatos, Menlo Park, Mill Valley, Millbrae, Milpitas, Monte Sereno, Mountain View, Newark, Pacifica, Palo Alto, Piedmont, Pinole, Portola Valley, Redwood City, Richmond, Ross, San Anselmo, San Bruno, San Carlos, San Leandro, San Mateo, San Pablo, San Rafael, Santa Clara, Saratoga, Sausalito, South San Francisco, Sunnyvale, Tiburon, Union City, Vallejo, Woodside

Inland, Delta and Coastal: American Canyon, Antioch, Benicia, Brentwood, Calistoga, Clayton, Cloverdale, Concord, Cotati, Danville, Dixon, Dublin, Fairfield, Gilroy, Half Moon Bay, Healdsburg, Lafayette, Livermore, Martinez, Moraga, Morgan Hill, Napa, Novato, Oakley, Orinda, Petaluma, Pittsburg, Pleasant Hill, Pleasanton, Rio Vista, Rohnert Park, San Ramon, Santa Rosa, Sebastopol, Sonoma, St. Helena, Suisun City, Vacaville, Walnut Creek, Windsor, Yountville

Unincorporated: all unincorporated towns

A. SUMMARY Medical provider confirmed COVID-19 cases and confirmed COVID-19 related deaths in San Francisco, CA aggregated by Census ZIP Code Tabulation 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. Cases 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 polygonal representations of USPS ZIP Code service area routes. Read how the Census develops ZCTAs on their website.

This dataset is a filtered view of another dataset You can find a full dataset of cases and deaths summarized by this and other geographic areas.

E. CHANGE LOG

• 9/11/2023 - data on COVID-19 cases and deaths summarized by ZIP code tabulation area are no longer being updated. This data is currently through 9/6/2023 and will not include any new data after this date.

This data release is comprised of geospatial and tabular data developed for the HayWired communities at risk analysis. The HayWired earthquake scenario is a magnitude 7.0 earthquake hypothesized to occur on the Hayward Fault on April 18, 2018, with an epicenter in the city of Oakland, CA. The following 17 counties are included in this analysis unless otherwise specified: Alameda, Contra Costa, Marin, Merced, Monterey, Napa, Sacramento, San Benito, San Francisco, San Joaquin, San Mateo, Santa Clara, Santa Cruz, Solano, Sonoma, Stanislaus, and Yolo. The vector data are a geospatial representation of building damage based on square footage damage estimates by Hazus occupancy class for developed areas covering all census tracts in 17 counties in and around the San Francisco Bay region in California, for (1) earthquake hazards (ground shaking, landslide, and liquefaction) and (2) all hazards (ground shaking, landslide, liquefaction, and fire) resulting from the HayWired earthquake scenario mainshock. The tabular data cover: (1) damage estimates, by Hazus occupancy class, of square footage, building counts, and households affected by the HayWired earthquake scenario mainshock for all census tracts in 17 counties in and around the San Francisco Bay region in California; (2) potential total population residing in block groups in nine counties in the San Francisco Bay region in California (Alameda, Contra Costa, Marin, Napa, San Francisco, San Mateo, Santa Clara, Solano, and Sonoma); (3) a subset of select tables for 17 counties in and around the San Francisco Bay region in California from the U.S. Census Bureau American Community Survey 5-year (2012-2016) estimates at the block group level selected to represent potentially vulnerable populations that may, in the event of a major disaster, leave an area rather than stay; and (4) building and contents damage estimates (in thousands of dollars, 2005 vintage), by Hazus occupancy class, for the HayWired earthquake scenario mainshock for 17 counties in and around the San Francisco Bay region in California. The vector .SHP datasets were developed and intended for use in GIS applications such as ESRI's ArcGIS software suite. The tab-delimited .TXT datasets were developed and intended for use in standalone spreadsheet or database applications (such as Microsoft Excel or Access). Please note that some of these data are not optimized for use in GIS applications (such as ESRI's ArcGIS software suite) as-is--census tracts or counties are repeated (the data are not "one-to-one"), so not all information belonging to a tract or county would necessarily be associated with a single record. Separate preparation is needed in a standalone spreadsheet or database application like Microsoft Excel or Microsoft Access before using these data in a GIS. These data support the following publications: Johnson, L.A., Jones, J.L., Wein, A.M., and Peters, J., 2020, Communities at risk analysis of the HayWired scenario, chaps. U1-U5 of Detweiler, S.T., and Wein, A.M., eds., The HayWired earthquake scenario--Societal consequences: U.S. Geological Survey Scientific Investigations Report 2017-5013, https://doi.org/10.3133/sir20175013.

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 2016-2020 American Community Survey (ACS) 5-year estimates for population data to calculate rate per 10,000 residents. On September 12, 2021, a new case definition of COVID-19 was introduced that includes criteria for enumerating new infections after previous probable or confirmed infections (also known as reinfections). A reinfection is defined as a confirmed positive PCR lab test more than 90 days after a positive PCR or antigen test. The first reinfection case was identified on December 7, 2021. 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 3/2/2020 when testing began. Geographic areas summarized are: 1. Analysis Neighborhoods 2. Census Tracts 3. Census Zip Code Tabulation Areas 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 2016-2020 American Community Survey (ACS) population estimates 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 daily at 7:30 Pacific Time. D. HOW TO USE THIS DATASET San Francisco population estimates for geographic regions can be found in a view based on the San Francisco Population and Demographic Census dataset. These population estimates are from the 2016-2020 5-year American Community Survey (ACS). 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, ongo

About this dataset

Context

The dataset presents the median household income across different racial categories in San Francisco township. It portrays the median household income of the head of household across racial categories (excluding ethnicity) as identified by the Census Bureau. The dataset can be utilized to gain insights into economic disparities and trends and explore the variations in median houshold income for diverse racial categories.

Key observations

Based on our analysis of the distribution of San Francisco township population by race & ethnicity, the population is predominantly White. This particular racial category constitutes the majority, accounting for 95.31% of the total residents in San Francisco township. Notably, the median household income for White households is $133,763. Interestingly, White is both the largest group and the one with the highest median household income, which stands at $133,763.

https://i.neilsberg.com/ch/san-francisco-township-mn-median-household-income-by-race.jpeg" alt="San Francisco township median household income diversity across racial categories">

Content

When available, the data consists of estimates from the U.S. Census Bureau American Community Survey (ACS) 2017-2021 5-Year Estimates.

Racial categories include:

• White
• Black or African American
• American Indian and Alaska Native
• Asian
• Native Hawaiian and Other Pacific Islander
• Some other race
• Two or more races (multiracial)

Variables / Data Columns

• Race of the head of household: This column presents the self-identified race of the household head, encompassing all relevant racial categories (excluding ethnicity) applicable in San Francisco township.
• Median household income: Median household income, adjusting for inflation, presented in 2022-inflation-adjusted dollars

Good to know

Margin of Error

Data in the dataset are based on the estimates and are subject to sampling variability and thus a margin of error. Neilsberg Research recommends using caution when presening these estimates in your research.

Custom data

If you do need custom data for any of your research project, report or presentation, you can contact our research staff at research@neilsberg.com for a feasibility of a custom tabulation on a fee-for-service basis.

Inspiration

Neilsberg Research Team curates, analyze and publishes demographics and economic data from a variety of public and proprietary sources, each of which often includes multiple surveys and programs. The large majority of Neilsberg Research aggregated datasets and insights is made available for free download at https://www.neilsberg.com/research/.

Recommended for further research

This dataset is a part of the main dataset for San Francisco township median household income by race. You can refer the same here

Table of population and demographic forecast numbers from Plan Bay Area 2040 for the San Francisco Bay Region. Population and demographic numbers are included for 2005, 2010, 2015, 2020, 2030, 2035, and 2040. There are no forecast numbers for 2025.The Plan Bay Area forecast numbers were generated by Transportation Analysis Zone (TAZ). The Population and Demographics forecast table will need to be joined to TAZ features in order to spatially visualize the data. The TAZ features are available for download here.2005-2040 data in this table:Total PopulationHousehold PopulationGroup Quarters Population0 - 4 Age Group5 - 19 Age Group20 - 44 Age Group44 - 64 Age Group65+ Age GroupShare of Total Population that is 62 and OverHigh School EnrollmentCollege Enrollment (full-time)College Enrollment (part-time)Other Plan Bay Area 2040 forecast tables:Employment (total employment, TAZ resident employment, retail employment, financial and professional services employment, health, educational, and recreational employment, manufacturing, wholesale, and transportation employment, agricultural and natural resources employment, and other employment)Households (number of households and household income quartile)Land Use and Transportation (area type, commercial or industrial acres, residential acres, number of single-family and multi-family dwelling units, time to get from automobile storage location to origin/destination, and hourly parking rates)

This feature set contains household and population projections from Projections 2040 for the San Francisco Bay Region. This forecast represents household and population projections resulting from Plan Bay Area 2040. Numbers are provided by county. Household and population numbers are included for 2010 (two versions), 2015, 2020, 2025, 2030, 2035, and 2040. For 2010, two data points are provided:A tabulation (base year A) from the 2010 model simulation (base year A); and(Preferred) A tabulation (base year B) from the 2010 pre-run microdata, designed to approximate (but may still differ from) Census 2010 counts.Projection data is included for total households, group quarter population, household population, persons per household, and total population.This feature set was assembled using unclipped county features. For those who prefer Projections 2040 data using county features with ocean and bay waters clipped out, the data in this feature service can be joined to San Francisco Bay Region Counties (clipped).Other Projections 2040 feature sets:Households and population per jurisdiction (incorporated place and unincorporated county)Households and population per Census TractJobs and employment per countyJobs and employment per jurisdiction (incorporated place and unincorporated county)Jobs per Census TractFemale population, by age range, per countyFemale population, by age range, per jurisdiction (incorporated place and unincorporated county)Male population, by age range, per countyMale population, by age range, per jurisdiction (incorporated place and unincorporated county)Total population, by age range, per countyTotal population, by age range, per jurisdiction (incorporated place and unincorporated county)

Tracts; January 1, 2019 vintage; Generalized

Features provide a view of 2020 Census tracts for the San Francisco Bay Region. Features are a subset of the Census Tracts 500k service at https://data.bayareametro.gov/dataset/Census-Tracts-500K/dg5p-pxcu.

Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses.

Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline.

Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy.

In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.

For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes.

Relationship to Other Geographic Entities—Within the standard census geographic hierarchy, census tracts never cross state or county boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian, Alaska Native, and Native Hawaiian areas.

Incorporated Places (cities and towns) are those reported to the Census Bureau as legally in existence as of May 28, 2021, under the laws of their respective states. Features were extracted from, and clipped using, California 2020 TIGER/Line shapefiles by the Metropolitan Transportation Commission. An incorporated place provides governmental functions for a concentration of people, as opposed to a minor civil division, which generally provides services or administers an area without regard, necessarily, to population. Places may extend across county and county subdivision boundaries, but never across state boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions.

Please refer to the downloadable XLSX attachment for the complete dataset, metadata, and instructions for use. On behalf of San Francisco Municipal Transportation Agency (SFMTA), Corey, Canapary & Galanis (CC&G) conducted the 2021 Mode Share Survey within the City and County of San Francisco as well as the eight surrounding Bay Area counties (Alameda, Contra Costa, San Mateo, Marin, Santa Clara, Napa, Sonoma and Solano). This study has been conducted periodically by CC&G since 2013. Primary goals of this study include: • Estimate mode share for trips into, within, and out of San Francisco, focusing on the percentage of trips made by walking, biking, and public transit compared to other modes (e.g. driving, TNC, etc.). This survey is the primary instrument for tracking the SFMTA Strategic Plan metric “transportation mode share” and provides information used by the agency across divisions. • Evaluation of the above statement based on the number of trips to, from, and within San Francisco by Bay Area residents. Note that trips by visitors from outside the Bay Area, and for commercial purposes whether originating in the Bay Area or not, are not included. • Provide additional trip details, including trip purpose for each trip in the mode share question series. • Collect demographic data on the population of Bay Area residents who travel to, from, and within San Francisco. The survey was conducted as a telephone study among 756 Bay Area residents aged 18 and older. Telephone surveying was conducted during May – September 2021. Interviewing was conducted in English, Spanish, and Chinese. Surveying was conducted via random digit dial (RDD) and cell phone sample. To enhance statistical accuracy, data was weighted by age and _location. Not all totals will add to 100% due to rounding. In portions of this report, a dash (-) is used to indicate no respondents answered with the response code listed. The margin of error at the 95% confidence level is +/-3.56% for the total sample (n = 756). For other sample sizes, the margin of error is as follows: • San Francisco residents; n = 470. Margin of error = +/- 4.52% • Bay Area residents (outside San Francisco) n = 286. Margin of error = +/- 5.79%

Analysis of ‘COVID-19 Cases and Deaths Summarized by Geography’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/d2e381bb-f395-4b40-979e-920a79a3db88 on 11 February 2022.

--- Dataset description provided by original source is as follows ---

Note: On January 22, 2022, system updates to improve the timeliness and accuracy of San Francisco COVID-19 cases and deaths data were implemented. You might see some fluctuations in historic data as a result of this change. Due to the changes, starting on January 22, 2022, the number of new cases reported daily will be higher than under the old system as cases that would have taken longer to process will be reported earlier.

Note: As of April 16, 2021, this dataset will update daily with a five-day data lag.

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

Geographic areas summarized are: 1. Analysis Neighborhoods 2. Census Tracts 3. Census Zip Code Tabulation Areas

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 2019 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 daily at 7:30 Pacific Time.

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.

--- Original source retains full ownership of the source dataset ---

Transportation Analysis Zones (TAZs) are used in the Metropolitan Transportation Commission travel and Urban Sim models for the San Francisco Bay Region. These models are used in processes to forecast population growth, economic growth, and transportation/transit capacity and responsiveness and then distribute those results throughout the region.Data tables containing modeling results are joined to the TAZ features using a zone id (taz1454). Tables currently available for download are as follows:Plan Bay Area 2040 ForecastEmployment (total employment, TAZ resident employment, retail employment, financial and professional services employment, health, educational, and recreational employment, manufacturing, wholesale, and transportation employment, agricultural and natural resources employment, and other employment)Households (number of households and household income quartile)Land Use and Transportation (area type, commercial or industrial acres, residential acres, number of single-family and multi-family dwelling units, time to get from automobile storage location to origin/destination, and hourly parking rates)Population and Demographics (total population, household and group quarter populations, population by age group, share of population that is 62+, high school enrollment, and college enrollment)

VITAL SIGNS INDICATOR Daily Miles Traveled (T14)

FULL MEASURE NAME Total vehicle miles traveled

LAST UPDATED July 2017

DESCRIPTION Daily miles traveled, commonly referred to as vehicle miles traveled (VMT), reflects the total and per-person number of miles traveled in personal vehicles on a typical weekday. The dataset includes metropolitan area, regional and county tables for total vehicle miles traveled.

DATA SOURCE California Department of Transportation: California Public Road Data/Highway Performance Monitoring System 2001-2015 http://www.dot.ca.gov/hq/tsip/hpms/datalibrary.php

CONTACT INFORMATION vitalsigns.info@mtc.ca.gov

METHODOLOGY NOTES (across all datasets for this indicator) Vehicle miles traveled reflects the mileage accrued within the county and not necessarily the residents of that county; even though most trips are due to local residents, additional VMT can be accrued by through-trips. City data was thus discarded due to this limitation and the analysis only examine county and regional data, where through-trips are generally less common.

The metropolitan area comparison was performed by summing all of the urbanized areas for which the majority of its population falls within a given metropolitan area (9-nine region for the San Francisco Bay Area and the primary MSA for all others). For the metro analysis, no VMT data is available in rural areas; it is only available for intraregional analysis purposes.

This feature layer contains census tracts for the San Francisco Bay Region for Census 2000. The features were extracted from a statewide data set downloaded from the United States Census Bureau by Metropolitan Transportation Commission staff.The purpose of this feature layer is for the production of feature sets for public access and download to avoid licensing issues related to the agency's base data.Source data downloaded from https://www.census.gov/geographies/mapping-files/time-series/geo/tiger-line-file.html_The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the United States Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation.Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the Census 2000 Participant Statistical Areas Program (PSAP). The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,500 and 8,000 people, with an optimum size of 4,000 people.When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, etc. may require boundary revisions before a census. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries are always census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.

2020 Census tracts for the San Francisco Bay Region. Features were extracted from California 2021 TIGER/Line shapefile by the Metropolitan Transportation Commission.Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses.Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline.Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy.In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous.For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.The Census Bureau uses suffixes to help identify census tract changes for comparison purposes. Local participants have an opportunity to review the existing census tracts before each census. If local participants split a census tract, the split parts usually retain the basic number, but receive different suffixes. In a few counties, local participants request major changes to, and renumbering of, the census tracts. Changes to individual census tract boundaries usually do not result in census tract numbering changes.Relationship to Other Geographic Entities—Within the standard census geographic hierarchy, census tracts never cross state or county boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian, Alaska Native, and Native Hawaiian areas.

VITAL SIGNS INDICATOR Daily Miles Traveled (T15)

FULL MEASURE NAME Per-capita vehicle miles traveled

LAST UPDATED July 2017

DESCRIPTION Daily miles traveled, commonly referred to as vehicle miles traveled (VMT), reflects the total and per-person number of miles traveled in personal vehicles on a typical weekday. The dataset includes metropolitan area, regional and county tables for per-capita vehicle miles traveled.

DATA SOURCE California Department of Transportation: California Public Road Data/Highway Performance Monitoring System 2001-2015 http://www.dot.ca.gov/hq/tsip/hpms/datalibrary.php

California Department of Finance: Population and Housing Estimates Forms E-8 and E-5 2001-2015 http://www.dof.ca.gov/research/demographic/reports/estimates/e-8/ http://www.dof.ca.gov/research/demographic/reports/estimates/e-5/2011-20/view.php

U.S. Census Bureau: Summary File 1 2010 http://factfinder2.census.gov

CONTACT INFORMATION vitalsigns.info@mtc.ca.gov

METHODOLOGY NOTES (across all datasets for this indicator) Vehicle miles traveled reflects the mileage accrued within the county and not necessarily the residents of that county; even though most trips are due to local residents, additional VMT can be accrued by through-trips. City data was thus discarded due to this limitation and the analysis only examine county and regional data, where through-trips are generally less common.

The metropolitan area comparison was performed by summing all of the urbanized areas within each metropolitan area (9-nine region for the San Francisco Bay Area and the primary MSA for all others). For the metro analysis, no VMT data is available outside of other urbanized areas; it is only available for intraregional analysis purposes.

VMT per capita is calculated by dividing VMT by an estimate of the traveling population. The traveling population does not include people living in institutionalized facilities, which are defined by the Census. Because institutionalized population is not estimated each year, the proportion of people living in institutionalized facilities from the 2010 Census was applied to the total population estimates for all years.