This web map displays data from the voter registration database as the percent of registered voters by census tract in King County, Washington. The data for this web map is compiled from King County Elections voter registration data for the years 2013-2019. The total number of registered voters is based on the geo-_location of the voter's registered address at the time of the general election for each year. The eligible voting population, age 18 and over, is based on the estimated population increase from the US Census Bureau and the Washington Office of Financial Management and was calculated as a projected 6 percent population increase for the years 2010-2013, 7 percent population increase for the years 2010-2014, 9 percent population increase for the years 2010-2015, 11 percent population increase for the years 2010-2016 & 2017, 14 percent population increase for the years 2010-2018 and 17 percent population increase for the years 2010-2019. The total population 18 and over in 2010 was 1,517,747 in King County, Washington. The percentage of registered voters represents the number of people who are registered to vote as compared to the eligible voting population, age 18 and over. The voter registration data by census tract was grouped into six percentage range estimates: 50% or below, 51-60%, 61-70%, 71-80%, 81-90% and 91% or above with an overall 84 percent registration rate. In the map the lighter colors represent a relatively low percentage range of voter registration and the darker colors represent a relatively high percentage range of voter registration. PDF maps of these data can be viewed at King County Elections downloadable voter registration maps. The 2019 General Election Voter Turnout layer is voter turnout data by historical precinct boundaries for the corresponding year. The data is grouped into six percentage ranges: 0-30%, 31-40%, 41-50% 51-60%, 61-70%, and 71-100%. The lighter colors represent lower turnout and the darker colors represent higher turnout. The King County Demographics Layer is census data for language, income, poverty, race and ethnicity at the census tract level and is based on the 2010-2014 American Community Survey 5 year Average provided by the United States Census Bureau. Since the data is based on a survey, they are considered to be estimates and should be used with that understanding. The demographic data sets were developed and are maintained by King County Staff to support the King County Equity and Social Justice program. Other data for this map is located in the King County GIS Spatial Data Catalog, where data is managed by the King County GIS Center, a multi-department enterprise GIS in King County, Washington. King County has nearly 1.3 million registered voters and is the largest jurisdiction in the United States to conduct all elections by mail. In the map you can view the percent of registered voters by census tract, compare registration within political districts, compare registration and demographic data, verify your voter registration or register to vote through a link to the VoteWA, Washington State Online Voter Registration web page.

Voting precincts are the most granular spatial units for reporting election outcomes, whereas census geographies, such as block groups, census tracts, and ZIP Code Tabulation Areas (ZCTAs), are commonly used for publishing demographic, economic, health, and environmental data. This dataset bridges the two by reallocating precinct-level votes to standard census geographies through a systematic and replicable framework. The reallocation assumes that votes within each precinct are distributed proportionally to the household population. Household population counts from census block groups—the smallest census unit with regularly updated population estimates—are used to allocate votes to fractions created by the intersection of precinct and census boundaries. This process is implemented using three allocation strategies: areal weighting, impervious surface weighting, and Regionalized Land Cover Regression (RLCR). Results from all three methods are provided. Among these, the RLCR method demonstrates the highest accuracy based on validation against voter-level ground truth data and is recommended as the primary version for analysis. The alternative methods may serve as robustness checks or sensitivity tests. The dataset currently includes the 2016 and 2020 U.S. general elections and is designed for seamless integration with other datasets, such as the American Community Survey (ACS), CDC PLACES, or IRS Statistics of Income (SOI), via the GEOID field.

Voting DistrictsThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), depicts Voting Districts (VTDs) in the United States and Puerto Rico. Per the USCB, "VTDs refer to the generic name for geographic entities, such as precincts, wards, and election districts, established by state governments for the purpose of conducting elections.”Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Voting Districts) and will support mapping, analysis, data exports and OGC API – Feature access.Data.gov: Not availableGeoplatform: Not availableFor more information, please visit: Voting and RegistrationFor feedback please contact: Esri_US_Federal_Data@esri.comThumbnail image courtesy of Mrs. GemstoneNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

