The 119th Congressional Districts dataset reflects boundaries from January 3rd, 2025 from the United States Census Bureau (USCB), and the attributes are updated every Sunday from the United States House of Representatives and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). 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. Information for each member of Congress is appended to the Census Congressional District shapefile using information from the Office of the Clerk, U.S. House of Representatives' website https://clerk.house.gov/xml/lists/MemberData.xml and its corresponding XML file. Congressional districts are the 435 areas from which people are elected to the U.S. House of Representatives. This dataset also includes 9 geographies for non-voting at large delegate districts, resident commissioner districts, and congressional districts that are not defined. After the apportionment of congressional seats among the states based on census population counts, each state is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The 119th Congress is seated from January 3, 2025 through January 3, 2027. In Connecticut, Illinois, and New Hampshire, the Redistricting Data Program (RDP) participant did not define the CDs to cover all of the state or state equivalent area. In these areas with no CDs defined, the code "ZZ" has been assigned, which is treated as a single CD for purposes of data presentation. The TIGER/Line shapefiles for the District of Columbia, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands) each contain a single record for the non-voting delegate district in these areas. The boundaries of all other congressional districts reflect information provided to the Census Bureau by the states by May 31, 2024. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529006

This map shows Congressional District boundaries for the United States. The map is set to middle Georgia.

Congressional districts are the 435 areas from which members are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the states, which is based on decennial census population counts, each state with multiple seats is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The boundaries and numbers shown for the congressional districts are those specified in the state laws or court orders establishing the districts within each state.

Congressional districts for the 108th through 112th sessions were established by the states based on the result of the 2000 Census. Congressional districts for the 113th through 115th sessions were established by the states based on the result of the 2010 Census. Boundaries are effective until January of odd number years (for example, January 2015, January 2017, etc.), unless a state initiative or court ordered redistricting requires a change. All states established new congressional districts in 2011-2012, with the exception of the seven single member states (Alaska, Delaware, Montana, North Dakota, South Dakota, Vermont, and Wyoming).

For the states that have more than one representative, the Census Bureau requested a copy of the state laws or applicable court order(s) for each state from each secretary of state and each 2010 Redistricting Data Program state liaison requesting a copy of the state laws and/or applicable court order(s) for each state. Additionally, the states were asked to furnish their newly established congressional district boundaries and numbers by means of geographic equivalency files. States submitted equivalency files since most redistricting was based on whole census blocks. Kentucky was the only state where congressional district boundaries split some of the 2010 Census tabulation blocks. For further information on these blocks, please see the user-note at the bottom of the tables for this state.

The Census Bureau entered this information into its geographic database and produced tabulation block equivalency files that depicted the newly defined congressional district boundaries. Each state liaison was furnished with their file and requested to review, submit corrections, and certify the accuracy of the boundaries.

These data depict the 117th Congressional Districts and their representatives for the United States. Congressional districts are the 435 areas from which members are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the states, which is based on decennial census population counts, each state with multiple seats is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The boundaries and numbers shown for the congressional districts are those specified in the state laws or court orders establishing the districts within each state.

Us House Congressional Representatives serving Macon-Bibb County.Congressional districts are the 435 areas from which members are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the states, which is based on decennial census population counts, each state with multiple seats is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The boundaries and numbers shown for the congressional districts are those specified in the state laws or court orders establishing the districts within each state.

Congressional districts for the 108th through 112th sessions were established by the states based on the result of the 2000 Census. Congressional districts for the 113th through 115th sessions were established by the states based on the result of the 2010 Census. Boundaries are effective until January of odd number years (for example, January 2015, January 2017, etc.), unless a state initiative or court ordered redistricting requires a change. All states established new congressional districts in 2011-2012, with the exception of the seven single member states (Alaska, Delaware, Montana, North Dakota, South Dakota, Vermont, and Wyoming).

For the states that have more than one representative, the Census Bureau requested a copy of the state laws or applicable court order(s) for each state from each secretary of state and each 2010 Redistricting Data Program state liaison requesting a copy of the state laws and/or applicable court order(s) for each state. Additionally, the states were asked to furnish their newly established congressional district boundaries and numbers by means of geographic equivalency files. States submitted equivalency files since most redistricting was based on whole census blocks. Kentucky was the only state where congressional district boundaries split some of the 2010 Census tabulation blocks. For further information on these blocks, please see the user-note at the bottom of the tables for this state.

The Census Bureau entered this information into its geographic database and produced tabulation block equivalency files that depicted the newly defined congressional district boundaries. Each state liaison was furnished with their file and requested to review, submit corrections, and certify the accuracy of the boundaries.

