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

State of Missouri Congressional districts created under House Bill 1 of the 103rd General Assembly's 2nd Extraordinary Session in September of 2025. This bill has not yet been signed into law by the Governor.

State Legislative Districts - Lower Houses This feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), displays State Legislative Districts (SLDs) in the lower houses of state legislatures in the United States. According to the USCB, "SLDs are the areas from which members are elected to state legislatures. They embody the upper (senate) and lower (house) chambers of a state legislature. Nebraska has a unicameral legislature and the District of Columbia has a single council, both of which the Census Bureau treats as upper-chamber legislative areas for data presentation; there are no data by lower houses for either Nebraska or the District of Columbia". California"s Assembly Districts 19 & 22 Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (2024 State Legislative Districts - Lower) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 91 (Series Information for State Legislative District (SLD) Lower Chamber State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (State Legislative Districts - Lower Houses - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: About State Legislative DistrictsFor feedback please contact: Esri_US_Federal_Data@esri.com NGDA Data Set This 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

Virginia's 1st Congressional District GIS

original data sets in .kml (high and low resolution), now also in .geojson, .topojson, and .shp.

This feature class includes States, Counties or Boroughs, Congressional Districts, Alaska Recording Districts, County Subdivisions, and Places boundaries that are derived from the latest official Census Bureau and Alaska Department of Natural Resources datasets. Features within Forest Service Administrative Forest boundaries may have been modified by the Forest Service for improved accuracy and spatial coincidence(vertical integration).This record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService OGC WMS CSV Shapefile GeoJSON KML For complete information, please visit https://data.gov.

Dear Commission: I have attached the GeoJSON data for a revised version of the Congressional map that I originally submitted to the Commission in early July 2021. This revised map takes into account the recently-released granular 2020 US Census results. You can also view this new map on Dave's Redistricting website at:https://davesredistricting.org/maps#viewmap::61ea57de-e691-47ad-aa1a-0f4b5eb39eb7I became interested in this process as a mapping and community nerd (rather than a political guru), after becoming aware that the initial preliminary plan cut my home city of Boulder off from the western part of Boulder county. I don't think that is a good idea -- Boulder is so linked to the communities to the west in the foothills up to the Continental Divide, and vice versa. So, I wanted to put my GIS background to work and help the Commission and staff envision alternate configurations of districts which solve that issue.In this new map based on the 2020 Census, I took much greater care to not split municipal boundaries between different districts. All Congressional districts are within +/1 person of the target population. Also, after reviewing a number of the public comments here and ones made during hearings, I put in my best effort to capture several communities of interest in this revised map:1) SLV counties kept whole and associated with district 3 2) Multiple El Paso County military installations all kept together in district 5 3) Continental Divide used as natural boundary for much of the northern Front Range (keeping Boulder, Gilpin, and Clear Creek counties together in district 2 along with all of Larimer Co.)4) Arkansas River valley kept together below Salida (running downslope/east through Pueblo County, etc)5) Northern Douglas County allocated to a southern/western Denver metro district (7th district)6) 7th district is made to be extremely competitive (within 1 point based on the 2016-2020 composite competitiveness score) 7) New 8th district centered solidly in north Denver metro (northern JeffCo, Broomfield, western Adams, far southwestern Weld) 8) Denver City/County kept whole with only minor population-balancing nibblesThank you for your continued work and consideration.Sincerely,Laura J. Westerfield

Context

Complete statewide mapping files of a state's precincts can be difficult to come by. This file has been compiled to fill that need.

Content

This is the most recent statewide precinct file for Arizona. The properties have been generated for efficiently slicing and dicing up counties so that the file can be merged with Legislative and Congressional districts as well as other political boundaries.

Acknowledgements

The precinct file is recompiled using data requested from one of Arizona's 15 county GIS departments whenever a county re-precincts.

Inspiration

Gain insight into Arizona's political demographics by combining this with election results files, census tracts and other publicly available geographic information.

Map showing the Virginia House of Delegates district boundaries and voting locations. Recommended print size: 31” X 37”.

This record provides metadata, schemas, and transformation functions for Minnesota boundary layers as part of the Civic Data Boundaries series within the Civic Interconnect ecosystem.

The Minnesota component serves as a data adapter, translating the Minnesota Secretary of State's public GeoJSON boundary files, covering precinct, county, congressional, and legislative districts, into a unified, cross-state Civic Interconnect schema.

Included in this release

• manifest.json - defines data layers, source URLs, and schema mappings

• api/v1.0.0/catalog.json - machine-readable catalog entry for programmatic discovery

• schemas/ - JSON Schemas for validating catalog and manifest structure

• js/adapter.js - state-level adapter for Minnesota boundary data

• js/transform.js - pure functions for property and geometry transformation

• .github/ and scripts/ - validation and continuous integration utilities

All derived metadata, schemas, and configuration files are released under the Creative Commons Attribution 4.0 International License (CC BY 4.0).
Official boundary geometries are accessed directly from the Minnesota Secretary of State:
https://www.sos.mn.gov/election-administration-campaigns/data-maps/voting-precincts/.

See the accompanying CITATION.cff file for citation details.

Overview

Kensho's Team Impact is excited to partner with the American Voter Project (the non-profit that runs the Ohio Voter Project) to make this dataset on Georgia voters available via Kaggle.

https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F73968%2Fe929cb6eb3d7a11dbef5feee4b336f91%2FOVP-Kensho_1000.jpg?generation=1608150215724319&alt=media" alt="">