Census Blocks from 2020. Redistricting Data (P.L. 94-171).Contact: District of Columbia, Office of Planning. Email: planning@dc.govGeography: Census BlocksCurrent Vintage: 2020P.L. 94-171 Table(s): P1. Race; P2. Hispanic or Latino, and Not Hispanic or Latino by Race; P3. Race for the Population 18 Years and Over; P4. Hispanic or Latino, and Not Hispanic or Latino by Race for the Population 18 Years and Over; P5. Group Quarters Population by Major Group Quarters Type; H1. Housing Occupancy StatusData downloaded from: https://www.census.gov/programs-surveys/decennial-census/about/rdo/summary-files.htmlNational Figures: data.census.govPublic Law 94-171, enacted in 1975, directs the U.S. Census Bureau to make special preparations to provide redistricting data needed by the 50 states.1 It specifies that within 1 year following Census Day, the Census Bureau must send the governor and legislative leadership in each state the data they need to redraw districts for the U.S. Congress and state legislatures. To meet this legal requirement, the Census Bureau set up a program that affords state officials an opportunity before each decennial census to define the small areas for which they wish to receive census population totals for redistricting purposes. Officials may receive data for voting districts (e.g., election precincts, wards) and state house and senate districts, in addition to standard census geographic areas such as counties, cities, census tracts, and blocks. State participation in defining areas is voluntary and nonpartisan. For further information on Public Law 94-171 and the 2020 Census Redistricting Data Program, see:www.census.gov/programs-surveys/decennial-census/about/rdo/program -management.htmlData processed using R statistical package and ArcGIS Desktop.

Election Data Attribute Field Definitions | Wisconsin Cities, Towns, & Villages Data Attributes Ward Data Overview: January 2025 municipal wards were collected in January 2025 by LTSB through LTSB's GeoData Collector. Current statutes require each county clerk, or board of election commissioners, no later than January 15 and July 15 of each year, to transmit to the LTSB, in an electronic format (approved by LTSB), a report confirming the boundaries of each municipality, ward and supervisory district within the county as of the preceding “snapshot” date of January 1 or July 1 respectively. Population totals for 2025 wards were estimated by aggregating 2020 US Census PL94-171 population data. LTSB has NOT topologically integrated the data. Election Data Overview: The 2024 Wisconsin election data that is included in this file was collected by LTSB from the *Wisconsin Elections Commission (WEC) after the general election. A disaggregation process was performed on this election data based on the municipal ward layer that was available at the time of the election. Disaggregation of Election Data: Election data is first disaggregated from reporting units to wards, and then to census blocks. Next, the election data is aggregated back up to wards, municipalities, and counties. The disaggregation of election data to census blocks is done based on total population. Detailed Methodology:Data is disaggregated first from reporting unit (i.e. multiple wards) to the ward level proportionate to the population of that ward.The data then is distributed down to the block level, again based on total population.When data is disaggregated to block or ward, we restrain vote totals not to exceed population 18 numbers, unless absolutely required.This methodology results in the following: Election data totals reported to the WEC at the state, county, municipal and reporting unit level should match the disaggregated election data total at the same levels. Election data totals reported to the WEC at ward level may not match the ward totals in the disaggregated election data file.Some wards may have more election data allocated than voter age population. This will occur if a change to the geography results in more voters than the 2020 historical population limits.Other things of note… We use a static, official ward layer (in this case created in 2025) to disaggregate election data to blocks. Using this ward layer creates some challenges. New wards are created every year due to annexations and incorporations. When these new wards are reported with election data, an issue arises wherein election data is being reported for wards that do not exist in our official ward layer. For example, if "Cityville" has four wards in the official ward layer, the election data may be reported for five wards, including a new ward from an annexation. There are two different scenarios and courses of action to these issues: When a single new ward is present in the election data but there is no ward geometry present in the official ward layer, the votes attributed to this new ward are distributed to all the other wards in the municipality based on population percentage. Distributing based on population percentage means that the proportion of the population of the municipality will receive that same proportion of votes from the new ward. In the example of Cityville explained above, the fifth ward may have five votes reported, but since there is no corresponding fifth ward in the official layer, these five votes will be assigned to each of the other wards in Cityville according the percentage of population.Another case is when a new ward is reported, but its votes are part of reporting unit. In this case, the votes for the new ward are assigned to the other wards in the reporting unit by population percentage; and not to wards in the municipality as a whole. For example, Cityville’s ward five was given as a reporting unit together with wards 1, 4, and 5. In this case, the votes in ward five are assigned to wards one and four according to population percentage. Outline Ward-by-Ward Election ResultsThe process of collecting election data and disaggregating to municipal wards occurs after a general election, so disaggregation has occurred with different ward layers and different population totals. We have outlined (to the best of our knowledge) what layer and population totals were used to produce these ward-by-ward election results.Election data disaggregates from WEC Reporting Unit -> Ward [Variant year outlined below]Elections 1990 – 2000: Wards 1991 (Census 1990 totals used for disaggregation)Elections 2002 – 2010: Wards 2001 (Census 2000 totals used for disaggregation)Elections 2012: Wards 2011 (Census 2010 totals used for disaggregation)Elections 2014 – 2016: Wards 2018 (Census 2010 totals used for disaggregation)Elections 2018: Wards 2018 (Census 2010 totals used for disaggregation)Elections 2020: Wards 2020 (Census 2020 totals used for disaggregation)Elections 2022: Wards 2022 (Census 2020 totals used for disaggregation)Elections 2024: Wards 2025 (Census 2020 totals used for disaggregation)Blocks -> Centroid geometry and spatially joined with Wards [All Versions]Each Block has an assignment to each of the ward versions outlined above.In the event that a ward exists now in which no block exists due to annexations, a block centroid was created with a population 0, and encoded with the proper Census IDs.Wards [All Versions] disaggregate -> Blocks This yields a block centroid layer that contains all elections from 1990 to 2024.Blocks [with all election data] -> Wards 2025 (then MCD 2025, and County 2025) All election data (including later elections) is aggregated to the Wards 2025 assignment of the blocks.Notes:Population of municipal wards 1991, 2001, 2011, 2020, 2022, and 2025 used for disaggregation were determined by their respective Census.Population and Election data will be contained within a county boundary. This means that even though MCD and ward boundaries vary greatly between versions of the wards, county boundaries have stayed the same, so data should total within a county the same between wards 2011 and wards 2025.Election data may be different for the same legislative district, for the same election, due to changes in the wards from 2011 and 2025. This is due to boundary corrections in the data from 2011 to 2025, and annexations, where a block may have been reassigned.*WEC replaced the previous Government Accountability Board (GAB) in 2016, which replaced the previous State Elections Board in 2008.