This edition of the Congressional District Atlas contains maps and tables for the 105th Congress of the United States. The maps show the boundaries of each congressional district. Tables listing the jurisdictions that are completely or partially within each congressional district are included. For states with only one congressional district, a state map is included but there is no table. The maps and tables are designed for page size (8 1/2 x 11) printed output. Although the map images use co lor for enhanced viewing, the design allows for acceptable black and white desktop printing. For more information, see the sections on Maps and Tables. Background: 103rd and 104th Congress Following the 1990 decennial census, most states redistricted for the 103rd Congress based upon the apportionment of the seats for the U.S. House of Representatives and the most recent decennial census data. For the 104th Congress, six states redistricted or through court action had either plans revised or redrawn. These states were Georgia, Louisiana, Maine, Minnesota, South Carolina and Virginia. The 104th Congress began January 1995 and continued through the beginning of January 1997. 105th Congress The 105th Congress began January 5, 1997 and continues through the beginning of January 1999. For the 105th Congress, Florida, Georgia, Kentucky, Louisiana, and Texas had new or revised congressional district plans. The Census Bureau retabulated demographic data from the 1990 census to accommodate any congressional district boundary changes from the previous Congress. This data is available on a separate CD-ROM from the Census Bureau Customer Service Branch (301) 457-4100. The 105th Congressional District Atlas CD-ROM provides maps showing the boundaries of the congressional districts of the 105th Congress. To meet the data needs for the 105th Congress, the Census Bureau designed this product on CD-ROM for all states. It contains maps and related entity tables in Adobe.

Note to Users: This CD is part of a collection located in the Data Archive of the Odum Institute for Research in Social Science, at the University of North Carolina at Chapel Hill. The collection is located in Room 10, Manning Hall. Users may check the CDs out subscribing to the honor system. Items can be checked out for a period of two weeks. Loan forms are located adjacent to the collection.

This layer was developed by the Research & Analytics Group of the Atlanta Regional Commission, using data from the U.S. Census Bureau’s American Community Survey 5-year estimates for 2013-2017, to show school enrollment, education attainments, and household composition by race and by US Congressional Districts in Georgia.

The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent.

The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2013-2017). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available.

For further explanation of ACS estimates and margin of error, visit Census ACS website.

Naming conventions:

Prefixes:

None

Count

p

Percent

r

Rate

m

Median

a

Mean (average)

t

Aggregate (total)

ch

Change in absolute terms (value in t2 - value in t1)

pch

Percent change ((value in t2 - value in t1) / value in t1)

chp

Change in percent (percent in t2 - percent in t1)

Suffixes:

None

Change over two periods

_e

Estimate from most recent ACS

_m

Margin of Error from most recent ACS

_00

Decennial 2000

Attributes:

Attributes and definitions available below under "Attributes" section and in Infrastructure Manifest (due to text box constraints, attributes cannot be displayed here).

Source: U.S. Census Bureau, Atlanta Regional Commission

Date: 2013-2017

For additional information, please visit the Census ACS website.

The 1998 Dress Rehearsal was conducted as a prelude to the United States Census of Population and Housing, 2000, in the following locations: (1) Columbia, South Carolina, and surrounding areas, including the town of Irmo and the counties of Chester, Chesterfield, Darlington, Fairfield, Kershaw, Lancaster, Lee, Marlboro, Newberry, Richland, and Union, (2) Sacramento, California, and (3) Menominee County, Wisconsin, including the Menominee American Indian Reservation. This collection contains map files showing various levels of geography (in the form of Census Tract Outline Maps, Voting District/State Legislative District Outline Maps, and County Block Maps), TIGER/Line digital files, and Corner Point files for the Census 2000 Dress Rehearsal sites. The Corner Point data files contain the bounding latitude and longitude coordinates for each individual map sheet of the 1998 Dress Rehearsal Public Law (P.L.) 94-171 map products. These files include a sheet identifier, minimum and maximum longitude, minimum and maximum latitude, and the map scale (integer value) for each map sheet. The latitude and longitude coordinates are in decimal degrees and expressed as integer values with six implied decimal places. There is a separate Corner Point File for each of the three map types: County Block Map, Census Tract Outline Map, and Voting District/State Legislative District Outline Map. Each of the three map file types is provided in two formats: Portable Document Format (PDF), for viewing, and Hewlett-Packard Graphics Language (HP-GL) format, for plotting. The County Block Maps show the greatest detail and the most complete set of geographic information of all the maps. These large-scale maps depict the smallest geographic entities for which the Census Bureau presents data -- the census blocks -- by displaying the features that delineate them and the numbers that identify them. These maps show the boundaries, names, and codes for American Indian/Alaska Native areas, county subdivisions, places, census tracts, and, for this series, the geographic entities that the states delineated in Phase 2, Voting District Project, of the Redistricting Data Program. The HP-GL version of the County Block Maps is broken down into index maps and map sheets. The map sheets cover a small area, and the index maps are composed of multiple map sheets, showing the entire area. The intent of the County Block Map series is to provide a map for each county on the smallest possible number of map sheets at the maximum practical scale, dependent on the area size of the county and the density of the block pattern. The latter affects the display of block numbers and feature identifiers. The Census Tract Outline Maps show the boundaries and numbers of census tracts, and name the features underlying the boundaries. These maps also show the boundaries and names of counties, county subdivisions, and places. They identify census tracts in relation to governmental unit boundaries. The mapping unit is the county. These large-format maps are produced to support the P.L. 94-171 program and all other 1998 Dress Rehearsal data tabulations. The Voting District/State Legislative District Outline Maps show the boundaries and codes for voting districts as delineated by the states in Phase 2, Voting District Project, of the Redistricting Data Program. The features underlying the voting district boundaries are shown, as well as the names of these features. Additionally, for states that submit the information, these maps show the boundaries and codes for state legislative districts and their underlying features. These maps also show the boundaries of and names of American Indian/Alaska Native areas, counties, county subdivisions, and places. The scale of the district maps is optimized to keep the number of map sheets for each area to a minimum, but the scale and number of map sheets will vary by the area size of the county and the voting districts and state legislative districts delineated by the states. The Census 2000 Dress Rehearsal TIGER/Line Files consist of line segments representing physical features and governmental and statistical boundaries. The files contain information distributed over a series of record types for the spatial objects of a county. These TIGER/Line Files are an extract of selected geographic and cartographic information from the Census TIGER (Topological

Modeled vote choice of geographic, demographic, and turnout subgroups with survey and ecological data in the US. The current version models Presidential vote choice in 2016 and 2020 for each contemporaneous congressional district and each of four racial groups. The methodology is introduced and explained in Kuriwaki et al. (2023). “The Geography of Racially Polarized Voting: Calibrating Surveys at the District Level.” American Political Science Review. https://osf.io/mk9e6/

This map shows median age in the US by country, state, county, tract, and congressional district for 2023. ArcGIS Online account required for use.The pop-up is configured to show median age, median age by sex, child age (under 18) population, senior age (over 65) population, the age dependency ratio, and population by 5 year age increments. Blending is used at the Tract level to highlight areas of human settlement. Congressional district is turned off by default and can be enabled in the Layers pane.Esri 2023 Age Dependency Ratio is the estimated ratio of the child population (Age 0-17) and senior population (Age 65+) to the working-age population (Age 18-64) in the geographic area. This ratio is then multiplied by 100. Higher ratios denote that a greater burden is carried by working-age people. Lower ratios mean more people are working who can support the dependent population. Read more. See Updated Demographics for more information on Esri Demographic variables.Esri Updated Demographics represent the suite of annually updated U.S. demographic data that provides current-year and five-year forecasts for more than two thousand demographic and socioeconomic characteristics, a subset of which is included in this layer. Included are a host of tables covering key characteristics of the population, households, housing, age, race, income, and much more. Esri's Updated Demographics data consists of point estimates, representing July 1 of the current and forecast years.Get started with U.S. Updated DemographicsHow to use and interpret U.S. Updated DemographicsEsri Updated Demographics DocumentationMethodologyEssential Esri Demographics vocabularyThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. This layer requires an ArcGIS Online subscription and does not consume credits. Please cite Esri when using this data. For information about purchasing additional Esri's Updated Demographics data, contact datasales@esri.com. Feedback: we would like to hear from you while this layer is in beta release. If you have any feedback regarding this item or Esri Demographics, please use this survey. Fields available:GEOIDNameState NameState Abbreviation2023 Total Population (Esri)2023 Household Population (Esri)2023 Group Quarters Population (Esri)2023 Population Density (Pop per Square Mile) (Esri)2023 Total Households (Esri)2023 Average Household Size (Esri)2023 Total Housing Units (Esri)2023 Owner Occupied Housing Units (Esri)2023 Renter Occupied Housing Units (Esri)2023 Vacant Housing Units (Esri)2020-2023 Population: Compound Annual Growth Rate (Esri)2020-2023 Households: Compound Annual Growth Rate (Esri)2023 Housing Affordability Index (Esri)2023 Percent of Income for Mortgage (Esri)2023 Wealth Index (Esri)2023 Socioeconomic Status Index (Esri)2023 Generation Alpha Population (Born 2017 or Later) (Esri)2023 Generation Z Population (Born 1999 to 2016) (Esri)2023 Millennial Population (Born 1981 to 1998) (Esri)2023 Generation X Population (Born 1965 to 1980) (Esri)2023 Baby Boomer Population (Born 1946 to 1964) (Esri)2023 Silent & Greatest Generations Population (Born 1945/Earlier) (Esri)2023 Population by Generation Base (Esri)2023 Child Population (Age <18) (Esri)2023 Working-Age Population (Age 18-64) (Esri)2023 Senior Population (Age 65+) (Esri)2023 Child Dependency Ratio (Esri)2023 Age Dependency Ratio (Esri)2023 Senior Dependency Ratio (Esri)2023 Total Population Age 0-4 (Esri)2023 Total Population Age 5-9 (Esri)2023 Total Population Age 10-14 (Esri)2023 Total Population Age 15-19 (Esri)2023 Total Population Age 20-24 (Esri)2023 Total Population Age 25-29 (Esri)2023 Total Population Age 30-34 (Esri)2023 Total Population Age 35-39 (Esri)2023 Total Population Age 40-44 (Esri)2023 Total Population Age 45-49 (Esri)2023 Total Population Age 50-54 (Esri)2023 Total Population Age 55-59 (Esri)2023 Total Population Age 60-64 (Esri)2023 Total Population Age 65-69 (Esri)2023 Total Population Age 70-74 (Esri)2023 Total Population Age 75-79 (Esri)2023 Total Population Age 80-84 (Esri)2023 Total Population Age 85+ (Esri)2023 Median Age (Esri)2023 Male Population (Esri)2023 Median Male Age (Esri)2023 Female Population (Esri)2023 Median Female Age (Esri)2023 Total Population by Five-Year Age Base (Esri)2023 Total Daytime Population (Esri)2023 Daytime Population: Workers (Esri)2023 Daytime Population: Residents (Esri)2023 Daytime Population Density (Pop per Square Mile) (Esri)2023 Civilian Population Age 16+ in Labor Force (Esri)2023 Employed Civilian Population Age 16+ (Esri)2023 Unemployed Population Age 16+ (Esri)2023 Unemployment Rate (Esri)2023 Civilian Population 16-24 in Labor Force (Esri)2023 Employed Civilian Population Age 16-24 (Esri)2023 Unemployed Population Age 16-24 (Esri)2023 Unemployment Rate: Population Age 16-24 (Esri)2023 Civilian Population 25-54 in Labor Force (Esri)2023 Employed Civilian Population Age 25-54 (Esri)2023 Unemployed Population Age 25-54 (Esri)2023 Unemployment Rate: Population Age 25-54 (Esri)2023 Civilian Population 55-64 in Labor Force (Esri)2023 Employed Civilian Population Age 55-64 (Esri)2023 Unemployed Population Age 55-64 (Esri)2023 Unemployment Rate: Population Age 55-64 (Esri)2023 Civilian Population 65+ in Labor Force (Esri)2023 Employed Civilian Population Age 65+ (Esri)2023 Unemployed Population Age 65+ (Esri)2023 Unemployment Rate: Population Age 65+ (Esri)2023 Child Economic Dependency Ratio (Esri)2023 Working-Age Economic Dependency Ratio (Esri)2023 Senior Economic Dependency Ratio (Esri)2023 Economic Dependency Ratio (Esri)2023 Hispanic Population (Esri)2023 White Non-Hispanic Population (Esri)2023 Black/African American Non-Hispanic Population (Esri)2023 American Indian/Alaska Native Non-Hispanic Population (Esri)2023 Asian Non-Hispanic Population (Esri)2023 Pacific Islander Non-Hispanic Population (Esri)2023 Other Race Non-Hispanic Population (Esri)2023 Multiple Races Non-Hispanic Population (Esri)2023 Diversity Index (Esri)2023 Population by Race Base (Esri)2023 Population Age 25+: Less than 9th Grade (Esri)2023 Population Age 25+: 9-12th Grade/No Diploma (Esri)2023 Population Age 25+: High School Diploma (Esri)2023 Population Age 25+: GED/Alternative Credential (Esri)2023 Population Age 25+: Some College/No Degree (Esri)2023 Population Age 25+: Associate's Degree (Esri)2023 Population Age 25+: Bachelor's Degree (Esri)2023 Population Age 25+: Graduate/Professional Degree (Esri)2023 Educational Attainment Base (Pop 25+)(Esri)2023 Household Income less than $15,000 (Esri)2023 Household Income $15,000-$24,999 (Esri)2023 Household Income $25,000-$34,999 (Esri)2023 Household Income $35,000-$49,999 (Esri)2023 Household Income $50,000-$74,999 (Esri)2023 Household Income $75,000-$99,999 (Esri)2023 Household Income $100,000-$149,999 (Esri)2023 Household Income $150,000-$199,999 (Esri)2023 Household Income $200,000 or greater (Esri)2023 Median Household Income (Esri)2023 Average Household Income (Esri)2023 Per Capita Income (Esri)2023 Households by Income Base (Esri)2023 Gini Index (Esri)2023 P90-P10 Ratio of Income Inequality (Esri)2023 P90-P50 Ratio of Income Inequality (Esri)2023 P50-P10 Ratio of Income Inequality (Esri)2023 80-20 Share Ratio of Income Inequality (Esri)2023 90-40 Share Ratio of Income Inequality (Esri)2023 Households in Low Income Tier (Esri)2023 Households in Middle Income Tier (Esri)2023 Households in Upper Income Tier (Esri)2023 Disposable Income less than $15,000 (Esri)2023 Disposable Income $15,000-$24,999 (Esri)2023 Disposable Income $25,000-$34,999 (Esri)2023 Disposable Income $35,000-$49,999 (Esri)2023 Disposable Income $50,000-$74,999 (Esri)2023 Disposable Income $75,000-$99,999 (Esri)2023 Disposable Income $100,000-$149,999 (Esri)2023 Disposable Income $150,000-$199,999 (Esri)2023 Disposable Income $200,000 or greater (Esri)2023 Median Disposable Income (Esri)2023 Home Value less than $50,000 (Esri)2023 Home Value $50,000-$99,999 (Esri)2023 Home Value $100,000-$149,999 (Esri)2023 Home Value $150,000-$199,999 (Esri)2023 Home Value $200,000-$249,999 (Esri)2023 Home Value $250,000-$299,999 (Esri)2023 Home Value $300,000-$399,999 (Esri)2023 Home Value $400,000-$499,999 (Esri)2023 Home Value $500,000-$749,999 (Esri)2023 Home Value $750,000-$999,999 (Esri)2023 Home Value $1,000,000-$1,499,999 (Esri)2023 Home Value $1,500,000-$1,999,999 (Esri)2023 Home Value $2,000,000 or greater (Esri)2023 Median Home Value (Esri)2023 Average Home Value (Esri)2028 Total Population (Esri)2028 Household Population (Esri)2028 Population Density (Pop per Square Mile) (Esri)2028 Total Households (Esri)2028 Average Household Size (Esri)2023-2028 Population: Compound Annual Growth Rate (Esri)2023-2028 Households: Compound Annual Growth Rate (Esri)2023-2028 Per Capita Income: Compound Annual Growth Rate (Esri)2023-2028 Median Household Income: Compound Annual Growth Rate (Esri)2028 Diversity Index (Esri)2028 Median Household Income (Esri)2028 Average Household Income (Esri)2028 Per Capita Income (Esri)

A predominance & size map featuring all 3 candidates running for U.S. Representative Race in Congressional District 2. It uses circles and color to represent the amount of votes each candidate got during this 2022 election. Pros-It shows how the population voted better then the average predominance mapCons-The map can become blurry and hard to read at times

Summary File 1 (SF1) Urban/Rural Update contains summary statistics on population and housing subjects derived from the responses to the 2010 Census questionnaire. Population items include sex, age, race, Hispanic or Latino origin, household relationship, household type, household size, family type, family size, and group quarters. Housing items include occupancy status, vacancy status, and tenure (whether a housing unit is owner-occupied or renter-occupied). The summary statistics are presented in 333 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 statistical areas, counties, county subdivisions, places, congressional districts, American Indian Areas, Alaska Native Areas, Hawaiian Home Lands, ZIP Code tabulation areas, census tracts, block groups, and blocks. There are 177 population tables and 58 housing tables shown down to the block level; 84 population tables and 4 housing tables shown down to the census tract level; and 10 population tables shown down to the county level. Some of the summary areas are iterated for "geographic components" or portions of geographic areas, e.g., the principal city of a metropolitan statistical area (MSA) or the urban and rural portions of a MSA. With one variable per table cell and additional variables with geographic information, the collection comprises 2,597 data files, 49 per state, the District of Columbia, Puerto Rico, and the National File. The Census Bureau released SF1 in three stages: initial release, National Update, and Urban/Rural Update. The National Update added summary levels for the United States, regions, divisions, and geographic areas that cross state lines such as Combined Statistical Areas. This update adds urban and rural population and housing unit counts, summary levels for urban areas and the urban/rural components of census tracts and block groups, geographic components involving urbanized areas and urban clusters, and two new tables (household type by relationship for the population 65 years and over and a new tabulation of the total population by race). The initial release and National Update is available as ICPSR 33461. ICPSR supplies this data collection in 54 ZIP archives. There is a separate archive for each state, the District of Columbia, Puerto Rico, and the National File. The last archive contains a Microsoft Access database shell and additional documentation files besides the codebook.

This layer was developed by the Research & Analytics Group of the Atlanta Regional Commission, using data from the U.S. Census Bureau’s American Community Survey 5-year estimates for 2013-2017, to show numbers and percentages for voting age population by US Congress in the Atlanta region.

The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent.

The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2013-2017). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available.

