This study is provided by ICPSR. ICPSR provides leadership and training in data access, curation, and methods of analysis for a diverse and expanding social science research community.
Principal Investigator(s): Twin Cities Metropolitan Council
The Twin Cities Metropolitan Area 1982 Travel Behavior Inventory (Home Interview Survey) was intended to document how Twin Cities residents use the streets, highways, and transit services in the region. Respondents were asked to record their travel and activities for a 24-hour period. They were also asked for detailed information regarding their trips, including mode of transportation, trip purpose, departure and arrival times, and number of passengers. Demographic variables include gender, age, employment status, household size, number of children under five years old in the household, whether household members were students on their given travel day, household income, and whether respondents had a valid drivers license at the time of the survey.
These data are available only to users at ICPSR member institutions. Because you are not logged in, we cannot verify that you will be able to download the data.
Twin Cities Metropolitan Council. Twin Cities Metropolitan Area 1982 Travel Behavior Inventory (Home Interview Survey). ICPSR34738-v1. Ann Arbor, MI: Inter-university Consortium for Political and Social Research[distributor], 2013-08-07. doi:10.3886/ICPSR34738.v1
Persistent URL: http://doi.org/10.3886/ICPSR34738.v1
Scope of Study
Subject Terms: automobile ownership, automobile use, automobiles, commuting (travel), driving habits, households, licenses, public transportation, schools, transportation, travel, vehicles, work, working hours
Smallest Geographic Unit: city
Date of Collection:
Unit of Observation: individual, household
Universe: Households within the Twin Cities seven county area (at the time): Ramsey, Hennepin, Dakota, Anoka, Washington, Carver, and Scott counties.
Data Types: survey data
Data Collection Notes:
The 1982 Travel Behavior Inventory is a collection of surveys administered in the Twin Cities area. The Home Interview Survey is one key part of this larger collection of surveys. The other surveys in the 1982 Travel Behavior Inventory have not been deposited with ICPSR, and are therefore not available through ICPSR.
For additional information regarding the Twin Cities Metropolitan Area 1982 Travel Behavior Inventory (Home Interview Survey), please refer to the Metropolitan Travel Survey Archive Web site.
Study Purpose: The purpose of the 1982 Travel Behavior Inventory was to update socio-economic and travel data gathered in a 1970 home interview survey. This 1970 data base was used to develop mathematical models to predict future regional travel patterns. For additional information regarding the purpose of this study, please refer to the Original P.I. Documentation section of the ICPSR codebook.
Study Design: For information regarding study design, please refer to the Original P.I. Documentation section of the ICPSR codebook.
Sample: It was determined that a sample of 2,000 households would yield data that are accurate within +/- .14 work trips per household. For additional information regarding the sampling method, please refer to the Original P.I. Documentation section of the ICPSR codebook.
Mode of Data Collection: mail questionnaire, telephone interview
Extent of Processing: ICPSR data undergo a confidentiality review and are altered when necessary to limit the risk of disclosure. ICPSR also routinely creates ready-to-go data files along with setups in the major statistical software formats as well as standard codebooks to accompany the data. In addition to these procedures, ICPSR performed the following processing steps for this data collection:
- Checked for undocumented or out-of-range codes.
Original ICPSR Release: 2013-08-07
- Citations exports are provided above.
Export Study-level metadata (does not include variable-level metadata)
If you're looking for collection-level metadata rather than an individual metadata record, please visit our Metadata Records page.