This data collection contains information compiled from the questions asked of all people and every housing unit enumerated in Census 2000. The questions cover sex, age, race, Hispanic or Latino origin, type of living quarters (household/group quarters), household relationship, housing unit vacancy status, and housing unit tenure (owner/renter). With subject content identical to that provided in Summary File 1, the information is presented in 286 tables that are tabulated for every geographic unit represented in the data. There is one variable per table cell, plus additional variables with geographic information. The data cover more than a dozen geographic levels of observation (known as "summary levels" in the Census Bureau's nomenclature) based on the 110th Congressional Districts, e.g., the 110th Congressional Districts themselves, census tracts within the 110th Congressional Districts, and county subdivisions within the 110th Congressional Districts. There are 40 data files for each state, the District of Columbia, and Puerto Rico.

The collection is supplied in 54 ZIP archives. There is a separate ZIP file for each state, the District of Columbia, and Puerto Rico, and, for the convenience of those who need all of the data, a separate ZIP archive with all 2,080 data files. The codebook and other documentation constitute the last ZIP archive.

Abstract (en): This data collection contains information compiled from the questions asked of a sample of persons and housing units enumerated in Census 2000. Population items include sex, age, race, Hispanic or Latino origin, type of living quarters (household/group quarters), urban/rural status, household relationship, marital status, grandparents as caregivers, language and ability to speak English, ancestry, place of birth, citizenship status and year of entry into the United States, migration, place of work, journey to work (commuting), school enrollment and educational attainment, veteran status, disability, employment status, occupation and industry, class of worker, income, and poverty status. Housing items include vacancy status, tenure (owner/renter), number of rooms, number of bedrooms, year moved into unit, household size, occupants per room, number of units in structure, year structure was built, heating fuel, telephone service, plumbing and kitchen facilities, vehicles available, value of home, and monthly rent. With subject content identical to that provided in Summary File 3, the information is presented in 813 tables that are tabulated for every geographic unit represented in the data. There is one variable per table cell, plus additional variables with geographic information. The data cover more than a dozen geographic levels of observation (known as "summary levels" in the Census Bureau's nomenclature) based on the 110th Congressional Districts, e.g., the 110th Congressional Districts, themselves, Census tracts within the 110th Congressional Districts, and county subdivisions within the 110th Congressional Districts. There are 77 data files for each state, the District of Columbia, and Puerto Rico. The collection is supplied in 54 ZIP archives. There is a separate ZIP file for each state, the District of Columbia, and Puerto Rico, and for the convenience of those who need all of the data, a separate ZIP archive with all 4,004 data files. The codebook and other documentation are located in the last ZIP archive. All persons and housing units in the United States and Puerto Rico. Every person and housing unit in the United States was asked basic demographic and housing questions (for example, race, age, and relationship to householder). A sample of these people and housing units was asked more detailed questions. The sampling unit for Census 2000 was the housing unit, including all occupants. There were four different housing unit sampling rates, 1-in-8, 1-in-6, 1-in-4, and 1-in-2, designed to yield an overall average of about 1-in-6. mail questionnaireICPSR has not checked this data collection.

The Bureau of the Census has released Census 2000 Summary File 1 (SF1) 100-Percent data. The file includes the following population items: sex, age, race, Hispanic or Latino origin, household relationship, and household and family characteristics. Housing items include occupancy status and tenure (whether the unit is owner or renter occupied). SF1 does not include information on incomes, poverty status, overcrowded housing or age of housing. These topics will be covered in Summary File 3. Data are available for states, counties, county subdivisions, places, census tracts, block groups, and, where applicable, American Indian and Alaskan Native Areas and Hawaiian Home Lands. The SF1 data are available on the Bureau's web site and may be retrieved from American FactFinder as tables, lists, or maps. Users may also download a set of compressed ASCII files for each state via the Bureau's FTP server. There are over 8000 data items available for each geographic area. The full listing of these data items is available here as a downloadable compressed data base file named TABLES.ZIP. The uncompressed is in FoxPro data base file (dbf) format and may be imported to ACCESS, EXCEL, and other software formats. While all of this information is useful, the Office of Community Planning and Development has downloaded selected information for all states and areas and is making this information available on the CPD web pages. The tables and data items selected are those items used in the CDBG and HOME allocation formulas plus topics most pertinent to the Comprehensive Housing Affordability Strategy (CHAS), the Consolidated Plan, and similar overall economic and community development plans. The information is contained in five compressed (zipped) dbf tables for each state. When uncompressed the tables are ready for use with FoxPro and they can be imported into ACCESS, EXCEL, and other spreadsheet, GIS and database software. The data are at the block group summary level. The first two characters of the file name are the state abbreviation. The next two letters are BG for block group. Each record is labeled with the code and name of the city and county in which it is located so that the data can be summarized to higher-level geography. The last part of the file name describes the contents . The GEO file contains standard Census Bureau geographic identifiers for each block group, such as the metropolitan area code and congressional district code. The only data included in this table is total population and total housing units. POP1 and POP2 contain selected population variables and selected housing items are in the HU file. The MA05 table data is only for use by State CDBG grantees for the reporting of the racial composition of beneficiaries of Area Benefit activities. The complete package for a state consists of the dictionary file named TABLES, and the five data files for the state. The logical record number (LOGRECNO) links the records across tables.

This map shows Congressional District boundaries for the United States. The map is set to middle Georgia.

Congressional districts are the 435 areas from which members are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the states, which is based on decennial census population counts, each state with multiple seats is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The boundaries and numbers shown for the congressional districts are those specified in the state laws or court orders establishing the districts within each state.

Congressional districts for the 108th through 112th sessions were established by the states based on the result of the 2000 Census. Congressional districts for the 113th through 115th sessions were established by the states based on the result of the 2010 Census. Boundaries are effective until January of odd number years (for example, January 2015, January 2017, etc.), unless a state initiative or court ordered redistricting requires a change. All states established new congressional districts in 2011-2012, with the exception of the seven single member states (Alaska, Delaware, Montana, North Dakota, South Dakota, Vermont, and Wyoming).

For the states that have more than one representative, the Census Bureau requested a copy of the state laws or applicable court order(s) for each state from each secretary of state and each 2010 Redistricting Data Program state liaison requesting a copy of the state laws and/or applicable court order(s) for each state. Additionally, the states were asked to furnish their newly established congressional district boundaries and numbers by means of geographic equivalency files. States submitted equivalency files since most redistricting was based on whole census blocks. Kentucky was the only state where congressional district boundaries split some of the 2010 Census tabulation blocks. For further information on these blocks, please see the user-note at the bottom of the tables for this state.

The Census Bureau entered this information into its geographic database and produced tabulation block equivalency files that depicted the newly defined congressional district boundaries. Each state liaison was furnished with their file and requested to review, submit corrections, and certify the accuracy of the boundaries.

NOTE: Data based on a sample except in P3, P4, H3, and H4. For.information on confidentiality protection, sampling error,.nonsampling error, definitions, and count corrections see.http://www.census.gov/prod/cen2000/doc/cd110s.pdf.Source: U.S. Census Bureau, 110th Congressional District Summary.File (Sample), Matrices H1, H7, H20, H23, H24, H30, H34, H38, H40,.H43, H44, H48, H51, H62, H63, H69, H74, H76, H90, H91, and H94...Where the boundary of a congressional district for the 110th.Congress splits a Census 2000 block, the Census Bureau's map.depicts its location correctly, but for data tabulation purposes,.that block is allocated in its entirety to the 110th Congressional.District specified by the state. For a list of 110th Congressional.Districts that split blocks, see.http://www.census.gov/geo/www/cd110th/spblk110.txt.(X) Not applicable..

NOTE: For information on confidentiality protection,.nonsampling error, definitions, and count corrections see.http://www.census.gov/prod/cen2000/doc/cd110h.pdf

The purpose of this dataset is to indicate the boundary of each US Congressional District within Cook County, Illinois. These boundaries are based off of Census 2000 geographies.Created for all users to view and understand jurisdictional boundaries within Cook County. US Congressional Districts are redrawn every 10 years based on the decennial census. Clerk Elections maintains the US Congressional District feature.

Us House Congressional Representatives serving Macon-Bibb County.Congressional districts are the 435 areas from which members are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the states, which is based on decennial census population counts, each state with multiple seats is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a state as practicable. The boundaries and numbers shown for the congressional districts are those specified in the state laws or court orders establishing the districts within each state.

Congressional districts for the 108th through 112th sessions were established by the states based on the result of the 2000 Census. Congressional districts for the 113th through 115th sessions were established by the states based on the result of the 2010 Census. Boundaries are effective until January of odd number years (for example, January 2015, January 2017, etc.), unless a state initiative or court ordered redistricting requires a change. All states established new congressional districts in 2011-2012, with the exception of the seven single member states (Alaska, Delaware, Montana, North Dakota, South Dakota, Vermont, and Wyoming).

For the states that have more than one representative, the Census Bureau requested a copy of the state laws or applicable court order(s) for each state from each secretary of state and each 2010 Redistricting Data Program state liaison requesting a copy of the state laws and/or applicable court order(s) for each state. Additionally, the states were asked to furnish their newly established congressional district boundaries and numbers by means of geographic equivalency files. States submitted equivalency files since most redistricting was based on whole census blocks. Kentucky was the only state where congressional district boundaries split some of the 2010 Census tabulation blocks. For further information on these blocks, please see the user-note at the bottom of the tables for this state.

The Census Bureau entered this information into its geographic database and produced tabulation block equivalency files that depicted the newly defined congressional district boundaries. Each state liaison was furnished with their file and requested to review, submit corrections, and certify the accuracy of the boundaries.

NOTE: For information on confidentiality protection,.nonsampling error, definitions, and count corrections see.http://www.census.gov/prod/cen2000/doc/cd110h.pdf

NOTE: For information on confidentiality protection,.nonsampling error, definitions, and count corrections see.http://www.census.gov/prod/cen2000/doc/cd110h.pdf

1 DVD-ROM ; 4 3/4 in. Abstract: "This DVD contains all State summary data files, documentation and software." System requirements: PC with DVD-ROM drive; Adobe Acrobat Reader. CD no.: V1-D00-C110-08-US1

Small Area Estimate Program (SAEP) April 1 population estimates for congressional districts, 2000-present.

The table 2000 Census Tract to 108th Congressional District is part of the dataset Census Tract Crosswalking Files, available at https://redivis.com/datasets/f8gs-807zsasy3. It contains 69748 rows across 13 variables.

Abstract (en): The State Legislative District Summary File Supplement contains geographic identification codes that relate each 2000 Census block to pre-2010 Census state legislative districts. Both upper and lower chamber districts are identified. In addition, these block-level data contain variables on land area, water area, latitude, longitude, total population size, and number of housing units, as well as geographic identification variables for other levels of observation such as states, metropolitan statistical areas, urban areas, congressional districts, counties, county subdivisions, places, census tracts, block groups, and ZIP code tabulation areas. There is one data file for each state, the District of Columbia, and Puerto Rico which are bundled together in a single ZIP archive. A second ZIP archive contains the codebook and other documentation. All persons and housing units in the United States and Puerto Rico. mail questionnaire

NOTE: Data based on a sample except in P3, P4, H3, and H4. For.information on confidentiality protection, sampling error,.nonsampling error, definitions, and count corrections see.http://www.census.gov/prod/cen2000/doc/cd110s.pdf

The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Congressional Districts are the 435 areas from which people are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the States based on census population counts, each State is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a State as practicable. The congressional districts for the 111th Congress (January 2009 to 2011) continue to be based on Census 2000 data. The TIGER/Line shapefiles for the District of Columbia, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands) each contain a single record for the non-voting delegate district in these areas. The boundaries of all other congressional districts are provided to the Census Bureau through the Redistricting Data Program (RDP).

The table 2000 Census Tract to 109th Congressional District is part of the dataset Census Tract Crosswalking Files, available at https://redivis.com/datasets/f8gs-807zsasy3. It contains 69876 rows across 13 variables.

The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Congressional Districts are the 435 areas from which people are elected to the U.S. House of Representatives. After the apportionment of congressional seats among the States based on census population counts, each State is responsible for establishing congressional districts for the purpose of electing representatives. Each congressional district is to be as equal in population to all other congressional districts in a State as practicable. The congressional districts for the 111th Congress (January 2009 to 2011) continue to be based on Census 2000 data. The TIGER/Line shapefiles for the District of Columbia, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands) each contain a single record for the non-voting delegate district in these areas. The boundaries of all other congressional districts are provided to the Census Bureau through the Redistricting Data Program (RDP).