For further explanation of ACS estimates and margin of error, visit Census ACS website.

Naming conventions:

Prefixes:

None

Count

p

Percent

r

Rate

m

Median

a

Mean (average)

t

Aggregate (total)

ch

Change in absolute terms (value in t2 - value in t1)

pch

Percent change ((value in t2 - value in t1) / value in t1)

chp

Change in percent (percent in t2 - percent in t1)

Suffixes:

None

Change over two periods

_e

Estimate from most recent ACS

_m

Margin of Error from most recent ACS

_00

Decennial 2000

Attributes:

SumLevel

Summary level of geographic unit (e.g., County, Tract, NSA, NPU, DSNI, SuperDistrict, etc)

GEOID

Census tract Federal Information Processing Series (FIPS) code

NAME

Name of geographic unit

Planning_Region

Planning region designation for ARC purposes

Acres

Total area within the tract (in acres)

SqMi

Total area within the tract (in square miles)

County

County identifier (combination of Federal Information Processing Series (FIPS) codes for state and county)

CountyName

County Name

VotingAgeCitizen_e

# Citizen, 18 and over population, 2017

VotingAgeCitizen_m

# Citizen, 18 and over population, 2017 (MOE)

VotingAgeCitizenMale_e

# Male citizen, 18 and over population, 2017