This dataset has two main components. The first is statewide Georgia voter lists for October, November, and December provided by the American Voter Project and originally sourced from the Georgia Secretary of State. The second is cartographic boundary files from the US Census.

Starter Notebook

Jump right in with a starter notebook that demonstrates reading the data, creating maps, and aggregating voter data.

https://www.kaggle.com/gabrielaltay/georgia-voter-list-starter

Voter File Descriptions

Voter files contain one row per person, are provided for October, November, and December of 2000, and use the following naming convention,

tbl_prod_GABUYYYYMM_sample.csv

The samples are defined as,

• all: all voters in the file provided by the secretary of state of Georgia for a given month
• dropped_records: voters that were in the all sample last month but are not in the all sample this month
• new_records: voters that are in the all sample this month but were not in the all sample last month
• address_change: voters with address info that changed from last month
• name_change: voters with name info that changed from last month
• voter_in_inactive: voters with voter_status = I in the all sample for this month
• voter_status_change: voters with voter_status that changed from last month

Due to privacy concerns we have removed names and addresses (except city, zipcode, and county) from the voter files.

Geographic File Descriptions

The geographic data we collected consists of geojson files that describe cartographic boundaries in the US. We obtained shapefiles from this website and converted them to geojson using geopandas. We follow the naming convention used for the census shape files,

cb_2019_us_entity_rr.geojson where,

entity = the geographic entity rr = resolution level (we use the 20m = 1:20,000,000 and 500k = 1:500,000 scale files)

Specifically, we include the following geographic entities,

cbsa: metropolitan / micropolitan statistical area cd116: congressional district (116th congress) county: county csa: combined statistical area division: national division (subdivisions of regions) nation: national outline region: national region (northeast, southeast, midwest, west) state: state and equivalent zcta510: 5-digit ZIP code tabulation area (Census 2010)

Usage Restrictions

A quote from the Georgia Secretary of State dataset website,

The Statewide Voter List is an electronic file that includes the date last voted for each registered voter in the state of Georgia.

By law, voter registration lists are available to the public and contain the following information: voter name, residential address, mailing address if different, race, gender, registration date and last voting date. The Statewide Voter List does not include telephone numbers, date of birth, Social Security number or Drivers License number. The Statewide Voter List includes Active and Inactive Voters.

Normal production time is 1-2 weeks upon receipt of order. The Statewide Voter List file will be provided to you electronically.

The pricing is set by the Secretary of State office. This data may not be used by any person for commercial purposes. O.C.G.A. § 21-2-225 ( c )

In accordance with O.C.G.A. § 21-2-601, any person who uses the list of electors provided for in O.C.G.A. § 21-2-225 for commercial purposes shall be guilty of a misdemeanor.

Acknowledgements

We would like to thank Steve Tingley-Hock in general for his years of work on behalf of voters and specifically for sharing this data. You can learn more about his work at the following links,

• (VICE) This Man Exposed 40K Voters Purged by Mistake
• (Wired) One IT Guy's Spreadsheet-Fueled Race to Restore Voting Rights
• (New York Times) Ohio Was Set to Purge 235,000 Voters. It Was Wrong About 20%

U.S. Census BlocksThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Census Bureau (USCB), displays Census Blocks in the United States. A brief description of Census Blocks, per USCB, is that "Census blocks are statistical areas bounded by visible features such as roads, streams, and railroad tracks, and by nonvisible boundaries such as property lines, city, township, school district, county limits and short line-of-sight extensions of roads." Also, "the smallest level of geography you can get basic demographic data for, such as total population by age, sex, and race."Census Block 1007Data currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Census Blocks) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 69 (Series Information for 2020 Census Block State-based TIGER/Line Shapefiles, Current)OGC API Features Link: (U.S. Census Blocks - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: What are census blocksFor 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

Context

GeoJSON file of NYC Neighborhood boundaries maintained by Ontodia.

Content

From source:

NYC Neighborhoods polygons and correlated data with their respective Postal Codes, Assembly Districts, Community Districts, Congressional Districts, Council Districts and State Senate Districts created by Ontodia. There are hundreds of neighborhoods in New York City's five boroughs, each with unique characteristics and histories. Many historical neighborhood names are derived from the names of the previously independent villages, towns, and cities that were incorporated into into the City of New York in the consolidation of 1898. Other neighborhood names have been introduced by real estate developers and urban planners, sometimes contentiously. Boundaries of neighborhoods are notoriously fuzzy, although many boundaries are widely agreed upon. Complicating the definition of neighborhood further, boundaries may overlap, some neighborhoods may function as a micro-neighborhood within another neighborhood, or a larger district which can be made up of multiple neighborhoods. Names and boundaries of neighborhoods shift over time; they are determined by the collective conscious of the people who live, work, and play in these places. There is never an official version of neighborhoods, but the concept is deeply meaningful to many people. In many cases a New Yorker is just as proud to claim identity with a particular neighborhood, and visitors plan their trips around visits to specific neighborhoods. To display data about neighborhoods on NYCpedia we created our own neighborhood boundaries, 264 in all. In order to display a continuous map with no overlap some boundaries have been stretched or shrunk, and neighborhoods have been omitted in this version. We intend to expand our work developing neighborhood polygon files (all released with open source license) and also to collect and organize as many meaningful alternative versions of neighborhood boundaries as possible. If you are a map geek or software developer who builds apps about New York City you can find the shapefile and geoJSON of the NYCpedia neighborhoods on Data Wrangler. Drop us a line if you see any errors, or if you have suggestions for how to improve our conception of NYC geography.

Acknowledgements

Data set from: http://catalog.opendata.city/dataset/pediacities-nyc-neighborhoods