This dataset contains population densities of 15 study watersheds in Gwinnett County, Georgia from 2000 to 2020. Population densities were determined for 2000, 2010, and 2020 from the decadal U.S. Census and for 2012 and 2017 from the American Community Survey 5-year estimates of 2010-14 and 2015¬-19 block group data, respectively. Population density within each watershed was determined by clipping the census block group data by the watershed boundaries and area-weighting the block group population density data within each watershed. Census block group data is the smallest geographic unit for which the census provides data.

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

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 total population and change by state of Georgia 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

# Area, Acres, 2017

SqMi

# Area, square miles, 2017

County

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

CountyName

County Name

TotPop_e

# Total population, 2017

TotPop_m

# Total population, 2017 (MOE)

rPopDensity

Population density (people per square mile), 2017

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.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census 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, 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 EcoTrends project was established in 2004 by Dr. Debra Peters (Jornada Basin LTER, USDA-ARS Jornada Experimental Range) and Dr. Ariel Lugo (Luquillo LTER, USDA-FS Luquillo Experimental Forest) to support the collection and analysis of long-term ecological datasets. The project is a large synthesis effort focused on improving the accessibility and use of long-term data. At present, there are ~50 state and federally funded research sites that are participating and contributing to the EcoTrends project, including all 26 Long-Term Ecological Research (LTER) sites and sites funded by the USDA Agriculture Research Service (ARS), USDA Forest Service, US Department of Energy, US Geological Survey (USGS) and numerous universities. Data from the EcoTrends project are available through an exploratory web portal (http://www.ecotrends.info). This web portal enables the continuation of data compilation and accessibility by users through an interactive web application. Ongoing data compilation is updated through both manual and automatic processing as part of the LTER Provenance Aware Synthesis Tracking Architecture (PASTA). The web portal is a collaboration between the Jornada LTER and the LTER Network Office. The following dataset from Georgia Coastal Ecosystems (GCE) contains human population density measurements in numberPerKilometerSquared units and were aggregated to a yearly timescale.

The 2015 cartographic boundary KMLs are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The records in this file allow users to map the parts of Urban Areas that overlap a particular county. 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. 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 as of January 1, 2010.

The 2020 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. 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 2,644 Urban Areas (UAs) in this data release with either a minimum population of 5,000 or a housing unit count of 2,000 units. Each urban area is identified by a 5-character numeric census code that may contain leading zeroes. This file includes revisions made to the 2020 Census New Orleans, LA Urban Area where the territory originally delineated as the 2020 Census Laplace--Lutcher--Gramercy, LA Urban Area was combined with the 2020 Census New Orleans, LA Urban Area to form the current New Orleans, LA Urban Area. This file includes revisions made to the 2020 Census Atlanta, GA Urban Area and Gainesville, GA Urban Area, where some urban territory originally designated to the Gainesville, GA Urban Area was reassigned to the Atlanta, GA Urban Area.

This layer was developed by the Research & Analytics Division of the Atlanta Regional Commission by joining Population 2000-2008 to Census Tracts (2000) for the 20 county Atlanta Region. Attributes:FIPSTCO = Federal Information Processing Code Standard (FIPS) codes for State and CountyTRACT = 2000 Census Tract numberSTFID = A concatenation of the two previous fieldsTRACTID = 2000 Census Tract number (to 2 decimal places)WFD, MPO etc. = Fields indicating to which ARC Planning Region each tract belongsACRES = Area of tracts in acresSQ_MILES = Area of tracts in square milesfipsco = Geographic Identifier (County)ct00 = Census Tract Numberacres = Number of acrespop08 = Population 2008pop00 = Population 2000pop_ch = Population change, 2000 - 2008pop_pch = Percent change in population, 2000 - 2008popch_ac = Number of persons added per acreaachange = Average Annual Changedens08 = Population density in 2008 (population/acres)dens00 = Population density in 2000 (population/acres)

An additional table is included in the tables folder, detailing population by region, county, city, superdistricts, and census tracts.

Source: U.S. Census Bureau, Atlanta Regional CommissionDate: 2000 (Census), 2008(ARC)For additional information, please visit the Atlanta Regional Commission at www.atlantaregional.com

A dataset listing Georgia counties by population for 2024.

This layer was developed by the Research & Analytics Division of the Atlanta Regional Commission to represent the United States Census Bureau's 2010 Decennial Census Urbanized Areas and Urban Clusters.In order for others to use the information in the Census MAF/TIGER database in a geographic information system (GIS) or for other geographic applications, the Census Bureau releases to the public extracts of the database in the form of TIGER/Line Shapefiles. 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. 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.Attributes:UACE10 = Census urbanized area/urban cluster codeGEOID10 = UACE10NAME10 = Name of the urbanized area or urban clusterNAMELSAD10 = NAME10 + "Urbanized Area" or "Urban Cluster"LSAD10 = Legal/statistical area descriptionMTFCC10 = MAF/TIGER feature class codeUATYP10 = Census urban area typeFUNCSTAT10 = Functional statusALAND10 = Total land area in square metersAWATER10 = Total water area in square metersINTPTLAT10 = Latitude of geography centroidINTPTLON10 = Longitude of geography centroidShape.STArea() = Total area in square feetSource: U.S. Census Bureau, Atlanta Regional CommissionDate: 2010For additional information, please visit the Atlanta Regional Commission at www.atlantaregional.com

In 2023, the share of urban population in Georgia remained nearly unchanged at around 60.73 percent. Still, the share reached its highest value in the observed period in 2023. A population may be defined as urban depending on the size (population or area) or population density of the village, town, or city. The urbanization rate then refers to the share of the total population who live in an urban setting. International comparisons may be inconsistent due to differing parameters for what constitutes an urban center.Find more key insights for the share of urban population in countries like Armenia and Azerbaijan.

description: This shapefile contains landscape factors representing human disturbances summarized to local and network catchments of river reaches for the state of Georgia. This dataset is the result of clipping the feature class 'NFHAP 2010 HCI Scores and Human Disturbance Data for the Conterminous United States linked to NHDPLUSV1.gdb' to the state boundary of Georgia. Landscape factors include land uses, population density, roads, dams, mines, and point-source pollution sites. The source datasets that were compiled and attributed to catchments were identified as being: (1) meaningful for assessing fish habitat; (2) consistent across the entire study area in the way that they were assembled; (3) representative of conditions in the past 10 years, and (4) of sufficient spatial resolution that they could be used to make valid comparisons among local catchment units. In this data set, these variables are linked to the catchments of the National Hydrography Dataset Plus Version 1 (NHDPlusV1) using the COMID identifier. They can also be linked to the reaches of the NHDPlusV1 using the COMID identifier. Catchment attributes are available for both local catchments (defined as the land area draining directly to a reach; attributes begin with "L_" prefix) and network catchments (defined by all upstream contributing catchments to the reach's outlet, including the reach's own local catchment; attributes begin with "N_" prefix). This shapefile also includes habitat condition scores created based on responsiveness of biological metrics to anthropogenic landscape disturbances throughout ecoregions. Separate scores were created by considering disturbances within local catchments, network catchments, and a cumulative score that accounted for the most limiting disturbance operating on a given biological metric in either local or network catchments. This assessment only scored reaches representing streams and rivers (see the process section for more details). Please use the following citation: Esselman, P., D.M. Infante, L. Wang, W. Taylor, W. Daniel, R. Tingley, J. Fenner, A. Cooper, D. Wieferich, D. Thornbrugh and J. Ross. (April 2011) National Fish Habitat Action Plan (NFHAP) 2010 HCI Scores and Human Disturbance Data (linked to NHDPLUSV1) for Georgia. National Fish Habitat Partnership Data System. http://dx.doi.org/doi:10.5066/F7WQ01SN; abstract: This shapefile contains landscape factors representing human disturbances summarized to local and network catchments of river reaches for the state of Georgia. This dataset is the result of clipping the feature class 'NFHAP 2010 HCI Scores and Human Disturbance Data for the Conterminous United States linked to NHDPLUSV1.gdb' to the state boundary of Georgia. Landscape factors include land uses, population density, roads, dams, mines, and point-source pollution sites. The source datasets that were compiled and attributed to catchments were identified as being: (1) meaningful for assessing fish habitat; (2) consistent across the entire study area in the way that they were assembled; (3) representative of conditions in the past 10 years, and (4) of sufficient spatial resolution that they could be used to make valid comparisons among local catchment units. In this data set, these variables are linked to the catchments of the National Hydrography Dataset Plus Version 1 (NHDPlusV1) using the COMID identifier. They can also be linked to the reaches of the NHDPlusV1 using the COMID identifier. Catchment attributes are available for both local catchments (defined as the land area draining directly to a reach; attributes begin with "L_" prefix) and network catchments (defined by all upstream contributing catchments to the reach's outlet, including the reach's own local catchment; attributes begin with "N_" prefix). This shapefile also includes habitat condition scores created based on responsiveness of biological metrics to anthropogenic landscape disturbances throughout ecoregions. Separate scores were created by considering disturbances within local catchments, network catchments, and a cumulative score that accounted for the most limiting disturbance operating on a given biological metric in either local or network catchments. This assessment only scored reaches representing streams and rivers (see the process section for more details). Please use the following citation: Esselman, P., D.M. Infante, L. Wang, W. Taylor, W. Daniel, R. Tingley, J. Fenner, A. Cooper, D. Wieferich, D. Thornbrugh and J. Ross. (April 2011) National Fish Habitat Action Plan (NFHAP) 2010 HCI Scores and Human Disturbance Data (linked to NHDPLUSV1) for Georgia. National Fish Habitat Partnership Data System. http://dx.doi.org/doi:10.5066/F7WQ01SN

The 2019 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. The records in this file allow users to map the parts of Urban Areas that overlap a particular county. 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. 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 generalized boundaries for counties and equivalent entities are as of January 1, 2010.

This layer was developed by the Research & Analytics Division of the Atlanta Regional Commission using U.S. Census Bureau TIGER/Line files. The polygon features in Census_2010_Blocks_GA are subsets of Census_Blockgroups and Census_Tracts.Attributes:STATEFP10 = The Federal Information Processing Series (FIPS) state code. FIPS codes were formerly known as Federal Information Processing Standards codes, until the National Institute of Standards and Technology (NIST) announced its decision in 2005 to remove geographic entity codes from its oversight. The Census Bureau continues to maintain and issue codes for geographic entities covered under FIPS oversight, albeit with a revised meaning for the FIPS acronym. Geographic entities covered under FIPS include states, counties, congressional districts, core based statistical areas, places, county subdivisions, subminor civil divisions, consolidated cities, and all types of American Indian, Alaska Native, and Native Hawaiian areas. FIPS codes are assigned alphabetically according to the name of the geographic entity and may change to maintain alphabetic sort when new entities are created or names change. FIPS codes for specific geographic entity types are usually unique within the next highest level of geographic entity with which a nesting relationship exists. For example, FIPS state, congressional district, and core based statistical area codes are unique within nation; FIPS county, place, county subdivision, and subminor civil division codes are unique within state. The codes for American Indian, Alaska Native, and Native Hawaiian areas also are unique within state; those areas in multiple states will have different codes for each state.COUNTYFP10 = The Federal Information Processing Series (FIPS) county code. TRACTCE10 = Census Tract Codes and Numbers—Census tracts are identified by an up to four-digit integer number and may have an optional two-digit suffix; for example 1457.02 or 23. The census tract codes consist of six digits with an implied decimal between the fourth and fifth digit corresponding to the basic census tract number but with leading zeroes and trailing zeroes for census tracts without a suffix. The tract number examples above would have codes of 145702 and 002300, respectively.BLOCKCE10 = Census block number - Census blocks are numbered uniquely with a four-digit census block number from 0000 to 9999 within census tract, which nest within state and county. The first digit of the census block number identifies the block group. Block numbers beginning with a zero (in Block Group 0) are only associated with water-only areas.GEOID10 = A concatenation of STATEFP10, COUNTYFP10, TRACTCE10, and BLOCKCE10, which produces the entire FIPS code for this geography.NAME10 = Block nameMTFCC10 = MAF/TIGER feature class codeUR10 = Census urban/rural indicatorUACE10 = Census urbanized area codesFUNCSTAT10 = Functional statusALAND10 = Land area in square metersAWATER10 = Water area in square metersINTPTLAT10 = Latitude of the centroid (center of this geography)INTPLON10 = Longitude of the centroid (center of this geography)STFID = The entire FIPS code of this geographyCOUNTY_NM = County namePLNG_REGIO = Planning regionSUMLEV = Summary level of census geography (code)NAME = Block namePLACE = Census place codeSTATE = The state FIPS codeCOUNTY = The county FIPS codeTRACT = The tract FIPS codeBLOCK = The block FIPS codetotpop10 = Total populationoner_10 = One race populationwhite_or10 = White, one race populationbl_or10 = Black, one race populationaian_or10 = American Indian and Alaska Native, one race populationasia_or10 = Asian, one race populationnhpi_or10 = Native Hawaiian and Other Pacific Islander, one race populationsomoth_or1 = Some other, one race populationtwoplusr10 = Two-plus races populationtotpop101 = Total populationhisp_lat10 = Total Hispanic/Latino populationnonhisp10 = Total non-Hispanic/Latino populationnh_or10 = Non-Hispanic/Latino, one race populationnhw_or10 = Non-Hispanic/Latino White, one race populationnhbl_or10 = Non-Hispanic/Latino Black, one race populationnhai_or10 = Non-Hispanic/Latino American Indian and Alaskan Native, one race populationnhas_or10 = Non-Hispanic/Latino Asian, one race populationnhhp_or10 = Non-Hispanic/Latino Native Hawaiian and Other Pacific Islander, one race populationnhot_or10 = Non-Hispanic/Latino Other, one race populationnh_twor10 = Non-Hispanic/Latino, two or more races populationtothu10 = Total housing unitstotoccu_10 = Total occupied housing unitstotvach_10 = Total vacant housing unitsAcresLand = Land area in acresAcresWater = Water area in acresAcresTotal = Total area in acresSqMiLand = Land area in square milesDensPPSqMi = Density: Population per square mile of landShape.STArea() = Total area in square feetSource: U.S. Census Bureau, Atlanta Regional CommissionDate: 2010For additional information, please visit the Atlanta Regional Commission at www.atlantaregional.com