Geoff,
I cannot provide guidance, but you might find our recent experience helpful. We have used 2010 SF1 data for households by size and ACS 5 year (2006-2010) shares for income. We chose this approach to be consistent with 2006-2010 ACS PUMS data that we also use, and in the absence of other information.
Joe
Joseph Huegy, AICP
Director
Travel Behavior Modeling Group
ITRE – NCSU
Box 8601
Raleigh, NC 27695-8601
ph. 919.513.7378
cell 919.606.8634
fax 919.515.8898
email: jbhuegy@ncsu.edu
From: ctpp-news-bounces@chrispy.net [mailto:ctpp-news-bounces@chrispy.net] On Behalf Of Geoff Olson
Sent: Thursday, January 02, 2014 9:59 AM
To: 'ctpp-news@chrispy.net'
Subject: [CTPP] Census 2010 vs 5-year ACS for TAZs
Hello Everyone,
Ive gotten started on our long range transportation plan, and one area we have an issue with is Census data. We've got 2010 Census data for our population and household counts, but we will also need the 5-year ACS data of number of households by household size by household income. We would prefer to use 2010 population counts for the base year of the model so we've decided there are two options. We could use the 5-year ACS data for our base model year population and household counts, but that doesn't create a true picture of 2010. The other option is we could mix datasets and proportionately apply characteristics of the 5-year ACS data to the 2010 counts. Can anyone give us some guidance needing to use both datasets on the same project?
Thank you,
Geoff Olson
Transportation Planner
Bi-State Regional Commission
1504 3rd Ave.
P.O. Box 3368
Rock Island, IL 61204
This email and all attachments are intended only for the listed recipient(s). This message may contain confidential or privileged information only for use by the listed recipient(s). Do not forward, post or otherwise disclose the contents of this email without the permission of the sender. If you received this message in error, please delete it and notify the sender immediately. Bi-State Regional Commission accepts no responsibility for any damages caused by this message, including those related to viruses or malware.