Voting DistrictsThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), depicts Voting Districts (VTDs) in the United States and Puerto Rico. Per the USCB, "VTDs refer to the generic name for geographic entities, such as precincts, wards, and election districts, established by state governments for the purpose of conducting elections.”Voting District 027 Danbury 1 (Ottawa County, OH)Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Voting Districts) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 63 (Series Information for 2020 Census Voting District (VTD) State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Voting Districts - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Voting Districts; My Congressional DistrictFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

This dataset was developed by the Research & Analytics Group at the Atlanta Regional Commission using data from the U.S. Census Bureau.For a deep dive into the data model including every specific metric, see the Infrastructure Manifest. The manifest details ARC-defined naming conventions, field names/descriptions and topics, summary levels; source tables; notes and so forth for all metrics.Naming conventions:Prefixes: None Countp Percentr Ratem Mediana 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)s Significance flag for change: 1 = statistically significant with a 90% CI, 0 = not statistically significant, blank = cannot be computed Suffixes: _e19 Estimate from 2014-19 ACS_m19 Margin of Error from 2014-19 ACS_00_v19 Decennial 2000, re-estimated to 2019 geography_00_19 Change, 2000-19_e10_v19 2006-10 ACS, re-estimated to 2019 geography_m10_v19 Margin of Error from 2006-10 ACS, re-estimated to 2019 geography_e10_19 Change, 2010-19The 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 2015-2019). 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: 2015-2019Data License: Creative Commons Attribution 4.0 International (CC by 4.0)Link to the manifest: https://www.arcgis.com/sharing/rest/content/items/3d489c725bb24f52a987b302147c46ee/data