Summary File 3 Data Profile 2 (SF3 Table DP-2) for Census Tracts in Minneapolis-St. Paul 7 County metropolitan area is a subset of the profile of selected social characteristics for 2000 prepared by the U.S. Census Bureau.

This table (DP-2) includes: School Enrollment, Educational Attainment, Marital Status, Grandparents as Caregivers, Veteran Status, Disability Status of the Civilian Noninstitutionalized Population, Residence in 1995, Nativity and Place of Birth, Region of Birth of Foreign Born, Language Spoken At Home, Ancestry

US Census 2000 Demographic Profiles: 100-percent and Sample Data

The profile includes four tables (DP-1 thru DP-4) that provide various demographic, social, economic, and housing characteristics for the United States, states, counties, minor civil divisions in selected states, places, metropolitan areas, American Indian and Alaska Native areas, Hawaiian home lands and congressional districts (106th Congress). It includes 100-percent and sample data from Census 2000. The DP-1 table is available as part of the Summary File 1 (SF 1) dataset, and the other three tables are available as part of the Summary File 3 (SF 3) dataset.

The US Census provides DP-1 thru DP-4 data at the Census tract level through their DataFinder search engine. However, since the Metropolitan Council and MetroGIS participants are interested in all Census tracts within the seven county metropolitan area, it was quicker to take the raw Census SF-1 and SF-3 data at tract levels and recreate the DP1-4 variables using the appropriate formula for each DP variable. This file lists the formulas used to create the DP variables.

NOTE: Data based on a sample except in P3, P4, H3, and H4. For.information on confidentiality protection, sampling error,.nonsampling error, definitions, and count corrections see.http://www.census.gov/prod/cen2000/doc/cd110s.pdf