1980 Block Boundaries

NHGIS 1980 census block shapefiles depict 1980 block boundaries for selected areas throughout the U.S. The current version (v4.0) includes all or part of 148 metropolitan areas. We will update and extend the shapefiles in future releases as we complete more areas.

These files provide a more accurate and complete representation of 1980 block boundaries than is available from the U.S. Census Bureau's 1992 TIGER/Line Files, the only previously existing source of digital 1980 block definitions for the nation.

We currently provide the boundary files through this web page along with documentation and census summary statistics for 1980 blocks. In the future, we will provide both the boundary files and summary tables through the NHGIS Data Finder, where we already provide block summary data for 1970 and both summary and boundary data for all census years after 1980.


The U.S. Census Bureau's 1992 TIGER/Line Files include both 1990 and 1980 census block boundaries, but the 1980 blocks are badly incomplete and often inaccurate. Of the 2.5 million blocks that appear in the 1980 census summary tables, about 765,000 do not appear in the 1992 TIGER/Line Files, and there are missing cases in nearly every county where block data were provided.

Using the 1980 paper census block maps as a guide, NHGIS staff are manually editing data from the 1992 TIGER/Line Files to recover as many missing blocks as possible. The Census Bureau published the paper maps separately by Standard Metropolitan Statistical Area (SMSA), so NHGIS editing work is also organized by SMSA.

Initial versions of our 1980 block shapefiles will cover only the SMSAs that we have completed. We plan to release more versions including more SMSAs at regular intervals until the project has ended.

NHGIS validates the edited geographic block data against the statistical block data from 1980 Summary Tape File 1 (STF1). For a small portion of the blocks that appear in STF1, we are unable to find corresponding blocks on the paper maps or in the TIGER/Line data, so we cannot provide complete block definitions for all reported statistics. Our validation process produces summaries of the discrepancies between the edited boundary data and statistical data. We supply these summaries for user reference along with the shapefiles.

We also provide separate files of block-level summary tables derived from the 1980 STF1 dataset. This is important because the original STF1 includes data only for block parts and not for the whole collection blocks that the boundary files depict.

Back to top

Technical Details


  • The boundary data are stored in shapefiles within ZIP archives
  • There is a separate shapefile for each state (or state equivalent) where boundaries are currently available
  • There is a nationwide shapefile that includes all block boundaries available at this time
  • Two supplemental CSV (comma-separated-values) files accompany each shapefile within the ZIP archives
    • data_missing_polygon - Lists blocks that have records in the statistical tables but do not have polygons in the shapefile
    • polygon_missing_data - Lists blocks that have polygons in the shapefile but do not have records in the statistical tables
  • The statistical and boundary files include standard NHGIS GISJOIN identifiers
  • The statistical table data are stored in a CSV file within a ZIP archive
  • There are two nationwide CSV files
    • One includes all tables
    • One includes a collection of popular tables
  • There is a CSV file for each state (or state equivalent) with boundaries currently available
  • All ZIP archives include human-readable codebooks describing the contents of the data files

Back to top

Geographic Coverage

We plan to produce 1980 block shapefiles for all of the Standard Metropolitan Statistical Area (SMSAs) that are covered (imperfectly) in the 1992 TIGER/Line Files. In 1980, the Census Bureau's block data program covered only urbanized areas and large incorporated places (those with 10,000 or more residents based on pre-1980 sources). State and local agencies also contracted with the Bureau to obtain block data for many additional areas, but the 1992 TIGER/Line Files provide very limited information for the blocks in these areas, so we do not expect to complete those.

The 1980 block shapefiles are organized by state for consistency with NHGIS block boundary files for later years. A given state's shapefile includes blocks only for counties that NHGIS has completed within that state. To obtain all block boundaries for an SMSA that crosses state boundaries, a user will need to combine block files from each corresponding state.

Future versions of the shapefiles will extend coverage within currently included states and add new files for other states. Our work was initially limited to a small set of SMSAs for which we could obtain block maps. We later found lending sources for nearly all SMSAs and have since then prioritized the largest SMSAs.

Some SMSAs do not have complete coverage in our shapefiles. In some SMSAs (e.g. Detroit), our block boundaries cover the central city, but we have not yet completed one or more suburban counties that have no blocks in the 1992 TIGER/Line files.

We detail current coverage by state and by SMSA in this spreadsheet:

Click below for a list of currently covered SMSAs ordered by population:

Covered Metro Areas by Population

