The Hispanic Oversample - IPUMS USA
Public Use Microdata Sample of the
1900 U.S. Census of American Indians:
User’s Guide
by
Minnesota Population Center
University of Minnesota
May, 2005
Introduction to the User’s Guide
This document describes the design and characteristics of the public use microdata sample of the 1900 U.S. Census of American Indians. The project was conducted at the Minnesota Population Center of the University of Minnesota, with funding provided by the National Institute of Child Health and Human Development (R01 HD 36451).
In 1900 the Office of the Census used a modified form to enumerate most American Indians. Instructions on the form state:
This modified form of Schedule No. 1 is to be used in making the enumeration of Indians, both those on reservations and those living in family groups outside of reservations.
Detached Indians either in white or negro families outside of reservations should be enumerated on the general population schedule as members of the families in which they are found; but detached whites or negroes living in Indian families should be enumerated on this schedule as members of the Indian families in which they are found. In other words, every family composed mainly of Indians should be reported entirely on this schedule, and every family composed mainly of persons not Indian should be reported entirely on the general population schedule (italics in the original).
The Indian schedule had the same questions as the general population schedule, but had 10 additional questions concerning Indian name, tribal information, percentage of white blood, polygamy, tax status, citizenship, and dwelling information.
Sample Design
The records included in the sample represent approximately 20 percent of the individuals enumerated on the Indian schedules. The sample is analogous to the existing public use microdata samples, which are simultaneously a sample of households and individuals. The sampling strategy is based on the manuscript page from the Indian schedules. Each page consists on an ‘A’ and a ‘B’ side, with lines 1 through 20 on the ‘A’ side and lines 21 through 40 on the ‘B’ side. We randomly generated a ‘window’ of 8 sample lines for each page. If one of the sample lines contained the head of a household, the entire household became part of the sample provided: the household contained fewer than 31 persons, and a) the household was the only household in the dwelling, or b) it was the 1st household in a dwelling of fewer than 31 persons (in which case all households in the dwelling were included in the sample). If the household was in a multi-household dwelling of more than 30 persons, then only the single household was included in the sample. If a household consisted of more than 30 persons we sampled at the individual level (i.e., only persons from the sample lines were included in the sample).
The sample design described above insures that all individuals enumerated on the Indian schedules had an equal probababilty of being included in the sample. The sample includes 45,651 individuals. But, as indicated in the enumerator instructions above, non-Indians were also enumerated on the Indian schedules. The current sample includes 1,574 individuals with a race of white and 350 individuals with a race of black. However, some of the non-Indians have tribal information indicating that they were Indian; we did not attempt to impose consistency between race and tribal information.
The enumerator instructions indicate that not all Indians (those living in predominantly white or black households) were enumerated on the special Indian schedules. And we do have 134 individuals with a race of Indian in our 1-percent sample of the general population in 1900. Users might want to include these records in their analysis. However, the Indians taken from the general schedules were not asked the supplemental Indian questions. In addition, users should be aware that we extracted 5 percent of the records in the Indian sample and added them to the 1-percent sample. Users can distinguish between the general schedule and extracted Indians in the 1-percent sample with the variable OVERSAMP.
Data Format
The dataset has a rectangular column-format structure. Household records are identified by a ‘H’ in the RECTYPE variable. Person records are identified by a ‘P’ in the RECTYPE variable.
The data dictionary on pages 3-6 provides variable descriptions, frequencies, column layouts, and coding schemes for all variables. Where possible, we have adopted IPUMS coding schemes
Data Dictionary
The data dictionary describes each variable in the sample. For each variable, the dictionary provides a universe statement and a description. In certain cases, additional user notes caution researchers against potential problems that some uses of the variable may entail.
Universe
The universe statement defines the population at risk for the given variable (i.e., who was asked the question, or to whom the question applies).
Codes and Frequencies
For some variables, a frequency table gives the value label for each code. The column numbers in the tables show the number of cases (frequencies) in each category.
Obtaining the Data
The data—in compressed ASCII format—documentation, and an SPSS syntax file with variable and value labels can be downloaded from the IPUMS website:
Citation and Use of the Data
All persons are granted a limited license to use and distribute this documentation and the accompanying data, subject to the following conditions:
No fee may be charged for use or distribution. Publications and research reports based on the database must cite it appropriately. The citation should include the following:
Steven Ruggles, Matthew Sobek, Trent Alexander, Catherine A. Fitch, Ron Goeken, Patricia Kelly Hall, Miriam King, and Chad Ronnander. Integrated Public Use Microdata Series: Version 3.0 [Machine-readable database]. Minneapolis, MN: Minnesota Population Center [producer and distributor], 2004.
If possible, citations should also include the URL for the IPUMS site: .
In addition, we request that users send us a copy of any publications, research reports, or educational material making use of the data or documentation. Printed matter should be sent to:
IPUMS
Minnesota Population Center
University of Minnesota
50 Willey Hall
225 19th Avenue South
Minneapolis, MN 55455
Send all electronic material to ipums@pop.umn.edu.
Record Layout for the
1900 American Indian Public Use Microdata Sample - Household
|Order |Variable |Variable Name |Width |Columns |
| |Record Type |RECTYPE |1 |1 |
| |Census Year |YEAR |2 |2-3 |
| |Data set number |DATANUM |2 |4-5 |
| |Household serial number |SERIAL |7 |6-13 |
| |Number of person records following |NUMPREC |2 |14-15 |
| |Subsample number |SUBSAMP |2 |16-17 |
| |Household weight |HHWT |4 |18-21 |
| |Number of persons in household |NUMPERHH |4 |22-25 |
| |Dwelling size |DWSIZE |4 |26-29 |
| |Number of households in dwelling |NUMHH |2 |30-31 |
| |Number of households sampled from dwelling |NUMHHTAK |1 |32 |
| |Census region and division |REGION |2 |33-34 |
|13. |State (ICPSR code) |STATEICP |2 |35-36 |
|14. |State (FIPS code) |STATEFIP |2 |37-38 |
|15. |County ICPSR code |COUNTY |4 |39-42 |
|16. |State economic area |SEA |3 |44-46 |
|17. |Metropolitan status |METRO |1 |47 |
|18. |Metropolitan area -- Detailed |METAREA |4 |48-51 |
|19. |Metropolitan District |METDIST |4 |52-55 |
|20. |City name -- Detailed |CITY |4 |56-59 |
|21. |City population (incorporated places) |CITYPOP |5 |60-64 |
|22. |Size of place |SIZEPL |2 |65-66 |
|23. |Urban/rural status |URBAN |1 |67 |
|24. |Urban area |URBAREA |4 |68-71 |
|25. |Group quarters status |GQ |1 |72 |
|26. |Group quarters type – Detailed |GQTYPE |3 |73-75 |
|27. |Group quarters funding |GQFUNDS |2 |76-77 |
|28. |Farm status |FARM |1 |78 |
|29. |Farm schedule |FARMSCHD |1 |79 |
|30. |Ownership of dwelling – Detailed |OWNERSHP |2 |80-81 |
|31. |Mortgage status |MORTGAGE |1 |82 |
|32. |Ward |WARD |3 |84-86 |
|33. |Sampling rule |SAMPRULE |1 |99 |
|34. |Microfilm reel number |REEL |4 |100-103 |
|35. |Microfilm page number |PAGENO |4 |106-109 |
|36. |Line number |LINE |3 |115-117 |
|37. |Microfilm sequence number |PAGESEQ |1 |119 |
|38. |Month of Enumeration |ENUMMO |2 |120-121 |
|39. |Day of Enumeration |ENUMDAY |2 |122-123 |
|40. |Enumeration District |ENUMDIST |4 |128-131 |
|41. |Supervisor’s district number |SUPDIST |3 |132-134 |
|42. |House number and street address |STREET |32 |157-188 |
|43. |Number of families in household |NFAMS |2 |190-191 |
|44. |Number of married couples in household |NCOUPLES |1 |192 |
|45. |Number of mothers in household |NMOTHERS |1 |193 |
|46. |Number of fathers in household |NFATHERS |1 |194 |
|47. |Mortgage status – Data quality flag |QMORTGAG |1 |208 |
|48. |Farm status – Data quality flag |QFARM |1 |214 |
|49. |Group quarters status – Data quality flag |QGQ |1 |219 |
|50. |Ownership of dwelling – Detailed – Data quality flag |QOWNERSH |1 |223 |
|51. |Group quarters type – Detailed – Data quality flag |QGQTYPE |1 |241 |
|52. |Minor civil division FIPS codes |FIPSMCD |5 |505-509 |
|53. |Incorporated Municipality FIPS codes |FIPSINC |5 |510-514 |
|54. |New England town population |NENGPOP |7 |517-521 |
|55. |Type of home |IHOME |1 |526 |
|56. |Urban population |URBPOP |5 |551-555 |
Record Layout for the
1900 American Indian Public Use Microdata Sample - Person
|Order |Variable |Variable Name |Width |Columns |
|1. |Record Type |RECTYPE |1 |1 |
|2. |Census Year |YEAR |2 |2-3 |
|3. |Data set number |DATANUM |2 |4-5 |
|4. |Household serial number |SERIAL |7 |6-13 |
|5. |Person number in sample unit |PERNUM |2 |14-15 |
|6. |Person weight |PERWT |4 |20-23 |
|7. |Mother's location in household |MOMLOC |2 |26-27 |
|8. |Probable step/adopted mother |STEPMOM |1 |28 |
|9. |Rule for linking mother |MOMRULE |1 |29 |
|10. |Father's location in household |POPLOC |2 |30-31 |
|11. |Probable step/adopted father |STEPPOP |1 |32 |
|12. |Rule for linking father |POPRULE |1 |33 |
|13. |Spouse's location in household |SPLOC |2 |34-35 |
|14. |Rule for linking spouse |SPRULE |1 |36 |
|15. |Number of own family members in household |FAMSIZE |2 |37-38 |
|16. |Number of own children in household |NCHILD |1 |39 |
|17. |Number of own children under age 5 in household |NCHLT5 |1 |40 |
|18. |Family unit membership |FAMUNIT |2 |41-42 |
|19. |Age of eldest own child in household |ELDCH |2 |43-44 |
|20. |Age of youngest own child in household |YNGCH |2 |45-46 |
|21. |Number of own siblings in household |NSIBS |1 |47 |
|22. |Relationship to household head -- Detailed |RELATE |4 |48-51 |
|23. |Age |AGE |3 |52-54 |
|24. |Sex |SEX |1 |55 |
|25. |Race – Detailed |RACE |3 |56-58 |
|26. |Marital Status |MARST |1 |59 |
|27. |Duration of current marital status |DURMARR |2 |60-61 |
|28. |Children ever born |CHBORN |2 |63-64 |
|29. |Children surviving |CHSURV |2 |65-66 |
|30. |Birthplace – Detailed |BPL |5 |67-71 |
|31. |Mother's birthplace – Detailed |MBPL |5 |72-76 |
|32. |Father's birthplace – Detailed |FBPL |5 |77-81 |
|33. |Nativity recode |NATIVITY |1 |82 |
|34. |Citizenship status |CITIZEN |1 |83 |
|35. |Year of birth |BIRTHYR |3 |84-86 |
|36. |Year of immigration |YRIMMIG |3 |87-89 |
|37. |Years in the United States, intervalled |YRSUSA2 |1 |90 |
|38. |Speaks English |SPEAKENG |1 |108 |
|39. |Spanish surname |SPANNAME |1 |109 |
|40. |School attendance |SCHOOL |1 |110 |
|41. |Months in school |SCHLMNTH |2 |111-112 |
|42. |Literacy |LIT |1 |114 |
|43. |Labor force status |LABFORCE |1 |118 |
|44. |Occupation, 1950 basis |OCC1950 |3 |119-121 |
|45. |Occupation |OCC |3 |122-124 |
|46. |Occupational income score |OCCSCORE |2 |125-126 |
|47. |Duncan Socioeconomic Index |SEI |2 |127-128 |
|48. |Industry, 1950 basis |IND1950 |3 |129-131 |
|49. |Years in the United States |YRSUSA1 |2 |145-146 |
|50. |Months unemployed last year |MOUNEMP |2 |147-148 |
|51. |Quarters unemployed last year |QTRUNEMP |1 |149 |
|52. |Last name |NAMELAST |16 |213-228 |
|53. |First name |NAMEFRST |16 |229-244 |
|54. |Age in months |AGEMONTH |2 |245-246 |
|55. |Month of birth |BIRTHMO |2 |247-248 |
|56. |Surname similarity |SURSIM |2 |259-260 |
|57. |Person received farm schedule |PFARMSCH |1 |269 |
|58. |Children surviving – Data quality flag |QCHSURV |1 |278 |
|59. |Age – Data quality flag |QAGE |1 |279 |
|60. |Age in months – Data quality flag |QAGEMONT |1 |280 |
|61. |Month of birth – Data quality flag |QBIRTHMO |1 |282 |
|62. |Birthplace – Detailed – Data quality flag |QBPL |1 |283 |
|63. |Literacy – Data quality flag |QLIT |1 |284 |
|64. |Children ever born – Data quality flag |QCHBORN |1 |285 |
|65. |Citizenship status – Data quality flag |QCITIZEN |1 |286 |
|66. |Father's birthplace – Detailed – Data quality flag |QFBPL |1 |290 |
|67. |Mother's birthplace – Detailed – Data quality flag |QMBPL |1 |303 |
|68. |Marital Status – Data quality flag |QMARST |1 |306 |
|69. |Occupation – Data quality flag |QOCC |1 |314 |
|70. |Quarters unemployed last year – Data quality flag |QQTRUNEM |1 |315 |
|71. |Race – Detailed – Data quality flag |QRACE |1 |316 |
|72. |Relationship to head – Detailed – Data quality flag |QRELATE |1 |317 |
|73. |Surname similarity – Data quality flag |QSURSIM |1 |318 |
|74. |Duration of current marital status – Data quality flag |QDURMARR |1 |321 |
|75. |School attendance – Data quality flag |QSCHOOL |1 |322 |
|76. |Sex – Data quality flag |QSEX |1 |323 |
|77. |Speaks English – Data quality flag |QSPEAKEN |1 |324 |
|78. |Year of immigration – Data quality flag |QYRIMM |1 |333 |
|79. |Indian name |INAME |35 |334-368 |
|80. |Tribe |TRIBE |5 |491-495 |
|81. |Father’s tribe |FTRIBE |5 |505-509 |
|82. |Mother’s tribe |MTRIBE |5 |510-514 |
|83. |Amount of white blood |BLOODW |3 |515-517 |
|84. |Polygamy |IMARST |1 |518 |
|85. |Tax status |ITAX |1 |519 |
|86. |Indian year of citizenship |IYRCIT |3 |520-522 |
|87. |Indian citizen status |ICITIZEN |1 |523 |
Data Dictionary - Household
RECTYP – Column 1
Record Type
Universe: All persons.
Description:
RECTYP assigns all household records the alphabetic string "H." This allows users to discriminate between household and person records; the latter are assigned the string "P" in the person-record variable RECTYP. Each household record is followed by one or more person records, and all data pertaining to any household usually pertain to all of the persons within it.
Codes and Frequencies:
| |Code |Frequency |
|Household record |H |12556 |
YEAR – Columns 2-3
Census Year
Universe: All persons.
Description:
YEAR identifies the census year of each case. YEAR is repeated on person records. The middle two digits of the census year are used: 90 indicates 1900.
Codes and Frequencies:
| |Code |Frequency |
|1900 |90 |12556 |
DATANUM – Columns 4-5
Dataset number
Universe: All persons.
Description:
DATANUM identifies the sample from which the case is drawn. All records in the Indian sample have a value of 4 for DATANUM.
Codes and Frequencies:
| |Code |Frequency |
|1900 American Indian Sample |4 |12556 |
SERIAL – Columns 6-13
Household serial number
Universe: All persons.
Description:
SERIAL is an identifying number unique to each household in a given census year sample. All person records are assigned the same serial number as the household record that they follow. (Person records also have their own unique identifiers—see PERNUM.) A combination of YEAR, DATANUM, and SERIAL provides a unique identifier for every household in the IPUMS; YEAR, DATANUM, SERIAL, and PERNUM uniquely identify every person in the database. In addition, the first six digits of SERIAL in 1900 provide the dwelling number for cases in which more than one household was sampled from a structure. The last two digits of SERIAL give the sequence of the household within the dwelling.
Codes: See text above.
NUMPREC – Columns 14-15
Number of person records following
Universe: All persons.
NUMPREC indicates how many person records are included in the sampled unit (household or group quarters). These person records will all have the same serial number (SERIAL) as the household record. The information contained in the household record will usually apply to all of these persons.
Codes: See text above.
SUBSAMP – Columns 16-17
Subsample number
Universe: All persons.
SUBSAMP allocates each household to one of 100 subsample replicates, randomly numbered from 0 to 99. Users who need a representative subset of a sample should use SUBSAMP to select their cases. For example, to randomly extract 10% of the cases from a sample, select any 10 of the 100 subsamples.
Codes: See text above.
HHWT – Columns 18-21
Sample weight
Universe: All persons.
Description:
HHWT describes how many households in the U.S. population in a census year are represented by a given household in the IPUMS. All records in the Indian sample have a HHWT of 5. For the 1900 Indian sample the use of the weight is optional, since every case represents the same number of households in the population (approximately equal to the sample density).
Codes : See text above.
NUMPERHH – Columns 22-25
Number of persons in household
Universe: All persons.
Description:
NUMPERHH indicates how many persons lived within the household or group quarters. This number is sometimes larger than NUMPREC (number of person records following) because the 1900 Indian sample did not sample large households/group quarters in their entirety.
Codes: See text above.
DWSIZE – Columns 26-29
Dwelling size
Universe: All persons.
Description:
DWSIZE indicates how many persons lived within the entire dwelling that contained the sampled household. If the entire dwelling is included in the sample, DWSIZE is based on a computer count of person records. If only one household was taken from a large multi-household dwelling, or the case was sampled as group quarters, DWSIZE is based on a hand count by the data-entry operator. A missing value indicates that the enumerator omitted the dwelling numbers.
Codes: See text above.
NUMHH – Columns 30-31
Dwelling size
Universe: All persons.
Description:
NUMHH indicates how many households lived within the entire dwelling that contained the sampled household. If the entire dwelling is included in the sample, NUMHH is based on a computer count of person records. If only one household was taken from a large multi-household dwelling, or the case was sampled as group quarters, NUMHH is based on a hand count by a data-entry operator. A missing value indicates the enumerator omitted the dwelling numbers.
Codes: See text above.
NUMHHTAK – Column 32
Number of households sampled from dwelling
Universe: All persons.
Description:
NUMHHTAK indicates how many households from the same dwelling that contained this household (including this household) are included in the sample. Only dwellings with 30 or fewer residents were sampled at the level of dwellings; larger dwellings were sampled at the level of households or as group quarters. To analyze multi-household dwellings, select the households with NUMHHTAK greater than 1 and combine the households using the first six digits of SERIAL. That is, the first six digits of SERIAL are common to all households contained in a dwelling.
Codes: See text above.
REGION – Columns 33-34
Census region and division
Universe: All persons.
Description:
REGION identifies the household's census region and division.
Codes and Frequencies:
| |Code |Frequency |
|New England |11 |50 |
|Middle Atlantic |12 |506 |
|East North Central |21 |591 |
|West North Central |22 |2607 |
|South Atlantic |31 |276 |
|East South Central |32 |91 |
|West South Central |33 |3119 |
|Mountain Division |41 |3669 |
|Pacific Division |42 |1647 |
STATEICP – Columns 35-36
State (ICPSR code)
Universe: All persons.
Description:
STATEICP identifies the household's state of enumeration using the Inter-University Consortium for Political and Social Research (ICPSR) coding scheme. The variable allows ICPSR state data to be easily merged with the IPUMS. The ICPSR scheme orders the states geographically by region. Note that the ICPSR regions do not correspond perfectly with the census regions used in the IPUMS variable REGION.
Codes and Frequencies:
| |Code |Frequency |
|Connecticut |1 |5 |
|Maine |2 |43 |
|Massachusetts |3 |1 |
|Rhode Island |5 |1 |
|New York |13 |258 |
|Pennsylvania |14 |248 |
|Illinois |21 |1 |
|Indiana |22 |6 |
|Michigan |23 |208 |
|Wisconsin |25 |376 |
|Iowa |31 |15 |
|Kansas |32 |200 |
|Minnesota |33 |454 |
|Missouri |34 |1 |
|Nebraska |35 |180 |
|North Dakota |36 |432 |
|South Dakota |37 |1325 |
|Virginia |40 |28 |
|Alabama |41 |4 |
|Arkansas |42 |1 |
|Louisiana |45 |18 |
|Mississippi |46 |80 |
|North Carolina |47 |244 |
|South Carolina |48 |4 |
|Texas |49 |9 |
|Kentucky |51 |6 |
|Oklahoma |53 |3091 |
|Tennessee |54 |1 |
|Arizona |61 |1500 |
|Colorado |62 |146 |
|Idaho |63 |254 |
|Montana |64 |559 |
|Nevada |65 |267 |
|New Mexico |66 |727 |
|Utah |67 |122 |
|Wyoming |68 |94 |
|California |71 |740 |
|Oregon |72 |332 |
|Washington |73 |575 |
STATEFIP – Columns 37-38
State (ICPSR code)
Universe: All persons.
Description:
STATEFIP identifies the household's state of enumeration using the Federal Information Processing Standards (FIPS) coding scheme, which orders the states alphabetically.
Codes and Frequencies:
| |Code |Frequency |
|Alabama |1 |4 |
|Arizona |4 |1500 |
|Arkansas |5 |1 |
|California |6 |740 |
|Colorado |8 |146 |
|Connecticut |9 |5 |
|Idaho |16 |254 |
|Illinois |17 |1 |
|Indiana |18 |6 |
|Iowa |19 |15 |
|Kansas |20 |200 |
|Kentucky |21 |6 |
|Louisiana |22 |18 |
|Maine |23 |43 |
|Massachusetts |25 |1 |
|Michigan |26 |208 |
|Minnesota |27 |454 |
|Mississippi |28 |80 |
|Missouri |29 |1 |
|Montana |30 |559 |
|Nebraska |31 |180 |
|Nevada |32 |267 |
|New Mexico |35 |727 |
|New York |36 |258 |
|North Carolina |37 |244 |
|North Dakota |38 |432 |
|Oklahoma |40 |3091 |
|Oregon |41 |332 |
|Pennsylvania |42 |248 |
|Rhode island |44 |1 |
|South Carolina |45 |4 |
|South Dakota |46 |1325 |
|Tennessee |47 |1 |
|Texas |48 |9 |
|Utah |49 |122 |
|Virginia |51 |28 |
|Washington |53 |575 |
|Wisconsin |55 |376 |
|Wyoming |56 |94 |
COUNTY – Columns 39-42
County (ICPSR code)
Universe: All persons.
Description:
COUNTY identifies the household's county of enumeration using the Inter-University Consortium for Political and Social Research (ICPSR) coding scheme. Counties are assigned codes alphabetically within states. The first 3 digits are identical to the FIPS county codes used in other datasets; ICPSR adds a digit to the FIPS codes to accommodate change over time (in general, if a county merged with another or was renamed before 1970, it receives an extra digit of "5"). Like STATEICP, COUNTY allows the IPUMS data to be easily merged with ICPSR data. The variable also identifies areas that were not part of any county, including the independent cities of Virginia. COUNTY is a state-dependent variable; it must be read with one of the STATE variables (STATEICP, STATEFIP) to distinguish between counties located in different states.
Note that many county boundaries and some county names changed over time. We have not attempted to impose a uniform county boundary system on the data, so a particular county listed for a particular year in the IPUMS should be assumed to have the boundaries that it had in that year.
Codes:
See ipums.umn.edu/usa/volii/ICPSR.html for a listing of county codes.
SEA – Columns 44-46
State economic area
Universe: All persons.
Description:
SEA stands for State Economic Area, a concept described fully in Donald J. Bogue, State Economic Areas, (Washington D.C., 1951). SEAs are generally either single counties or groups of contiguous counties within the same state that had similar economic characteristics when they were originally defined prior to the 1950 census.
The census first used SEAs in 1950 and the concept was applied retroactively to the 1940 sample. We constructed SEAs for 1850-1930 for the IPUMS by combining counties to match as closely as possible the components of the 1940-1950 SEAs. However, shifts in county boundaries, primarily resulting from the creation of new counties as populations shifted and grew, mean that these earlier SEAs do not always contain exactly the same territory as their 1940-1950 counterparts (see COUNTY). This is particularly true of areas with relatively small populations in earlier years which generally had more unstable county boundaries. There are exceptions, of course. Users who need to know the precise boundaries of counties for earlier years can refer to the boundary files available from Geoscience Publications; see COUNTY for information.
Codes:
See ipums.umn.edu/usa/volii/seacodes.html for listing of SEA codes.
METRO – Column 47
Metropolitan status
Universe: All persons.
Description:
METRO indicates whether metropolitan-area households resided within a metropolitan area's central city (or cities), or within the remainder of the metropolitan area. It also indicates which households were not in a metropolitan area.
Codes:
| |Code |Frequency |
|Not in metro area |1 |12328 |
|In metro area, central city |2 |85 |
|In metro area, not central city |3 |143 |
METAREA – Columns 48-51
Metropolitan area - Detailed
Universe: All persons.
Description:
Metropolitan areas are counties or combinations of counties centering on a substantial urban area. METAREA identifies the household's metropolitan area of enumeration if the household was located in a metropolitan area large enough to meet confidentiality requirements.
Codes:
See ipums.umn.edu/usa/hgeographic/metareagb.html for a listing of METAREA codes.
METDIST – Columns 52-55
Metropolitan district
Universe: All persons.
Description:
METDIST identifies each household's Metropolitan District of enumeration. Prior to the introduction of Standard Metropolitan Areas (SMAs) in 1950, the Census Bureau used a metropolitan classification known as Metropolitan Districts. These metropolitan areas were made up of large urban centers and "thickly settled" adjacent minor civil divisions. Metropolitan Districts, as implemented in the IPUMS, use a variation of the Census Bureau's 1940 definition. IPUMS Metropolitan Districts are composed of urban centers with populations of at least 50,000, along with contiguous minor civil divisions that have population densities of at least 150 persons per square mile. The criteria for designating urban centers as central cities are almost identical to those used for SMAs; see METAREA for more details about SMA classification.
CITY – Columns 56-59
City name - Detailed
Universe: All persons.
Description:
CITY identifies the household's city of residence if the household resided in one of the cities identified in a given sample. To see which cities are identified for each year, check the codes and frequencies table below. The detailed code allows the identification of some cities that merged with others in the past, but most users will probably find this extra detail unnecessary.
Codes:
See ipums.umn.edu/usa/hgeographic/citydb.html for a listing of CITY codes.
CITYYPOP – Columns 60-64
City name - Detailed
Universe: All persons.
Description:
CITYPOP gives the population in hundreds for all incorporated municipalities.
Codes: See text above.
SIZEPL – Columns 65-66
Size of place
Universe: All persons.
Description:
SIZEPL is a recode of CITYPOP that groups places of similar sizes.
Codes:
| |Code |Frequency |
|Under 1,000, or unincorporated |1 |11847 |
|1,000 - 2,499 |2 |162 |
|2,500 - 3,999 |3 |39 |
|4,000 - 4,999 |4 |22 |
|5,000 - 9,999 |5 |389 |
|10,000 - 24,999 |6 |6 |
|25,000 - 49,999 |7 |6 |
|75,000 - 99,999 |9 |43 |
|200,000 - 299,999 |20 |1 |
|1,000,000 - 1,999,999 |80 |41 |
URBAN – Column 67
Urban/rural status
Universe: All persons.
Description:
URBAN indicates whether the household's location was urban or rural. Definitions of "urban" vary from year to year, but the term generally denotes places of 2,500+ people. (All areas not classified as urban are designated rural.)
Codes:
| |Code |Frequency |
|Rural |1 |12007 |
|Urban |2 |549 |
URBAREA – Columns 68-71
Urban area
Universe: All persons.
Description:
URBAREA identifies urbanized areas, which includes central cities and the densely populated areas immediately adjacent to the central city. Generally, a UA contains the urban and excludes the rural parts of a particular metropolitan area. Like metropolitan areas, they may cross state boundaries. Some metropolitan areas contain more than one UA, and some UAs extend beyond metropolitan area boundaries and occasionally into another metropolitan area. A few UAs denote areas not within any metropolitan area.
Codes:
See ipums.umn.edu/usa/volii/1980urbarea.html for a listing of URBAREA codes.
GQ – Column 72
Group quarters status
Universe: All persons.
Description:
GQ classifies all units as falling into one of three main categories: households, group quarters, or vacant units. It also identifies fragmentary sample units in some sample years. In all years, the data available about a person and their coresidents depends on whether the person lives in a household or group quarters. Households are sampled as units, meaning that everyone in the household is included in the sample and household-level variables are available. People living in group quarters are sampled as individuals; other people in their unit may or may not be included in the sample and there is no way of linking co-residents' records to one another. Household-level variables are occasionally not available for residents of group quarters.
Group quarters are generally institutions and other group living arrangements such as rooming houses and military barracks. The definitions vary from year to year, but in the IPUMS we have generally used a group quarters definition that includes units with 10 or more individuals unrelated to the householder.
Codes:
| |Code |Frequency |
|HH in 1970 definition, but sampled as larger unit |1 |10216 |
|Additional hhs under 1990 definition |2 |19 |
|Institution |3 |96 |
|Other group quarters |4 |2218 |
|Fragment |6 |7 |
GQTYPE – Columns 73-75
Group quarters type - Detailed
Universe: Group quarters.
Description:
GQTYPE describes in detail the type of group quarters in which a group-quarters member resided.
Codes:
| |Code |Frequency |
|NA (non-group quarters households) |0 |10235 |
|Family group, someone related to head |10 |5 |
|Prison |211 |21 |
|Penitentiary |212 |33 |
|Jail |221 |1 |
|Orphans home, asylum |432 |41 |
|Hotel |801 |11 |
|House, lodging apartments |802 |22 |
|Schools |910 |66 |
|Boarding schools |911 |5 |
|Academy, institute |912 |17 |
|Industrial training |913 |5 |
|Indian school |914 |2077 |
|Mission |934 |4 |
|Farms, ranches |945 |2 |
|Other group quarters |960 |4 |
|Fragment (boarders and lodgers, 1900) |999 |7 |
GQFUNDS – Columns 76-77
Group quarters funding
Universe: Group quarters.
Description:
GQTYPE describes in detail the type of group quarters in which a group-quarters member resided.
Codes:
| |Code |Frequency |
|N/A |0 |10235 |
|Federal support |11 |223 |
|State support |13 |66 |
|Local support |14 |1 |
|Government, not specified |16 |1880 |
|Private, Nonprofit |21 |56 |
|Private, Commercial |22 |35 |
|Religious |23 |48 |
|Private, unknown |25 |5 |
FARM – Column 78
Farm status
Universe: All persons.
Description:
FARM identifies farm households. All group quarters are coded as non-farm. Census methods for defining and identifying farms have changed several times. For 1900, the census counted a household as a farm if a member of the household operated a farm. It is not possible to tell whether or not the household actually lived on or owned the farm they operated in 1900.
Codes:
| |Code |Frequency |
|Non-Farm |1 |7336 |
|Farm |2 |5220 |
FARMSCHD – Column 79
Farm Schedule
Universe: All persons.
Description:
FARMSCHD indicates whether any member of the household received a farm schedule to be filled out for the agricultural census. The IPUMS variable PFARMSCH indicates which people within the household filled out the farm schedule(s).
Codes:
| |Code |Frequency |
|No |1 |8203 |
|Yes, 1 schedule |2 |4275 |
|Yes, 2 schedules |3 |70 |
|Yes, 3 schedules |4 |6 |
|Yes, 4 schedules |5 |2 |
OWNERSHP – Columns 80-81
Ownership of dwelling - Detailed
Universe: Not Group Quarters.
Description:
OWNERSHP indicates whether the household rented or owned its housing unit. Households that acquired their unit with a mortgage or other lending arrangement are understood to "own" their unit even if they had not yet completed repayment.
Codes:
| |Code |Frequency |
|N/A |0 |2321 |
|Owned or being bought |10 |9286 |
|Rented |20 |949 |
MORTGAGE – Column 82
Ownership of dwelling - Detailed
Universe: Not Group Quarters.
Description:
MORTGAGE indicates whether or not owner-occupied housing units were owned free and clear or encumbered by a mortgage, loan, or other type of debt. (See also OWNERSHP.)
Codes:
| |Code |Frequency |
|N/A |0 |3270 |
|No, owned free and clear |1 |9165 |
|Yes, mortgaged/ deed of trust or similar debt |3 |121 |
WARD – Columns 84-86
Ward
Universe: All persons.
Description:
WARD is an unrecoded variable that identifies the household's political ward of enumeration if the household was located in an area (usually a large city) that was divided into wards. Households not located within an identifiable ward are assigned an IPUMS code of "000."
Codes: See text above.
SAMPRULE – Column 99
Sampling rule
Universe: All persons.
Description:
SAMPRULE identifies the sampling rule used for each case. SAMPRULE differs from GQ because it refers to the original sampling rules, whereas GQ has been adjusted to conform to modern definitions. Essentially, cases may be taken as entire dwellings, households, related groups, or individuals according to the following rules (which sometimes differ among census samples):
1 = A household in a dwelling with fewer than 31 persons; all households (1 or more) in the dwelling were sampled.
2 = A household in a dwelling with more than 30 persons. This household was the only one in the dwelling that was sampled.
3 = A group of related individuals sampled within a unit with more than 30 persons.
4 = Individuals sampled within units with more than 30 persons.
5 = A household fragment (see GQ).
Codes: See text above.
REEL – Columns 100-103
Microfilm reel number
Universe: All persons.
Description:
REEL gives the National Archives number of the microfilm reel from which the case was entered. For each year, REEL can be used in conjunction with other variables to locate and view the case as it appeared on the original census form
Codes: See text above.
PAGENO – Columns 106-109
Microfilm page number
Universe: All persons.
Description:
PAGENO gives the microfilm page number from which the case was entered. For 1900 these are the page numbers stamped on the forms before microfilming.
Codes: See text above.
LINE – Columns 115-117
Line number
Universe: All persons.
Description:
LINE gives the census-form line number of the randomly selected sample point that identifies the case. LINE can be used in conjunction with other variables to locate and view the case as it appeared on the original census form - see REEL.
Codes: See text above.
PAGESEQ – Column 119
Microfilm sequence number
Universe: All persons.
Description:
On some microfilm reels, the page numbers are not unique (they start over again from "1"). MICROSEQ identifies which sequence of page numbers within the microfilm reel the case was drawn from.
MICROSEQ can be used in conjunction with REEL, PAGENO, and LINE to locate the case as it appeared on the original census form - see REEL.
Codes: See text above.
ENUMMO – Columns 120-121
Month of enumeration
Universe: All persons.
Description:
ENUMMO gives the month in which the enumerator began to gather information for the census page containing the case.
Codes: See text above.
ENUMDAY – Columns 122-123
Day of enumeration
Universe: All persons.
Description:
ENUMDAY, which should be read with ENUMMO, gives the day of the month in which the enumerator began to gather information for the census page containing the case.
Codes: See text above.
ENUMDIST – Columns 128-131
Enumeration district
Universe: All persons.
Description:
ENUMDIST gives the household's census enumeration district.
Codes: See text above.
SUPDIST – Columns 132-134
Supervisor’s district number
Universe: All persons.
Description:
SUPDIST gives the household's census supervisor’s enumeration district.
Codes: See text above.
STREET – Columns 157-188
Street Address
Μ User Caution: STREET is an alphabetic variable.
Universe:
All households and group quarters.
Description:
STREET is an alphabetic variable that reports the household's entire street address, as written on the original census form.
Codes: See text above.
NFAMS – Columns 190-191
Number of families in household
Universe: All persons.
Description:
NFAMS is a constructed variable that indicates the number of families within each household. A "family" is any group of persons related by blood, adoption, or marriage. An unrelated individual within the household is considered a separate family. Thus, a household consisting of a widow and her servant contains two families; a household consisting of a large, multiple-generation extended family with no boarders, lodgers, or servants would count as a single family.
Codes: See text above.
NCOUPLES – Column 192
Number of married couples in household
Universe: All persons.
Description:
NCOUPLES is a constructed variable (using SPLOC) that counts the number of married couples within each household.
Codes: See text above.
NMOTHERS – Column 193
Number of mothers in household
Universe: All persons.
Description:
NMOTHERS is a constructed variable (using MOMLOC) that indicates the number of mothers within each household.
Codes: See text above.
NFATHERS – Column 194
Number of fathers in household
Universe: All persons.
Description:
NFATHERS is a constructed variable (using POPLOC) that indicates the number of fathers within each household.
Codes: See text above.
QMORTGAG – Column 208
Mortgage status – Data quality flag
Universe: All persons.
Description:
See ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QFARM – Column 214
Farm status – Data quality flag
Universe: All persons.
Description:
See ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QGQ – Column 219
Group quarters status – Data quality flag
Universe: All persons.
Description:
See ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QOWNERSH – Column 223
Ownership of dwelling – Detailed – Data quality flag
Universe: All persons.
Description:
See ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QGQTYPE – Column 241
Group quarters type – Detailed – Data quality flag
Universe: All persons.
Description:
See ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
FIPSMCD – Columns 505-509
Minor civil division FIPS code
Universe: All persons.
Description:
FIPSMCD provides the Federal Information Processing Standards (FIPS) codes for minor civil divisions. Minor civil divisions are the principle independent political division at the sub-county level. Historically, the most common example of a minor civil division is the township, but they have a variety of state-specific descriptive terms, including town, precinct, beat, and district.
Coding of FIPSMCD was based on a listing of codes used for the 1990 U. S. census. However, many minor civil divisions that we encounter in the historical census data no longer exist because of political and administrative reorganization at the sub-county level. In these cases we assigned non-standard FIPS codes consistent with the present-day FIPS coding format.
All FIPSMCD codes are unique within each state (i.e., to identify a specific minor civil division, you must combine the FIPSMCD code with either STATEICP or STATEFIP).
Codes:
See
FIPSINC – Columns 510-514
Incorporated municipality FIPS code
Universe: All persons.
Description:
FIPSINC provides the Federal Information Processing Standards (FIPS) codes for incorporated municipalities (e.g., cities and villages).
Coding of FIPSINC was based on a listing of codes used for the 1990 U. S. census. In cases where a specific incorporated municipality no longer exists, we assigned non-standard FIPS codes consistent with the present-day FIPS coding format
All FIPSINC codes are unique within each state (i.e., to identify a specific incorporated municipality, you must combine the FIPSINC code with either STATEICP or STATEFIP).
Codes:
See
NENGPOP – Columns 517-521
New England town population
Description:
NENGPOP gives the population in hundreds for minor civil divisions in New England, including towns and independent cities. For New England towns with incorporated municipalities, NENGPOP will be larger than the population reported in CITYPOP, which reports the portion of the town population considered “urban” by the Census Bureau’s 1930 definition. Using NENGPOP, users can construct a definition of “urban” compatible with the published reports of censuses prior to 1930.
Codes: See text above.
IHOME – Column 526
Type of home
Universe: All persons.
Description:
The Indian schedule contained the question: “Is this Indian living in a fixed or movable dwelling.”
Codes:
| |Code |Frequency |
|Movable |1 |1862 |
|Fixed |2 |8383 |
|Illegible |8 |12 |
|Blank |9 |2101 |
URBPOP – Column 551-555
Population of urbanized area
Universe: All persons.
Description:
URBPOP gives the population of places considered "urban" according to the Census Bureau's 1930-1940 definition. All incorporated municipalities with a population of 2,500 or more were defined as urban, but this definition of urban also included some places that were not incorporated municipalities.
Codes: See text above.
Data Dictionary – Person
RECTYP – Column 1
Record Type
Universe: All persons.
Description:
RECTYP assigns all person records the alphabetic string "P" This allows users to discriminate between household and person records; the former are assigned the string "H in the household variable RECTYP.
Codes and Frequencies:
|Code |Frequency |
|P |45651 |
YEAR – Columns 2-3
Census Year
Universe: All persons.
Description:
YEAR identifies the census year of each case. YEAR is repeated on person records. The middle two digits of the census year are used: 90 indicates 1900.
Codes: See text above.
DATANUM – Columns 4-5
Dataset number
Universe: All persons.
Description:
DATANUM identifies the sample from which the case is drawn.
Codes: See text above.
SERIAL – Columns 6-13
Household serial number
Universe: All persons.
Description:
SERIAL is an identifying number unique to each SERIAL is an identifying number unique to each household in a given census year sample. All person records are assigned the same serial number as the household record that they follow. (Person records also have their own unique identifiers—see PERNUM) A combination of YEAR, DATANUM, and SERIAL provides a unique identifier for every household in the IPUMS; YEAR, DATANUM, SERIAL, and PERNUM uniquely identify every person in the database. In addition, the first six digits of SERIAL in 1900 provide the dwelling number, for cases in which more than one household was sampled from a structure. In these years, the last two digits of SERIAL give the sequence of the household within the dwelling.
Codes: See text above.
PERNUM – Columns 14-15
Person number in sample unit
Universe: All persons.
Description:
PERNUM numbers all persons within each household consecutively (starting from "1" for each household) in the order in which they appear on the original census form. When combined with YEAR, DATANUM, and SERIAL, PERNUM uniquely identifies each person within the IPUMS.
Codes: See text above.
PERWT – Columns 20-23
Person weight
Universe: All persons.
Description:
PERWT indicates how many persons in the U.S. population are represented by a given person in an IPUMS sample. All records in the Indian sample have a PERWT of 5. For the 1900 Indian sample the use of the weight is optional, since every case represents the same number of individuals in the population (approximately equal to the sample density).
Codes: See text above.
MOMLOC – Columns 26-27
Mother’s location in household
Universe: All persons.
Description:
MOMLOC is a constructed variable that indicates whether or not the person's mother lived in the same household and, if so, gives the person number of the mother (see PERNUM). The method by which probable child-mother links are identified is described in MOMRULE; see also Chapter 5, "Family Inter-relationships" for a general discussion of IPUMS-constructed family interrelationship variables.
MOMLOC makes it easy for researchers to link the characteristics of children and their (probable) mothers.
User Caution: MOMLOC identifies social relationships (such as stepmother and adopted mother) as well as biological relationships. Researchers wishing to exclude these social relationships from their analysis should use STEPMOM as well.
Codes: See text above.
STEPMOM – Column 28
Probable step/adopted mother
Universe: All persons.
Description:
STEPMOM indicates whether a person's mother, as identified by MOMLOC, was likely to have been the person's stepmother or adoptive mother. Non-zero values of STEPMOM explain why it is probable that the person's mother was a step- or adopted mother. A value of 0 indicates no likely stepmother because (1) the mother identified in MOMLOC was probably the biological mother or (2) there is no mother of this person present in the household. We assume that the mother is the biological mother if she is (1) the householder and reported the child to be her son/daughter, or (2) the wife of the householder, who reported the child to be his son/daughter. Users should note that there are many stepmothers and adopted mothers in the population that cannot be identified with information available in the census. Therefore, STEPMOM will always underrepresent their actual number in the population.
See MOMRULE and the general discussion of IPUMS-constructed family interrelationship variables in Chapter 5, "Family Interrelationships."
0 = Biological mother or no mother of this person present in household.
1 = Age difference between mother and child was less than 15 or greater than 49 years .
2 = Link was established only because the mother was married to the father (using SPLOC). The listed order of family members on the census form is non-standard.
3 = Census explicitly identified as stepmother.
4 = Mother has 0 children surviving.
5 = Census explicitly identified as adopted.
6 = Child is older than mother's current marriage and mother's response in BPL does not match child's response in MBPL.
7 = If the number of children linked to each mother exceeds the number of children born or the number of children surviving (whichever is valid), unlink the eldest child(ren) with the same surname unless the mother is listed as wife and the child is listed as a stepchild of the head.
If more than one value applied to the case, the lowest value was assigned.
Codes: See text above.
MOMRULE – Column 29
Rule for linking mother
Universe: All persons.
Description:
MOMRULE explains why the IPUMS variable MOMLOC linked the person to a probable mother. The IPUMS establishes mother-child links according to seven basic rules, and MOMRULE gives the number of the rule that applied to the link in question. If a link could be made according to more than one rule, the lower-numbered rule was the one applied. See also MOMLOC, STEPMOM, and Chapter 5, "Family Interrelationships" for more information on these constructed variables.
Comparability:
This variable is comparable across census years. Users who wish to limit their analysis to links that could be made for all years should eliminate from their research universe all persons for whom MOMRULE = 4, 5, 6, or 7. (Few links were made using these four rules; over 95% of the links were made using rule 1 alone.)
0 = No mother of this person present in the household.
1 = Unambiguous relationship, based upon relationships to the head of household as listed on the census record. This covers three basic cases:
1. a person listed as a son or daughter is linked to a person listed as wife/spouse.
2. a person listed as head, brother, or sister is linked to a person listed as mother.
3. a person listed as wife, brother-in-law, or sister-in-law is linked to a person listed as mother-in-law.
2 = Persons listed as grandchildren are linked to the most proximate preceding (on the census form) ever-married daughter, unmarried daughter (if immediately followed by a grandchild), or daughter-in-law of the head if the daughter/daughter-in-law is 11-59 years older than the grandchild. If no link is formed with a preceding female, the program looks for the most proximate subsequent female who satisfies the same criteria.
3 = Other persons are linked to any preceding ever-married female who is 15-49 years older so long as:
1. the two persons have listed relationships to the head that, when compared with one another, make a child-mother link plausible, and
2. there are no persons listed between the potential child and mother, except the potential mother's other children or husband.
4 = Same as rule 3, but surname similarity overrides part b of rule 3. If more than one potential mother is found in this way, the most proximate is linked. This rule can be applied only to samples with surname codes: 1880 to 1950.
5 = Same as rule 2, except evidence on children-ever-born (or children surviving for 1900 and 1910) overrides the potential mother's lack of "ever-married" status. This rule can be applied only to samples with children-ever-born or children surviving information: 1900, 1910, 1960, 1970, 1980, and 1990.
6 = Same as rule 3, except evidence on children-ever-born (or children surviving for 1900 and 1910) overrides the potential mother's lack of "ever-married" status. Like rule 5, this rule can be applied only to the 1900, 1910, 1960, 1970, 1980, and 1990 samples.
7 = If the child is already linked to a father (see POPLOC and POPRULE), and that father has a wife present in the household who has not been linked to the child by another rule, the wife is linked to the child as a stepmother, regardless of the age gap between child and wife.
Consistency checks:
1. If a husband and wife were both linked to the same mother, the IPUMS chose the best mother link based on detailed relationship, surname, and proximity within the household as listed on the census form.
2. If both parents were present but they were not married to each other, the IPUMS unlinks the one with the mismatched surname. For years that lack surname (1960 to 2000), the least proximate parent is unlinked.
Codes: See text above.
POPLOC – Columns 30-31
Father’s location in household
Universe: All persons.
Description:
POPLOC is a constructed variable that indicates whether or not the person's father lived in the same household and, if so, gives the person number (see PERNUM) of the father. The method by which probable child-father links are identified is described in POPRULE; see also Chapter 5, "Family Interrelationships."
POPLOC makes it easy for researchers to link the characteristics of children and their (probable) fathers.
User Caution: POPLOC identifies social relationships (such as stepmother and adopted mother) as well as biological relationships. Researchers wishing to exclude these social relationships from their analysis should use STEPPOP.
Codes: See text above.
STEPPOP – Column 32
Probable step/adopted father
Universe: All persons.
Description:
STEPPOP indicates whether or not a person's father, as identified by the IPUMS variable POPLOC, was likely to have been the person's stepfather or adoptive father. Non-zero values of STEPPOP explain why it is probably that the person’s father was a step- or adopted father. A value of 0 indicates no likely stepfather because (1) the father identified in POPLOC was probably the biological father or (2) there is no father of this person present in the household. We assume that the father is the biological father if he is (1) the householder and reported the child to be his son/daughter, or (2) the husband of the householder, who reported the child to be her son/daughter. From 1940-1990, the category "son/daughter" included adopted and/or stepchildren as well as biological children (see RELATE). Users should note that there are many stepfathers and adopted fathers in the population that cannot be identified with information available in the census. Therefore, STEPPOP will always underrepresent their actual number in the population.
See POPRULE and Chapter 5 on "Family Interrelationships" for a more complete explanation.
0 = Biological father or no father of this person present in household.
1 = Age difference between father and child was less than 15 or more than 64 years.
2 = Link was established only because the father was married to mother. The listed order of family members on the census form is non-standard.
3 = Census explicitly identified as stepfather—information not available for 1960, 1970, or 1980.
5 = Census explicitly identified as adopted—information available only for 1880, 1900, 1910, and 1920.
6 = Child is older than father's marriage (current marriage for 1900 and 1910, first marriage for 1960 and 1970), and father's response in BPL does not match child's response in FBPL.
7 = Surname differs and child is a male or never-married female (female under age 15, 1850-1870).
If more than one value applied to the case, the lowest value was assigned.
Codes: See text above.
POPRULE – Column 33
Rule for linking father
Universe: All persons.
Description:
POPRULE explains why the IPUMS variable POPLOC linked the person to a probable father. Father-child links were established according to five basic rules, and POPRULE gives the number of the rule that applied to the link in question. If a link could be made according to more than one rule; the lower-numbered rule was the one applied. See also POPLOC, STEPPOP, and Chapter 5 on "Family Interrelationships" for a discussion of these IPUMS-constructed variables.
Comparability:
This variable is comparable across census years. Users who wish to limit their analysis to links that could be made for all years should eliminate from their research universe all persons for whom POPRULE = 4 or 7. (Few links were made using these two rules; over 95% of the links were made using rule 1 alone.)
0 = No father of this person present in household.
1 = Unambiguous relationship, based upon relationships to the head of household as listed on the census record. This covers three basic cases:
1. a person listed as a son or daughter is linked to the person listed as head.
2. a person listed as head, brother, or sister is linked to the person listed as father.
3. a persons listed as wife, brother-in-law, or sister-in-law is linked to a person listed as father-in-law.
2 = Persons listed as grandchildren are linked to the most proximate preceding (on the census form) ever-married son, an unmarried son (if immediately followed by the grandchild), or son-in-law of the head if the son/son-in-law is 15-79 years older than the grandchild. If no link is formed with a preceding male, the program looks for the most proximate subsequent male who satisfies these criteria.
3 = Other persons are linked to any preceding ever-married male who is 15-64 years older so long as:
1. the two persons have listed relationships to the head that, when compared with one another, make a child-father link plausible, and
2. there are no persons listed between the potential child and father, except the potential father's other children or wife.
4 = Same as rule 3, but surname similarity overrides part b of rule 3. If more than one potential father is found in this way, the most proximate preceding male is linked. This rule can be applied only to samples with surname codes: 1880 to 1950.
7 = If the child is already linked to a mother (see MOMLOC and MOMRULE), and that mother has a husband present in the household who has not been linked to the child by another rule, the husband is linked to the child as a stepfather, regardless of the age difference between the child and the stepfather.
Consistency Checks:
1. If the child was linked to a father and mother who were not married to one another, the IPUMS unlinked the father. If a husband and wife were both linked to the same father and/or mother, the IPUMS chose the best parental link based on detailed relationship, surname, and proximity within the household as listed on the census form.
2. If both parents were present but they were not married to each other, the IPUMS unlinks the one with the mismatched surname. For years that lack surname (1960 to 2000), the least proximate parent is unlinked.
Codes: See text above.
SPLOC – Columns 34-35
Spouse’s location in household
Universe: All persons.
Description:
SPLOC is a constructed variable that indicates whether or not the person's spouse lived in the same household and, if so, gives the person number (PERNUM) of the spouse. The method by which probable spouse-spouse links are identified is described in SPRULE.
SPLOC makes it easy for researchers to link the characteristics of (probable) spouses.
Codes: See text above.
SPRULE – Column 36
Rule for linking father
Universe: All persons.
Description:
SPRULE explains why the IPUMS variable SPLOC linked the person to a probable spouse. The IPUMS establishes spouse-spouse links according to five basic rules, and SPRULE gives the number of the rule that applied to the link in question. See Chapter 5 on "Family Interrelationships" for more information on IPUMS-constructed family interrelationship variables.
This variable works the same way for all years.
0 = No spouse of this person present in household.
1 = A married woman and a married man were linked because she was listed immediately after him on the census form and both persons’ relationship to the household head/householder, when compared with one another, justified a link, as follows:
Man's relationship to head Woman's relationship to head
Head of household Wife
Son Daughter-in-law
Father Mother
Father-in-law Mother-in-law
Brother Sister-in-law
Brother-in-law Sister
2 = Same as rule 1, but the married woman's name appeared immediately before the married man's name on the census form.
3 = A married woman and a married man who did not appear adjacently on the census form were linked because
1. they had one of the relationship sets listed in rule 1;
2. they were both age 16+;
3. the man was not more than 25 years older than the woman; and
4. the woman was not more than 10 years older than the man
4 = A married woman whose relationship to the head was not listed, or did not match the married man's as specified in rule 1, was still linked to a married man because he was listed immediately before her on the census form, their ages fit parts c and d of rule 3, and the resulting link did not link a nonrelative to a relative.
5 = Same as rule 4, but the married woman's name appeared immediately before the married man's name on the census form.
6 = For links made under rules 1-5, check to see if this link creates an inconsistency with SURSIM, surname similarity, (in pre-1960 years other than 1900 and 1910) or DURMARR, duration of marriage, (in 1900 and 1910) or AGEMARR, age of first marriage (for those married at least once in 1960-1980). If a conflict is identified, search the household for alternative partner.
Codes: See text above.
FAMSIZE – Columns 37-38
Number of own family members in household
Universe: All persons.
Description:
FAMSIZE counts the number of the person's own family members living in the household with her/him, including the person her/himself. For all years except 1850-1870, these include all persons that the census form indicates are related to the person by blood, adoption, or marriage (see RELATE); for 1850-1870, relationships determined in IMPREL (Imputed relationship) are used. FAMSIZE also incorporates information contained in MOMLOC, IMPMOM, POPLOC, IMPPOP, SPLOC, and IMPSP. These IPUMS-constructed variables are discussed in Chapter 5 on "Family Interrelationships."
Codes: See text above.
NCHILD – Column 39
Number of own children in household
Universe: All persons.
Description:
NCHILD counts the number of the person's own children (of any age or marital status) living in the household with her/him. From 1880 to 2000 these include all children linked to the person via MOMLOC/MOMRULE or POPLOC/POPRULE. 1850-1870 use IMPMOM and IMPPOP to locate own children.
Codes: See text above.
NCHLT5 – Column 40
Number of own children in household
Universe: All persons.
Description:
NCHLT5 counts the number of the person's own children age 4 and under living in the household with her/him. From 1880 to 2000 these include all children of this age linked to the person via MOMLOC/MOMRULE or POPLOC/POPRULE. 1850-1870 use IMPMOM and IMPPOP to locate own children.
Codes: See text above.
FAMUNIT – Columns 41-42
Family unit membership
Universe: All persons.
Description:
FAMUNIT indicates which family within the household each person belongs to. If there is only one group of related individuals within the household, all of them will be coded "1;" if there is a second, separate such group listed on the form, all of them will be coded "2," and so on. All persons with a RELATE code less than "1100" are included in FAMUNIT "1". See our general discussion of these IPUMS-constructed variables in Chapter 5, "Family Interrelationships," for further information.
The Census Bureau defines "primary families" as groups of persons related to the head of household, and "primary individuals" as household heads/householders residing without kin. In the IPUMS, primary families and primary individuals are identified in FAMUNIT with a code of "1;" each secondary family or secondary individual receives a higher code.
FAMUNIT is not analagous to the Census Bureau concept of "subfamily." People in "subfamilies" are necessarily related to the householder, and will be included in FAMUNIT "1."
Under the definition of group quarters used for the 1940-1970 census years, there can be a maximum of five families in a household; in 1980-2000, the maximum is 9. See GQ. In 1850-1870, FAMUNIT is based on IMPREL.
Codes: See text above.
ELDCH – Columns 43-44
Age of eldest own child in household
Universe: All persons.
Description:
ELDCH gives the age of the person's eldest own child (if any) living in the household with her/him, regardless of the child's age or marital status. From 1880 to 2000 these include all children linked to the person via MOMLOC/MOMRULEor POPLOC/POPRULE. 1850-1870 use IMPMOMand IMPPOP to locate own children. ELDCH includes step-children and adopted children as well as biological children.
Codes: See text above.
YNGCH – Columns 45-46
Age of youngest own child in household
Universe: All persons.
Description:
YNGCH gives the age of the person's youngest own child (if any) living in the household with her/him, regardless of the child's age or marital status. From 1880 to 2000 these include all children linked to the person via MOMLOC/MOMRULE or POPLOC/POPRULE. 1850-1870 use IMPMOM and IMPPOP to locate own children. YNGCH includes step-children and adopted children as well as biological children.
Codes: See text above.
NSIBS – Column 47
Number of own siblings in household
Universe: All persons.
Description:
NSIBS counts the number of the person's own siblings (including half-siblings, step-siblings, and adopted siblings) living in the household with her/him. Persons with no siblings present are coded "0." NSIBS is generally based on information contained in RELATE (Relationship to household head) for all years except 1850-1870. In these years it is constructed from IMPREL (Imputed relationship).
In addition to the information from RELATE/IMPREL, NSIBS counts the number of children linked to the same mother or father via MOMLOC and POPLOC (or IMPMOM and IMPPOP for 1850-1870).
Codes: See text above.
RELATE – Column 48-51
Relationship to household head - Detailed
Universe: All persons.
Description:
RELATE describes an individual’s relationship to the head of household or householder. Beginning in 1880, data on household relationship was asked of every person. The general relationship code is reasonably comparable across years. The detailed code makes distinctions that cannot be made in all years.
The relationship codes are divided into two categories: relatives (codes 1-10) and non-relatives (codes 11-13). In general, the codes for relatives are self-explanatory. The non-relative codes are divided into three groups: "Partner, Friend, Visitor," roughly described as persons who do not pay or work for their accommodations (unless they share ownership); "Other Non-Relatives," including those persons paying or working for accommodations; and "Institutional Inmates." See the comparability discussion for further information about the coding scheme.
Codes:
| |Code |Frequency |
|Head/Householder |101 |10305 |
|Spouse |201 |7601 |
|2nd/3rd Wife (Polygamous) |202 |163 |
|Child |301 |18352 |
|Adopted Child |302 |82 |
|Stepchild |303 |808 |
|Child-in-law |401 |370 |
|Step Child-in-law |402 |2 |
|Parent |501 |454 |
|Stepparent |502 |20 |
|Parent-in-Law |601 |291 |
|Stepparent-in-law |602 |1 |
|Sibling |701 |695 |
|Step/Half/Adopted Sibling |702 |29 |
|Sibling-in-Law |801 |371 |
|Grandchild |901 |1282 |
|Adopted Grandchild |902 |1 |
|Step Grandchild |903 |15 |
|Grandchild-in-law |904 |10 |
|Grandparent |1011 |75 |
|Grandparent-in-law |1013 |1 |
|Aunt or Uncle |1021 |128 |
|Aunt,Uncle-in-law |1022 |2 |
|Nephew, Niece |1031 |677 |
|Nephew/Niece-in-law |1032 |6 |
|Step/Adopted Nephew/Niece |1033 |6 |
|Grand Niece/Nephew-in-law |1034 |24 |
|Cousin |1041 |237 |
|Cousin-in-law |1042 |1 |
|Great Grandchild |1051 |28 |
|Other relatives, nec |1061 |2 |
|Friend |1111 |4 |
|Partner |1112 |16 |
|Visitor |1131 |7 |
|Boarders |1202 |729 |
|Lodgers |1203 |188 |
|Roomer |1204 |27 |
|Foster child |1206 |47 |
|Servant |1211 |197 |
|Housekeeper |1212 |3 |
|Cook |1214 |4 |
|Other probable domestic employee |1216 |2 |
|Other employee |1217 |114 |
|Relative of employee |1219 |26 |
|Students |1222 |2168 |
|Members of religious orders |1223 |10 |
|Other non-relatives |1230 |39 |
|Institutional inmates |1301 |31 |
AGE – Columns 52-54
Age
Universe: All persons.
Description:
AGE gives the person’s age in years as of their last birthday prior to or on the day of enumeration.
Data on year of birth (BIRTHYR) is also available in 1900.
Codes: See text above.
SEX – Column 55
Sex
Universe: All persons.
Codes:
| |Code |Frequency |
|Male |1 |23283 |
|Female |2 |22368 |
RACE – Column 56-58
Race – Detailed
Universe: All persons.
Description:
RACE was asked of every person in all census years. The concept of race has changed over the 150 years represented in the IPUMS. Currently, the Census Bureau and others consider race to be a socio-political construct, not a scientific or anthropological one. Race categories include national origin groups as well.
Codes:
| |Code |Frequency |
|White |100 |1574 |
|Black/Negro |200 |350 |
|American Indian |300 |43727 |
MARST – Column 59
Marital status
Universe: Persons age 12+ .
Description:
MARST gives each person's current marital status.
Codes:
| |Code |Frequency |
|Married, spouse present |1 |16473 |
|Married, spouse absent |2 |702 |
|Divorced |4 |226 |
|Widowed |5 |3158 |
|Never married/single |6 |25092 |
DURMARR – Columns 60-61
Duration of current marriage
Universe: Currently-married persons.
Description:
DURMARR reports the number of years of each person’s current marriage.
Codes:
| |Code |Frequency |
|Less than 1 year |0 |604 |
|1 year |1 |1087 |
|2 |2 |864 |
|3 |3 |859 |
|4 |4 |774 |
|5 |5 |804 |
|6 |6 |698 |
|7 |7 |656 |
|8 |8 |661 |
|9 |9 |543 |
|10 |10 |910 |
|11 |11 |430 |
|12 |12 |571 |
|13 |13 |339 |
|14 |14 |370 |
|15 |15 |633 |
|16 |16 |371 |
|17 |17 |292 |
|18 |18 |384 |
|19 |19 |269 |
|20 |20 |882 |
|21 |21 |249 |
|22 |22 |308 |
|23 |23 |278 |
|24 |24 |190 |
|25 |25 |466 |
|26 |26 |148 |
|27 |27 |159 |
|28 |28 |159 |
|29 |29 |92 |
|30 |30 |588 |
|31 |31 |98 |
|32 |32 |128 |
|33 |33 |81 |
|34 |34 |59 |
|35 |35 |173 |
|36 |36 |82 |
|37 |37 |44 |
|38 |38 |60 |
|39 |39 |26 |
|40 |40 |313 |
|41 |41 |30 |
|42 |42 |34 |
|43 |43 |28 |
|44 |44 |31 |
|45 |45 |49 |
|46 |46 |14 |
|47 |47 |8 |
|48 |48 |27 |
|49 |49 |16 |
|50 |50 |133 |
|51 |51 |8 |
|52 |52 |14 |
|53 |53 |12 |
|55 |55 |25 |
|56 |56 |4 |
|57 |57 |3 |
|59 |59 |4 |
|60 |60 |16 |
|61 |61 |2 |
|63 |63 |2 |
|65 |65 |2 |
|66 |66 |1 |
|70 |70 |6 |
|73 |73 |2 |
|80 |80 |2 |
|N/A |99 |28476 |
CHBORN – Columns 63-64
Children ever born
Universe: Ever-married females, age 12+ .
Description:
CHBORN reports the number of children ever born to each woman of whom the question was asked. The women were to report all live births by all fathers, whether or not the child was still living; they were to exclude still births, adoptions, and stepchildren.
Codes:
| |Code |Frequency |
|N/A |0 |34654 |
|No children |1 |1560 |
|1 child |2 |1610 |
|2 children |3 |1386 |
|3 |4 |1272 |
|4 |5 |1180 |
|5 |6 |980 |
|6 |7 |798 |
|7 |8 |633 |
|8 |9 |494 |
|9 |10 |359 |
|10 |11 |363 |
|11 |12 |161 |
|12 |13 |103 |
|13 |14 |36 |
|14 |15 |31 |
|15 |16 |15 |
|16 |17 |4 |
|17 |18 |3 |
|18 |19 |2 |
|19 |20 |2 |
|20 |21 |4 |
|23 |24 |1 |
CHSURV – Columns 65-66
Children surviving
Universe: Ever-married females, age 12+ .
Description:
CHSURV indicates how many of the children ever born to each ever-married woman age 12 and over were still living on census day (see CHBORN). This includes all children born to that woman by all fathers, and regardless of the child's current place of residence. Women were not to count adopted or step- children.
Codes:
| |Code |Frequency |
|N/A |0 |34654 |
|No children surviving |1 |2143 |
|1 child |2 |2518 |
|2 children |3 |2075 |
|3 |4 |1549 |
|4 |5 |1073 |
|5 |6 |684 |
|6 |7 |386 |
|7 |8 |260 |
|8 |9 |150 |
|9 |10 |89 |
|10 |11 |41 |
|11 |12 |14 |
|12 |13 |6 |
|13 |14 |4 |
|14 |15 |2 |
|15 |16 |2 |
|16 |17 |1 |
BPL – Columns 67-71
Birthplace - Detailed
Universe: All persons.
Description:
BPL indicates the person's state or foreign country of birth.
Codes:
See ipums.umn.edu/usa/pethnicity/bpldb.html for a listing of birthplace codes.
MBPL – Columns 72-76
Mother’s birthplace - Detailed
Universe: All persons.
Description:
MBPL indicates the state, territory, or foreign country of the person's mother's birth as reported by the respondent. The IPUMS codes for MBPL are the same as for BPL (Birthplace). As with BPL, MBPL has a general code distinguishing places available in multiple years and a detailed code noting places unique to certain years or describing areas that are strictly subsets of other countries.
Codes:
See ipums.umn.edu/usa/pethnicity/mbpldb.html for a listing of birthplace codes.
FBPL – Columns 77-81
Mother’s birthplace - Detailed
Universe: All persons.
Description:
FBPL indicates the state, territory, or foreign country of the person's father's birth as reported by the respondent. The IPUMS codes for FBPL are the same as for BPL (Birthplace). As with BPL, FBPL has a general code distinguishing places available in multiple years and a detailed code noting places unique to certain years or describing areas that are strictly subsets of other countries.
Codes:
See ipums.umn.edu/usa/pethnicity/fbpldb.html for a listing of birthplace codes.
NATIVITY – Column 82
Nativity recode
Universe: All persons.
Description:
NATIVITY is constructed from the IPUMS variables BPL, MBPL, and FBPL. It identifies the respondent as either native-born or foreign-born, and for native-born respondents it indicates whether his/her mother and/or father were native-born or foreign-born. Those U.S. possessions and territories classified as "U.S. outlying areas" in BPL are considered foreign.
Codes:
| |Code |Frequency |
|Both parents native-born |1 |43591 |
|Father foreign, mother native |2 |924 |
|Mother foreign, father native |3 |324 |
|Both parents foreign |4 |271 |
|Foreign-Born |5 |541 |
CITIZEN – Column 83
Citizenship status
Universe: Foreign born men age 21+ .
Description:
CITIZEN reports the citizenship status of those individuals who were not U.S. citizens at birth from 1900-1940 and foreign-born individuals since 1950. In 1870, the variable reports the citizenship status of all men over the age of 20 regardless of birthplace. Respondents are classified as either naturalized or non-citizens. Note that the universe prior to 1920 did not include women and children under age 21, but in 1920-1940 the question was asked of all persons who were not U.S. citizens at birth. In 1950, the universe was expanded to include all foreign-born individuals, regardless of their U.S. citizenship status at birth, introducing the category "Born abroad of American parents." In 1990 and 2000, information was also collected for persons born in outlying U.S. territories (Guam, the U.S. Virgin Islands, the Northern Marianas) and the Commonwealth of Puerto Rico; these persons fall into the N/A category (not foreign-born). Prior to 1950, respondents who were not yet citizens but who had begun the naturalization process ("received first papers") can also be identified. For later years, these persons can not be distinguished from other non-citizens.
Codes:
| |Code |Frequency |
|N/A |0 |45392 |
|Naturalized citizen |2 |109 |
|Not a citizen |3 |134 |
|Has received first papers, but not a citizen |4 |16 |
BIRTHYR – Columns 84-86
Year of birth
Universe: All persons.
Description:
BIRTHYR gives the person's year of birth (891=1891, etc). In addition:
996 = Not Classified
997 = Illegible
998 = Unknown (enumerator response)
999 = Blank
Codes: See text above.
YRIMMIG – Columns 87-89
Year of immigration
Universe: Foreign born.
Description:
YRIMMIG gives the year in which a foreign-born person first entered the United States. Researchers who are interested in the length of time spent in the United States, as opposed to the year of immigration, should see the IPUMS variables YRSUSA1 and YRSUSA2. For 1900 YRIMMIG provides the exact year of immigration. In addition:
0 = N/A
996 = Not Classified
997 = Illegible
998 = Unknown (enumerator response)
999 = Blank
Codes: See text above.
YRSUSA2 – Column 90
Years in the United States, intervalled
Universe: Foreign born.
Description:
YRSUSA2 indicates how long each foreign-born person had been living in the United States. (Researchers who are interested in the year of immigration, as opposed to the length of time spent in the United States, should see the IPUMS variable YRIMMIG.)
Codes:
| |Code |Frequency |
|N/A |0 |45155 |
|0 to 5 years |1 |112 |
|6 to 10 years |2 |74 |
|11 to 15 years |3 |52 |
|16 to 20 years |4 |63 |
|21+ years |5 |195 |
SPEAKENG – Column 108
Speaks English
Universe: Age 10+.
Description:
SPEAKENG indicates whether or not the respondent was able to speak English.
Codes:
| |Code |Frequency |
|N/A |0 |12463 |
|Does not speak English |1 |13557 |
|Yes, speaks English |2 |17535 |
|Unknown |7 |4 |
|Illegible |8 |29 |
|Blank |9 |2063 |
SPANNAME – Column 109
Spanish surname
Universe: All persons.
Description:
SPANNAME identifies persons with Spanish surnames by comparing the surnames with various lists of Spanish surnames.
Codes:
| |Code |Frequency |
|No, not Spanish surname |1 |44446 |
|Yes, Spanish surname |2 |1205 |
SCHOOL – Column 110
School attendance
Universe: All persons.
Description:
SCHOOL indicates whether or not the respondent attended school within a specified period.
Codes:
| |Code |Frequency |
|No, not in school |1 |39163 |
|Yes, in school |2 |6488 |
SCHLMNTH – Columns 111-112
Months in school
Universe: All persons.
Description:
SCHLMNTH indicates the number of months that the respondent attended school during the past year.
Codes:
| |Code |Frequency |
|0 months |0 |2650 |
|1 |1 |89 |
|2 |2 |194 |
|3 |3 |361 |
|4 |4 |374 |
|5 |5 |232 |
|6 |6 |404 |
|7 |7 |358 |
|8 |8 |612 |
|9 |9 |1399 |
|10 |10 |2158 |
|11 |11 |38 |
|12 |12 |269 |
|N/A (blank) |99 |36513 |
LIT – Column 114
Literacy
Universe: Age 10+.
Description:
LIT indicates whether or not the respondent could read and/or write in any language.
Codes:
| |Code |Frequency |
|N/A |0 |12463 |
|No, illiterate (cannot read or write) |1 |18857 |
|Cannot read, can write |2 |27 |
|Cannot write, can read |3 |712 |
|Yes, literate (reads and writes) |4 |13592 |
LABFORCE – Column 118
Labor force status
Universe: Age 16+.
Description:
LABFORCE is a dichotomous variable identifying whether a person participated in the labor force. The definition of labor force participation is considerably different for 1850-1920 than for 1940-2000. From 1850 to 1920, participation is defined as reporting any gainful occupation, as recorded in OCC1950 (except for institutional inmates, as explained below). From 1940 to 1990, participation follows the modern labor force definition as explicated in EMPSTAT: working or seeking work within a specific reference week.
Institutional inmates, as defined in the variable RELATE, are coded as being "not in the labor force" for all years, although such persons were able to report an occupation (OCC/OCC1950) from 1850 to 1920.
The gainful employment (1850-1920) and labor force (1940-2000) definitions are likely to produce different results with respect to seasonal and part-time labor. Also, new workers who were looking for their first job are likely to be reported out of the labor force before 1940, but are classified in the labor force 1940-2000.
Some scholars argue that the labor force and gainful employment definitions create an additional disparity in the measurement of married female labor. Historically, occupational status was inherently somewhat ambiguous for married women, who might have considered their principal occupation "housewife" despite other labor they performed. The labor force concept instituted in 1940 removed some of this ambiguity by treating even a single hour of paid employment as labor force participation. For years prior to 1940, users should carefully examine the enumerator instructions for each year with respect to women and children, since the criteria for gainful employment changed between censuses. Even later censuses applied special rules for the treatment of unpaid family labor.
Codes:
| |Code |Frequency |
|N/A |0 |18757 |
|No, not in labor force |1 |15023 |
|Yes, in labor force |2 |11871 |
OCC1950 – Columns 119-121
Occupation, 1950 basis
Universe: Age 10+.
Description:
OCC1950 recodes information contained in the IPUMS variable OCC into the 1950 Census Bureau occupational classification system. Codes above 970 are non-occupational responses retained in the historical census samples. OCC1950 is intended to enhance comparability of occupational data across all years contained in the IPUMS. The design of OCC1950 is described at length in our general discussion of occupational coding. See Chapter 4, "Occupation Codes and Income Scores." The composition of the occupation categories is described in detail in U.S. Bureau of the Census, Alphabetic Index of Occupations and Industries: 1950 (Washington D. C., 1950).
In 1850-1900 the farm laborer and housekeeper categories are augmented by the following imputation procedures. Any laborer in a household with a farmer is recoded into farm labor. In 1860-1880 any woman with an occupational response of "housekeeper" is recoded into the non-occupational category "keeping house" if she is related to the head of household. These cases are identified by an appropriate data quality flag.
Codes:
See ipums.umn.edu/usa/pwork/occ1950b.html for a listing of OCC1950 codes.
OCC – Columns 122-124
Occupation
Universe: Age 10+.
Description:
OCC reports the person's primary occupation, coded into a contemporary census classification scheme. (Some non-occupational activities are also recorded in the pre-1940 samples.) Generally, the primary occupation is that from which the person earns the most money; if the respondent was not sure about this, s/he was to report the one at which s/he spent the most time. Unemployed persons were to give their most recent occupation. If persons listed more than one occupation, the samples use the first one listed.
The meaning of the OCC codes differs by year and, in 2000, by sample. The methodology by which each year's codes were derived can be found in "Occupation Coding Guidelines" in Volume 2: User’s Guide Supplement. The codes themselves are listed in "Occupation Appendices," in Volume 2: User’s Guide Supplement. In 2000, the Census Bureau suppressed about 7% of occupation codes in the 5% data. Instead of coding these occupations individually, as they did in the 2000 1% data, the bureau included the suppressed occupations in other categories. See the 2000 occupation codes page for specific recodes.
For all years except 1850-1900, the occupations are classified according to the contemporary Census Bureau classification system. In 1850-1900, occupations are classified according to the 1880 system. The classification systems have changed markedly over the years. The 1880 census occupational classification was oriented more to work settings and economic sectors—what is now termed "industry"—than to workers' specific technical functions. The 1910 and 1920 classifications incorporate function as well as setting and sector, and are very detailed. By 1940, the census generally equated occupation with workers' functions, and relegated work setting and economic sector to a separate industry variable. (The IPUMS variables IND and IND1950, available for 1910 to 1990, classify work in this way).
In 1850-1900 the farm laborer and housekeeper categories are augmented by the following imputation procedures. Any laborer in a household with a farmer is recoded into farm labor. Any woman with an occupational response of "housekeeper" is recoded into the non-occupational category "keeping house" if she is related to the head of household. These cases are identified by an appropriate data quality flag.
The IPUMS provides another key occupational variable, OCC1950, which recodes the OCC codes into a common classification system—the one used in 1950. OCC and OCC1950 are discussed at length in our general discussion of occupational coding in Chapter 4, "Occupation Codes and Income Scores."
The term "labor force" and other vital employment concepts are defined in the documentation for the IPUMS variables EMPSTAT and LABFORCE.
User Note:
Enumerator instructions for occupation were often quite long and complicated. The specific wording of the instructions in a given year may affect how particular groups (e.g., women, children, retirees) were enumerated. See "Enumerator Instructions" and "Census Enumeration Forms" in Volume 3: Counting the Past for replications.
Users should also take particular note of the changing universe of persons subject to the occupation question (e.g., the rising minimum ages). Persons currently in the armed forces are out of the universe for OCC from 1960 to 1980, yet persons may still report an occupation in the armed services if they are not in the labor force but their last job (within 5 or 10 years) was in the military.
Codes:
See ipums.umn.edu/usa/volii/88occup.html for a listing of OCC codes.
OCCSCORE – Columns 125-126
Occupational index score
Universe: Age 10+.
Description:
OCCSCORE is a constructed variable that assigns occupational income scores to each occupation on the basis of OCC1950. The construction of this variable is described in Chapter 4, "Occupation Codes and Income Scores," which users should read before using this variable. In essence, OCCSCORE assigns each occupation in all years a value representing the median total income (in hundreds of 1950 dollars) of all persons with that particular occupation in 1950. That is, it provides a continuous measure of occupations according to the economic rewards enjoyed by people working at them in 1950.
Codes:
00=N/A
SEI – Columns 127-128
Duncan Socioeconomic Index
Universe: Age 10+.
Description:
SEI is a constructed variable that assigns a Duncan Socioeconomic Index (SEI) score to each occupation. The SEI, which is based on the 1950 occupational classification system, is a measure of occupational status based upon the income level and educational attainment associated with each occupation in 1950. The score was derived by using median income and education levels for men in 1950 to predict prestige assessments from a 1947 survey (of a select group of occupations). The resulting statistical model was used to generate scores for the entire range of 1950 occupations. See O. D. Duncan, "A Socioeconomic Index for All Occupations," in A. Reiss et al., Occupations and Social Status (Free Press, 1961).
The SEI variable is based on OCC1950. For more information on the construction of that variable, see Chapter 4, "Occupation Codes and Income Scores." Users must judge for themselves how socioeconomic or prestige status may have changed relative to the circa-1950 survey results.
Codes:
00=N/A
Maximum value: 96
IND1950 – Columns 129-131
Industry, 1950 basis
Universe: Age 10+.
Description:
IND1950 recodes information contained in the IPUMS variable IND into the 1950 Census Bureau industrial classification system. We designed it to enhance comparability of industry data across all years for which IND is available. IND1950 was designed the same way as OCC1950 (Occupation, 1950 basis), the procedure for which is discussed in detail in Chapter 4, "Occupation Codes and Income Scores." The composition of the industry categories is described in detail in U.S. Bureau of the Census, Alphabetic Index of Occupations and Industries: 1950 (Washington D. C., 1950).
The term "labor force" and other vital employment concepts are defined in the documentation for the IPUMS variables EMPSTAT and LABFORCE.
Prior to 1910, the census did not directly inquire about industry. In many instances, however, we were able to classify industry based on information in the occupation response. In a substantial number of cases, we were unable to determine an industry—these are given the missing code "999."
User Caution: Industry was first asked as a distinct question in the 1910 census. The samples from 1850 to 1880 infer industry on the basis of the occupation response. Often, the industry was unambiguous. In fact, one of the difficulties in coding occupations in the nineteenth-century censuses was the penchant for people to report their industry rather than their occupation. Nevertheless, the 1850-1880 industry information is undoubtedly inferior to the later censuses. Each of these years contains a large "not classifiable" category (code 997). We did not attempt to impute these missing values.
Codes:
See ipums.umn.edu/usa/pwork/ind1950b.html for a listing of IND1950 codes.
YRSUSA1 – Columns 145-146
Years in the United States
Universe: Foreign born.
Description:
YRSUSA1 indicates how long each foreign-born person had been living in the United States. (Researchers who are interested in the year of immigration, as opposed to the length of time spent in the United States, should see the IPUMS variable YRIMMIG).
Comparability:
In 1900, the census asked both for the year of immigration (see YRIMMIG) and for the number of complete years elapsed since the person's arrival, which is reported in YRSUSA1. In some cases, these numbers might be in conflict, since a person might have spent some time living outside of the United States since the time of their original arrival - the census gave no explicit directions for these cases, so enumerators and/or respondents may have interpreted them inconsistently.
Codes:
00 = N/A or less than one year.
MOUNEMP – Columns 147-148
Months unemployed last year
Universe: Age 10+.
Description:
MOUNEMP gives the number of months out of the previous twelve that each person who reported having an occupation (i.e., those who ordinarily worked) had been unemployed.
Codes:
| |Code |Frequency |
|0 Months |0 |9259 |
|1 |1 |72 |
|2 |2 |306 |
|3 |3 |536 |
|4 |4 |571 |
|5 |5 |226 |
|6 |6 |904 |
|7 |7 |185 |
|8 |8 |226 |
|9 |9 |240 |
|10 |10 |156 |
|11 |11 |44 |
|12 |12 |104 |
|Not stated/Missing |99 |32822 |
QTRUNEMP – Column 149
Quarters unemployed last year
Universe: Age 10+.
Description:
QTRUNEMP describes how many quarter-year equivalents a person was unemployed last year (rounded up).
Codes:
| |Code |Frequency |
|N/A |0 |32822 |
|Not unemployed last year |1 |9259 |
|Up to one quarter unemployed last year |2 |914 |
|Two quarters unemployed |3 |1701 |
|Three quarters unemployed |4 |651 |
|Four quarters unemployed |5 |304 |
NAMELAST – Columns 213-228
Last name
Universe: All persons.
Description:
NAMELAST is an alphabetic variable giving the first 16 letters of the person's last name as the enumerator recorded it on the census form. A question mark embedded in a name indicates an illegible character. A question mark and space preceding a name means that the entry was difficult to read and the name is the best interpretation possible. An exclamation point indicates the entire entry was illegible. An asterisk indicates the field was blank.
Codes: See text above.
NAMEFRST – Columns 229-244
First name
Universe: All persons.
Description:
NAMEFRST is an alphabetic variable giving the first 16 letters of the person's first name as the enumerator recorded it on the census form. Middle initials and names follow the first name if the enumerator recorded them. A question mark embedded in a name indicates an illegible character. A question mark and space preceding a name means that the entry was difficult to read and the name is the best interpretation possible. An exclamation point indicates the entire entry was illegible. An asterisk mark indicates the field was blank.
Codes: See text above.
AGEMONTH – Columns 245-246
Age in months
Universe: Age under 1 year.
Description:
AGEMONTH gives the age in months of persons less than one year old (AGE = 0) on census day. For 1910, it also gives the age in months beyond one year for persons age 1. (That is, an 18-month-old would be coded "1" in the IPUMS variable AGE and "6" in AGEMONTH; a 6-month-old would also be coded "6" in AGEMONTH, but would be coded "0" in AGE.) For 1920, it does this not only for 1-year-olds, but for 2-, 3, and 4-year-olds as well. Most users who analyze 1910 and/or 1920 in conjunction with the other years will therefore want to select only persons for whom the IPUMS variable AGE = "0." If this is done, the variable is comparable for all years.
Age in months was originally recorded as a fraction of a year on the census forms. The enumerator instructions suggest that it be recorded as some number over 12, but the frequency distributions indicate that some enumerators recorded it as a round number (often as "1/2," coded in the samples as 6 months—the most common code in all years) instead of the exact figure. It appears enumerators in 1850-1880 recorded children under one month old as one month old.
Codes: See text above.
BIRTHMO – Columns 247-248
Month of birth
Universe: All persons.
Description:
BIRTHMO gives the person's month of birth.
Codes:
| |Code |Frequency |
|January |1 |5099 |
|February |2 |3650 |
|March |3 |4986 |
|April |4 |4122 |
|May |5 |5441 |
|June |6 |3762 |
|July |7 |2834 |
|August |8 |3064 |
|September |9 |3040 |
|October |10 |3122 |
|November |11 |2920 |
|December |12 |3611 |
SURSIM – Columns 259-260
Surname similarity
Universe: All persons.
Description:
SURSIM assigns the same code to all persons within each household who had the same surname. All persons coded "1," including the household head, had the same surname as the household head. Other surnames are assigned codes in the order in which they appear within the household on the census form. Persons within any household who shared a surname will have the same code.
Codes: See text above.
PFARMSCH – Column 269
Person received farm schedule
Universe: All persons.
Description:
PFARMSCH identifies which persons within the household (if any) filled out farm schedules for the agricultural census.
Codes: See text above.
QCHSURV – Column 278
Children surviving – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QAGE – Column 279
Age – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QAGEMONT – Column 280
Age in months – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QBIRTHMO – Column 282
Month of birth – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QBPL – Column 283
Birthplace – Detailed – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QLIT – Column 284
Literacy – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QCHBORN – Column 285
Children born – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QCITIZEN – Column 286
Children born – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QFBPL – Column 290
Father’s birthplace – Detailed – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QMBPL – Column 303
Mother’s birthplace – Detailed – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QMARST – Column 306
Marital status – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QOCC – Column 314
Occupation – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QQTRUNEM – Column 315
Quarters unemployed last year – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QRACE – Column 316
Race – Detailed – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QRELATE – Column 317
Relationship to household head – Detailed – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QSURSIM – Column 318
Surname similarity – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QDURMARR – Column 321
Duration of current marriage – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QSCHOOL – Column 322
School attendance – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QSEX – Column 323
Sex – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QSPEAKEN – Column 324
Speaks English – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
QYRIMM – Column 333
Year of immigration – Data quality flag
Universe: All persons.
Description:
Refer to the Data Quality Flag Introduction at ipums.umn.edu/usa/flags.html for a general description of IPUMS data quality flags.
Codes:
0 - Unaltered case
2 - Logical hand edit by Census Office or by census sample research staff
3 - Logical computer edit by IPUMS
4 - Hot deck allocation by IPUMS
INAME – Columns 334-368
Indian name
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Other name, if any.” Enumerators were instructed to “Write the Indian name, if the person has one, in additiion to the English name given in column 3. If the Indian only has one name, Indian or English, repeat the name in this column.”
Codes: See text above.
TRIBE – Columns 491-495
Individual’s Tribe
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Tribe of this Indian.” Enumerators were instructed to “… secure the name of the tribe with which the person is connected ….”
The first two digits of TRIBE represent a general code, with the last tree digits providing a detailed code.
Codes:
|TRIBE |GEN |DET |
|Missing, Blank |00 |000 |
|Amerind White |00 |548 |
|Not Indian, White |00 |971 |
|Not Indian, Black |00 |972 |
|Chinese |00 |976 |
|Not Indian |00 |999 |
|Alaskan Athabaskan - Tanaina |01 |008 |
|Alaskan Athabaskan |01 |014 |
|Alaska Indian |01 |019 |
|Canadian Athabaskan |01 |525 |
|Apache |02 |255 |
|Apache - Jicarilla |02 |257 |
|Apache - Lipan |02 |258 |
|Apache - Mescalero |02 |259 |
|Apache - Payson |02 |263 |
|Apache - White Mountain |02 |264 |
|Blackfoot |03 |360 |
|Cherokee |04 |416 |
|Cherokee - Black |04 |549 |
|Cheyenne |05 |361 |
|Chickasaw |06 |436 |
|Chippewa |07 |330 |
|Chippewa - French American Indian |07 |553 |
|Choctaw - Mississippi Choctaw |08 |226 |
|Choctaw |08 |434 |
|Choctaw - Chitimacha |08 |460 |
|Comanche |09 |325 |
|Creek |10 |425 |
|Crow |11 |322 |
|Iroquois |12 |405 |
|Iroquois - Seneca |12 |406 |
|Iroquois - Cayuga |12 |410 |
|Iroquois - Onondaga |12 |411 |
|Iroquois - Oneida |12 |412 |
|Iroquois - Mohawk |12 |413 |
|Iroquois - Tuscarora |12 |414 |
|Iroquois - Wyandotte |12 |415 |
|Iroquois - Amerind White |12 |548 |
|Kiowa |13 |276 |
|Navajo |15 |275 |
|Osage |16 |320 |
|Paiute |17 |175 |
|Paiute - Kaibab |17 |189 |
|Pima |18 |217 |
|Potawatomie |19 |367 |
|Pueblo |20 |229 |
|Pueblo - Tigua |20 |230 |
|Pueblo - Taos |20 |231 |
|Pueblo - Keres |20 |235 |
|Pueblo - Acoma |20 |236 |
|Pueblo - Cochiti |20 |237 |
|Pueblo - Laguna |20 |238 |
|Pueblo - Tewa |20 |243 |
|Pueblo - Arizona Tewa |20 |250 |
|Pueblo - Hopi |20 |252 |
|Pueblo - Zuni |20 |253 |
|Seminole |21 |438 |
|Shoshone |22 |195 |
|Shoshone - Goshute |22 |200 |
|Shoshone - South Fork |22 |203 |
|Sioux |23 |282 |
|Sioux - Rosebud |23 |295 |
|Sioux - Sisseton-Wahpeton |23 |297 |
|Sioux - Teton |23 |298 |
|Sioux - Brule |23 |299 |
|Sioux - Lower Brule |23 |300 |
|Sioux - Sans Arc |23 |301 |
|Sioux - Two Kettle |23 |302 |
|Sioux - Oglala |23 |304 |
|Sioux - Miniconjou |23 |305 |
|Sioux - Yanktonai |23 |306 |
|Sioux - Yankton |23 |307 |
|Sioux - Santee |23 |308 |
|Sioux - Sisseton |23 |309 |
|Sioux - Mdewakanton |23 |310 |
|Sioux - Wahpekute |23 |311 |
|Sioux - Wahpeton |23 |312 |
|Sioux - Wazhaza |23 |327 |
|Sioux - Amerind White |23 |548 |
|Tlingit |24 |017 |
|Tohono O'Odham |25 |218 |
|Tohono O'Odham - Central American Indian |25 |551 |
|Iowa |26 |314 |
|Umpqua |26 |013 |
|Alaska Native |26 |015 |
|Haida |26 |016 |
|Tsimshian |26 |018 |
|Alaska Indian |26 |019 |
|Chehalis |26 |020 |
|Klallam |26 |022 |
|Port Gamble Klallam |26 |025 |
|Coquilles |26 |026 |
|Cowlitz |26 |027 |
|Lummi |26 |028 |
|Sauk-Suiattle |26 |038 |
|Quinault |26 |050 |
|Quileute |26 |051 |
|Hoh |26 |052 |
|Makah |26 |053 |
|Chinook |26 |055 |
|Clatsop |26 |056 |
|Upper Chinook |26 |059 |
|Alsea |26 |062 |
|Cayuse |26 |063 |
|Coos |26 |065 |
|Kalapuya |26 |066 |
|Klamath |26 |067 |
|Molala |26 |068 |
|Oregon Athabaskan |26 |069 |
|Tenino |26 |072 |
|Tillamook |26 |073 |
|Umatilla |26 |075 |
|Walla-Walla |26 |076 |
|Cahuilla |26 |084 |
|Chemehuevi |26 |087 |
|Chumash |26 |089 |
|Diegueno |26 |093 |
|Digger |26 |094 |
|Hoopa |26 |096 |
|Karok |26 |098 |
|La Jolla |26 |100 |
|Luiseno |26 |103 |
|Konkow |26 |109 |
|Mattole |26 |110 |
|Miwok |26 |111 |
|Modoc |26 |113 |
|Mono |26 |114 |
|Nomalaki |26 |115 |
|Pit River |26 |119 |
|Pomo |26 |120 |
|Serrano |26 |134 |
|Shasta |26 |135 |
|Soboba |26 |136 |
|Sycuan |26 |137 |
|Tolowa |26 |138 |
|Kern River |26 |140 |
|Tule River |26 |141 |
|Wailaki |26 |143 |
|Wintu |26 |146 |
|Chukchansi |26 |151 |
|Yuki |26 |152 |
|Yurok |26 |153 |
|Columbia |26 |155 |
|Kalispel |26 |156 |
|Salish |26 |157 |
|Coeur D'Alene |26 |158 |
|Colville |26 |159 |
|Spokane |26 |160 |
|Nez Perce |26 |161 |
|Washo |26 |162 |
|Wishram |26 |167 |
|Trinity |26 |169 |
|Ute |26 |170 |
|Uintah Ute |26 |172 |
|Shoshone Paiute |26 |174 |
|Bannock |26 |207 |
|Kootenai |26 |208 |
|Havasupai |26 |209 |
|Hualapai |26 |211 |
|Maricopa |26 |213 |
|Quechan |26 |214 |
|Cocopah |26 |215 |
|Mohave |26 |216 |
|Jemez |26 |251 |
|Tonkawa |26 |277 |
|Arikara |26 |279 |
|Wichita |26 |281 |
|Assiniboine |26 |313 |
|Otoe-Missouria |26 |315 |
|Winnebago |26 |316 |
|Kaw |26 |317 |
|Omaha |26 |318 |
|Ponca |26 |319 |
|Quapaw |26 |321 |
|Mandan |26 |324 |
|Leelanau |26 |337 |
|Cree |26 |354 |
|Arapaho |26 |364 |
|Menominee |26 |366 |
|Ottawa |26 |375 |
|Miami |26 |376 |
|Sac and Fox |26 |377 |
|Peoria |26 |378 |
|Kickapoo |26 |380 |
|Shawnee |26 |381 |
|Algonquian |26 |382 |
|Micmac |26 |383 |
|Mailseet |26 |384 |
|Passamaquoddy |26 |385 |
|Penobscot |26 |388 |
|Abenaki |26 |389 |
|Narragansett |26 |392 |
|Pequot |26 |393 |
|Mohegan |26 |394 |
|Brotherton |26 |397 |
|Shinnecock |26 |398 |
|Stockbridge |26 |399 |
|Munsee |26 |400 |
|Yuchi |26 |427 |
|Hitchiti |26 |428 |
|Alabama Coushatta |26 |433 |
|Matinecock |26 |445 |
|Nansemond |26 |452 |
|Catawba |26 |459 |
|Croatan |26 |462 |
|Powhatan |26 |466 |
|Tunica |26 |467 |
|Coushatta |26 |471 |
|Grand Ronde |26 |486 |
|Mission Indians |26 |488 |
|Morongo |26 |489 |
|Siletz |26 |493 |
|Gros Ventres |26 |502 |
|Warm Springs |26 |504 |
|Red Wood |26 |507 |
|Georgetown |26 |509 |
|Scotts Valley |26 |512 |
|Canadian Indian |26 |525 |
|Caddo |26 |533 |
|Pawnee |26 |534 |
|Wenatchee |26 |543 |
|French American Indian |26 |553 |
|Spanish American Indian |26 |554 |
|Tribal resonse, not elsewhere classified |26 |598 |
|American Indian |26 |973 |
|Tribe not specified, Canadian Indian |27 |525 |
|Tribe not specified, Amerind White |27 |548 |
|Tribe not specified, Mexican American Indian |27 |550 |
|Tribe not specified, French American Indian |27 |553 |
|Tribe not specified |27 |973 |
|Aleut |30 |019 |
|Eskimo |40 |019 |
|Delaware |50 |401 |
|Mexican American Indian |51 |550 |
|Central American Indian |51 |551 |
|South American Indian |51 |552 |
|Puget Sound Salish - Nooksack |52 |029 |
|Puget Sound Salish |52 |030 |
|Puget Sound Salish - Duwamish |52 |031 |
|Puget Sound Salish - Kikiallus |52 |032 |
|Puget Sound Salish - Muckleshoot |52 |034 |
|Puget Sound Salish - Nisqually |52 |035 |
|Puget Sound Salish - Puyallup |52 |036 |
|Puget Sound Salish - Samish |52 |037 |
|Puget Sound Salish - Upper Skagit |52 |039 |
|Puget Sound Salish - Skykomish |52 |040 |
|Puget Sound Salish - Snohomish |52 |041 |
|Puget Sound Salish - Snoqualmie |52 |042 |
|Puget Sound Salish - Steilacoom |52 |044 |
|Puget Sound Salish - Suquamish |52 |046 |
|Puget Sound Salish - Swinomish |52 |047 |
|Puget Sound Salish - Tulalip |52 |048 |
|Puget Sound Salish - Port Madison |52 |049 |
|Puget Sound Salish - Skokomish |52 |079 |
|Yakima |53 |078 |
|Yaqui |54 |223 |
|Hawaiian |57 |653 |
FTRIBE – Columns 505-509
Father’s tribe
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Tribe of this Indian.” Enumerators were instructed to “… secure the name of the tribe with which the person is connected ….”
The first two digits of FTRIBE represent a general code, with the last tree digits providing a detailed code.
Codes:
See codes above for TRIBE.
MTRIBE – Columns 510-514
Mother’s tribe
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Tribe of this Indian.” Enumerators were instructed to “… secure the name of the tribe with which the person is connected ….”
The first two digits of MTRIBE represent a general code, with the last tree digits providing a detailed code.
Codes:
See codes above for TRIBE.
BLOODW – Columns 515-517
Amount of white blood
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Has this Indian any white blood; if so, how much? (0, 1/2, 1/4, 1/8).” Enumerator instuctions stated “If the Indian has no white blood, write 0. If he or she has white blood, write 1/2, 1/4, 1/8. whichever fraction is nearest the truth.”
Enumerators entered a wide variety of fractions in response to this question. We converted the fractions to a percentage; thus the values of BLOODW range from 0 (no white blood) to 100 (presumably meaning all white blood). In addition:
997 = illegible
998 = unknown
999 = missing/blank
Codes: See text above.
IMARST – Columns 518
Polygamy
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Is this Indian, if married, living in polygamy.” Enumerator instuctions stated “If the Indian is living with more than one wife, of if the Indian woman is a plural wife or has more than one husband, write ‘Yes.’ If not, write ‘No.’ If the Indian is single, leave the column blank.”
Codes:
| |Code |Frequency |
|No |1 |13460 |
|Yes |2 |453 |
|Not classified |6 |6 |
|Illegible |7 |22 |
|Unknown |8 |4 |
|Missing/Blank |9 |31706 |
ITAX – Columns 519
Tax status
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Is this Indian taxed?” Enumerator instuctions stated “An Indian is considered ‘taxed’ if he or she is detached from his or her tribe and living among whit epeople as an individual, and as such subject to taxation, whether he or she actually pays taxes or not; also if he or she is living with his or her tribe but has received an allotment , and thereby has acquired citizenship; in either of these two cases the answer to this inquiry is Yes.”
Codes:
| |Code |Frequency |
|No |1 |20935 |
|Yes |2 |6797 |
|Illegible |7 |1 |
|Unknown |8 |9 |
|Missing/Blank |9 |17909 |
IYRCIT – Columns 520-522
Year of citizenship
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Year of acquiring citizenship.” Enumerator instuctions stated “If the Indian was born in tribal relations, but has acquired citizenship, write the year in which it ws acquired.”
Codes:
996 = not classified
997 = illegible
998 = unknown
999 = missing/blank
ICITIZEN – Columns 523
Citizenship acquired by allotment
Universe: All persons.
Description:
The modified schedule used to enumerate Indians contained a field labeled “Was citizenship acquired by allotment?” Enumerator instuctions stated “If the Indian acquired citizenship by receiving an allotment of land from the Government, write Yes. If he or she acquired citizenship by other means, write No. If he or she has not acquired American citizenship, leave the column blank.”
Codes:
| |Code |Frequency |
|No |1 |1755 |
|Yes |2 |4419 |
|Not classified |6 |2 |
|Illegible |8 |3 |
|Missing/Blank |9 |39472 |
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- education in the usa facts
- understanding the hispanic latino culture
- what is the usa gnp
- facts about the usa kids
- history of the usa flag
- hispanic population in the us
- hispanic population in the world
- hispanic education in the us
- what is the hispanic race
- what s the difference between hispanic and latino
- education in the hispanic culture
- understanding the hispanic culture