This study is provided by ICPSR. ICPSR provides leadership and training in data access, curation, and methods of analysis for a diverse and expanding social science research community.
103rd Congressional District Geographic Entity File, 1990: [United States] (ICPSR 6425)
These data describe the geographic relationships of the 103rd congressional districts to selected governmental and statistical geographic entities for the entire United States, American Samoa, Guam, Puerto Rico, and the Virgin Islands. Each record represents a census geographic tabulation unit (GTUB), a unique combination of geographic codes expressing specific geographic relationships. This file provides the following information: state, congressional district, county and county subdivision, place, American Indian/Alaska Native area, urbanized area, urban/rural descriptor, and Metropolitan Statistical Area/Primary Metropolitan Statistical Area (MSA/PMSA).
Data in this collection are available only to users at ICPSR member institutions. Please log in so we can determine if you are with a member institution and have access to these data files.
U.S. Dept. of Commerce, Bureau of the Census. 103RD CONGRESSIONAL DISTRICT GEOGRAPHIC ENTITY FILE, 1990: [UNITED STATES]. Washington, DC: U.S. Dept. of Commerce, Bureau of the Census [producer], 1993. Ann Arbor, MI: Inter-university Consortium for Political and Social Research [distributor], 1994. http://doi.org/10.3886/ICPSR06425.v1
Persistent URL: https://doi.org/10.3886/ICPSR06425.v1
Scope of Study
A list of all 1990 Census blocks split by a 103rd congressional district boundary and the congressional district to which they were assigned is available in Appendix A of the documentation.
equivalency files and listings submitted by the appropriate agency or official within each state, usually from the Secretary of State's Office
Original ICPSR Release: 1995-03-16
- Citations exports are provided above.
Export Study-level metadata (does not include variable-level metadata)
If you're looking for collection-level metadata rather than an individual metadata record, please visit our Metadata Records page.