This map shows population density of the United States. Areas in darker magenta have much higher population per square mile than areas in orange or yellow. Data is from the U.S. Census Bureau’s 2020 Census Demographic and Housing Characteristics. The map's layers contain total population counts by sex, age, and race groups for Nation, State, County, Census Tract, and Block Group in the United States and Puerto Rico. From the Census:"Population density allows for broad comparison of settlement intensity across geographic areas. In the U.S., population density is typically expressed as the number of people per square mile of land area. The U.S. value is calculated by dividing the total U.S. population (316 million in 2013) by the total U.S. land area (3.5 million square miles).When comparing population density values for different geographic areas, then, it is helpful to keep in mind that the values are most useful for small areas, such as neighborhoods. For larger areas (especially at the state or country scale), overall population density values are less likely to provide a meaningful measure of the density levels at which people actually live, but can be useful for comparing settlement intensity across geographies of similar scale." SourceAbout the dataYou can use this map as is and you can also modify it to use other attributes included in its layers. This map's layers contain total population counts by sex, age, and race groups data from the 2020 Census Demographic and Housing Characteristics. This is shown by Nation, State, County, Census Tract, Block Group boundaries. Each geography layer contains a common set of Census counts based on available attributes from the U.S. Census Bureau. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis.Vintage of boundaries and attributes: 2020 Demographic and Housing Characteristics Table(s): P1, H1, H3, P2, P3, P5, P12, P13, P17, PCT12 (Not all lines of these DHC tables are available in this feature layer.)Data downloaded from: U.S. Census Bureau’s data.census.gov siteDate the Data was Downloaded: May 25, 2023Geography Levels included: Nation, State, County, Census Tract, Block GroupNational Figures: included in Nation layer The United States Census Bureau Demographic and Housing Characteristics: 2020 Census Results 2020 Census Data Quality Geography & 2020 Census Technical Documentation Data Table Guide: includes the final list of tables, lowest level of geography by table and table shells for the Demographic Profile and Demographic and Housing Characteristics.News & Updates This map is ready to be used in ArcGIS Pro, ArcGIS Online and its configurable apps, Story Maps, dashboards, Notebooks, Python, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the U.S. Census Bureau when using this data. Data Processing Notes: These 2020 Census boundaries come from the US Census TIGER geodatabases. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For Census tracts and block groups, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract and block group boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are unchanged and available as attributes within the data table (units are square meters).  The layer contains all US states, Washington D.C., and Puerto Rico. Census tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99). Block groups that fall within the same criteria (Block Group denoted as 0 with no area land) have also been removed.Percentages and derived counts, are calculated values (that can be identified by the "_calc_" stub in the field name). Field alias names were created based on the Table Shells file available from the Data Table Guide for the Demographic Profile and Demographic and Housing Characteristics. Not all lines of all tables listed above are included in this layer. Duplicative counts were dropped. For example, P0030001 was dropped, as it is duplicative of P0010001.To protect the privacy and confidentiality of respondents, their data has been protected using differential privacy techniques by the U.S. Census Bureau.

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) Database (MTDB). The MTDB 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. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2010 Census.

