TIGER/Line Download and Formats: U.S. Census Geography Data for GIS

TIGER/Line is the U.S. Census Bureau’s family of geographic data products derived from the Master Address File/Topologically Integrated Geographic Encoding and Referencing system. The download ecosystem includes annual Shapefiles, GeoPackages, and geodatabases covering census boundaries, governmental areas, roads, address ranges, hydrography, railroads, school districts, congressional districts, and many other geographic features. This guide explains what the files contain, how their vintages work, which formats are available, how to access them, and where they fit in defensible GIS and location-data workflows.

TIGER/Line is one of the most important reference datasets in the U.S. geospatial ecosystem because it provides a consistent geographic framework for Census statistics, mapping, spatial joins, and analysis. It is not one layer or one download. It is a collection of annual and specialized products, with different geographic themes, file formats, vintages, and update schedules. The correct workflow is to identify the geography and vintage you need, download the matching files and documentation, preserve the source identifiers, and validate whether the result is suitable for your intended map or computation.

How EDK fits

For: GIS analysts, cartographers, researchers, developers, data journalists, planners, demographers, and location-data teams working with U.S. geographic boundaries and Census-related spatial data.

TIGER/Line is a useful example of how the physical world becomes computable through geographic reference systems. Its boundaries, roads, address ranges, and geographic identifiers provide a structured way to locate and relate places across the United States. When combined with demographic tables, imagery, environmental layers, roads, buildings, service records, or other physical-world data, TIGER/Line can act as a geographic indexing framework: features can be assigned to counties, tracts, places, school districts, states, or other areas; regions can be compared; distances and overlaps can be calculated; and observations can be aggregated into consistent geographic units. E2’s world-model perspective is broader than TIGER/Line alone. TIGER/Line supplies selected Census geographies and reference features, while a world model can connect those geographies to the wider set of roads, buildings, infrastructure, natural systems, public assets, imagery, and other location-based evidence needed to understand and compute about places.

  • •Use TIGER/Line geographic identifiers and polygons as a reference framework for assigning physical features, service events, roads, buildings, or environmental observations to Census areas and comparing results across cities, counties, tracts, or states.
  • •Combine TIGER/Line boundaries and road or address-range layers with broader physical-world data to measure proximity, aggregate features by geography, detect geographic change, and analyze how mapped conditions vary from one region to another.
Maintainer
U.S. Census Bureau, Geography Division.
Geographic scope
United States, Puerto Rico, and other U.S. territories and areas covered by the selected TIGER/Line product.
Current Shapefile vintage identified by the Census Bureau
2025; released September 23, 2025, with legal boundaries and names generally as of January 1, 2025.
Other current formats
GeoPackage and geodatabase products are available for selected 2024–2026 layers; availability is product-specific.
Primary delivery methods
Census web interface, FTP archive, direct web or FTP access, and Data.gov links.
Demographic data included?
No. Core TIGER/Line files provide geographic features and identifiers that can be linked to Census statistical data.

Dataset profile

license
The Census Bureau offers TIGER/Line files to the public free of charge. Census Bureau trademark and repackaging notices apply, and users should consult the current official documentation for the applicable legal language.
geography
United States, Puerto Rico, and other covered U.S. territories and areas, depending on the selected TIGER/Line layer.
resolution
Feature and geographic-unit resolution varies by layer, from national, state, county, and district boundaries to census blocks, roads, address ranges, hydrography, railroads, and other reference features.
update cadence
Many products are annual, but update schedules and reference dates vary by layer. Specialized district, redistricting, and statistical products may follow separate release cycles.
temporal coverage
Annual and product-specific vintages, with historical files available from 1992 onward for many Shapefile themes. Current releases are product-specific; the 2025 Shapefiles and selected 2026 GeoPackage and geodatabase products are available as of September 9, 2026.

Formats

ESRI Shapefile for modern releases from 2007 onward.

TIGER/Line ASCII format for 2006 and earlier releases; Census 2000 is available in both ASCII and Shapefile forms.

OGC GeoPackage for selected recent national and state-based products.

TIGER/Line geodatabases for selected national and state-based products intended for ArcGIS workflows.

Compressed ZIP archives containing data files, metadata, and related documentation or relationship files.

Access methods

Census Bureau web download interface.

Census FTP archive and direct FTP access.

Direct web access to downloadable archives.

Data.gov links to TIGER/Line products as they become available.