RankStandard Metropolitan Statistical AreaPopulation
1.New York, N.Y.-N.J.9,120,346
2.Los Angeles-Long Beach, Calif.7,477,503
3.Chicago, Ill.7,103,624
4.Philadelphia, Pa.-N.J.4,716,818
5.Detroit, Mich. *4,353,413
6.San Francisco-Oakland, Calif.3,250,630
7.Washington, D.C.-Md.-Va.3,060,922
8.Dallas-Fort Worth, Tex.2,974,805
9.Houston, Tex.2,905,353
10.Boston, Mass.2,763,357
11.Nassau-Suffolk, N.Y.2,605,813
12.St. Louis, Mo.-Ill.2,356,460
13.Pittsburgh, Pa.2,263,894
14.Baltimore, Md.2,174,023
15.Minneapolis-St. Paul, Minn.-Wis.2,113,533
16.Atlanta, Ga.2,029,710
17.Newark, N.J.1,965,969
18.Anaheim-Santa Ana-Garden Grove, Calif.1,932,709
19.Cleveland, Ohio1,898,825
20.San Diego, Calif.1,861,846
22.Denver-Boulder, Colo.1,620,902
23.Seattle-Everett, Wash.1,607,469
24.Tampa-St. Petersburg, Fla. *1,569,134
26.Phoenix, Ariz.1,509,052
27.Cincinnati, Ohio-Ky.-Ind.1,401,491
28.Milwaukee, Wis.1,397,143
29.Kansas City, Mo.-Kans.1,327,106
30.San Jose, Calif.1,295,071
33.New Orleans, La. *1,187,073
34.Indianapolis, Ind.1,166,575
35.Columbus, Ohio *1,093,316
37.Fort Lauderdale-Hollywood, Fla.1,018,200
38.Sacramento, Calif.1,014,002
39.Rochester, N.Y. *971,230
40.Salt Lake City-Ogden, Utah *936,255
41.Providence-Warwick-Pawtucket, R.I.-Mass.919,216
42.Memphis, Tenn.-Ark.-Miss.913,472
43.Louisville, Ky.-Ind.906,152
44.Nashville-Davidson, Tenn.850,505
45.Birmingham, Ala.847,487
46.Oklahoma City, Okla. *834,088
47.Dayton, Ohio *830,070
51.Toledo, Ohio-Mich.791,599
52.Honolulu, Hawaii762,565
53.Jacksonville, Fla.737,541
54.Hartford, Conn.726,114
55.Orlando, Fla. *700,055
59.Gary-Hammond-East Chicago, Ind.642,781
64.Grand Rapids, Mich.601,680
65.New Brunswick-Perth Amboy-Sayreville, N.J.595,893
67.Omaha, Nebr.-Iowa569,614
68.Greenville-Spartanburg, S.C.569,066
69.Jersey City, N.J.556,972
70.Austin, Tex.536,688
71.Tucson, Ariz.531,443
74.Springfield-Chicopee-Holyoke, Mass.-Conn.530,668
76.Wilmington, Del.-N.J.-Md.523,221
77.Flint, Mich.521,589
78.Fresno, Calif.514,621
80.Baton Rouge, La.494,151
81.Tacoma, Wash.485,643
82.El Paso, Tex.479,899
85.Las Vegas, Nev.463,087
87.Paterson-Clifton-Passaic, N.J.447,585
93.New Haven-West Haven, Conn.417,592
98.Bridgeport, Conn.395,455
99.Little Rock-North Little Rock, Ark.393,774
105.Worcester, Mass.372,940
114.Corpus Christi, Tex.326,228
115.Madison, Wis.323,545
125.Trenton, N.J.307,863
127.Santa Rosa, Calif.299,681
130.Salinas-Seaside-Monterey, Calif.290,444
133.Lawrence-Haverhill, Mass.-N.H.281,981
136.Rockford, Ill.279,514
137.Kalamazoo-Portage, Mich.279,192
138.Eugene-Springfield, Oreg.275,226
143.Duluth-Superior, Minn.-Wis.266,650
144.Modesto, Calif.265,900
149.Daytona Beach, Fla.258,762
152.New London-Norwich, Conn.-R.I.248,554
156.Columbus, Ga.-Ala.239,196
157.Lowell, Mass.-N.H.233,410
159.Waterbury, Conn.228,178
160.Saginaw, Mich.228,059
163.Provo-Orem, Utah218,106
164.Killeen-Temple, Tex.214,656
166.Brownsville-Harlingen-San Benito, Tex.209,727
170.Sarasota, Fla.202,251
171.Stamford, Conn.198,854
174.Reno, Nev.193,623
175.Lincoln, Nebr.192,884
183.Springfield, Ohio183,885
184.Portland, Maine183,625
185.Muskegon-Norton Shores-Muskegon Heights, Mich.179,591
188.Fall River, Mass.-R.I.176,831
189.Terre Haute, Ind.176,583
190.Green Bay, Wis.175,280
194.Boise City, Idaho173,036
199.New Bedford, Mass.169,425
200.Brockton, Mass.169,374
202.Lake Charles, La.167,223
203.Portsmouth-Dover-Rochester, N.H.-Maine163,880
204.St. Cloud, Minn.163,256
207.Manchester, N.H.160,767
210.Alexandria, La.151,985
211.Longview-Marshall, Tex.151,752
212.Jackson, Mich.151,495
215.Lafayette, La.150,017
219.Danbury, Conn.146,405
222.New Britain, Conn.142,241
228.Waterloo-Cedar Falls, Iowa137,961
229.Fargo-Moorhead, N. Dak.-Minn.137,574
231.Elkhart, Ind.137,330
232.Altoona, Pa.136,621
234.Anderson, S.C.133,235
237.Decatur, Ill.131,375
240.Wichita Falls, Tex.130,664
248.Texarkana, Tex.-Texarkana, Ark.127,019
249.Norwalk, Conn.126,692
253.Kenosha, Wis.123,137
255.Lafayette-West Lafayette, Ind.121,702
259.Bloomington-Normal, Ill.119,149
261.Pascagoula-Moss Point, Miss.118,015
262.Sioux City, Iowa-Nebr.117,457
264.Odessa, Tex.115,374
265.Nashua, N.H.114,221
266.Burlington, Vt.114,070
278.Sioux Falls, S. Dak.109,435
281.Rock Hill, S.C.106,720
283.Kokomo, Ind.103,715
288.Grand Forks, N. Dak.-Minn.100,944
291.Fitchburg-Leominster, Mass.99,957
294.Bloomington, Ind.98,785
299.Bryan-College Station, Tex.93,588
300.Rochester, Minn.92,006
301.La Crosse, Wis.91,056
303.Pittsfield, Mass.90,505
304.Sherman-Denison, Tex.89,796
306.San Angelo, Tex.84,784
307.Bangor, Maine83,919
308.Midland, Tex.82,636
309.Iowa City, Iowa81,717
310.Great Falls, Mont.80,696
311.Bismarck, N. Dak.79,988
312.Bristol, Conn.73,762
313.Lewiston-Auburn, Maine72,378
318.Meriden, Conn.57,118

* Partial coverage—one or more peripheral counties unavailable

Back to top

Data for Whole Collection Blocks, Not Tabulation Blocks

The Census Bureau defines two types of census blocks: collection blocks and tabulation blocks. As implied by these names, the Census Bureau generally tabulates and publishes data only for tabulation blocks, not collection blocks. The collection blocks are defined first, before census operations, and their boundaries mainly follow observable physical features like roads, railroads, streams, shorelines, etc. Most tabulation blocks match collection blocks, but tabulation blocks can include additional subdivisions wherever collection blocks are split by higher-level reporting areas, such as incorporated places and minor civil divisions (MCDs). As explained in the Census Bureau's Geographic Areas Reference Manual (p. 11-14), "This methodology permits the Census Bureau to accommodate changes to the boundaries of legally recognized entities as they occur and still maintain a stable inventory of collection blocks."

In 1980 block data and on 1980 block maps, the block identifiers correspond only to collection blocks and do not distinguish the parts of collection blocks (i.e., the tabulation blocks) that lie in different places or MCDs. The Census Bureau revised this practice in 1990, adding suffixes to tabulation block codes to distinguish each part of a split collection block. As a result, every census reporting area at every census summary level now corresponds exactly to a set of uniquely identified tabulation blocks, but that is not the case in 1980 data.

Example of a Block Split by a Place Boundary with Summary Data for the Split Block Parts and the Corresponding Whole Block

Figure 1. Two STF1 block data records have the same tract and block identifiers but unique place identifiers. We generate new data for the whole collection block with a population equal to the sum of the two split parts' populations.

In the original block-level statistical data in 1980 STF1, there are separate records for each part of a split collection block, each with unique statistics, but without a unique tabulation block identifier. A user must examine the place or MCD codes to determine which part of the collection block each record corresponds to. Unfortunately, there are discrepancies between the place and MCD identifiers in the statistical data and the place and MCD boundaries in TIGER/Line Files and on the paper maps, preventing us from exactly matching the block boundary data to the original tabulation blocks.

To resolve these discrepancies, NHGIS provides boundary data for whole 1980 collection blocks only, and we derive new statistical data for the whole blocks.

