If you have spent any time around redistricting software or GIS professionals, you have probably heard the term “shapefile” and possibly nodded along without knowing what it means. A shapefile is a digital file format that stores the geographic boundaries of a defined area as a map layer. Think of it as the outline of a jurisdiction, your city limits, your county boundaries, your voting precincts, your census tracts, all saved in a format that mapping software can read, display, and analyze. TIGER boundary files are shapefiles from the Census Bureau that are important for drawing legally compliant district maps. They are geospatial data, meaning they are designed to be used with Geographic Information Systems (GIS) software to create digital maps. Without them, census tables are just rows of numbers. TIGER/Line provides the boundary polygons and linear features, such as roads, railroads, and rivers, that those numbers attach to via a geographic identifier field. Every piece of census-based spatial analysis in the United States ultimately depends on TIGER/Line. In the redistricting context, a shapefile is what allows a mapping tool to show you where your district lines actually fall on the ground and whether they cross roads, rivers, or community boundaries in ways that could create legal or practical problems.
The Census Bureau is the authoritative source for redistricting shapefiles, and it provides them free of charge through its TIGER/Line program. The core TIGER/Line files and shapefiles do not include demographic data, but they contain geographic entity codes that can be linked to the Census Bureau’s demographic data available on data.census.gov. The 2025 TIGER/Line Shapefiles, reflecting all legal boundaries and names as of January 1, 2025, were released on September 23, 2025. TIGER files contain information about many different geographic features, including roads, rivers, lakes, political boundaries such as state and county lines, and census boundaries, including blocks, block groups, and census tracts. They are available to download as polygon boundary shapefiles at multiple geographies within a state. For a local official, the layers most relevant to redistricting are census blocks, which are the smallest unit, and the building blocks from which all district maps are assembled – along with county subdivisions, places, voting districts, and school district boundaries. All of these are available individually by state or county directly from the Census Bureau’s download page.
Knowing where to get shapefiles is one thing; knowing when you actually need to work with them directly is another. For most local officials overseeing or participating in a redistricting process, the answer is: probably not as often as you might think. There are several high-quality redistricting tools available for free online, including Dave’s Redistricting App, DistrictBuilder, Districtr, and the QGIS Redistricting Plugin, that handle the underlying shapefile data on the user’s behalf. Dave’s Redistricting App, in particular, requires no GIS expertise; it runs entirely in a browser, includes census block data already loaded, and allows users to draw, analyze, and share district maps without ever downloading or opening a shapefile. Full desktop GIS software, such as QGIS (free) or ArcGIS (paid) becomes necessary when you need to work with custom data layers such as your jurisdiction’s own precinct boundaries, local street files, or annexation records that are not already built into a browser-based tool, or when the scale and complexity of your redistricting project requires more analytical control than a browser app provides. As long as maps created in any of these tools are downloaded as shapefiles, they can be shared with the redistricting body for formal consideration.
One area where shapefiles reveal significant practical limitations is in day-to-day election administration, and local officials should understand this gap before assuming that a redistricting shapefile and an election administration shapefile are interchangeable. The core problem is that census geographies and local election geographies do not always match. Since precincts are not census geographies, there is no demographic or racial data that is readily available at the precinct level, and one or both datasets must be converted (via aggregation or disaggregation) to a common geography so they can be used in tandem.
Making matters more complicated, state and local precinct shapefiles are not nearly as readily available as other local election data, and where they are available, they may not be centrally accessible. The files are not produced to a uniform standard, and VTD names, the identifiers used to match census geography to local election geography, are usually reported by individual jurisdictions, often leading to significant differences in naming schemes, standardization, and data quality both between and within states. Generally, only election authorities with higher budgets maintain their precinct boundaries as shapefiles.
A frequently recurring challenge involves local municipality annexations in localities that require municipal and precinct boundaries to coincide, a detail that often surfaces only when researchers or officials detect conflicts and must contact local election officials to resolve them.
The practical takeaway for local administrators is that a redistricting shapefile, whether from the Census Bureau or drawn in a mapping tool, describes where district lines should fall, but does not automatically update your voter registration system, your precinct boundary files, or your ballot assignment logic. Those downstream administrative tasks require their own data reconciliation process and, in most jurisdictions, hands-on GIS work or vendor support to complete correctly after a new map is adopted.
Find us on:
