Abstract

A crosswalk dataset matching US ZIP codes to corresponding census tracts

Documentation

The denominators used to calculate the address ratios are the ZIP code totals. When a ZIP is split by any of the other geographies, that ZIP code is duplicated in the crosswalk file.

**Example: **ZIP code 03870 is split by two different Census tracts, 33015066000 and 33015071000, which appear in the tract column. The ratio of residential addresses in the first ZIP-Tract record to the total number of residential addresses in the ZIP code is .0042 (.42%). The remaining residential addresses in that ZIP (99.58%) fall into the second ZIP-Tract record.

So, for example, if one wanted to allocate data from ZIP code 03870 to each Census tract located in that ZIP code, one would multiply the number of observations in the ZIP code by the residential ratio for each tract associated with that ZIP code.

https://redivis.com/fileUploads/4ecb405e-f533-4a5b-8286-11e56bb93368%3E" alt="">(Note that the sum of each ratio column for each distinct ZIP code may not always equal 1.00 (or 100%) due to rounding issues.)

Census tract definition

A census tract, census area, census district or meshblock is a geographic region defined for the purpose of taking a census. Sometimes these coincide with the limits of cities, towns or other administrative areas and several tracts commonly exist within a county. In unincorporated areas of the United States these are often arbitrary, except for coinciding with political lines.

Further reading

The following article demonstrates how to more effectively use the U.S. Department of Housing and Urban Development (HUD) United States Postal Service ZIP Code Crosswalk Files when working with disparate geographies.

Wilson, Ron and Din, Alexander, 2018. “Understanding and Enhancing the U.S. Department of Housing and Urban Development’s ZIP Code Crosswalk Files,” Cityscape: A Journal of Policy Development and Research, Volume 20 Number 2, 277 – 294. URL: https://www.huduser.gov/portal/periodicals/cityscpe/vol20num2/ch16.pdf

Contact information

Questions regarding these crosswalk files can be directed to Alex Din with the subject line HUD-Crosswalks.

Acknowledgement

This dataset is taken from the U.S. Department of Housing and Urban Development (HUD) office: https://www.huduser.gov/portal/datasets/usps_crosswalk.html#codebook

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) System (MTS). The MTS represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block groups are clusters of blocks within the same census tract. Each census tract contains at least one block group, and are uniquely numbered within census tracts. Block groups have a valid code range of 0 through 9. They also have the same first digit of their 4-digit census block number from the same decennial census. For example, tabulation blocks numbered 3001, 3002, 3003,.., 3999 within census tract 1210.02 are also within block group 3 within that census tract. Block groups coded 0 are intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. Block groups generally contain between 600 and 3,000 people. A block group usually covers a contiguous area but never crosses county or census tract boundaries. They may, however, cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. The block group boundaries in this release are those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

This data set contains Census 2020 population data for the State of Tennessee broken down by Census Tract. To read more about the 2020 Census data, you can go to the link below:

https://www.census.gov/programs-surveys/decennial-census/about/rdo/summary-files.html

This dataset contains data from the P.L. 94-171 2020 Census Redistricting Program. The 2020 Census Redistricting Data Program provides states the opportunity to delineate voting districts and to suggest census block boundaries for use in the 2020 Census redistricting data tabulations (Public Law 94-171 Redistricting Data File). In addition, the Redistricting Data Program will periodically collect state legislative and congressional district boundaries if they are changed by the states. The program is also responsible for the effective delivery of the 2020 Census P.L. 94-171 Redistricting Data statutorily required by one year from Census Day. The program ensures continued dialogue with the states in regard to 2020 Census planning, thereby allowing states ample time for their planning, response, and participation. The U.S. Census Bureau will deliver the Public Law 94-171 redistricting data to all states by Sept. 30, 2021. COVID-19-related delays and prioritizing the delivery of the apportionment results delayed the Census Bureau’s original plan to deliver the redistricting data to the states by April 1, 2021.

Data in this dataset contains information on population, diversity, race, ethnicity, housing, household, vacancy rate for 2020 for various geographies (county, MCD, Philadelphia Planning Districts (referred to as county planning areas [CPAs] internally, Census designated places, tracts, block groups, and blocks)

For more information on the 2020 Census, visit https://www.census.gov/programs-surveys/decennial-census/about/rdo/summary-files.html

PLEASE NOTE: 2020 Decennial Census data has had noise injected into it because of the Census's new Disclosure Avoidance System (DAS). This can mean that population counts and characteristics, especially when they are particularly small, may not exactly correspond to the data as collected. As such, caution should be exercised when examining areas with small counts. Ron Jarmin, acting director of the Census Bureau posted a discussion of the redistricting data, which outlines what to expect with the new DAS. For more details on accuracy you can read it here: https://www.census.gov/newsroom/blogs/director/2021/07/redistricting-data.html

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, 2016-2020 American Community Survey (ACS) population estimates are included to calculate the cumulative rate per 10,000 residents. Dataset covers cases going back to 3/2/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. Geographic areas summarized are: 1. Analysis Neighborhoods 2. Census Tracts 3. Census Zip Code Tabulation Areas 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 2016-2020 American Community Survey (ACS) population estimates 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 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). 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 spec

Notice: The U.S. Census Bureau is delaying the release of the 2016-2020 ACS 5-year data until March 2022. For more information, please read the Census Bureau statement regarding this matter. -----------------------------------------This layer shows population broken down by race and Hispanic origin. This layer shows Census data from Esri's Living Atlas and is clipped to only show Tempe census tracts. This layer is symbolized to show the predominant race living within an area. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online). Data is from US Census American Community Survey (ACS) 5-year estimates. Vintage: 2015-2019 ACS Table(s): B03002 (Not all lines of this ACS table are available in this feature layer.) Data downloaded from: Census Bureau's API for American Community Survey Date of Census update: December 10, 2020 National Figures: data.census.gov Additional Census data notes and data processing notes are available at the Esri Living Atlas Layer: https://tempegov.maps.arcgis.com/home/item.html?id=23ab8028f1784de4b0810104cd5d1c8f&view=list&sortOrder=desc&sortField=defaultFSOrder#overview (Esri's Living Atlas always shows latest data)