Census Tracts from 2020. Redistricting Data (P.L. 94-171).Contact: District of Columbia, Office of Planning. Email: planning@dc.govGeography: Census TractsCurrent Vintage: 2020P.L. 94-171 Table(s): P1. Race; P2. Hispanic or Latino, and Not Hispanic or Latino by Race; P3. Race for the Population 18 Years and Over; P4. Hispanic or Latino, and Not Hispanic or Latino by Race for the Population 18 Years and Over; P5. Group Quarters Population by Major Group Quarters Type; H1. Housing Occupancy StatusData downloaded from: https://www.census.gov/programs-surveys/decennial-census/about/rdo/summary-files.htmlNational Figures: data.census.govPublic Law 94-171, enacted in 1975, directs the U.S. Census Bureau to make special preparations to provide redistricting data needed by the 50 states.1 It specifies that within 1 year following Census Day, the Census Bureau must send the governor and legislative leadership in each state the data they need to redraw districts for the U.S. Congress and state legislatures. To meet this legal requirement, the Census Bureau set up a program that affords state officials an opportunity before each decennial census to define the small areas for which they wish to receive census population totals for redistricting purposes. Officials may receive data for voting districts (e.g., election precincts, wards) and state house and senate districts, in addition to standard census geographic areas such as counties, cities, census tracts, and blocks. State participation in defining areas is voluntary and nonpartisan. For further information on Public Law 94-171 and the 2020 Census Redistricting Data Program, see:www.census.gov/programs-surveys/decennial-census/about/rdo/program -management.htmlData processed using R statistical package and ArcGIS Desktop.

Public Law 94-171, enacted in 1975, requires the Census Bureau to provide redistricting data in a format requested by state governments. Within one year following the Decennial Census (by April 1, 1991), the Census Bureau must provide the governor and legislature of each state with the population data needed to redraw legislative districts. To meet this requirement, the Census Bureau established a voluntary program to allow states to receive data for voting districts (e.g., election precincts, city wards) in addition to standard census geographic areas such as counties, cities, census tracts, and blocks. These files contain data for voting districts for those counties for which a state outlined voting district boundaries around a set of census blocks on census maps, in accordance with the guidelines of the program. Each state file provides data for the state and its subareas in the following order: state, county, voting district, county subdivision, place, census tract, block group, and block. Additionally, complete summaries are provided for the following geographic areas: county subdivision, place, consolidated city, state portion of American Indian and Alaska Native area, and county portion of American Indian and Alaska Native area. Area characteristics such as land area, water area, latitude, and longitude are provided. Summary statistics are provided for all persons and housing units in the geographic areas. Counts by race and by Hispanic and non-Hispanic origin are also given.

Public Law 94-171, enacted in 1975, directs the Census Bureau to make special preparations to provide redistricting data needed by the 50 states. It specifies that within a year following Census Day, the Census Bureau must send the governor and legislative leadership in each state the data they need to redraw districts for the United States Congress and state legislature. To meet this legal requirement, the Census Bureau set up a program that affords state officials an opportunity before each decennial census to define the small areas for which they wish to receive census population totals for redistricting purposes. Officials may receive data for voting districts (e.g., election precincts, wards) and state house and senate districts, in addition to standard census geographic areas such as counties, cities, census tracts, and tabulation blocks. State participation in defining areas is voluntary and nonpartisan.

Voting DistrictsThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), depicts Voting Districts (VTDs) in the United States and Puerto Rico. Per the USCB, "VTDs refer to the generic name for geographic entities, such as precincts, wards, and election districts, established by state governments for the purpose of conducting elections.”Voting District 027 Danbury 1 (Ottawa County, OH)Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Voting Districts) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 63 (Series Information for 2020 Census Voting District (VTD) State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (Voting Districts - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: Voting Districts; My Congressional DistrictFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Data SetThis data set is part of the NGDA Governmental Units, and Administrative and Statistical Boundaries Theme Community. Per the Federal Geospatial Data Committee (FGDC), this theme is defined as the "boundaries that delineate geographic areas for uses such as governance and the general provision of services (e.g., states, American Indian reservations, counties, cities, towns, etc.), administration and/or for a specific purpose (e.g., congressional districts, school districts, fire districts, Alaska Native Regional Corporations, etc.), and/or provision of statistical data (census tracts, census blocks, metropolitan and micropolitan statistical areas, etc.). Boundaries for these various types of geographic areas are either defined through a documented legal description or through criteria and guidelines. Other boundaries may include international limits, those of federal land ownership, the extent of administrative regions for various federal agencies, as well as the jurisdictional offshore limits of U.S. sovereignty. Boundaries associated solely with natural resources and/or cultural entities are excluded from this theme and are included in the appropriate subject themes."For other NGDA Content: Esri Federal Datasets

