U.S. Bureau of the Census 1990 digital data Reston, Virginia U.S. Geological Survey http://water.usgs.gov/lookup/getspatial?cd104 This is a polygon coverage of 104th Congressional District boundaries obtained from the U.S. Bureau of the Census. The 103rd Congress was the first Congress that reflected the reapportionment and delineation of congressional districts based on the 1990 census. The next (104th) Congress reflects redelineation of districts that occurred for six states: Georgia, Louisiana, Maine, Minnesota, South Carolina, and Virginia. Congressional Districts U.S. House of Representatives Census TIGER/Line Files The intended use of the data is to depict the locations of the Congressional Districts. Knowing the locations and extents of the Congressional Districts allows us to overlay them with locations of programs and project areas of the U.S. Geological Survey. For example, the National Water-Quality Assessment (NAWQA) program obtained the Congressional District coverages to see the relation between the NAWQA study units and the Congressional Districts and to present NAWQA findings about water quality in terms of Congressional Districts. Procedures_Used: The ARC/INFO export file of 104th congressional district boundaries (cd_99.e00) was transferred from the Census Bureau's ftp site at URL ftp://ftp.census.gov/pub/outgoing/amyb/. Amy Bishton (301/457-1101; abishton@census.gov) provided the export file. The file was imported into ARC/INFO and was projected using these output parameters: PROJECTION ALBERS UNITS METERS PARAMETERS 29 30 00 45 30 00 -96 00 00 23 00 00 0.0 0.0 Polygons were built. The items ST, CD, and FULLCODE were originally character items. They were altered to be integer items. Revisions: The items in the original coverage were changed from character to integer and the coverage was re-projected to the national projection used by NAWQA, as described above. Reviews_Applied_to_Data: Related_Spatial_and_Tabular_Data_Sets: Other_References_Cited: Notes: The following is from: ftp://ftp.census.gov/pub/tiger/boundary/readme.txt TIGER Extract - Thinned Boundary Files This site contains thinned boundary files extracted from the Census Bureau's TIGER Data Base. The boundary files are in a polygon format, and are suitable for thematic mapping or other small-scale displays. BOUNDARY TYPES Boundary files exist for the following geographic entities: 1990 State (ST) 1990 County (CO) 1990 Minor Civil Division (MC) 1990 Census Tract/Block Numbering Area (TR) 1990 American Indian Reservation/Alaska Native village stat area (IR) 1990 Alaska Native Regional Corporation (AN) 1990 Urbanized Areas (UA) 1993 Metropolitan Areas (MA) 103rd Congressional District (C3) 104th Congressional District (C4) FILENAMING CONVENTION A boundary file actually consists of two ASCII files: a polygon coordinate file and a polygon attribute file. A filename incorporates an abbreviation for a boundary type (noted above) and a 2-digit State code. The 2-digit code is the FIPS State code except for the use of 99 to indicate the coterminous United States. The boundary files use a filenaming convention of: BB_SS_P.DAT for polygon coordinate files, and BB_SS_PA.DAT for polygon attribute files, where BB = boundary type abbreviation, and SS = State code. For example, ST_02_P.DAT is the state polygon coordinate file for Alaska, and C4_99_PA.DAT is the 104th Congressional District polygon attribute file for the coterminous U.S.. In addition to the boundary files, a name file is provided for most boundary types listing name by geocode (TR, C3 and C4 do not have names). The name files use the filenaming convention of: BB_NAME.DAT FILE FORMAT Polygon coordinate files follow the format: ID LON LAT LON1 LAT1 LON2 LAT2 . . . LONx LATx END ID LON LAT LON1 LAT1 LON2 LAT2 . . . LONx LATx END END where ID = a unique polygon identification number, LON/LAT = a longitude/latitude coordinate internal to the polygon, LONn/LATn = a sequence of longitude/latitude coordinate pairs defining the polygon vertices, with matching first and last vertices. An END statement indicates the termination of each polygon, and a final END statement indicates the termination of the polygon file. Islands or exclusions within a polygon are flagged with an ID number of -99999. The outer cycle of a complex polygon is listed first, followed by any islands. For example: 31 LON LAT LON1 LAT1 . . . LONx LATx END -99999 LON LAT LON1 LAT1 . . . LONx LATx END See FILE CONTENT for greater detail on longitude/latitude values. Polygon attribute files follow the format: ID CODE An entry exists for each ID in the polygon coordinate file (except ID -99999). CODE equals the polygon geocode. In some polygon attribute files, CODE equals all blanks. These entries correspond to enclaves, that is, polygons that belong to no geographic entity in the boundary network. Enclaves are provided for network completeness, but can probably be ignored by most applications. See FILE CONTENT for greater detail on geographic entities and geocodes. Name files follow the format: CODE NAME An entry exists for each CODE found in the polygon attribute file. FILE COVERAGE & ORGANIZATION In general, files for each boundary type cover the 50 States and the State equivalents of the District of Columbia, Puerto Rico, American Samoa, Guam, the Northern Mariana Islands, Palau and the Virgin Islands of the United States. TR files are organized by State; that is, each TR boundary file covers one State or State equivalent. With one exception, all other boundary files are organized as contiguous areas; that is, for each boundary type one file covers the coterminous United States, and one file each covers Alaska, Hawaii, Puerto Rico, etc. An exception exists for MC files, which only cover the New England states (Connecticut, Maine, Massachusetts, New Hampshire, Rhode Island and Vermont). Where a geographic entity is completely absent from a given area, no boundary file exists. For example, no IR file exists for Hawaii, because no American Indian reservation/Alaska Native Village statistical areas exist in that State. A summary of coverage by boundary type follows, with existence of name file noted: AK HI AS GU MP PW PR VI By Name 02 15 60 66 69 70 72 78 99 State File ST x x x x x x x x x x CO x x x x x x x x x x MC x* x TR x IR x x x AN x x UA x x x x x MA x x x x x C3 x x x x x x x x x C4 x x x x x x x x x (*) New England States only FILE CONTENT Coordinates - Longitude, latitude coordinates are expressed in decimal degree, with longitude values ranging from -180 to 180 and latitude values ranging form -90 to 90. The intersection of the Greenwich Prime Meridian and the Equator is taken as the origin. A coordinate pair is signed according to the quadrant in which it falls relative to the origin. Signs of coordinate pairs by quadrant are: Northeast + Lon + Lat Northwest - Lon + Lat Southeast + Lon - Lat Southwest - Lon - Lat Coordinate values are based on Clarke's spheriod of 1866, also referred to as the North American Datum, 1927 (NAD27). 1990 State - In addition to the 50 States, the Census Bureau treats the District of Columbia, Puerto Rico, and each of the outlying areas (American Samoa, Guam, the Northern Mariana Islands, Palau, and the Virgin Islands of the United States) as the statistical equivalent of a State for the purpose of data presentation. The State geocode consists of a 2-digit State FIPS code. 1990 County - The first order-division of each State are counties for 48 States, parishes for Louisiana, and boroughs and census areas for Alaska. In addition, the Census Bureau treats the following entities as equivalents of counties for purposes of data presentation: independent cities in Maryland, Missouri, Nevada, and Virginia; the portion of Yellowstone National Park in Montana; "District of Columbia" for the District of Columbia; municipios in Puerto Rico; and a variety of entities in the outlying areas. The 5-digit county geocode consists of a 2-digit State FIPS code and a 3-digit FIPS county code. 1990 Minor Civil Division (MCD) - MCDs are legally defined subcounty areas such as towns and townships. For some States, some incorporated places are not part of any MCD, and are treated as MCD-equivalent entities. In Maine, American Indian reservations exist outside the jurisdiction of any MCD, and are treated as MCD-equivalent entities. Portions of Maine that are not part of any MCD, incorporated place, or AIR, are designated by the Census Bureau as Unorganized Territories and are treated as MCD- equivalent entities. The 7-digit MCD geocode consists of a 2-digit FIPS State code and a 5-digit FIPS place code 1990 Census Tract/Block Numbering Area (BNA) - Census tracts are geographic entities within a county defined by a committee of local data users. When first established, census tracts should have relatively homogeneous demographic characteristics. Generally, Census tracts have a population size between 2,500 and 8,000 persons, and average about 4,000 persons. BNAs are areas delineated by State agencies and/or the Census Bureau for counties without Census tracts. The delineation of BNAs follows the same basic criteria as Census tracts. Because BNAs appear more often in lightly populated counties, they may have fewer people. The 11-digit census tract/BNA geocode consists of a 2-digit FIPS State code, a 3- digit FIPS county code, a 4-digit census tract/BNA base number, and a 2- digit census tract/BNA suffix code. For Census tracts, base numbers range from 0001 to 9499, and suffix codes range from 01 to 99. For BNAs, base numbers range from 9500 to 9989, and suffix codes range from 85 to 99. Non-suffixed Census tract/BNAs have blank suffix codes. Small Census tract/BNAs with zero population may have been eliminated from the boundary file. Also, the boundary file does not include crews-of-vessels Census tract/BNAs which represent the population on military and/or merchant ships. 1990 American Indian reservation (AIR)/Alaska Native village statistical area (ANVSA) - AIRs are legal entities having boundaries established by treaty, statute and/or executive or court order. They are identified by either the Bureau of Indian Affairs for Federal reservations or the individual States for State reservations. The Census Bureau also tabulates data for American Indian trust lands; these are off-reservation lands associated with a specific tribe or reservation held in trust by the Federal government. Trust lands are only included in the boundary file where no AIR exists for a tribe. ANVSAs are census statistical areas that delineate the settled area of each Alaska Native village (ANV). ANVs consists of tribes, bands, clans, villages, communities, and associations that are recognized in pursuant to the Alaska Native Claims Settlement Act, but do not have legally recognized boundaries. Officials of Alaska Native Regional Corporations and other knowledgeable officials delineated the ANVSAs for the Census Bureau. The AIR/ANVSA geocode consist of a 4-digit Census code. For AIRs, the code ranges from 0001 to 4989. For ANVSAs, the code ranges from 6001 to 8989. 1990 Alaska Native Regional Corporation - ANRCs are corporate entities established by the Alaska Native Claims Settlement Act to carry out business and nonprofit operations for Alaska Natives. The ANRC geocode consists of a 2-digit Census code. 1990 Urbanized Areas (UA) - The Census Bureau designates and defines UAs to provide better identification of urban and rural population in the vicinity of large places. UAs are densely settled areas containing at least 50,000 persons. UAs include one or more central cities, together with adjacent areas having a population density of at least 1,000 persons per square mile. Most UAs form the core of a MA, but a few UAs are not part of any MA. The UA geocode consist of a 4-digit Census code. 1993 Metropolitan Areas (MA) - The Federal Office of Management and Budget (OMB) designates and defines MAs. MAs include Metropolitan Statistical Areas (MSAs), Consolidated Metropolitan Statistical Areas (CMSAs), and Primary Metropolitan Statistical Areas (PMSAs), of which MSAs are the most numerous. This boundary file contains only PMSAs and MSAs. The underlying concept of an MSA is that of a core area containing a large population nucleus, together with adjacent communities having a high degree of economic and social integration with that core. MSAs are composed of entire counties, except for New England, where the component entities are MCDs. According to the OMB criteria , each MSA must include either a city with at least 50,000 persons, or a Census Bureau- defined urbanized area and a total population of at least 100,000 (75,000 in New England). Within an area that meets the requirements to be an MSA and also has a population of one million or more, the OMB recognizes individual component areas if they meet specified criteria and local opinion supports their recognition. If recognized, the component areas are designated PMSAs, and the entire area that contains them becomes a CMSA. If no PMSAs are recognized, the entire area is designated an MSA. The boundary file contains PMSAs and MSAs recognized as of June, 1993, although the actual boundaries of the areas are based on 1990 counties and 1990 MCDs. The PMSA/MSA geocode consists of a 4-digit Census code. 103rd Congressional District (C3) and 104th Congressional District (C4) - CDs are the areas from which members are elected to the U. S. House of Representatives. After the Federal apportionment of congressional seats among the States based on the decennial census population counts, State officials are responsible for establishing CDs for the purpose of electing representatives; occasionally, the courts are called upon to delineate the CDs. The 103rd Congress was the first Congress that reflects the reapportionment and delineation of CDs based on the 1990 census. The next Congress, the 104th Congress reflects redelineation that occurred for six states only: Georgia, Lousiana, Maine, Minnesota, South Carolina and Virginia. The CD geocode consists of a 2-digit FIPS State code and a 2-digit CD number. CD numbers of 01 to 52 represent individual district codes, 00 represents an at-large seat, 98 indicates a nonvoting delegate, and 99 indicates no representation in Congress. FILE LOCATION All boundary files are found under a directory with the following URL: file://ftp.census.gov/pub/tiger/boundary/. Compressed boundary files are located within two zip files, lvset1.zip and lvset2.zip. These zip files were created using zip version 2.0.1 on a UNIX platform. This utility is compatible with pkzip 2.04. Files were zipped with options to make unzipped files compatible with MSDOS. (If unzipping on a UNIX platform, use the -a option for text file.) Lvset1.zip contains files for States, counties, MCDs, AIR/ANVSAs, MAs, and CDs. Lvset2.zip contains files for census tracts/BNAs. Uncompressed boundary files are located under individual subdirectories within the main boundary directory, with subdirectory names corresponding to boundary type. For example, uncompressed state boundary files can be found with the following URL: file://ftp.census.gov/pub/tiger/boundary/state/. FILE CREATION Original boundary file coordinates and geocodes were extracted from the TIGER data base from internal files equivalent to the publicly available TIGER/Line files. For all boundary types except 104th CD, the internal files equate to 1992 TIGER/Line files. For 104th CD boundaries only, the internal files equate to 1994 TIGER/Line files. Data were imported into an ARCINFO system as simple ASCII files. All coordinate manipulation was performed within the ARC environment. The thinning process included reduction of coordinate pairs, elimination of small polygons for discontiguous entities, and eliminationof small Census tract/BNAs with zero population. Different degrees of coordinate thinning were used for different boundary types. State, county, MCD and MA boundaries were aggressively thinned, although lines coincident amongst these separate boundary networks retain a precise nesting quality. ANRC boundaries were also aggressively thinned. The Census tract/BNA, UA and AIR/ANVSA boundaries were moderately thinned, while CD boundaries were only minimally thinned. Geographic relationships amongst boundary types can not be inferred from boundary location, because boundary networks were thinned independently of one another (except for the previously mentioned State, county, MCD and MA boundaries). After thinning, all boundary networks were clipped against a national coastline. This coastline was also derived from the TIGER data base and then thinned within the ARCINFO system. COMMENTS & QUESTIONS These boundary files were created for inclusion in Landview II, a geographic viewing system developed by the Environmental Protection Agency (EPA). The boundary types selected and the degree of thinning employed were largly related to EPA's requirements. We have placed the boundary files here because we believe they may be of value to others. The Census Bureau is interested in learning your reaction to these boundary files or your thoughts on boundary files as a product, in general. Some questions you might answer for us: - how have you used these boundary files? - with what GIS or mapping system did you use the files? - what file format would you prefer? Simple ASCII? Vendor-specific? - do you prefer boundary files as a polygon network or a line network? - are there other boundary types for which you would like files? - would you prefer more/less/different coordinate thinning? For which boundaries? - would you prefer boundaries clipped against a different coastline? - do you have any use for boundaries without any coastline clipping? Direct any questions to Amy Bishton, GEO Division, Census Bureau (phone: 301-457-1101, internet: abishton@census.gov) 1990 unspecified Complete Unknown -127.88722375 -65.37157901 48.25041716 22.93932776 None 104th Congressional District Boundaries inlandWaters None Conterminous United States None None None None None The coverage no longer will be valid if the Congressional District boundaries change (redistricting). Kerie J. Hitt U.S. Geological Survey,Water Resources Div. (WRD) Hydrologist, NAWQA National Synthesis Project mailing address