The statistical data files include all collection blocks identified in 1980 STF1, including areas not yet covered in the NHGIS boundary files. Out of the 2.5 million blocks identified in 1980 STF1, only about 61,000 are split by place or MCD boundaries. Of these blocks, only 35,000 (those that had non-zero counts for two or more of their parts) required data aggregation.

We derived new data for all tables in the NHGIS dataset "1980 Census: STF1 - 100% Data". That dataset currently provides block data at two geographic levels, which separately cover states with strong MCDs and those without:

  • MCD States: State--Standard Metropolitan Statistical Area--County--County Subdivision--Place--Census Tract--Block
  • Non-MCD States: State--Standard Metropolitan Statistical Area--County--Place--Census Tract--Block

To aggregate the data, we first sum the counts for all records that share the same codes for state--county--census tract--block. Then for tables that report median values rather than counts, where aggregation is necessary, we use the same method that the the Census Bureau used, interpolating median estimates from the associated binned count data. For instance, to interpolate an estimate for median age, we use the aggregated counts of persons age 0-4, 5-9, and so on. We provide complete details on this methodology in the codebooks that accompany the data files.

The aggregated collection block data are therefore provided at the following geographic level for all states:

  • State--County--Census Tract--Block

A more detailed explanation of the aggregation process and variable definitions is available in the codebook that accompanies the data file.

Back to top

Whole Block Suppression

Data from 1980 STF1 include suppression, whereby certain counts for blocks with few people or households were not published. When aggregating data for block parts to whole blocks, we suppress data for a given variable whenever at least one of the component block parts had suppressed data for that variable.

In our 1980 block summary statistics, suppressed values are indicated with blanks, but not all blank values are due to suppression; median values that could not be calculated are also left blank. You can use the SUPFLG fields to determine whether a value is suppressed or not. For more information about suppression, see the STF1 Technical Documentation.

Back to top

For user convenience, the tables most requested by NHGIS users are available in a separate CSV file. This file contains 16 of the 82 tables in 1980 Summary Tape File 1. A full description of these tables is available in the codebook, which is included with the data file in the download ZIP file. Click below for an overview of the tables.

 Table NameDescription
1.PersonsPopulation count
2.Urban/Rural StatusUrbanized area, outside urbanized area, and rural population counts
3.HouseholdsCount of households
4.Housing UnitsCount of housing units
5.Occupancy StatusCounts of occupied and vacant year-round housing units
6.RacePopulation count by race
7.Spanish OriginPopulation count by Spanish origin
8.Persons of Spanish OriginCount of persons of Spanish origin
9.Race [Persons of Spanish Origin]Count of persons of Spanish origin by Race
10.AgePopulation count by age
11.TenureCounts of owner-occupied and renter occupied housing units
12.Tenure by Race of HouseholderCounts of owner-occupied and renter occupied housing units by race of householder
13.ValueCounts of specified owner-occupied housing units by value
14.Median ValueMedian value of specified owner-occupied housing units
15.Contract RentCounts of specified renter occupied housing units by contract rent
16.Median Contract RentMedian contract rent for specified renter-occupied housing units paying cash rent

Back to top

Download: Boundaries

The 1980 block boundaries are available as statewide or nationwide shapefiles.

The nationwide file includes boundaries for all covered metro areas, as listed here:


1980 Census Block Boundary Data by State
ColoradoMassachusettsRhode Island
ConnecticutMichiganSouth Carolina
DelawareMinnesotaSouth Dakota
District of ColumbiaMississippiTennessee
IllinoisNew HampshireWashington
IndianaNew JerseyWisconsin
IowaNew York 
KansasNorth Dakota 

Back to top

Download: Statistics

Summary statistics for whole collection blocks, derived from 1980 STF1, are available as statewide or nationwide comma-separated values (CSV) files.

* If you run into issues unzipping a data file, we recommend using the Unarchiver tool or the command line. See this IPUMS User Forum post for additional information.

1980 Census Block Statistical Data by State
ColoradoMassachusettsRhode Island
ConnecticutMichiganSouth Carolina
DelawareMinnesotaSouth Dakota
District of ColumbiaMississippiTennessee
IllinoisNew HampshireWashington
IndianaNew JerseyWisconsin
IowaNew York 
KansasNorth Dakota 

Back to top

Feedback and Questions

You may direct any comments or questions about these files to nhgis@umn.edu.

Back to top

Citation and Use

Use of the NHGIS 1980 Block Boundary Files is subject to the same conditions as for all NHGIS data. See Citation and Use of NHGIS Data.

Back to top


Our production of 1980 Block Boundary Files is supported by funding from the Eunice Kennedy Shriver National Institute of Child Health and Human Development (NICHD) (R01HD057929).

Back to top