TIGER/Line: U.S. Census Geography, Roads, Boundaries, and GIS Data
TIGER/Line is a family of geographic data products maintained by the U.S. Census Bureau’s Geography Division. It provides spatial representations of U.S. states and equivalents, counties, places, census tracts, block groups, blocks, roads, address ranges, hydrography, railroads, school districts, congressional and legislative districts, American Indian and Alaska Native areas, and many other geographic entities. The files are designed primarily to support census data collection, tabulation, mapping, and statistical analysis. They are especially useful as a geographic framework for joining Census demographic data to physical locations, but they should not be treated as a parcel database, legal boundary survey, authoritative routing network, or complete inventory of every feature on the ground.
For GIS users, TIGER/Line is one of the most important U.S. geographic reference datasets. It supplies the shapes, lines, codes, names, and relationship files needed to work with Census geographies and selected physical features across the United States, Puerto Rico, and the Island Areas. The dataset is broad rather than narrowly specialized: one project may use TIGER/Line roads, another census tracts or blocks, another address ranges, hydrography, school districts, or political boundaries. Its most important role is often not visual mapping alone, but providing a stable geographic key for connecting places to statistical, administrative, environmental, transportation, and location-based information.
How EDK fits
For: GIS analysts, cartographers, data engineers, researchers, planners, demographers, public-sector teams, and developers building U.S.-focused mapping or spatial-analysis workflows.
TIGER/Line is a useful example of how the physical world becomes computable through geographic reference systems. It does not attempt to model everything on Earth, and it is not a replacement for a broader world model. Instead, it provides carefully organized U.S. boundaries, road features, address ranges, hydrography, and geographic identifiers that can anchor other observations to places. In a world-model workflow, TIGER/Line can serve as a reference layer for asking which census tract, block, county, school district, or legislative area contains a building, road segment, environmental feature, public asset, or reported event. Its geographic identifiers also support aggregation and comparison: features can be counted by district, measured within a boundary, ranked by region, or compared across geography vintages. The important distinction is that TIGER/Line supplies a Census geography framework; the broader physical-world interpretation still depends on the other datasets joined to it and on the quality and date of those sources.
- •Use TIGER/Line boundaries and geographic identifiers as a reference framework for assigning physical features, infrastructure, roads, buildings, environmental observations, or public-service records to counties, places, tracts, block groups, blocks, school districts, or legislative areas.
- •Compare physical-world features across geographic vintages by measuring counts, coverage, proximity, or change within consistent Census geographies, while preserving the vintage and boundary definitions used for each calculation.
- •Combine TIGER/Line road, hydrography, and address-range layers with other location data to support map production, geographic joins, accessibility analysis, regional summaries, and place-based search.
Dataset profile
Formats
Esri Shapefile archives with .shp, .shx, .dbf, and .prj components
GeoPackage files based on the OGC GeoPackage standard
File geodatabases for selected national and state-level products
Compressed ZIP archives and FTP-distributed packages
Metadata, relationship files, technical documentation, record layouts, and geographic code references
Access methods
Census Bureau web download interface by year, layer, and geography
Census Bureau FTP archives for bulk and automated downloads
National, state, and geography-specific packages depending on the layer
Local GIS software such as QGIS or ArcGIS after extraction
Spatial databases or data-engineering pipelines after conversion and validation
Quality and limits
The Census Bureau provides no warranty for positional or attribute accuracy.
Boundaries are intended for statistical collection and tabulation, not legal land descriptions or ownership determinations.
Roads, address ranges, and hydrography are reference layers and may not satisfy operational routing, navigation, engineering, or regulatory requirements.
Different vintages may change boundaries, codes, names, and feature geometry.
The data does not include demographic measures, current imagery, comprehensive parcels, complete building inventories, or every local physical feature.
Layer completeness, precision, and update timing vary across geographic programs and feature classes.
Analysis workflows
Select a vintage and layer that match the statistical, administrative, or physical-world question.
Download the smallest appropriate geography or national package and preserve the original archive.
Read the layer-specific technical documentation, record layout, feature codes, and relationship-file instructions.
Validate the NAD83 coordinate reference system and reproject to a suitable projected CRS for distance, area, and buffer calculations.
Join Census statistical tables through geographic identifiers, checking that the statistical data uses the same geography vintage.
Use point-in-polygon, line intersection, spatial aggregation, proximity, and regional ranking to connect physical features to Census geographies.
For longitudinal analysis, document geography changes and use crosswalks or standardized geography methods where appropriate.
For routing or address validation, combine TIGER/Line with specialized network, access, address, parcel, or operational data rather than relying on it alone.
Store vintage, source URL, download date, file name, CRS, processing steps, and any geometry repairs in the analysis record.
Value inside EDK
What TIGER/Line contains
TIGER/Line refers to a collection of geographic layers derived from the Census Bureau’s Master Address File/Topologically Integrated Geographic Encoding and Referencing system. The exact contents vary by vintage and file family, but the ecosystem covers both statistical geography and selected physical features.
Common layers include states and equivalents, counties and equivalents, county subdivisions, places, census designated places, census tracts, block groups, census blocks, public-use microdata areas, ZIP Code Tabulation Areas, metropolitan and micropolitan statistical areas, school districts, congressional districts, state legislative districts, American Indian and Alaska Native areas, roads, address ranges, rails, linear hydrography, and areal hydrography. The official technical documentation defines the feature classes, record layouts, geographic codes, relationship files, and MAF/TIGER Feature Class Codes used to interpret them. (census.gov)
- •Statistical and administrative boundaries
- •Census blocks, block groups, tracts, places, counties, and states
- •Road centerlines, address ranges, rails, and hydrography
- •School, congressional, legislative, tribal, and other special-purpose geographies
- •Geographic identifiers, feature codes, names, metadata, and relationship files
Geography, vintages, and update cadence
TIGER/Line is primarily a U.S. geographic dataset, including Puerto Rico and the Island Areas represented in Census geography products. It is published by vintage rather than as one continuously edited live map. The vintage determines which boundaries, codes, names, road features, and other records are present, so analysts should record the year alongside every download and derived result.
The latest traditional TIGER/Line Shapefile release identified on the Census Bureau’s official time-series page is the 2025 vintage. It was released on September 23, 2025, and its legal boundaries and names are generally as of January 1, 2025. The Census Bureau also publishes separate TIGER/Line GeoPackages and geodatabases, including 2026 products. These newer formats should not be casually treated as identical to the 2025 shapefile release: format, layer availability, vintage, and update scope can differ. (census.gov)
- •Use the vintage that matches the statistical or administrative data being analyzed.
- •Do not assume a 2025 boundary is interchangeable with a 2020 Census boundary.
- •Preserve download dates, file names, technical documentation, and any relationship files.
- •Check whether a layer is current, historical, legal, statistical, or specially defined for a particular program.
Formats, access methods, and licensing
Traditional TIGER/Line Shapefiles have been the standard distribution format since 2007. A typical download is a compressed archive containing shapefile components such as .shp, .shx, .dbf, and .prj, along with metadata or related documentation. The Census Bureau provides a web interface for selecting a year, layer, and geographic area, as well as FTP-based access for larger or more systematic downloads. (census.gov)
The Census Bureau now also distributes TIGER/Line GeoPackages and geodatabases. GeoPackages follow the Open Geospatial Consortium GeoPackage standard and can package multiple related layers in a single SQLite-based file. The 2026 GeoPackage catalog includes national products for address ranges, areal and linear hydrography, census blocks, legislative areas, rails, roads, school districts, and other geography groups. National files can be large; for example, the official page lists a 4.5 GB compressed national roads GeoPackage and a 4.9 GB compressed census blocks GeoPackage for 2026. (census.gov)
- •Shapefile archives for broad GIS compatibility
- •GeoPackage and geodatabase distributions for grouped or larger workflows
- •Web interface and FTP access from the Census Bureau
- •NAD83 geographic coordinates in Census-generated shapefiles
- •Government-produced data with citation, disclaimer, and trademark considerations
Suitable GIS and spatial-analysis workflows
TIGER/Line works well as a geographic framework for U.S.-focused analysis. A common workflow begins by selecting the correct vintage and layer, downloading only the geographic areas required, inspecting the technical documentation, and loading the data into a GIS or spatial database. The analyst then validates the coordinate reference system, checks geometry validity, confirms geographic identifiers, and joins the layer to demographic, environmental, infrastructure, service, or business records.
For Census analysis, the main operation is often a key-based join. A tract, block group, place, or county layer can be joined to tabular statistics using the relevant geographic code. For physical-world analysis, the same boundary can be used for point-in-polygon assignment, line or polygon intersection, zonal aggregation, proximity calculations, and regional ranking. Roads and address ranges can support address-oriented mapping and network context, but routing and travel-time analysis generally require additional topology, turn restrictions, access rules, traffic data, and network-quality controls.
- •Download and preserve the exact vintage and source archive.
- •Read the layer-specific technical documentation and record layout.
- •Validate CRS, geometry, identifiers, and relationship files before joining.
- •Use projected coordinates for measurements and buffering.
- •Separate geographic assignment from demographic, physical, legal, or operational interpretation.
- •Retain source provenance when converting to databases or cloud-native formats.
Limitations, interpretation, and tradeoffs
The Census Bureau explicitly states that TIGER/Line boundaries and features are intended for statistical data collection and tabulation. They are not legal land descriptions, ownership determinations, or definitive evidence of jurisdictional authority. The Bureau also provides no warranty regarding positional or attribute accuracy. (www2.census.gov)
TIGER/Line is broad but not universal. It does not provide a complete parcel fabric, detailed building inventory, comprehensive point-of-interest catalog, authoritative traffic network, current imagery, or all local infrastructure. Road centerlines and address ranges can be valuable for reference and Census operations without being sufficient for turn-by-turn routing, driveway access, curb-level navigation, or emergency response.
- •Not a legal survey or ownership dataset
- •Not guaranteed to be positionally or attribute-accurate for every local use
- •Not a complete address, parcel, building, POI, or routing database
- •Different vintages may contain materially different geography
- •Layer semantics and update timing vary across feature classes
Questions teams ask
Does TIGER/Line include Census population and demographic data?
No. Core TIGER/Line files provide geographic features, names, codes, and boundaries. Those identifiers can be linked to demographic and socioeconomic data distributed separately by the Census Bureau, including through data.census.gov. (census.gov)
What is the latest TIGER/Line release?
As of September 9, 2026, the Census Bureau’s traditional TIGER/Line Shapefile page identifies 2025 as the latest shapefile vintage, released September 23, 2025. The Bureau separately publishes 2026 TIGER/Line GeoPackages and geodatabases, so users should specify both the format and vintage when documenting a source. (census.gov)
Can TIGER/Line be used for routing?
It can provide useful road and address-range context, but it should not automatically be treated as a complete routing graph. Routing normally requires additional network topology, turn restrictions, access rules, travel speeds, barriers, and current operational data. Whether a TIGER/Line road layer is adequate depends on the intended accuracy and application.
Is TIGER/Line authoritative for property boundaries?
No. The Census Bureau states that TIGER/Line boundary information is for statistical collection and tabulation and does not constitute a legal land description, determination of jurisdictional authority, ownership, or entitlement. (www2.census.gov)
Which format should I use: Shapefile, GeoPackage, or geodatabase?
Use Shapefile when maximum legacy GIS compatibility matters, GeoPackage when you want a standards-based container that can hold multiple related layers, and geodatabase when your existing workflow depends on that format. For large-scale processing, convert after download into the spatial database or columnar format best suited to your analysis, while preserving the original files and documentation.
Keep exploring
nhgis
NHGIS supplies historical U.S. Census and survey statistics that can be joined to TIGER/Line geographic boundaries for time-aware demographic and socioeconomic analysis.
openstreetmap planet
OpenStreetMap Planet provides a broader, community-maintained map of roads, buildings, amenities, and other physical features that can complement TIGER/Line’s Census geography and reference layers.
Sources
U.S. Census Bureau: TIGER/Line Shapefiles
Official download page, release vintage, formats, geographic coverage, and relationship to Census demographic data.
Open sourceU.S. Census Bureau: TIGER/Line Shapefiles and TIGER/Line Files Technical Documentation
Official technical documentation covering feature classes, record layouts, geographic codes, file conventions, and user guidance.
Open sourceU.S. Census Bureau: TIGER/Line GeoPackages
Official documentation and download catalog for 2026 GeoPackage products, including roads, hydrography, blocks, legislative areas, and other layers.
Open sourceU.S. Census Bureau: 2025 TIGER/Line Shapefile Technical Documentation, Chapter 1
Official legal disclaimer, citation guidance, government-work statement, and restrictions concerning interpretation and repackaging.
Open sourceU.S. Census Bureau: 2025 TIGER/Line Shapefile Technical Documentation, Chapter 3
Official information on 2025 file contents, geographic changes, layer updates, and vintage interpretation.
Open source