analyze the american community survey (acs) with r and monetdb experimental. think of the american community survey (acs) as the united states' census for off-years - the ones that don't end in zero. every year, one percent of all americans respond, making it the largest complex sample administered by the u.s. government (the decennial census has a much broader reach, but since it attempts to contact 100% of the population, it's not a sur vey). the acs asks how people live and although the questionnaire only includes about three hundred questions on demography, income, insurance, it's often accurate at sub-state geographies and - depending how many years pooled - down to small counties. households are the sampling unit, and once a household gets selected for inclusion, all of its residents respond to the survey. this allows household-level data (like home ownership) to be collected more efficiently and lets researchers examine family structure. the census bureau runs and finances this behemoth, of course. the dow nloadable american community survey ships as two distinct household-level and person-level comma-separated value (.csv) files. merging the two just rectangulates the data, since each person in the person-file has exactly one matching record in the household-file. for analyses of small, smaller, and microscopic geographic areas, choose one-, three-, or fiv e-year pooled files. use as few pooled years as you can, unless you like sentences that start with, "over the period of 2006 - 2010, the average american ... [insert yer findings here]." rather than processing the acs public use microdata sample line-by-line, the r language brazenly reads everything into memory by default. to prevent overloading your computer, dr. thomas lumley wrote the sqlsurvey package principally to deal with t his ram-gobbling monster. if you're already familiar with syntax used for the survey package, be patient and read the sqlsurvey examples carefully when something doesn't behave as you expect it to - some sqlsurvey commands require a different structure (i.e. svyby gets called through svymean) and others might not exist anytime soon (like svyolr). gimme some good news: sqlsurvey uses ultra-fast monetdb (click here for speed tests), so follow the monetdb installation instructions before running this acs code. monetdb imports, writes, recodes data slowly, but reads it hyper-fast . a magnificent trade-off: data exploration typically requires you to think, send an analysis command, think some more, send another query, repeat. importation scripts (especially the ones i've already written for you) can be left running overnight sans hand-holding. the acs weights generalize to the whole united states population including individuals living in group quarters, but non-residential respondents get an abridged questionnaire, so most (not all) analysts exclude records with a relp variable of 16 or 17 right off the bat. this new github repository contains four scripts: 2005-2011 - download all microdata.R create the batch (.bat) file needed to initiate the monet database in the future download, unzip, and import each file for every year and size specified by the user create and save household- and merged/person-level replicate weight complex sample designs create a well-documented block of code to re-initiate the monet db server in the future fair warning: this full script takes a loooong time. run it friday afternoon, commune with nature for the weekend, and if you've got a fast processor and speedy internet connection, monday morning it should be ready for action. otherwise, either download only the years and sizes you need or - if you gotta have 'em all - run it, minimize it, and then don't disturb it for a week. 2011 single-year - analysis e xamples.R run the well-documented block of code to re-initiate the monetdb server load the r data file (.rda) containing the replicate weight designs for the single-year 2011 file perform the standard repertoire of analysis examples, only this time using sqlsurvey functions 2011 single-year - variable reco de example.R run the well-documented block of code to re-initiate the monetdb server copy the single-year 2011 table to maintain the pristine original add a new age category variable by hand add a new age category variable systematically re-create then save the sqlsurvey replicate weight complex sample design on this new table close everything, then load everything back up in a fresh instance of r replicate a few of the census statistics. no muss, no fuss replicate census estimates - 2011.R run the well-documented block of code to re-initiate the monetdb server load the r data file (.rda) containing the replicate weight designs for the single-year 2011 file match every nation wide statistic on the census bureau's estimates page, using sqlsurvey functions click here to view these four scripts for more detail about the american community survey (acs), visit: < ul> the us census...

The TIGER/Line Files are shapefiles and related database files (.dbf) that 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) 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. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data from Census 2000. The Census Bureau creates ZCTAs for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands for the 2010 Census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. For the 2010 Census, ZCTAs should more accurately represent the actual ZIP Codes at the time of their delineation than they did for Census 2000. This is because that before the tabulation blocks, which the ZCTAs are built from, were delineated for the 2010 Census, the Census Bureau undertook the process of inserting lines that could be used as 2010 Census tabulation block boundaries, and these lines split polygons where the result would be that a significant number of addresses would occur on either one or both sides of the line associated with a single ZIP Code. Each 2010 Census tabulation block that contains addresses is assigned to a single ZCTA, usually to the ZCTA that reflects the most frequently occurring ZIP Code for the addresses within that tabulation block. As a result, ZIP Codes associated with address ranges found in the Address Ranges relationship file may not always match the ZCTA. Blocks that do not contain addresses but are completely surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. A ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks were it exists. The Census Bureau uses the addresses stored within MTDB to delineate ZCTAs, and at the time of the 2010 Census the MTDB primarily included addresses for residential or at least potentially residential structures, so ZCTAs representing only non-residential structures are infrequent. Also, in each tabulation block, if a choice existed between using a potential city-style mail delivery ZIP Code for an address or a post office box ZIP Code, the city-style mail delivery ZIP Code was preferred for the 2010 Census ZCTA delineation. The Census Bureau identifies 5-digit ZCTAs using a five-character numeric code that represents the most frequently occurring USPS ZIP Code within that ZCTA, and this code may contain leading zeros.

This map shows what country naturalized US citizens were born in using the Charts & Size and Predominance mapping styles. The area with the highest amount of foreign born naturalized US citizens is shown by color. Areas are: Africa, Asia, Europe, Latin America, Northern America, and Oceania.Data are available in 5-year estimates at the state, county, and tract level for the entire US.The data in this map contains the most recent American Community Survey (ACS) data from the U.S. Census Bureau. The Living Atlas layer in this map updates annually when the Census releases their new figures. To learn more, visit this FAQ, or visit the ACS website. Web Map originally owned by Summers Cleary

U.S. Census Bureau QuickFacts statistics for Virginia. QuickFacts data are derived from: Population Estimates, American Community Survey, Census of Population and Housing, Current Population Survey, Small Area Health Insurance Estimates, Small Area Income and Poverty Estimates, State and County Housing Unit Estimates, County Business Patterns, Nonemployer Statistics, Economic Census, Survey of Business Owners, Building Permits.

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) Database (MTDB). The MTDB 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. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