2020 Census Tract polygons for all of Pierce County, realigned to Pierce County roads, parcels, hydro, railroads, powerlines, etc. Population figures for race, ethnicity, median age, household size, household count, etc were downloaded from the US Census website and joined to this layer. Please read metadata for additional information (https://matterhorn.co.pierce.wa.us/GISmetadata/pdbis_census2020_tracts.html). Any data download constitutes acceptance of the Terms of Use (https://matterhorn.co.pierce.wa.us/Disclaimer/PierceCountyGISDataTermsofUse.pdf).

Historic 2000 Census Block Group polygons (have the same first digit of their four-digit identifiers within a census tract) for all of Pierce County, realigned to Pierce County roads, tax parcels, hydro, railroads, powerlines, etc. Population figures for race, ethnicity, median age, household size, household count, etc were downloaded from the US Census website and joined to this layer. Please read metadata for additional information (https://matterhorn.co.pierce.wa.us/GISmetadata/pdbis_census2000_block_groups.html). Any data download constitutes acceptance of the Terms of Use (https://matterhorn.co.pierce.wa.us/Disclaimer/PierceCountyGISDataTermsofUse.pdf).

2010 Census Tract polygons for all of Pierce County, realigned to Pierce County roads, parcels, hydro, railroads, powerlines, etc. Population figures for race, ethnicity, median age, household size, household count, etc were downloaded from the US Census website and joined to this layer. Please read metadata for additional information (https://matterhorn.co.pierce.wa.us/GISmetadata/pdbis_census2010_tracts.html). Any data download constitutes acceptance of the Terms of Use (https://matterhorn.co.pierce.wa.us/Disclaimer/PierceCountyGISDataTermsofUse.pdf).

Notice: The U.S. Census Bureau is delaying the release of the 2016-2020 ACS 5-year data until March 2022. For more information, please read the Census Bureau statement regarding this matter. -----------------------------------------This layer shows household income ranges for households, families, married couple families, and nonfamily households (as defined by the U.S. Census). Data is from US Census American Community Survey (ACS) 5-year estimates and joined with Tempe census tracts.This layer is symbolized to show median household income. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online). Layer includes: <!--· Total households (of various types including households, families, married couple families, and nonfamily households as defined by the U.S. Census) <!--· Household income brackets <!--· Household median income in dollars <!--· Household mean income in dollars An 'N' entry in the estimate indicates that data for this geographic area cannot be displayed because the number of sample cases is too small (per the U.S. Census). Data is from US Census American Community Survey (ACS) 5-year estimates. Current Vintage: 2015-2019 ACS Table(s): S1901 (Not all lines of this ACS table are available in this feature layer.) Data downloaded from: Census Bureau's API for American Community Survey Date of Census update: December 10, 2020 National Figures: data.census.gov

Historic 2000 Census Tract polygons for all of Pierce County, realigned to Pierce County roads, parcels, hydro, railroads, powerlines, etc. Population figures for race, ethnicity, median age, household size, household count, etc were downloaded from the US Census website and joined to this layer. Please read metadata for additional information (https://matterhorn.co.pierce.wa.us/GISmetadata/pdbis_census2000_tracts.html). Any data download constitutes acceptance of the Terms of Use (https://matterhorn.co.pierce.wa.us/Disclaimer/PierceCountyGISDataTermsofUse.pdf).

Abstract

A crosswalk matching US ZIP codes to corresponding CBSA (core-based statistical area)

Documentation

The denominators used to calculate the address ratios are the ZIP code totals. When a ZIP is split by any of the other geographies, that ZIP code is duplicated in the crosswalk file.

**Example: **ZIP code 03870 is split by two different Census tracts, 33015066000 and 33015071000, which appear in the tract column. The ratio of residential addresses in the first ZIP-Tract record to the total number of residential addresses in the ZIP code is .0042 (.42%). The remaining residential addresses in that ZIP (99.58%) fall into the second ZIP-Tract record.

So, for example, if one wanted to allocate data from ZIP code 03870 to each Census tract located in that ZIP code, one would multiply the number of observations in the ZIP code by the residential ratio for each tract associated with that ZIP code.

https://redivis.com/fileUploads/4ecb405e-f533-4a5b-8286-11e56bb93368%3E" alt="">(Note that the sum of each ratio column for each distinct ZIP code may not always equal 1.00 (or 100%) due to rounding issues.)

CBSA definition

A core-based statistical area (CBSA) is a U.S. geographic area defined by the Office of Management and Budget (OMB) that consists of one or more counties (or equivalents) anchored by an urban center of at least 10,000 people plus adjacent counties that are socioeconomically tied to the urban center by commuting. Areas defined on the basis of these standards applied to Census 2000 data were announced by OMB in June 2003. These standards are used to replace the definitions of metropolitan areas that were defined in 1990. The OMB released new standards based on the 2010 Census on July 15, 2015.

Further reading

The following article demonstrates how to more effectively use the U.S. Department of Housing and Urban Development (HUD) United States Postal Service ZIP Code Crosswalk Files when working with disparate geographies.

Wilson, Ron and Din, Alexander, 2018. “Understanding and Enhancing the U.S. Department of Housing and Urban Development’s ZIP Code Crosswalk Files,” Cityscape: A Journal of Policy Development and Research, Volume 20 Number 2, 277 – 294. URL: https://www.huduser.gov/portal/periodicals/cityscpe/vol20num2/ch16.pdf

Contact authors

Questions regarding these crosswalk files can be directed to Alex Din with the subject line HUD-Crosswalks.

Acknowledgement

This dataset is taken from the U.S. Department of Housing and Urban Development (HUD) office: https://www.huduser.gov/portal/datasets/usps_crosswalk.html#codebook

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

Notice: The U.S. Census Bureau is delaying the release of the 2016-2020 ACS 5-year data until March 2022. For more information, please read the Census Bureau statement regarding this matter. -----------------------------------------This layer shows language group of language spoken at home by age. This layer is Census data from Esri's Living Atlas and is clipped to only show Tempe census tracts. This layer is symbolized to show the percentage of the population age 5+ who speak Spanish at home. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Data is from US Census American Community Survey (ACS) 5-year estimates. Vintage: 2015-2019 ACS Table(s): B16007 (Not all lines of these ACS tables are available in this feature layer.) Data downloaded from: Census Bureau's API for American Community Survey Date of Census update: December 10, 2020 National Figures: data.census.gov Additional Census data notes and data processing notes are available at the Esri Living Atlas Layer: https://tempegov.maps.arcgis.com/home/item.html?id=527ea2b5ba814c8ca1c34a2945e1b751

Analysis of ‘Income - ACS 2015-2019 - Tempe Tracts’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/67536dc9-838b-44c0-bfaf-55ba748711ce on 11 February 2022.

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

Notice: The U.S. Census Bureau is delaying the release of the 2016-2020 ACS 5-year data until March 2022. For more information, please read the Census Bureau statement regarding this matter.

-----------------------------------------

This layer shows household income ranges for households, families, married couple families, and nonfamily households (as defined by the U.S. Census). Data is from US Census American Community Survey (ACS) 5-year estimates and joined with Tempe census tracts.

This layer is symbolized to show median household income. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online).

Layer includes:

· Total households (of various types including households, families, married couple families, and nonfamily households as defined by the U.S. Census)

· Household income brackets

· Household median income in dollars

· Household mean income in dollars

An 'N' entry in the estimate indicates that data for this geographic area cannot be displayed because the number of sample cases is too small (per the U.S. Census).

Data is from US Census American Community Survey (ACS) 5-year estimates.

Current Vintage: 2015-2019

ACS Table(s): S1901 (Not all lines of this ACS table are available in this feature layer.)

Data downloaded from: Census Bureau's API for American Community Survey

Date of Census update: December 10, 2020

National Figures: data.census.gov

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

The Priority Neighborhoods dataset is a part of the City of Oakland Department of Transportation's (OakDOT's) Geographic Equity Toolbox. The Priority Neighborhoods GIS dataset relies upon demographic data from the American Community Survey (ACS). This dataset assigns each census tract in Oakland a numerical priority value and a quantile from lowest and highest, as determined by the following seven weighted demographic factors (with weights in brackets "[XX%]"): • People of Color [25%] • Low-income Households (<50% of Area Median Income for a 4-person household) [25%] • People with Disability [10%] • Seniors 65 Years and Over [10%] • Single Parent Families [10%] • Severely Rent-Burdened Households [10%] • Low Educational Attainment (less than a bachelor's degree) [10%]

This dataset was last updated in October 2024 with data from the 2022 5-year (i.e., averaged from 2018 through 2022) American Community Survey (ACS). The ACS is managed by the United States Census Bureau; learn more about the ACS at: https://www.census.gov/programs-surveys/acs.

See the online map and read the methodology at: https://www.oaklandca.gov/resources/oakdot-geographic-equity-toolbox. This dataset is maintained by the OakDOT Race and Equity Team; learn more about the team at: https://www.oaklandca.gov/topics/oakdot-race-and-equity-team.

Field Descriptions: • TRACT: Census Tract Number • QUINTILE: Priority Quintile (calculated) • PLAN_AREA: OakDOT Planning Area • POPULATION: Population (average from 2018 through 2022) • PCT_POC: Percent People of Color • PCT_INC: Percent Low Income • PCT_SRB: Percent Severely Rent-Burdened • PCT_PWD: People with a Disability • PCT_SENIOR: Percent Seniors • PCT_SPH: Percent Single Parent Households • PCT_EDU: Percent Low Educational Attainment • RAT_POC: Ratio of People of Color (compared to Citywide average) • RAT_INC: Ratio of Low Income (compared to Citywide average) • RAT_SRB: Ratio of Severely Rent-Burdened (compared to Citywide average) • RAT_PWD: Ratio of People with a Disability (compared to Citywide average) • RAT_SENIOR: Ratio of Seniors (compared to Citywide average) • RAT_SPH: Ratio of Single Parent Households (compared to Citywide average) • RAT_EDU: Ratio of Low Educational Attainment (compared to Citywide average) • RAT_SCORE: Priority Ratio (compared to Citywide average) • ALAND: Land Area in square feet

City of Oakland, Department of Transportation (OakDOT) 250 Frank H. Ogawa Plaza, Suite 4314 | Oakland, CA 94612

Notice: The U.S. Census Bureau is delaying the release of the 2016-2020 ACS 5-year data until March 2022. For more information, please read the Census Bureau statement regarding this matter. -----------------------------------------This layer shows six different types of disability. Data is from US Census American Community Survey (ACS) 5-year estimates and joined with Tempe census tracts. This layer is symbolized to show the percent of population with a disability. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online). Layer includes percent of population with a disability categorized as: · an independent living difficulty · a hearing difficulty · an ambulatory difficulty · a vision difficulty · a cognitive difficulty · a selfcare difficulty Data is from US Census American Community Survey (ACS) 5-year estimates. Vintage: 2015-2019 ACS Table(s): S1810 (Not all lines of this ACS table are available in this feature layer.) Data downloaded from: Census Bureau's API for American Community Survey Date of Census update: December 10, 2020 National Figures: data.census.gov

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

Analysis of ‘Poverty rate - ACS 2015-2019 - Tempe Tracts’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/65c43ceb-ca8c-49b7-a222-df271a777135 on 11 February 2022.

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

Notice: The U.S. Census Bureau is delaying the release of the 2016-2020 ACS 5-year data until March 2022. For more information, please read the Census Bureau statement regarding this matter.

-----------------------------------------

This layer shows poverty status by age group. This layer is Census data from Esri's Living Atlas and is clipped to only show Tempe census tracts.

This layer is symbolized to show the percentage of the population whose income falls below the Federal poverty line. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right (in ArcGIS Online).

Data is from US Census American Community Survey (ACS) 5-year estimates.

Vintage: 2015-2019

ACS Table(s): B17020 (Not all lines of these ACS tables are available in this feature layer.)

Data downloaded from: Census Bureau's API for American Community Survey

Date of Census update: December 10, 2020

National Figures: data.census.gov

Additional Census data notes and data processing notes are available at the Esri Living Atlas Layer:

https://tempegov.maps.arcgis.com/home/item.html?id=0e468b75bca545ee8dc4b039cbb5aff6 (Esri's Living Atlas always shows latest data)

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

Notice: The U.S. Census Bureau is delaying the release of the 2016-2020 ACS 5-year data until March 2022. For more information, please read the Census Bureau statement regarding this matter. -----------------------------------------This layer shows language group of language spoken at home by age. This layer is Census data from Esri's Living Atlas and is clipped to only show Tempe census tracts. This layer is symbolized to show the percentage of the population age 5+ who speak Spanish at home. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Data is from US Census American Community Survey (ACS) 5-year estimates. Vintage: 2015-2019 ACS Table(s): B16007 (Not all lines of these ACS tables are available in this feature layer.) Data downloaded from: Census Bureau's API for American Community Survey Date of Census update: December 10, 2020 National Figures: data.census.gov Additional Census data notes and data processing notes are available at the Esri Living Atlas Layer: https://res1tempegovd-o-tmapsd-o-tarcgisd-o-tcom.vcapture.xyz/home/item.html?id=527ea2b5ba814c8ca1c34a2945e1b751