VotingAgeCitizenMale_m

# Male citizen, 18 and over population, 2017 (MOE)

pVotingAgeCitizenMale_e

% Male citizen, 18 and over population, 2017

pVotingAgeCitizenMale_m

% Male citizen, 18 and over population, 2017 (MOE)

VotingAgeCitizenFemale_e

# Female citizen, 18 and over population, 2017

VotingAgeCitizenFemale_m

# Female citizen, 18 and over population, 2017 (MOE)

pVotingAgeCitizenFemale_e

% Female citizen, 18 and over population, 2017

pVotingAgeCitizenFemale_m

% Female citizen, 18 and over population, 2017 (MOE)

last_edited_date

Last date the feature was edited by ARC

Source: U.S. Census Bureau, Atlanta Regional Commission

Date: 2013-2017

For additional information, please visit the Census ACS website.

These data were developed by the Research & Analytics Department at the Atlanta Regional Commission using data from the U.S. Census Bureau across all standard and custom geographies at statewide summary level where applicable.For a deep dive into the data model including every specific metric, see the ACS 2019-2023. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics. Find naming convention prefixes/suffixes, geography definitions and user notes below.Prefixes:NoneCountpPercentrRatemMedianaMean (average)tAggregate (total)chChange in absolute terms (value in t2 - value in t1)pchPercent change ((value in t2 - value in t1) / value in t1)chpChange in percent (percent in t2 - percent in t1)sSignificance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computedSuffixes:_e23Estimate from 2019-23 ACS_m23Margin of Error from 2019-23 ACS_e102006-10 ACS, re-estimated to 2020 geography_m10Margin of Error from 2006-10 ACS, re-estimated to 2020 geography_e10_23Change, 2010-23 (holding constant at 2020 geography)GeographiesAAA = Area Agency on Aging (12 geographic units formed from counties providing statewide coverage)ARC21 = Atlanta Regional Commission modeling area (21 counties merged to a single geographic unit)ARWDB7 = Atlanta Regional Workforce Development Board (7 counties merged to a single geographic unit)BeltLineStatistical (buffer)BeltLineStatisticalSub (subareas)Census Tract (statewide)CFGA23 = Community Foundation for Greater Atlanta (23 counties merged to a single geographic unit)City (statewide)City of Atlanta Council Districts (City of Atlanta)City of Atlanta Neighborhood Planning Unit (City of Atlanta)City of Atlanta Neighborhood Statistical Areas (City of Atlanta)County (statewide)CCDIST = County Commission Districts (statewide where applicable)CCSUPERDIST = County Commission Superdistricts (DeKalb)Georgia House (statewide)Georgia Senate (statewide)HSSA = High School Statistical Area (11 county region)MetroWater15 = Atlanta Metropolitan Water District (15 counties merged to a single geographic unit)Regional Commissions (statewide)State of Georgia (single geographic unit)Superdistrict (ARC region)US Congress (statewide)UWGA13 = United Way of Greater Atlanta (13 counties merged to a single geographic unit)ZIP Code Tabulation Areas (statewide)The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2019-2023). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2019-2023Open Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the data manifest: https://opendata.atlantaregional.com/documents/182e6fcf8201449086b95adf39471831/about