12201 Sunrise Valley Drive, MS-413

Reston VA 20191 USA 1-888-275-8747 703-648-5295 kjhitt@usgs.gov 9:00am-5:30pm EST Please contact thru email http://water.usgs.gov/GIS/browse/104thcongress.jpg Illustration of data set jpg None Unclassified None dgux, 5.4R3.10, AViiON UNIX, ARC/INFO version 7.0.4 U.S. Bureau of the Census 000000 URL:http://ftp.census.gov/pub/tiger/boundary See Entity_Attribute_Information See Explanation Attribute accuracy is described, where present, with each attribute defined in the Entity and Attribute Section. Polygon topology present. unspecified Unspecified 0000 100,000 Unspecified 0000 Unspecified Unspecified Unspecified DISSOLVE EDIT104 DIS104 FULLCODE POLY None 19950726 1810 None AMYB RENAME DIS104 LV99CE_104 None 19951128 1633 None LINDAO ARCEDIT /SQUASH/POLYGON/CD/LV99CE_104 None 19960124 0758 None LINDAO BUILD LV99CE_104 None 19960124 0800 None LINDAO ARCEDIT /SQUASH/POLYGON/CD/LV99CE_104 None 19960125 0736 None LINDAO BUILD LV99CE_104 None 19960125 0737 None LINDAO ARCEDIT /SQUASH/POLYGON/CD/LV99CE_104 None 19960125 0921 None LINDAO BUILD LV99CE_104 None 19960125 0921 None KJHITT IMPORT COVER CD99.E00 CD104 None 19960215 0955 None KJHITT PROJECT COVER CD104 CD104B None 19960215 1001 None KJHITT BUILD CD104B None 19960215 1100 None KJHITT RENAME CD104B CD104 None 19960215 1139 None KJHITT DOCUMENT CD104 CREATE KJHITT None 19960215 1303 None KJHITT DOCUMENT CD104 UPDATE KJHITT None 19960215 1324 None KJHITT COPY CD104 /HOME/WILY/CD104/CD104 None 19960215 1403 None KJHITT EXPORT COVER CD104 CD104.E00 None 19960227 1254 None MNEGRI IMPORT COVER CD104.E00 CD104 None 19960312 0942 None MNEGRI EXPORT COVER CD104 CD104.E00 None 19960312 1453 None MNEGRI UNGENERATE POLY /DSDL1/CUSA/TILES/CUSA/CD104 CD104.UGEN None 19960327 0836 None MNEGRI UNGENERATE POLY /DSDL1/CUSA/TILES/CUSA/CD104 CD104.UGEN None 19960327 0923 None MNEGRI UNGENERATE POLY /DSDL1/CUSA/TILES/CUSA/CD104 CD104.UGEN None 19960327 0949 None MNEGRI UNGENERATE POLY /DSDL1/CUSA/TILES/CUSA/CD104 CD104.UGEN None 19960327 0956 None MNEGRI UNGENERATE POLY /DSDL1/CUSA/TILES/CUSA/CD104 CD104.UGEN None 19960327 1014 None MNEGRI DOCUMENT CD104 UPDATE MNEGRI None 19960409 1433 None MNEGRI DOCUMENT CD104 UPDATE MNEGRI None 19960410 0920 None MNEGRI DOCUMENT CD104 UPDATE MNEGRI None 19960410 0957 None Vector Point 537 String 1837 GT-polygon composed of chains 538 Albers Conical Equal Area 29.5 45.5 -96 23 0.00000 0.00000 coordinate pair 1.0 1.0 METERS Unknown Clarke 1866 6378206.4 294.98 CD104.PAT Congressional district polygon attribute table Census Bureau - Congressional district polygon attribute table Census Bureau - unspecified unspecified AREA Area of poly in square coverage units Computed Positive real numbers unspecified unspecified PERIMETER Perimeter of polygon in coverage units Computed Positive real numbers unspecified unspecified CD104# Internal feature number Computed Sequential unique positive integer unspecified unspecified CD104-ID User-assigned feature number User-defined Integer unspecified unspecified ST State FIPS code Census Bureau 1-56 unspecified unspecified CD Congressional district Census Bureau 01-52 (individual district);00 (at-large);98 (nonvoting);99 (no rep) unspecified unspecified FULLCODE Combination of State FIPS + congressional district Census Bureau unspecified unspecified unspecified COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC 1 AREA 4 12 F 3 5 PERIMETER 4 12 F 3 9 CD104# 4 5 B - 13 CD104-ID 4 5 B - 17 ST 2 2 I - 19 CD 2 2 I - ** REDEFINED ITEMS ** 17 FULLCODE 4 4 I - ST is the state FIPS code. CD is the congressional district: 01 to 52...individual district codes 00.........at-large seat 98.........nonvoting delegate 99.........no representation in Congress FULLCODE is a combination of state and congressional district codes. Not Available U.S. Geological Survey Ask USGS - Water Webserver Team mailing

445 National Center

Reston VA 20192 1-888-275-8747 (1-888-ASK-USGS) http://water.usgs.gov/user_feedback_form.html Although this data set has been used by the U.S. Geological Survey, U.S. Department of the Interior, no warranty expressed or implied is made by the U.S. Geological Survey as to the accuracy of the data and related materials. The act of distribution shall not constitute any such warranty, and no responsibility is assumed by the U.S. Geological Survey in the use of this data, software, or related materials. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Export Full coverage zipped 1 http://water.usgs.gov/GIS/dsdl/cd104.e00.gz Other Full coverage zipped 1 http://water.usgs.gov/GIS/dsdl/cd104.tar.gz None. This dataset is provided by USGS as a public service. 20041108 U.S. Geological Survey Ask USGS -- Water Webserver Team mailing

445 National Center

Reston VA 20192 1-888-275-8747 (1-888-ASK-USGS) http://answers.usgs.gov/cgi-bin/gsanswers?pemail=h2oteam&subject=GIS+Dataset+cd104 FGDC Content Standards for Digital Geospatial Metadata FGDC-STD-001-1998