Age, Sex, Race, Ethnicity, Total Housing Units, and Voting Age Population. This service is updated annually with American Community Survey (ACS) 5-year data. Contact: District of Columbia, Office of Planning. Email: planning@dc.gov. Geography: Census Tracts. Current Vintage: 2019-2023. ACS Table(s): DP05. Data downloaded from: Census Bureau's API for American Community Survey. Date of API call: January 2, 2025. National Figures: data.census.gov. Please cite the Census and ACS when using this data. Data Note from the Census: Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables. Data Processing Notes: This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2020 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page. Data processed using R statistical package and ArcGIS Desktop. Margin of Error was not included in this layer but is available from the Census Bureau. Contact the Office of Planning for more information about obtaining Margin of Error values.

This map shows what the most common year naturalized for foreign-born population is in an area using the predominance style. Areas with weaker predominance have higher transparency. The popup is configured to show:Total foreign-born population out of total populationTotal naturalized citizensPredominant year naturalizedBreakdown by year naturalizedData is available in 5-year estimates at the state, county, and tract level for the entire US.The data in this map contains the most recent American Community Survey (ACS) data from the U.S. Census Bureau. The Living Atlas layer in this map updates annually when the Census releases their new figures. To learn more, visit this FAQ, or visit the ACS website.

This map shows what country naturalized US citizens were born in using the predominance mapping style. The area with the highest amount of foreign born naturalized US citizens is shown by color. Areas are: Africa, Asia, Europe, Latin America, Northern America, and Oceania.Data is available in 5-year estimates at the state, county, and tract level for the entire US.The data in this map contains the most recent American Community Survey (ACS) data from the U.S. Census Bureau. The Living Atlas layer in this map updates annually when the Census releases their new figures. To learn more, visit this FAQ, or visit the ACS website.

(Link to Metadata) 2020 Census ZCTAs (ZIP Code Tabulation Areas); data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. 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) Database (MTDB). The MTDB 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. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2020 Census.

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) Database (MTDB). The MTDB 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. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2010 Census.

The 2014 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files.

ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery.

The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros.

Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists.

The generalized ZCTA boundaries in this file are based on those delineated following the 2010 Census.

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

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) Database (MTDB). The MTDB 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. ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery. The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros. Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists. The ZCTA boundaries in this release are those delineated following the 2020 Census.Download Link:https://ky.box.com/v/kymartian-zip-code-boundaries

ZIP Code Tabulation Areas (ZCTAs) are approximate area representations of U.S. Postal Service (USPS) ZIP Code service areas that the Census Bureau creates to present statistical data for each decennial census. The Census Bureau delineates ZCTA boundaries for the United States, Puerto Rico, American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands once each decade following the decennial census. Data users should not use ZCTAs to identify the official USPS ZIP Code for mail delivery. The USPS makes periodic changes to ZIP Codes to support more efficient mail delivery.

The Census Bureau uses tabulation blocks as the basis for defining each ZCTA. Tabulation blocks are assigned to a ZCTA based on the most frequently occurring ZIP Code for the addresses contained within that block. The most frequently occurring ZIP Code also becomes the five-digit numeric code of the ZCTA. These codes may contain leading zeros.

Blocks that do not contain addresses but are surrounded by a single ZCTA (enclaves) are assigned to the surrounding ZCTA. Because the Census Bureau only uses the most frequently occurring ZIP Code to assign blocks, a ZCTA may not exist for every USPS ZIP Code. Some ZIP Codes may not have a matching ZCTA because too few addresses were associated with the specific ZIP Code or the ZIP Code was not the most frequently occurring ZIP Code within any of the blocks where it exists.

The generalized ZCTA boundaries in this file are based on those delineated following the 2010 Census.

This statistic shows the types of frozen potato products used most often in the United States in 2020. The data has been calculated by Statista based on the U.S. Census data and Simmons National Consumer Survey (NHCS). According to this statistic, ****** million Americans used french fried frozen potato products in 2020.

This statistic shows the types of pudding eaten most often in the United States in 2020. The data has been calculated by Statista based on the U.S. Census data and Simmons National Consumer Survey (NHCS). According to this statistic, ****** million Americans consumed regular pudding in 2020.

This statistic shows the types of condoms used most often in the United States in 2020. The data has been calculated by Statista based on the U.S. Census data and Simmons National Consumer Survey (NHCS). According to this statistic, **** million Americans used latex condoms in 2020.

This statistic shows the brands of frosting used most often in the United States in 2020. The data has been calculated by Statista based on the U.S. Census data and Simmons National Consumer Survey (NHCS). According to this statistic, ***** million Americans used Betty Crocker Rich & Creamy in 2020.