Although the American Community Survey (ACS) produces population, demographic and housing unit estimates, it is the Census Bureau's Population Estimates Program that produces and disseminates the official estimates of the population for the nation, states, counties, cities, and towns and estimates of housing units for states and counties..Supporting documentation on code lists, subject definitions, data accuracy, and statistical testing can be found on the American Community Survey website in the Technical Documentation section.Sample size and data quality measures (including coverage rates, allocation rates, and response rates) can be found on the American Community Survey website in the Methodology section..Source: U.S. Census Bureau, 2017-2021 American Community Survey 5-Year Estimates.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 roughly 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 ACS Technical Documentation). The effect of nonsampling error is not represented in these tables..In 2016, changes were made to the languages and language categories presented in tables B16001, C16001, and B16002. For more information, see: 2016 Language Data User note..Geographical restrictions have been applied to Table B16001 - LANGUAGE SPOKEN AT HOME BY ABILITY TO SPEAK ENGLISH FOR THE POPULATION 5 YEARS AND OVER for the 5-year data estimates. These restrictions are in place to protect data privacy for the speakers of smaller languages. Geographic areas published for the 5-year B16001 table include: Nation (010), States (040), Metropolitan Statistical Area-Metropolitan Divisions (314), Combined Statistical Areas (330), Congressional Districts (500), and Public Use Microdata Sample Areas (PUMAs) (795). For more information on these geographical delineations, see the Metropolitan Statistical Area Reference Files. County and tract-level data are no longer available for table B16001; for specific language data for these smaller geographies, please use table C16001. Additional languages are also available in the Public Use Microdata Sample (PUMS), at the State and Public Use Microdata Sample Area (PUMA) levels of geography..The 2017-2021 American Community Survey (ACS) data generally reflect the March 2020 Office of Management and Budget (OMB) delineations of metropolitan and micropolitan statistical areas. In certain instances, the names, codes, and boundaries of the principal cities shown in ACS tables may differ from the OMB delineation lists due to differences in the effective dates of the geographic entities..Estimates of urban and rural populations, housing units, and characteristics reflect boundaries of urban areas defined based on Census 2010 data. As a result, data for urban and rural areas from the ACS do not necessarily reflect the results of ongoing urbanization..Explanation of Symbols:- The estimate could not be computed because there were an insufficient number of sample observations. For a ratio of medians estimate, one or both of the median estimates falls in the lowest interval or highest interval of an open-ended distribution. For a 5-year median estimate, the margin of error associated with a median was larger than the median itself.N The estimate or margin of error cannot be displayed because there were an insufficient number of sample cases in the selected geographic area. (X) The estimate or margin of error is not applicable or not available.median- The median falls in the lowest interval of an open-ended distribution (for example "2,500-")median+ The median falls in the highest interval of an open-ended distribution (for example "250,000+").** The margin of error could not be computed because there were an insufficient number of sample observations.*** The margin of error could not be computed because the median falls in the lowest interval or highest interval of an open-ended distribution.***** A margin of error is not appropriate because the corresponding estimate is controlled to an independent population or housing estimate. Effectively, the corresponding estimate has no sampling error and the margin of error may be treated as zero.