Local GIS or programmatic processing after downloading and extracting the official archives.

Quality and limits

The Census Bureau provides no warranty for positional or attribute accuracy.

Boundary depictions are intended for statistical data collection and tabulation, not legal land descriptions or jurisdictional determinations.

Accuracy, completeness, field structure, and update timing vary by layer, feature type, source, and vintage.

The core files do not include general Census demographic tables.

TIGER/Line is not a complete current inventory of parcels, buildings, businesses, infrastructure, traffic restrictions, or all physical features on the ground.

Large national files and multi-file Shapefile packages can require substantial storage, extraction, and schema-management work.

Analysis workflows

Select the geographic question, layer, and vintage before downloading data.

Download the spatial file and matching technical documentation together.

Preserve the original archive and record the release year, reference date, source URL, and processing history.

Inspect field definitions, geographic identifiers, MTFCC values, relationship files, and metadata before analysis.

Keep FIPS and other geographic identifiers as strings so leading zeros are not lost.

Join Census statistical tables to TIGER/Line polygons using the appropriate vintage and geographic identifier.

Use spatial joins, overlays, area summaries, proximity calculations, and regional aggregation to connect physical-world observations to Census geographies.

Combine TIGER/Line with roads, buildings, imagery, environmental data, public assets, or local authoritative sources when the analysis requires more detailed or current physical-world coverage.

Validate results against authoritative local or specialized sources when accuracy, legal status, routing, property, or current operational conditions matter.

Value inside EDK

What TIGER/Line contains

TIGER/Line products are spatial extracts from the Census Bureau’s Master Address File/Topologically Integrated Geographic Encoding and Referencing system. Depending on the layer and vintage, they represent states and equivalents, counties, county subdivisions, places, census tracts, block groups, blocks, voting districts, school districts, congressional and state legislative districts, American Indian and Alaska Native areas, public-use microdata areas, urban areas, ZIP Code Tabulation Areas, roads, address ranges, hydrography, railroads, landmarks, and other geographic entities. (census.gov)

The core files do not include Census demographic tables. Instead, they provide geographic entity codes and attributes that can be joined to demographic and socioeconomic data published through Census systems such as data.census.gov. That separation is important: the boundary file supplies the spatial framework, while the statistical table supplies the measurements. (census.gov)

  • •Boundary and statistical geographies for joining Census data to places.
  • •Road, address-range, hydrography, railroad, landmark, and transportation-related reference features.
  • •Geographic codes, names, area measurements, internal points, functional status fields, and MAF/TIGER Feature Class Codes where applicable.
  • •Specialized district and redistricting products whose dates and boundary vintages may differ from ordinary annual layers.

Geography, vintages, and update cadence

TIGER/Line is primarily an annual-vintage ecosystem, but the release schedule is product-specific. The official Shapefile page identifies the 2025 TIGER/Line Shapefiles as the current Shapefile vintage listed by the Census Bureau, released on September 23, 2025. Those files use legal boundaries and names as of January 1, 2025. (census.gov)

As of September 9, 2026, the Census Bureau also publishes 2026 GeoPackage and geodatabase products for selected layers. The 2026 materials include, among other products, address-range national files and district-related layers. This does not mean that every TIGER/Line theme has a 2026 replacement. Analysts should select the newest vintage available for the exact layer they need and record the vintage in project metadata. (census.gov)

  • •Use the same vintage when joining geography to statistics designed for that vintage.
  • •Record both the file release year and the legal or statistical reference date.
  • •Treat congressional, legislative, school-district, and other specialized products as having their own temporal rules.
  • •Use boundary-change notes, county-change files, and technical documentation when comparing years.

Formats, downloads, and access methods

For most modern TIGER/Line downloads, the traditional format is the ESRI Shapefile. The Census Bureau lists Shapefile as the standard format from 2007 onward, while TIGER/Line ASCII is associated with 2006 and earlier releases; Census 2000 is available in both formats. A Shapefile download is normally a ZIP archive containing multiple companion files, such as geometry, attributes, projection information, and metadata. (census.gov)

