Population estimates by the U.S. Census Bureau by U.S. Census Block.

This data collection contains summary statistics on population and housing subjects derived from the responses to the 2010 Census questionnaire. Population items include sex, age, average household size, household type, and relationship to householder such as nonrelative or child. Housing items include tenure (whether a housing unit is owner-occupied or renter-occupied), age of householder, and household size for occupied housing units. Selected aggregates and medians also are provided. The summary statistics are presented in 71 tables, which are tabulated for multiple levels of observation (called "summary levels" in the Census Bureau's nomenclature), including, but not limited to, regions, divisions, states, metropolitan/micropolitan areas, counties, county subdivisions, places, ZIP Code Tabulation Areas (ZCTAs), school districts, census tracts, American Indian and Alaska Native areas, tribal subdivisions, and Hawaiian home lands. There are 10 population tables shown down to the county level and 47 population tables and 14 housing tables shown down to the census tract level. Every table cell is represented by a separate variable in the data. Each table is iterated for up to 330 population groups, which are called "characteristic iterations" in the Census Bureau's nomenclature: the total population, 74 race categories, 114 American Indian and Alaska Native categories, 47 Asian categories, 43 Native Hawaiian and Other Pacific Islander categories, and 51 Hispanic/not Hispanic groups. Moreover, the tables for some large summary areas (e.g., regions, divisions, and states) are iterated for portions of geographic areas ("geographic components" in the Census Bureau's nomenclature) such as metropolitan/micropolitan statistical areas and the principal cities of metropolitan statistical areas. The collection has a separate set of files for every state, the District of Columbia, Puerto Rico, and the National File. Each file set has 11 data files per characteristic iteration, a data file with geographic variables called the "geographic header file," and a documentation file called the "packing list" with information about the files in the file set. Altogether, the 53 file sets have 110,416 data files and 53 packing list files. Each file set is compressed in a separate ZIP archive (Datasets 1-56, 72, and 99). Another ZIP archive (Dataset 100) contains a Microsoft Access database shell and additional documentation files besides the codebook. The National File (Dataset 99) constitutes the National Update for Summary File 2. The National Update added summary levels for the United States as a whole, regions, divisions, and geographic areas that cross state lines such as Core Based Statistical Areas.

The 2010 Census Production Settings Redistricting Data (P.L. 94-171) Demonstration Noisy Measurement Files are an intermediate output of the 2020 Census Disclosure Avoidance System (DAS) TopDown Algorithm (TDA) (as described in Abowd, J. et al [2022], and implemented in https://github.com/uscensusbureau/DAS_2020_Redistricting_Production_Code). The NMF was produced using the official "production settings," the final set of algorithmic parameters and privacy-loss budget allocations that were used to produce the 2020 Census Redistricting Data (P.L. 94-171) Summary File and the 2020 Census Demographic and Housing Characteristics File. The NMF consists of the full set of privacy-protected statistical queries (counts of individuals or housing units with particular combinations of characteristics) of confidential 2010 Census data relating to the redistricting data portion of the 2010 Demonstration Data Products Suite - Redistricting and Demographic and Housing Characteristics File - Production Settings (2023-04-03). These statistical queries, called "noisy measurements" were produced under the zero-Concentrated Differential Privacy framework (Bun, M. and Steinke, T [2016]; see also Dwork C. and Roth, A. [2014]) implemented via the discrete Gaussian mechanism (Cannone C., et al., [2023]), which added positive or negative integer-valued noise to each of the resulting counts. The noisy measurements are an intermediate stage of the TDA prior to the post-processing the TDA then performs to ensure internal and hierarchical consistency within the resulting tables. The Census Bureau has released these 2010 Census demonstration data to enable data users to evaluate the expected impact of disclosure avoidance variability on 2020 Census data. The 2010 Census Production Settings Redistricting Data (P.L. 94-171) Demonstration Noisy Measurement Files (2023-04-03) have been cleared for public dissemination by the Census Bureau Disclosure Review Board (CBDRB-FY22-DSEP-004). The data include zero-Concentrated Differentially Private (zCDP) (Bun, M. and Steinke, T [2016]) noisy measurements, implemented via the discrete Gaussian mechanism. These are estimated counts of individuals and housing units included in the 2010 Census Edited File (CEF), which includes confidential data initially collected in the 2010 Census of Population and Housing. The noisy measurements included in this file were subsequently post-processed by the TopDown Algorithm (TDA) to produce the 2010 Census Production Settings Privacy-Protected Microdata File - Redistricting (P.L. 94-171) and Demographic and Housing Characteristics File (2023-04-03) (https://www2.census.gov/programs-surveys/decennial/2020/program-management/data-product- planning/2010-demonstration-data-products/04 Demonstration_Data_Products_Suite/2023-04-03/). As these 2010 Census demonstration data are intended to support study of the design and expected impacts of the 2020 Disclosure Avoidance System, the 2010 CEF records were pre-processed before application of the zCDP framework. This pre-processing converted the 2010 CEF records into the input-file format, response codes, and tabulation categories used for the 2020 Census, which differ in substantive ways from the format, response codes, and tabulation categories originally used for the 2010 Census. The NMF provides estimates of counts of persons in the CEF by various characteristics and combinations of characteristics, including their reported race and ethnicity, whether they were of voting age, whether they resided in a housing unit or one of 7 group quarters types, and their census block of residence, after the addition of discrete Gaussian noise (with the scale parameter determined by the privacy-loss budget allocation for that particular query under zCDP). Noisy measurements of the counts of occupied and vacant housing units by census block are also included. Lastly, data on constraints--information into which no noise was infused by the Disclosure Avoidance System (DAS) and used by the TDA to post-process the noisy measurements into the 2010 Census Production Settings Privacy-Protected Microdata File - Redistricting (P.L. 94-171) and Demographic and Housing Characteristics File (2023-04-03) --are provided. These data are available for download (i.e. not restricted access). Due to their size, they must be downloaded through the link on this

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.

After each decennial census, the Census Bureau delineates urban areas that represent densely developed territory, encompassing residential, commercial, and other nonresidential urban land uses. In general, this territory consists of areas of high population density and urban land use resulting in a representation of the "urban footprint." There are two types of urban areas: urbanized areas (UAs) that contain 50,000 or more people and urban clusters (UCs) that contain at least 2,500 people, but fewer than 50,000 people (except in the U.S. Virgin Islands and Guam which each contain urban clusters with populations greater than 50,000). Each urban area is identified by a 5-character numeric census code that may contain leading zeroes.

Source: U.S. Census Bureau, PL 94-171 Redistricting data, 2000 and 2010. Note: Census numbers for the cities of Burien and Kent do not include annexations that took place after March 31, 2010. These annexations would increase Burien to 48,072, Kent to 118,565, and decrease uninc King County to 284,089.

The 2010 Census Blocks with Demographic Profile dataset was produced by joining the U.S.Census Bureau's 2010 TIGER/Line File-derived Census Blocks for Fulton County with selected 2010 Summary File 1 data fields. The result is a census block boundary layer attributed with some the more commonly used demographics such as total population, population by race, population by age group, median age, and housing and household characteristics. Because the dataset was derived from the TIGER/Line File Census Blocks, the U.S.Census Bureau's metadata for that dataset is provided below.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. 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 2010 Census blocks nest within every other 2010 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.

The 2010 Census Production Settings Demographic and Housing Characteristics (DHC) Demonstration Noisy Measurement File (2023-06-30) is an intermediate output of the 2020 Census Disclosure Avoidance System (DAS) TopDown Algorithm (TDA) (as described in Abowd, J. et al [2022] https://doi.org/10.1162/99608f92.529e3cb9 , and implemented in https://github.com/uscensusbureau/DAS_2020_Redistricting_Production_Code). The NMF was produced using the official “production settings,” the final set of algorithmic parameters and privacy-loss budget allocations, that were used to produce the 2020 Census Redistricting Data (P.L. 94-171) Summary File and the 2020 Census Demographic and Housing Characteristics File. The NMF consists of the full set of privacy-protected statistical queries (counts of individuals or housing units with particular combinations of characteristics) of confidential 2010 Census data relating to the 2010 Demonstration Data Products Suite – Redistricting (P.L. 94-171) and Demographic and Housing Characteristics File – Production Settings (2023-04-03). These statistical queries, called “noisy measurements” were produced under the zero-Concentrated Differential Privacy framework (Bun, M. and Steinke, T [2016] https://arxiv.org/abs/1605.02065; see also Dwork C. and Roth, A. [2014] https://www.cis.upenn.edu/~aaroth/Papers/privacybook.pdf) implemented via the discrete Gaussian mechanism (Cannone C., et al., [2023] https://arxiv.org/abs/2004.00010), which added positive or negative integer-valued noise to each of the resulting counts. The noisy measurements are an intermediate stage of the TDA prior to the post-processing the TDA then performs to ensure internal and hierarchical consistency within the resulting tables. The Census Bureau has released these 2010 Census demonstration data to enable data users to evaluate the expected impact of disclosure avoidance variability on 2020 Census data. The 2010 Census Production Settings Demographic and Housing Characteristics (DHC) Demonstration Noisy Measurement File (2023-04-03) has been cleared for public dissemination by the Census Bureau Disclosure Review Board (CBDRB-FY22-DSEP-004).

The 2010 Census Production Settings Demographic and Housing Characteristics Demonstration Noisy Measurement File includes zero-Concentrated Differentially Private (zCDP) (Bun, M. and Steinke, T [2016]) noisy measurements, implemented via the discrete Gaussian mechanism. These are estimated counts of individuals and housing units included in the 2010 Census Edited File (CEF), which includes confidential data initially collected in the 2010 Census of Population and Housing. The noisy measurements included in this file were subsequently post-processed by the TopDown Algorithm (TDA) to produce the 2010 Census Production Settings Privacy-Protected Microdata File - Redistricting (P.L. 94-171) and Demographic and Housing Characteristics File (2023-04-03) (https://www2.census.gov/programs-surveys/decennial/2020/program-management/data-product-planning/2010-demonstration-data-products/04-Demonstration_Data_Products_Suite/2023-04-03/). As these 2010 Census demonstration data are intended to support study of the design and expected impacts of the 2020 Disclosure Avoidance System, the 2010 CEF records were pre-processed before application of the zCDP framework. This pre-processing converted the 2010 CEF records into the input-file format, response codes, and tabulation categories used for the 2020 Census, which differ in substantive ways from the format, response codes, and tabulation categories originally used for the 2010 Census.

The NMF provides estimates of counts of persons in the CEF by various characteristics and combinations of characteristics including their reported race and ethnicity, whether they were of voting age, whether they resided in a housing unit or one of 7 group quarters types, and their census block of residence after the addition of discrete Gaussian noise (with the scale parameter determined by the privacy-loss budget allocation for that particular query under zCDP). Noisy measurements of the counts of occupied and vacant housing units by census block are also included. Lastly, data on constraints—information into which no noise was infused by the Disclosure Avoidance System (DAS) and used by the TDA to post-process the noisy measurements into the 2010 Census Production Settings Privacy-Protected Microdata File - Redistricting (P.L. 94-171) and Demographic and Housing Characteristics File (2023-04-03) —are provided.

Household Demographics in the 2010 CensusThis feature layer contains demographics about households as reported by the U.S. Census Bureau (USCB) in the 2010 U.S. Census. These attributes cover topics such as household types, household size, nonfamily households, householder age, and households with children. A small subset of attributes from the 2000 Census are also included as reference.Per the Census, "Also known as the Population and Housing Census, the Decennial U.S. Census is designed to count every resident in the United States. It is mandated by Article I, Section 2 of the Constitution and takes place every 10 years. The data collected by the decennial census determine the number of seats each state has in the U.S. House of Representatives and is also used to distribute hundreds of billions of dollars in federal funds to local communities."Four layers are available: state, county, census tract, and census block group. Each layer contains the same set of demographic attributes. Each geography level has a viewing range optimal for the geography size, and the map detail increases when zooming to local areas. Only one geography is in view at any time.Household Demographics 2010 CensusData currency: 2010Data download: Explore Census DataFor more information: Households and Families: 2010For feedback please contact: ArcGIScomNationalMaps@esri.comData Processing notes:State and county boundaries are simplified representations offered from the Census Bureau's 2010 MAF/TIGER databaseTract and block group boundaries are 2010 TIGER boundaries with select water area boundaries erased (coastlines and major water bodies)Field names and aliases are processed by Esri as created for the ArcGIS Platform.For a list of fields and alias names, access the following excel document.U.S. Census BureauPer USCB, "the Census Bureau is the federal government’s largest statistical agency. We are dedicated to providing current facts and figures about America’s people, places, and economy. Federal law protects the confidentiality of all the information the Census Bureau collects."

Population by U.S. Postal ZIP Code from the 2010 Decennial Census

Annual Resident Population Estimates by Age Group, Sex, Race, and Hispanic Origin; for the United States, States, Counties; and for Puerto Rico and its Municipios: April 1, 2010 to July 1, 2019 // Source: U.S. Census Bureau, Population Division // The contents of this file are released on a rolling basis from December through June. // Note: 'In combination' means in combination with one or more other races. The sum of the five race-in-combination groups adds to more than the total population because individuals may report more than one race. Hispanic origin is considered an ethnicity, not a race. Hispanics may be of any race. Responses of 'Some Other Race' from the 2010 Census are modified. This results in differences between the population for specific race categories shown for the 2010 Census population in this file versus those in the original 2010 Census data. The estimates are based on the 2010 Census and reflect changes to the April 1, 2010 population due to the Count Question Resolution program and geographic program revisions. // Current data on births, deaths, and migration are used to calculate population change since the 2010 Census. An annual time series of estimates is produced, beginning with the census and extending to the vintage year. The vintage year (e.g., Vintage 2019) refers to the final year of the time series. The reference date for all estimates is July 1, unless otherwise specified. With each new issue of estimates, the entire estimates series is revised. Additional information, including historical and intercensal estimates, evaluation estimates, demographic analysis, research papers, and methodology is available on website: https://www.census.gov/programs-surveys/popest.html.

The 2010 Census Blocks with Demographic Profile dataset was produced by joining the U.S.Census Bureau's 2010 TIGER/Line File-derived Census Blocks for Fulton County with selected 2010 Summary File 1 data fields. The result is a census block boundary layer attributed with some the more commonly used demographics such as total population, population by race, population by age group, median age, and housing and household characteristics. Because the dataset was derived from the TIGER/Line File Census Blocks, the U.S.Census Bureau's metadata for that dataset is provided below.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. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2010 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, 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.

This dataset includes census tracts as defined by the U.S. Census Bureau and made available through their TIGER/Line files. These delineations were prepared for tabulation of the 2010 decennial census data, but are also used in other tabulations such as those of American Community Survey data. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity. Census 2010 tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. For more information about census geographies, see http://www.census.gov/geo/reference/ . This file is for reference use only. NCTCOG and its members are not responsible for errors or inaccuracies in the file.

Monthly Population Estimates by Universe, Age, Sex, Race, and Hispanic Origin for the United States: April 1, 2010 to December 1, 2020 // Source: U.S. Census Bureau, Population Division // Note: 'In combination' means in combination with one or more other races. The sum of the five race-in-combination groups adds to more than the total population because individuals may report more than one race. Hispanic origin is considered an ethnicity, not a race. Hispanics may be of any race. Responses of 'Some Other Race' from the 2010 Census are modified. This results in differences between the population for specific race categories shown for the 2010 Census population in this file versus those in the original 2010 Census data. // The estimates are based on the 2010 Census and reflect changes to the April 1, 2010 population due to the Count Question Resolution program and geographic program revisions. // Persons on active duty in the Armed Forces were not enumerated in the 2010 Census. Therefore, variables for the 2010 Census civilian, civilian noninstitutionalized, and resident population plus Armed Forces overseas populations cannot be derived and are not available on this file. // Current data on births, deaths, and migration are used to calculate population change since the 2010 Census. A time series of estimates is produced, beginning with the census. The reference date for all estimates is the first of the month. With each new issue of estimates, the entire estimates series is revised. Additional information, including historical and intercensal estimates, evaluation estimates, demographic analysis, research papers, and methodology is available on website: https://res1wwwd-o-tcensusd-o-tgov.vcapture.xyz/programs-surveys/popest.html.

2010 Census Tract data for use with GIS mapping software, databases, and web applications are from Caliper Corporation. Available for Maptitude or in any format such as shapefile, KML, KMZ, GeoJSON.

Monthly Population Estimates by Universe, Age, Sex, Race, and Hispanic Origin for the United States: April 1, 2010 to December 1, 2018 // Source: U.S. Census Bureau, Population Division // The contents of this file are released on a rolling basis from December through June. // Note: 'In combination' means in combination with one or more other races. The sum of the five race-in-combination groups adds to more than the total population because individuals may report more than one race. Hispanic origin is considered an ethnicity, not a race. Hispanics may be of any race. Responses of 'Some Other Race' from the 2010 Census are modified. This results in differences between the population for specific race categories shown for the 2010 Census population in this file versus those in the original 2010 Census data. For more information, see https://www2.census.gov/programs-surveys/popest/technical-documentation/methodology/modified-race-summary-file-method/mrsf2010.pdf. // The estimates are based on the 2010 Census and reflect changes to the April 1, 2010 population due to the Count Question Resolution program and geographic program revisions. // Persons on active duty in the Armed Forces were not enumerated in the 2010 Census. Therefore, variables for the 2010 Census civilian, civilian noninstitutionalized, and resident population plus Armed Forces overseas populations cannot be derived and are not available on these files. // For detailed information about the methods used to create the population estimates, see https://www.census.gov/programs-surveys/popest/technical-documentation/methodology.html. // Each year, the Census Bureau's Population Estimates Program (PEP) utilizes current data on births, deaths, and migration to calculate population change since the most recent decennial census, and produces a time series of estimates of population. The annual time series of estimates begins with the most recent decennial census data and extends to the vintage year. The vintage year (e.g., V2017) refers to the final year of the time series. The reference date for all estimates is July 1, unless otherwise specified. With each new issue of estimates, the Census Bureau revises estimates for years back to the last census. As each vintage of estimates includes all years since the most recent decennial census, the latest vintage of data available supersedes all previously produced estimates for those dates. The Population Estimates Program provides additional information including historical and intercensal estimates, evaluation estimates, demographic analysis, and research papers on its website: https://www.census.gov/programs-surveys/popest.html.

What is unique about LA County’s data?It is clipped to the ocean boundary. Raw Census data includes a 3 mile buffer into the ocean, which impacts cartography.IMPORTANT! It has been updated to the 2012 Census Geography Update, which merged Tracts 1370.00 and 9304.01 into the combined tract 1370.00. So the CT10 field actually reflects the 2012 Census update, which is used for all population products 2012 and later.How was this data created?This data was downloaded from Census Bureau website: http://www.census.gov/cgi-bin/geo/shapefiles2010/file-download and clipped to the County Boundary using ESRI’s ArcGIS Desktop. Two new fields were added in census tract data – area in square feet and shape length in feet. This dataset has unique identifier field “GEOID10” for each record and the census tract number fields “CT10” and “LABEL” (6-digit number and 6-digit number with decimal point, respectively).

Monthly Population Estimates by Universe, Age, Sex, 5 Races, and Hispanic Origin for the United States: April 1, 2010 to July 1, 2013 // File: 7/1/2013 National Population Estimates // Source: U.S. Census Bureau, Population Division // Release Date: June 2014 // Note: 'In combination' means in combination with one or more other races. The sum of the five race groups adds to more than the total population because individuals may report more than one race. The estimates are based on the 2010 Census and reflect changes to the April 1, 2010 population due to the Count Question Resolution program and geographic program revisions. Hispanic origin is considered an ethnicity, not a race. Hispanics may be of any race. Responses of 'Some Other Race' from the 2010 Census are modified. This results in differences between the population for specific race categories shown for the 2010 Census population in this file versus those in the original 2010 Census data. For more information, see http://www.census.gov/popest/data/historical/files/MRSF-01-US1.pdf. // Persons on active duty in the Armed Forces were not enumerated in the 2010 Census. Therefore, variables for the 2010 Census civilian, civilian noninstitutionalized, and resident population plus Armed Forces overseas populations cannot be derived and are not available on these files. // For detailed information about the methods used to create the population estimates, see http://www.census.gov/popest/methodology/index.html. // Each year, the Census Bureau's Population Estimates Program (PEP) utilizes current data on births, deaths, and migration to calculate population change since the most recent decennial census, and produces a time series of estimates of population. The annual time series of estimates begins with the most recent decennial census data and extends to the vintage year. The vintage year (e.g., V2013) refers to the final year of the time series. The reference date for all estimates is July 1, unless otherwise specified. With each new issue of estimates, the Census Bureau revises estimates for years back to the last census. As each vintage of estimates includes all years since the most recent decennial census, the latest vintage of data available supersedes all previously produced estimates for those dates. The Population Estimates Program provides additional information including historical and intercensal estimates, evaluation estimates, demographic analysis, and research papers on its website: http://www.census.gov/popest/index.html.

The 2010 Census Block Groups with Demographic Profile dataset was produced by joining the U.S.Census Bureau's 2010 TIGER/Line File-derived Census Block Groups for Fulton County with selected 2010 Summary File 1 data fields. The result is a census block group boundary layer attributed with some the more commonly used demographics such as total population, population by race, population by age group, median age, and housing and household characteristics. Because the dataset was derived from the TIGER/Line File Census Block Groups, the U.S.Census Bureau's metadata for that dataset is provided below.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. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may 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. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.

This data comes from the 2010 Census Profile of General Population and Housing Characteristics. Zip codes are limited to those that fall at least partially within LA city boundaries. The dataset will be updated after the next census in 2020. To view all possible columns and access the data directly, visit http://factfinder.census.gov/faces/affhelp/jsf/pages/metadata.xhtml?lang=en&type=table&id=table.en.DEC_10_SF1_SF1DP1#main_content.

Housing Demographics in the 2010 CensusThis feature layer contains demographics about housing as reported by the U.S. Census Bureau (USCB) in the 2010 U.S. Census. These attributes cover topics such as owner status of housing units (vacant, owner, renter), count of residents per housing unit, and housing unit by householder age. A small subset of attributes from the 2000 Census are also included as reference.Per the Census, "Also known as the Population and Housing Census, the Decennial U.S. Census is designed to count every resident in the United States. It is mandated by Article I, Section 2 of the Constitution and takes place every 10 years. The data collected by the decennial census determine the number of seats each state has in the U.S. House of Representatives and is also used to distribute hundreds of billions of dollars in federal funds to local communities."Four layers are available: state, county, census tract, and census block group. Each layer contains the same set of demographic attributes. Each geography level has a viewing range optimal for the geography size, and the map has increasing detail as you zoom in to smaller areas. Only one geography is in view at any time.Housing Demographics 2010 CensusData currency: 2010Data modification: NoneData source: Explore Census DataFor more information: Households and Families: 2010For feedback, please contact: ArcGIScomNationalMaps@esri.comData Processing notes:State and county boundaries are simplified representations offered from the Census Bureau's 2010 MAF/TIGER databaseTract and block group boundaries are 2010 TIGER boundaries with select water area boundaries erased (coastlines and major water bodies)Field names and aliases are processed by Esri as created for the ArcGIS Platform.For a list of fields and alias names, access the following excel document.U.S. Census BureauPer USCB, "the Census Bureau is the federal government’s largest statistical agency. We are dedicated to providing current facts and figures about America’s people, places, and economy. Federal law protects the confidentiality of all the information the Census Bureau collects."