The 2015 TIGER Geodatabases are extracts of selected nation based and state based geographic and cartographic information from the U.S. Census Bureau's Master Address File/Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) database. The geodatabases include feature class layers of information for the fifty states, the District of Columbia, Puerto Rico, and the Island areas (American Samoa, the Commonwealth of the Northern Mariana Islands, Guam, and the United States Virgin Islands). The geodatabases do not contain any sensitive data. The 2015 TIGER Geodatabases are designed for use with Esriâ s ArcGIS.

        The State Geodatabase for Indiana geodatabase contains multiple layers. These layers are the Block, Block Group, Census Designated Place, Census
        Tract, Consolidated City, County, County Subdivision and Incorporated Place layers.

        Block Groups (BGs) are clusters of blocks within the same census tract. Each census tract contains at least one BG, and BGs are uniquely numbered
        within census tracts. BGs have a valid code range of 0 through 9. BGs 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 BG 3 within that
        census tract. BGs 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 BG 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 BG boundaries in this release are
        those that were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census. 

        An incorporated place, or census designated place, is established to provide governmental functions for a concentration of people as opposed to a
        minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places
        always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village,
        or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated
        places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally
        incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local,
        and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP
        boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in
        an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some
        housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2013, as reported through the Census
        Bureau's Boundary and Annexation Survey (BAS). Limited updates that occurred after January 1, 2013, such as newly incorporated places, are also
        included. The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010
        Census.

        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. 

         A consolidated city is a unit of local government for which the functions of an incorporated place and its county or minor civil division (MCD) have
        merged. This action results in both the primary incorporated place and the county or MCD continuing to exist as legal entities, even though the
        county or MCD performs few or no governmental functions and has few or no elected officials. Where this occurs, and where one or more other
        incorporated places in the county or MCD continue to function as separate governments, even though they have been included in the consolidated
        government, the primary incorporated place is referred to as a consolidated city. The Census Bureau classifies the separately incorporated places
        within the consolidated city as place entities and creates a separate place (balance) record for the portion of the consolidated city not within any
        other place. The boundaries of the consolidated cities are those as of January 1, 2013, as reported through the Census Bureau's Boundary and
        Annexation Survey(BAS).

        The primary legal divisions of most states are termed counties. In Louisiana, these divisions are known as parishes. In Alaska, which has no
        counties, the equivalent entities are the organized boroughs, city and boroughs, municipalities, and for the unorganized area, census areas. The
        latter are delineated cooperatively for statistical purposes by the State of Alaska and the Census Bureau. In four states (Maryland, Missouri,
        Nevada, and Virginia), there are one or more incorporated places that are independent of any county organization and thus constitute primary
        divisions of their states. These incorporated places are known as independent cities and are treated as equivalent entities for purposes of data
        presentation. The District of Columbia and Guam have no primary divisions, and each area is considered an equivalent entity for purposes of data
        presentation. The Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: Municipios in Puerto
        Rico, Districts and Islands in American Samoa, Municipalities in the Commonwealth of the Northern Mariana Islands, and Islands in the U.S. Virgin
        Islands. The entire area of the United States, Puerto Rico, and the Island Areas is covered by counties or equivalent entities. The boundaries for
        counties and equivalent entities are mostly as of January 1, 2013, primarily as reported through the Census Bureau's Boundary and Annexation Survey
        (BAS). However, some changes made after January 2013, including the addition and deletion of counties, are included.

        County subdivisions are the primary divisions of

These data were developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau across all standard and custom geographies at statewide summary level where applicable.For a deep dive into the data model including every specific metric, see the ACS 2018-2022 Data Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics. Find naming convention prefixes/suffixes, geography definitions and user notes below.Prefixes:NoneCountpPercentrRatemMedianaMean (average)tAggregate (total)chChange in absolute terms (value in t2 - value in t1)pchPercent change ((value in t2 - value in t1) / value in t1)chpChange in percent (percent in t2 - percent in t1)sSignificance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computedSuffixes:_e22Estimate from 2018-22 ACS_m22Margin of Error from 2018-22 ACS_e102006-10 ACS, re-estimated to 2020 geography_m10Margin of Error from 2006-10 ACS, re-estimated to 2020 geography_e10_22Change, 2010-22 (holding constant at 2020 geography)GeographiesAAA = Area Agency on Aging (12 geographic units formed from counties providing statewide coverage)ARC21 = Atlanta Regional Commission modeling area (21 counties merged to a single geographic unit)ARWDB7 = Atlanta Regional Workforce Development Board (7 counties merged to a single geographic unit)BeltLineStatistical (buffer)BeltLineStatisticalSub (subareas)Census Tract (statewide)CFGA23 = Community Foundation for Greater Atlanta (23 counties merged to a single geographic unit)City (statewide)City of Atlanta Council Districts (City of Atlanta)City of Atlanta Neighborhood Planning Unit (City of Atlanta)City of Atlanta Neighborhood Statistical Areas (City of Atlanta)County (statewide)Georgia House (statewide)Georgia Senate (statewide)HSSA = High School Statistical Area (11 county region)MetroWater15 = Atlanta Metropolitan Water District (15 counties merged to a single geographic unit)Regional Commissions (statewide)State of Georgia (single geographic unit)Superdistrict (ARC region)US Congress (statewide)UWGA13 = United Way of Greater Atlanta (13 counties merged to a single geographic unit)ZIP Code Tabulation Areas (statewide)The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2018-2022). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2018-2022Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the data manifest: https://opendata.atlantaregional.com/documents/3b86ee614e614199ba66a3ff1ebfe3b5/about