The Census Bureau also publishes TIGER/Line GeoPackages based on the Open Geospatial Consortium GeoPackage standard. GeoPackage is often easier to move as a single SQLite-based spatial file and can be more convenient for QGIS, Python, R, desktop GIS, and reproducible project packaging. Current official GeoPackage downloads include national and state-based products, but availability varies by layer and year. (census.gov)

  • •Shapefile: broad compatibility with GIS software and many legacy workflows.
  • •GeoPackage: single-file delivery, useful for modern desktop and programmatic GIS workflows.
  • •Geodatabase: suitable for ArcGIS-centered environments and feature-class workflows.
  • •ZIP archives: common delivery container for the downloadable products.
  • •Technical documentation and metadata: necessary for interpreting fields, codes, relationships, and vintages.

Suitable GIS and spatial-analysis workflows

A reliable TIGER/Line workflow begins with a geographic question, not a file format. Decide whether the analysis needs a legal or statistical boundary, a road centerline, an address-range layer, a district, or another feature class. Then choose the matching vintage and download the official data and documentation together.

For demographic mapping, join Census tables to TIGER/Line polygons using the published geographic identifiers. For regional analysis, calculate areas, centroids, intersections, containment, and adjacency only after checking the coordinate reference system and the intended geographic unit. For physical-world analysis, use TIGER/Line as a framework for assigning roads, buildings, imagery observations, environmental measurements, incidents, permits, or public assets to Census geographies.

  • •Demographic and socioeconomic mapping by tract, county, place, block group, or other Census geography.
  • •Spatial joins that assign physical features or observations to standardized U.S. geographic units.
  • •Boundary overlays, area summaries, proximity analysis, regional comparisons, and change tracking.
  • •Road, address-range, hydrography, railroad, and district reference mapping.
  • •Reproducible data pipelines that preserve source archives, identifiers, documentation, and vintage information.

Limitations, interpretation, and tradeoffs

The Census Bureau’s technical documentation states that no warranty is made regarding positional or attribute accuracy and that boundary information is intended for statistical data collection and tabulation. TIGER/Line boundaries are therefore not legal land descriptions and should not be used as a substitute for a survey, parcel fabric, title record, or authoritative jurisdictional determination. (www2.census.gov)

Spatial accuracy and completeness vary by feature type and source. The technical documentation notes that accuracy information attached to selected line features does not describe the accuracy of every line in the entire layer. Roads, address ranges, boundaries, hydrography, and other features can have different positional histories and update behavior. (www2.census.gov)

  • •Strong for Census geography, identifiers, statistical joins, and broad reference mapping.
  • •Not authoritative for property rights, legal boundary disputes, parcel ownership, or survey-grade positioning.
  • •Not guaranteed to contain every physical feature or the most current local road and address condition.
  • •Different layers and vintages can have different schemas, accuracy characteristics, and update dates.
  • •Some large downloads and multi-file Shapefile workflows require more data management than cloud-native formats.

Questions teams ask

What is the difference between TIGER/Line Shapefiles, GeoPackages, and geodatabases?

They are different delivery formats for spatial extracts from the Census Bureau’s MAF/TIGER system. Shapefiles are broadly compatible and common in legacy GIS workflows; GeoPackages package spatial layers in a single OGC-standard file; and geodatabases are designed for ArcGIS-oriented workflows. The exact layers available depend on the year and product.

Does TIGER/Line include Census population and demographic data?

The core TIGER/Line files do not include demographic tables. They contain geographic features and identifiers that can be joined to demographic and socioeconomic data from Census statistical products. Some specialized 2020 Census products may include selected population or housing fields, so inspect the specific record layout before assuming the schema.

How often is TIGER/Line updated?

Many TIGER/Line products are released in annual vintages, but not every layer is updated or replaced every year. Specialized products may follow different schedules and reference dates. For example, the 2025 Shapefiles were released on September 23, 2025, while selected GeoPackage and geodatabase layers have 2026 releases. Always check the official page for the exact layer and vintage.

Can TIGER/Line be used for parcel mapping or legal boundary decisions?

No. The Census Bureau states that TIGER/Line boundaries are intended for statistical collection and tabulation and are not legal land descriptions. Use authoritative cadastral, surveying, title, or jurisdictional sources for legal or property-related decisions.

Which TIGER/Line format should a GIS analyst choose?

Choose based on the software and workflow. Shapefile is a practical compatibility choice; GeoPackage is convenient for single-file desktop and programmatic workflows; and geodatabase is appropriate for ArcGIS-centered projects. Regardless of format, the geographic layer, vintage, identifiers, and documentation matter more than the container.

Keep exploring

Sources

More in Datasets