This GIS layer contains the geographical boundaries of the 2020 census blocks for Loudoun County, Virginia. The 2020 Census block boundaries were used for statistical data collection and tabulation purposes for the 2020 Decennial Census. Census blocks are the smallest geographic area for publishing data from the decennial Census. The geographical area covered by this geographic feature class is generally very small in densely settled areas, for instance one city block. In sparsely settled areas they may cover several square miles. Census blocks nest within every 2020 Census geographic area (i.e. block groups, tracts, census designated places, and local, state, and federal election districts). This nesting of blocks allows Census Bureau statistical data to be tabulated to the appropriate geographic areas by aggregating the block data up. Census blocks are uniquely numbered within census tracts, with the blocks valid range being 1 to 9999 with leading zeros added (i.e. 0001, 0023) when necessary to create a four digit unique identifier. This 2010 Census block layer is based on the U.S. Census Bureau Census 2020 TIGER/Line files. The boundaries are an extract of aerial photography and cartographic information, such as roads and streams, from the Loudoun County GIS system. Census Blocks are bounded on all sides by visible features, such as roads, streams, lakes, power lines, and railroad tracks, and/or by non-visible boundaries such as town and county boundaries, and short line-of-sight extensions of streets and roads.

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 ARC 20 County 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.

2020 Census data for the city of Boston, Boston neighborhoods, census tracts, block groups, and voting districts. In the 2020 Census, the U.S. Census Bureau divided Boston into 207 census tracts (~4,000 residents) made up of 581 smaller block groups. The Boston Planning and Development Agency uses the 2020 tracts to approximate Boston neighborhoods. The 2020 Census Redistricting data also identify Boston’s voting districts.

For analysis of Boston’s 2020 Census data including graphs and maps by the BPDA Research Division and Office of Digital Cartography and GIS, see 2020 Census Research Publications

For a complete official data dictionary, please go to 2020 Census State Redistricting Data (Public Law 94-171) Summary File, Chapter 6. Data Dictionary. 2020 Census State Redistricting Data (Public Law 94-171) Summary File

2020 Census Tracts In Boston

2020 Census Block Groups In Boston

Boston Neighborhood Boundaries Approximated By 2020 Census Tracts

Boston Voting District Boundaries

2020 Census Redistricting data for North Carolina census tracts. Census tracts and block groups are statistical subdivisions of counties. Tract and block group boundaries are revised for each decennial Census. Data include population, population by race and Hispanic Origin, voting age (18+) population by race and Hispanic Origin, housing units by occupancy status, and group quarters population by type of group quarters.

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. 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 2020 Census.

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

Standard block groups are clusters of blocks within the same census tract that have the same first digit of their 4-character census block number (e.g., Blocks 3001, 3002, 3003 to 3999 in census tract 1210.02 belong to block group 3). Current block groups do not always maintain these same block number to block group relationships due to boundary and feature changes that occur throughout the decade. For example, block 3001 might move due to a change in the census tract boundary. Even if the block is no longer in block group 3, the block number (3001) will not change. However, the GEOID for that block, identifying block group 3, would remain the same in the attribute information in the TIGER/Line Shapefiles because block GEOIDs are always built using the decennial geographic codes.Block groups delineated for the 2020 Census generally contain 600 to 3,000 people. Local participants delineated most block groups as part of the Census Bureau's PSAP. The Census Bureau delineated block groups only where a local or tribal government declined to participate or where the Census Bureau could not identify a potential local participant.A block group usually covers a contiguous area. Each census tract contains one or more block groups and block groups have unique numbers within census tract. Within the standard census geographic hierarchy, block groups never cross county or census tract boundaries, but may cross the boundaries of county subdivisions, places, urban areas, voting districts, congressional districts, and AIANNH areas.Block groups have a valid range of zero (0) through nine (9). Block groups beginning with a zero generally are in coastal and Great Lakes water and territorial seas. Rather than extending a census tract boundary into the Great Lakes or out to the 3-mile territorial sea limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore.

The Social Environment refers to characteristics of the people and institutions in a census tract, including: 1) Religious organizations (churches and places of worship); and 2) Voter turnout for the 2012 Presidential Election. Coverage for all data: 10-county Detroit-Warren-Ann Arbor Combined Statistical Area.

Analysis of ‘Loudoun 2020 Census Blocks’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/6b9c0749-8be5-4cdc-a242-ad2b9de838b7 on 27 January 2022.

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

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