description: 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 table contains housing data derived from the U.S. Census 2010 Summary file 1 database for block groups. The 2010 Summary File 1 (SF 1) contains data compiled from the 2010 Decennial Census questions. This table contains data on housing units, owner and rental. This table contains population data derived from the U.S. Census 2010 Summary file 1 database for block groups. The 2010 Summary File 1 (SF 1) contains data compiled from the 2010 Decennial Census questions. This table contains data on ancestry groups, age, and sex.; abstract: 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 table contains housing data derived from the U.S. Census 2010 Summary file 1 database for block groups. The 2010 Summary File 1 (SF 1) contains data compiled from the 2010 Decennial Census questions. This table contains data on housing units, owner and rental. This table contains population data derived from the U.S. Census 2010 Summary file 1 database for block groups. The 2010 Summary File 1 (SF 1) contains data compiled from the 2010 Decennial Census questions. This table contains data on ancestry groups, age, and sex.

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau across all standard and custom geographies at statewide summary level where applicable. For a deep dive into the data model including every specific metric, see the ACS 2017-2021 Data Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics. Find naming convention prefixes/suffixes, geography definitions and user notes below.Prefixes:NoneCountpPercentrRatemMedianaMean (average)tAggregate (total)chChange in absolute terms (value in t2 - value in t1)pchPercent change ((value in t2 - value in t1) / value in t1)chpChange in percent (percent in t2 - percent in t1)sSignificance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computedSuffixes:_e21Estimate from 2017-21 ACS_m21Margin of Error from 2017-21 ACS_e102006-10 ACS, re-estimated to 2020 geography_m10Margin of Error from 2006-10 ACS, re-estimated to 2020 geography_e10_21Change, 2010-21 (holding constant at 2020 geography)GeographiesAAA = Area Agency on Aging (12 geographic units formed from counties providing statewide coverage)ARC21 = Atlanta Regional Commission modeling area (21 counties merged to a single geographic unit)ARWDB7 = Atlanta Regional Workforce Development Board (7 counties merged to a single geographic unit)BeltLine (buffer)BeltLine Study (subareas)Census Tract (statewide)CFGA23 = Community Foundation for Greater Atlanta (23 counties merged to a single geographic unit)City (statewide)City of Atlanta Council Districts (City of Atlanta)City of Atlanta Neighborhood Planning Unit (City of Atlanta)City of Atlanta Neighborhood Planning Unit STV (3 NPUs merged to a single geographic unit within City of Atlanta)City of Atlanta Neighborhood Statistical Areas (City of Atlanta)City of Atlanta Neighborhood Statistical Areas E02E06 (2 NSAs merged to single geographic unit within City of Atlanta)County (statewide)Georgia House (statewide)Georgia Senate (statewide)MetroWater15 = Atlanta Metropolitan Water District (15 counties merged to a single geographic unit)Regional Commissions (statewide)SPARCC = Strong, Prosperous And Resilient Communities ChallengeState of Georgia (single geographic unit)Superdistrict (ARC region)US Congress (statewide)UWGA13 = United Way of Greater Atlanta (13 counties merged to a single geographic unit)WFF = Westside Future Fund (subarea of City of Atlanta)ZIP Code Tabulation Areas (statewide)The user should note that American Community Survey data represent estimates derived from a surveyed sample of the population, which creates some level of uncertainty, as opposed to an exact measure of the entire population (the full census count is only conducted once every 10 years and does not cover as many detailed characteristics of the population). Therefore, any measure reported by ACS should not be taken as an exact number – this is why a corresponding margin of error (MOE) is also given for ACS measures. The size of the MOE relative to its corresponding estimate value provides an indication of confidence in the accuracy of each estimate. Each MOE is expressed in the same units as its corresponding measure; for example, if the estimate value is expressed as a number, then its MOE will also be a number; if the estimate value is expressed as a percent, then its MOE will also be a percent. The user should also note that for relatively small geographic areas, such as census tracts shown here, ACS only releases combined 5-year estimates, meaning these estimates represent rolling averages of survey results that were collected over a 5-year span (in this case 2017-2021). Therefore, these data do not represent any one specific point in time or even one specific year. For geographic areas with larger populations, 3-year and 1-year estimates are also available. For further explanation of ACS estimates and margin of error, visit Census ACS website.Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2017-2021Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the data manifest: https://garc.maps.arcgis.com/sharing/rest/content/items/34b9adfdcc294788ba9c70bf433bd4c1/data

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