Difference between revisions of "3.5 Synthetic Population"

From NFTPO Model
Jump to: navigation, search
Line 1: Line 1:
 
[[Category:3.0 Model Design]]
 
[[Category:3.0 Model Design]]
  
h1. Wikifier RT
+
<h3 id="id-3.5SYNTHETICPOPULATION-Overview"><span style="color: rgb(255,102,0);">Overview</span></h3><p class="BodyParagraph">In trip-based models, trip rates are applied to aggregate households grouped in Traffic Analysis Zones (TAZs) to generate trips. On the other hand, in an activity-based model (ABM), choices involving activities and trips are simulated for each of the individual persons in households. Hence, it is necessary to first develop a “synthetic population” of the regions’ residents. Synthetic population is a list of households and persons that is based on observed or forecasted distributions of socioeconomic attributes and created by sampling detailed Census microdata. This produces individual household agents and individual person agents that are subjects of the simulation.</p><p class="BodyParagraph">Prior to their use in the simulation, synthetic populations are represented in data tables, often in a relational database or some equivalently structured file system. Typically there are separate tables for households and person records. The household records file provides details about various household-level socio-demographic attributes such as household income, size, number of workers, etc. Similarly, the person records file provides information about person-level attributes such as age, gender, employment status, etc. Person records are linked to household records through ID numbers.</p><h4 class="BodyParagraph" id="id-3.5SYNTHETICPOPULATION-TABLE3-2SAMPLEHOUSEHOLDRECORDSFILE">TABLE 3-2 SAMPLE HOUSEHOLD RECORDS FILE</h4><div class="table-wrap">
 
+
{|  class="confluenceTable"
h3. {color:#FF6600}Overview{color}
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong> TAZ</strong></p>
 
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>HHID</strong></p>
In trip-based models, trip rates are applied to aggregate households grouped in Traffic Analysis Zones (TAZs) to generate trips. On the other hand, in an activity-based model (ABM), choices involving activities and trips are simulated for each of the individual persons in households. Hence, it is necessary to first develop a “synthetic population” of the regions’ residents. Synthetic population is a list of households and persons that is based on observed or forecasted distributions of socioeconomic attributes and created by sampling detailed Census microdata. This produces individual household agents and individual person agents that are subjects of the simulation.
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Age of Household Head</strong></p>
 
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Number of persons</strong></p>
Prior to their use in the simulation, synthetic populations are represented in data tables, often in a relational database or some equivalently structured file system. Typically there are separate tables for households and person records. The household records file provides details about various household-level socio-demographic attributes such as household income, size, number of workers, etc. Similarly, the person records file provides information about person-level attributes such as age, gender, employment status, etc. Person records are linked to household records through ID numbers.
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Income Group</strong></p>
 
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Presence of Children</strong></p>
h4. TABLE 3-2 SAMPLE HOUSEHOLD RECORDS FILE
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Number Workers</strong></p>
 
+
|-
|* TAZ*|*HHID*|*Age of Household Head*|*Number of persons*|*Income Group*|*Presence of Children*|*Number Workers*|
+
| class="confluenceTd" | <p>143</p>
|143|16667|1|2|1|1|1|
+
| class="confluenceTd" | <p align="center">16667</p>
|193|17392|1|2|4|0|1|
+
| class="confluenceTd" | <p align="center">1</p>
|77|232|1|3|1|1|2|
+
|  class="confluenceTd" | <p align="center">2</p>
|18|5042|1|4|3|1|3|
+
|  class="confluenceTd" | <p align="center">1</p>
 
+
| class="confluenceTd" | <p align="center">1</p>
h4. TABLE 3-3 SAMPLE PERSON RECORDS FILE
+
| class="confluenceTd" | <p align="center">1</p>
 
+
|-
|* TAZ*|*HHID*|*Person ID*|*Age*|*Works from Home*|*Employment Status*|*Gender*|*Hours Worked per Week*|
+
| class="confluenceTd" | <p>193</p>
|77|232|1|22|1|1|2|9|
+
| class="confluenceTd" | <p align="center">17392</p>
|77|232|2|24|1|0|1|45|
+
| class="confluenceTd" | <p align="center">1</p>
|77|232|3|1|0|1|2|0|
+
| class="confluenceTd" | <p align="center">2</p>
 
+
|  class="confluenceTd" | <p align="center">4</p>
Population synthesized by any synthetic population generator may be used with DaySim as long as the required household and person socio-demographic attributes are provided to it in the appropriate format. PopGen, the synthetic population generator developed at Arizona State University (ASU) was chosen for this effort primarily for two reasons. First, it has the ability to control for both household and person level demographic attributes simultaneously. Second, it has an easy-to-use and simple graphical user interface (GUI).
+
| class="confluenceTd" | <p align="center">0</p>
 
+
| class="confluenceTd" | <p align="center">1</p>
h3. {color:#FF6600}Preparing Synthetic Populations for DaySim{color}
+
|-
 
+
| class="confluenceTd" | <p>77</p>
The design of the synthetic population should support the design of the activity-based model (DaySim in this case) and provide the variables it needs. In addition, the activity-based model should only rely on information that can be realistically provided in the synthetic population.
+
| class="confluenceTd" | <p align="center">232</p>
 
+
| class="confluenceTd" | <p align="center">1</p>
Population synthesis generally consists of the synthesis of two sub-populations – those living in regular households and those living in non-institutionalized group quarters such as college dormitories. For this effort, an additional segment of population was synthesized which comprised of seasonal households. These segments were established to reflect the differences in travel patterns associated with these sub-populations as well as to provide the ability to support seasonal analyses. For example, the seasonal population is generally older than the permanent population, has lower levels of workforce participation, and clusters in certain geographic areas. All of these attributes influence travel patterns and the demand for travel.
+
|  class="confluenceTd" | <p align="center">3</p>
 
+
|  class="confluenceTd" | <p align="center">1</p>
There are three major steps in creating a synthetic population:
+
| class="confluenceTd" | <p align="center">1</p>
 
+
| class="confluenceTd" | <p align="center">2</p>
# Specifying the inputs to the process—the control variables and sample households as well as the level of geographic resolution. Specifying the control variables is essential. In addition, there is often an additional step of specifying additional, uncontrolled variables to be added to the synthetic population.
+
|-
# Actually running a program that produces the synthetic households.
+
| class="confluenceTd" | <p>18</p>
# The third major step would be transforming the model-generated outputs into characteristics of the population that will be used throughout the rest of the model system. This could involve creating categorical variables out of continuous variables, reformulating income, or allocating households from the zonal level to a finer level of geographic resolution, such as a parcel.
+
| class="confluenceTd" | <p align="center">5042</p>
 
+
| class="confluenceTd" | <p align="center">1</p>
h4. _DaySim Person Types_
+
| class="confluenceTd" | <p align="center">4</p>
 
+
|  class="confluenceTd" | <p align="center">3</p>
Although person are being modeled in disaggregate form in an ABM, it is often useful to create person type categories. DaySim uses 8 such person types. Person type categories may be used for various purposes:
+
| class="confluenceTd" | <p align="center">1</p>
 
+
| class="confluenceTd" | <p align="center">3</p>
# As a basic segmentation for certain models, such as daily activity pattern models
+
|}</div><h4 id="id-3.5SYNTHETICPOPULATION-TABLE3-3SAMPLEPERSONRECORDSFILE">TABLE 3-3 SAMPLE PERSON RECORDS FILE</h4><div class="table-wrap">
# To summarize and compare observed versus estimated data and calibrate models
+
{|  class="confluenceTable"
# As explanatory variables in models
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong> TAZ</strong></p>
# As constraints on alternatives that are available; for example, work and school activities are only available to workers and student; and driving is restricted by age
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>HHID</strong></p>
 
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Person ID</strong></p>
h4. TABLE 3-4 DAYSIM PERSON TYPES
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Age</strong></p>
 
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Works from Home</strong></p>
|* No.*|*Person Type*|*Age*|*Work Status*|*School Status*|
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Employment Status</strong></p>
|1|Full-time worker|18 or more|Full-time|None/Part-time|
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Gender</strong></p>
|2|Part-time worker|18 or more|Part-time|None/Part-time|
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Hours Worked per Week</strong></p>
|3|Retired person|65 or more|Unemployed| |
+
|-
|4|Non-working adult|Less than 65|Unemployed|None/Part-time|
+
| class="confluenceTd" | <p>77</p>
|5|University student|18 or more|Unemployed/Part-time|Full-time|
+
| class="confluenceTd" | <p align="center">232</p>
|6|High school student|16 or more|Unemployed/Part-time|Full-time|
+
| class="confluenceTd" | <p align="center">1</p>
|7|Primary school child|5-15|Unemployed|Full-time|
+
| class="confluenceTd" | <p align="center">22</p>
|8|Preschool child|0-4|Unemployed|None|
+
| class="confluenceTd" | <p align="center">1</p>
 
+
| class="confluenceTd" | <p align="center">1</p>
h4. _Control Attributes and Target Distributions_
+
|  class="confluenceTd" | <p align="center">2</p>
 
+
|  class="confluenceTd" | <p align="center">9</p>
There are three major inputs required for population synthesis of which the first step is to identify a set of control attributes and their levels. Next, target distributions of the control attributes and their levels are derived at appropriate geographic units. These target distributions are also known as marginal control totals since they represent the margins of a joint distribution of multiple attributes. Typically, the smallest level of spatial resolution that can be feasibly and reliably used to control attributes is used. If control attribute totals are not accurate at a particular spatial unit, they could be specified at a lower resolution.
+
|-
 
+
| class="confluenceTd" | <p>77</p>
The following considerations are usually important in choosing control variables:
+
| class="confluenceTd" | <p align="center">232</p>
 
+
|  class="confluenceTd" | <p align="center">2</p>
* The number of control variables is important. If there are too few, the synthetic population may not accurately reflect the true population. On the other hand, too many control attributes may cause sample issues. There may not be any sample households with joint attributes of the control variables and this could distort the synthetic population.
+
| class="confluenceTd" | <p align="center">24</p>
* Control attributes may be single or multi-dimensional. Multi-dimensional attributes can be treated as single dimensional attributes with number of categories equal to the product of the numbers of categories in individual attributes. The primary advantage of multi-dimensional attributes is more precise regional control over the correlation between attributes. The disadvantage again is with sparse sample.
+
| class="confluenceTd" | <p align="center">1</p>
* The best choices of variables, will be meaningful attributes that are somewhat “orthogonal” to each other, which means that their variance in the population is largely independent. Conversely, if there are two attributes that are highly correlated, then controlling for both may not achieve much more than controlling for just one.
+
| class="confluenceTd" | <p align="center">0</p>
* Finally, different sets of control attributes may be used for base and forecast years, if limited by forecasting accuracy.   This is not necessarily desirable, though. The ability to forecast marginal control totals should be a consideration when specifying control attributes for this base year.
+
| class="confluenceTd" | <p align="center">1</p>
 
+
| class="confluenceTd" | <p align="center">45</p>
Target distributions of control variables for the base year could be obtained from a variety of data sources including the following:
+
|-
 
+
| class="confluenceTd" | <p>77</p>
* Decennial Census: ~100% sample
+
|  class="confluenceTd" | <p align="center">232</p>
* American Community Survey (ACS) summary files: 3% sample, rolling 5-year sample, yields an estimate of ~15% of population
+
| class="confluenceTd" | <p align="center">3</p>
* Census Transportation Planning Products (CTPP)
+
| class="confluenceTd" | <p align="center">1</p>
* Other zonal data developed locally (TAZs)
+
| class="confluenceTd" | <p align="center">0</p>
 
+
| class="confluenceTd" | <p align="center">1</p>
For the forecast year, regional socio-economic forecasts or outputs from a land-use model are often used.
+
| class="confluenceTd" | <p align="center">2</p>
 
+
| class="confluenceTd" | <p align="center">0</p>
The following tables provide the list of control attributes and their levels along with the specific data sources used to obtain corresponding target distributions. All the distributions were obtained at the TAZ level.
+
|}</div><p class="BodyParagraph">Population synthesized by any synthetic population generator may be used with DaySim as long as the required household and person socio-demographic attributes are provided to it in the appropriate format. PopGen, the synthetic population generator developed at Arizona State University (ASU) was chosen for this effort primarily for two reasons. First, it has the ability to control for both household and person level demographic attributes simultaneously. Second, it has an easy-to-use and simple graphical user interface (GUI).</p><h3 id="id-3.5SYNTHETICPOPULATION-PreparingSyntheticPopulationsforDaySim"><span style="color: rgb(255,102,0);">Preparing Synthetic Populations for DaySim</span></h3><p class="BodyParagraph">The design of the synthetic population should support the design of the activity-based model (DaySim in this case) and provide the variables it needs. In addition, the activity-based model should only rely on information that can be realistically provided in the synthetic population.</p><p class="BodyParagraph">Population synthesis generally consists of the synthesis of two sub-populations – those living in regular households and those living in non-institutionalized group quarters such as college dormitories. For this effort, an additional segment of population was synthesized which comprised of seasonal households. These segments were established to reflect the differences in travel patterns associated with these sub-populations as well as to provide the ability to support seasonal analyses. For example, the seasonal population is generally older than the permanent population, has lower levels of workforce participation, and clusters in certain geographic areas. All of these attributes influence travel patterns and the demand for travel.</p><p class="BodyParagraph">There are three major steps in creating a synthetic population:</p><ol><li>Specifying the inputs to the process—the control variables and sample households as well as the level of geographic resolution. Specifying the control variables is essential. In addition, there is often an additional step of specifying additional, uncontrolled variables to be added to the synthetic population.</li><li>Actually running a program that produces the synthetic households.</li><li>The third major step would be transforming the model-generated outputs into characteristics of the population that will be used throughout the rest of the model system. This could involve creating categorical variables out of continuous variables, reformulating income, or allocating households from the zonal level to a finer level of geographic resolution, such as a parcel.</li></ol><h4 id="id-3.5SYNTHETICPOPULATION-DaySimPersonTypes"><em>DaySim Person Types</em></h4><p class="BodyParagraph">Although person are being modeled in disaggregate form in an ABM, it is often useful to create person type categories. DaySim uses 8 such person types. Person type categories may be used for various purposes:</p><ol><li>As a basic segmentation for certain models, such as daily activity pattern models</li><li>To summarize and compare observed versus estimated data and calibrate models</li><li>As explanatory variables in models</li><li>As constraints on alternatives that are available; for example, work and school activities are only available to workers and student; and driving is restricted by age</li></ol><h4 id="id-3.5SYNTHETICPOPULATION-TABLE3-4DAYSIMPERSONTYPES">TABLE 3-4 DAYSIM PERSON TYPES</h4><div class="table-wrap">
 
+
{|  class="confluenceTable"
h4. TABLE 3-5 HOUSEHOLD CONTROL DATA FOR PERMANENT HOUSEHOLDS
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong> No.</strong></p>
 
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Person Type</strong></p>
|*Household Attribute*|*Category Number*|*Categories*|*Data Source*|
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Age</strong></p>
|Householder unit type|1|Single family dwelling|NERPM TAZ Data|
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Work Status</strong></p>
| |2|Multi family dwelling| |
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>School Status</strong></p>
|Presence of children|1|Yes|Census 2010 and ACS 2006-10|
+
|-
| |2|No| |
+
| class="confluenceTd" | <p align="center">1</p>
|Householder age|1|15 to 24 years|Census 2010 and ACS 2006-10|
+
|  class="confluenceTd" | <p align="center">Full-time worker</p>
| |2|25 to 54 years| |
+
| class="confluenceTd" | <p align="center">18 or more</p>
| |3|55 to 64 years| |
+
| class="confluenceTd" | <p align="center">Full-time</p>
| |4|65 to 74 years| |
+
| class="confluenceTd" | <p align="center">None/Part-time</p>
| |5|75 years and over| |
+
|-
|Household income (annual)|1|Less than $20,000|Census 2010 and ACS 2006-10|
+
| class="confluenceTd" | <p align="center">2</p>
| |2|$20,000 to $39,999| |
+
| class="confluenceTd" | <p align="center">Part-time worker</p>
| |3|$40,000 to $59,999| |
+
|  class="confluenceTd" | <p align="center">18 or more</p>
| |4|$60,000 to $99,999| |
+
|  class="confluenceTd" | <p align="center">Part-time</p>
| |5|$100,000 or more| |
+
| class="confluenceTd" | <p align="center">None/Part-time</p>
|Household size|1|1 person|Census 2010 and ACS 2006-10|
+
|-
| |2|2 persons| |
+
| class="confluenceTd" | <p align="center">3</p>
| |3|3 persons| |
+
| class="confluenceTd" | <p align="center">Retired person</p>
| |4|4 persons| |
+
| class="confluenceTd" | <p align="center">65 or more</p>
| |5|5 persons| |
+
| class="confluenceTd" | <p align="center">Unemployed</p>
| |6|6 persons| |
+
|  class="confluenceTd" | <p align="center"></p>
| |7|7 or more persons| |
+
|-
|Household size and workers joint|1|1 person, no worker|Census 2010 and ACS 2006-10|
+
| class="confluenceTd" | <p align="center">4</p>
| |2|1 person, 1 worker| |
+
| class="confluenceTd" | <p align="center">Non-working adult</p>
| |3|2 persons, no worker| |
+
| class="confluenceTd" | <p align="center">Less than 65</p>
| |4|2 persons, 1 worker| |
+
| class="confluenceTd" | <p align="center">Unemployed</p>
| |5|2 persons, 2 workers| |
+
| class="confluenceTd" | <p align="center">None/Part-time</p>
| |6|3 persons, no worker| |
+
|-
| |7|3 persons, 1 worker| |
+
| class="confluenceTd" | <p align="center">5</p>
| |8|3 persons, 2 workers| |
+
|  class="confluenceTd" | <p align="center">University student</p>
| |9|3 persons, 3 workers| |
+
|  class="confluenceTd" | <p align="center">18 or more</p>
| |10|4 or more persons, no worker| |
+
| class="confluenceTd" | <p align="center">Unemployed/Part-time</p>
| |11|4 or more persons, 1 worker| |
+
| class="confluenceTd" | <p align="center">Full-time</p>
| |12|4 or more persons, 2 workers| |
+
|-
| |13|4 or more persons, 3 workers| |
+
| class="confluenceTd" | <p align="center">6</p>
 
+
| class="confluenceTd" | <p align="center">High school student</p>
h4. TABLE 3-6 PERSON CONTROL DATA FOR PERMANENT HOUSEHOLDS
+
| class="confluenceTd" | <p align="center">16 or more</p>
 
+
|  class="confluenceTd" | <p align="center">Unemployed/Part-time</p>
|*Person Attribute*|*Category Number*|*Categories*|*Data Source*|
+
|  class="confluenceTd" | <p align="center">Full-time</p>
|Gender|1|Male|Census 2010 and ACS 2006-10|
+
|-
| |2|Female| |
+
| class="confluenceTd" | <p align="center">7</p>
|Age|1|Under 5 years|Census 2010 and ACS 2006-10|
+
| class="confluenceTd" | <p align="center">Primary school child</p>
| |2|5 to 14 years| |
+
|  class="confluenceTd" | <p align="center">5-15</p>
| |3|15 to 17 years| |
+
| class="confluenceTd" | <p align="center">Unemployed</p>
| |4|18 to 24 years| |
+
| class="confluenceTd" | <p align="center">Full-time</p>
| |5|25 to 39 years| |
+
|-
| |6|40 to 54 years| |
+
| class="confluenceTd" | <p align="center">8</p>
| |7|55 to 64 years| |
+
| class="confluenceTd" | <p align="center">Preschool child</p>
| |8|65 to 74 years| |
+
| class="confluenceTd" | <p align="center">0-4</p>
| |9|75 years and over| |
+
|  class="confluenceTd" | <p align="center">Unemployed</p>
 
+
|  class="confluenceTd" | <p align="center">None</p>
h4. TABLE 3-7 HOUSEHOLD CONTROL DATA FOR SEASONAL HOUSEHOLDS
+
|}</div><h4 id="id-3.5SYNTHETICPOPULATION-ControlAttributesandTargetDistributions"><em>Control Attributes and Target Distributions</em></h4><p class="BodyParagraph">There are three major inputs required for population synthesis of which the first step is to identify a set of control attributes and their levels. Next, target distributions of the control attributes and their levels are derived at appropriate geographic units. These target distributions are also known as marginal control totals since they represent the margins of a joint distribution of multiple attributes. Typically, the smallest level of spatial resolution that can be feasibly and reliably used to control attributes is used. If control attribute totals are not accurate at a particular spatial unit, they could be specified at a lower resolution.</p><p class="BodyParagraph">The following considerations are usually important in choosing control variables:</p><ul><li>The number of control variables is important. If there are too few, the synthetic population may not accurately reflect the true population. On the other hand, too many control attributes may cause sample issues. There may not be any sample households with joint attributes of the control variables and this could distort the synthetic population.</li><li>Control attributes may be single or multi-dimensional. Multi-dimensional attributes can be treated as single dimensional attributes with number of categories equal to the product of the numbers of categories in individual attributes. The primary advantage of multi-dimensional attributes is more precise regional control over the correlation between attributes. The disadvantage again is with sparse sample.</li><li>The best choices of variables, will be meaningful attributes that are somewhat “orthogonal” to each other, which means that their variance in the population is largely independent. Conversely, if there are two attributes that are highly correlated, then controlling for both may not achieve much more than controlling for just one.</li><li>Finally, different sets of control attributes may be used for base and forecast years, if limited by forecasting accuracy.   This is not necessarily desirable, though. The ability to forecast marginal control totals should be a consideration when specifying control attributes for this base year.</li></ul><p class="BodyParagraph">Target distributions of control variables for the base year could be obtained from a variety of data sources including the following:</p><ul><li>Decennial Census: ~100% sample</li><li>American Community Survey (ACS) summary files: 3% sample, rolling 5-year sample, yields an estimate of ~15% of population</li><li>Census Transportation Planning Products (CTPP)</li><li>Other zonal data developed locally (TAZs)</li></ul><p class="BodyParagraph">For the forecast year, regional socio-economic forecasts or outputs from a land-use model are often used.</p><p class="BodyParagraph">The following tables provide the list of control attributes and their levels along with the specific data sources used to obtain corresponding target distributions. All the distributions were obtained at the TAZ level.</p><h4 id="id-3.5SYNTHETICPOPULATION-TABLE3-5HOUSEHOLDCONTROLDATAFORPERMANENTHOUSEHOLDS">TABLE 3-5 HOUSEHOLD CONTROL DATA FOR PERMANENT HOUSEHOLDS</h4><div class="table-wrap">
 
+
{|  class="confluenceTable"
|*Household Attribute*|*Category Number*|*Categories*|*Data Source*|
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Household Attribute</strong></p>
|Householder unit type|1|Single family dwelling|NHTS 2009 add-on survey for Florida|
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Category Number</strong></p>
| |2|Multi family dwelling| |
+
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Categories</strong></p>
|Presence of children|1|Yes|NHTS 2009 add-on survey for Florida|
+
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Data Source</strong></p>
| |2|No| |
+
|-
|Householder age|1|15 to 24 years|NHTS 2009 add-on survey for Florida|
+
| class="confluenceTd" | <p>Householder unit type</p>
| |2|25 to 54 years| |
+
|  class="confluenceTd" | <p align="center">1</p>
| |3|55 to 64 years| |
+
| class="confluenceTd" | <p align="center">Single family dwelling</p>
| |4|65 to 74 years| |
+
| class="confluenceTd" | <p align="center">NERPM TAZ Data</p>
| |5|75 years and over| |
+
|-
|Household income (annual)|1|Less than $20,000|NHTS 2009 add-on survey for Florida|
+
|  class="confluenceTd" | <p></p>
| |2|$20,000 to $39,999| |
+
|  class="confluenceTd" | <p align="center">2</p>
| |3|$40,000 to $59,999| |
+
| class="confluenceTd" | <p align="center">Multi family dwelling</p>
| |4|$60,000 to $99,999| |
+
| class="confluenceTd" | <p align="center"></p>
| |5|$100,000 or more| |
+
|-
|Household size|1|1 person|NHTS 2009 add-on survey for Florida|
+
| class="confluenceTd" | <p>Presence of children</p>
| |2|2 persons| |
+
| class="confluenceTd" | <p align="center">1</p>
| |3|3 persons| |
+
|  class="confluenceTd" | <p align="center">Yes</p>
| |4|4 or more persons| |
+
|  class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
|Household size and workers joint|1|1 person, no worker|NHTS 2009 add-on survey for Florida|
+
|-
| |2|1 person, 1 worker| |
+
|  class="confluenceTd" | <p></p>
| |3|2 persons, no worker| |
+
| class="confluenceTd" | <p align="center">2</p>
| |4|2 persons, 1 worker| |
+
|  class="confluenceTd" | <p align="center">No</p>
| |5|2 persons, 2 workers| |
+
| class="confluenceTd" | <p align="center"></p>
| |6|3 persons, no worker| |
+
|-
| |7|3 persons, 1 worker| |
+
|  class="confluenceTd" | <p>Householder age</p>
| |8|3 persons, 2 workers| |
+
|  class="confluenceTd" | <p align="center">1</p>
| |9|4 or more persons, no worker| |
+
| class="confluenceTd" | <p align="center">15 to 24 years</p>
| |10|4 or more persons, 1 worker| |
+
| class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
| |11|4 or more persons, 2 workers| |
+
|-
| |12|4 or more persons, 3 workers| |
+
| class="confluenceTd" | <p></p>
 
+
| class="confluenceTd" | <p align="center">2</p>
h4. TABLE 3-8 PERSON CONTROL DATA FOR SEASONAL HOUSEHOLDS
+
| class="confluenceTd" | <p align="center">25 to 54 years</p>
 
+
|  class="confluenceTd" | <p align="center"></p>
|*Person Attribute*|*Category Number*|*Categories*|*Data Source*|
+
|-
|Gender|1|Male|NHTS 2009 add-on survey for Florida|
+
| class="confluenceTd" | <p></p>
| |2|Female| |
+
|  class="confluenceTd" | <p align="center">3</p>
|Age|1|0 to 17 years|NHTS 2009 add-on survey for Florida|
+
|  class="confluenceTd" | <p align="center">55 to 64 years</p>
| |2|18 to 24 years| |
+
| class="confluenceTd" | <p align="center"></p>
| |3|25 to 39 years| |
+
|-
| |4|40 to 54 years| |
+
| class="confluenceTd" | <p></p>
| |5|55 to 64 years| |
+
|  class="confluenceTd" | <p align="center">4</p>
| |6|65 to 74 years| |
+
|  class="confluenceTd" | <p align="center">65 to 74 years</p>
| |7|75 years and over| |
+
| class="confluenceTd" | <p align="center"></p>
 
+
|-
h4. TABLE 3-9 CONTROL DATA FOR GROUPQUARTERS RESIDENTS
+
| class="confluenceTd" | <p></p>
 
+
|  class="confluenceTd" | <p align="center">5</p>
|*Person Attribute*|*Category Number*|*Categories*|*Data Source*|
+
|  class="confluenceTd" | <p align="center">75 years and over</p>
|Gender|1|Male|Census 2010 and ACS 2006-10|
+
| class="confluenceTd" | <p align="center"></p>
| |2|Female| |
+
|-
|Age|1|Under 18 years|Census 2010 and ACS 2006-10|
+
|  class="confluenceTd" | <p>Household income (annual)</p>
| |2|18 to 64 years| |
+
|  class="confluenceTd" | <p align="center">1</p>
| |3|65 years and over| |
+
|  class="confluenceTd" | <p align="center">Less than $20,000</p>
 
+
| class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
h4. _Sample Data_
+
|-
 
+
| class="confluenceTd" | <p></p>
During population synthesis, individual household and person records are drawn from a disaggregate sample of households to match target distributions of controlled attributes. It may not be possible to control all the desired attributes and so “uncontrolled” attributes are added to the synthetic population from disaggregate sample data. It is essential that the disaggregate sample is representative of the population of the entire region.
+
|  class="confluenceTd" | <p align="center">2</p>
 
+
| class="confluenceTd" | <p align="center">$20,000 to $39,999</p>
In most cases, the primary source of disaggregate sample data will is Public Use Microdata Sample (PUMS) data, which is now part of the ACS, and follows the same sampling framework, but provides disaggregate records for households and persons across numerous different attributes. PUMS is sampled and grouped according to geographic units, better known as PUMAs. PUMAs cover contiguous areas of roughly 100,000 population, including persons living in group quarters. For example, a metro area of 850,000 might be covered by 8 or more likely 9 PUMAs. In general, ACS-PUMS provides good representative coverage of most regions and is rigorously tested and monitored, so it is was used for creating sample data for this effort.
+
|  class="confluenceTd" | <p align="center"></p>
 
+
|-
h4. _PopGen Run_
+
| class="confluenceTd" | <p></p>
 
+
| class="confluenceTd" | <p align="center">3</p>
The control totals and disaggregate sample data are input into a population synthesizer to generate a synthetic population. The joint distribution of the control attributes from the disaggregate sample is fitted to the control totals. This fitting or balancing is general done using the Iterative Proportional Fitting (IPF) algorithm or some variant of it which is at the core of most populations synthesizers. PopGen goes one step further in applying what is called an Iterative Proportional Updating (IPU) algorithm that not only matches household-level attribute totals but also person-level attribute controls simultaneously. The final step is then to draw individual household and person synthetic records from the disaggregate sample to match the fitted distribution.
+
| class="confluenceTd" | <p align="center">$40,000 to $59,999</p>
 
+
|  class="confluenceTd" | <p align="center"></p>
h3. {color:#FF6600}Microzone / Parcel Allocation{color}
+
|-
 
+
| class="confluenceTd" | <p></p>
As stated previously, DaySim operates at the parcel level. Since population synthesizers typically synthesize households at the TAZ level, synthetics households are then required to be assigned individual parcels or microzones. The process that does this need not be very complex. Currently, synthesized households of a particular TAZ are randomly assigned to all parcels within the TAZ based on parcel capacities. The parcel capacity or the number of housing units on a parcel is a required field in the base parcel file. The following steps are involved in the allocation process:
+
|  class="confluenceTd" | <p align="center">4</p>
 
+
|  class="confluenceTd" | <p align="center">$60,000 to $99,999</p>
# For all TAZs, parcel capacities are adjusted proportionately so that the total capacity obtained as a sum of capacities of all parcels within a TAZ is equal to the total number of households synthesized.
+
|  class="confluenceTd" | <p align="center"></p>
# Each of the synthetic households within a TAZ is randomly located in one of the parcels within the TAZ.
+
|-
 
+
| class="confluenceTd" | <p></p>
The process is the same for group quarter population and this requires group quarter capacities for each parcel. In case there are other sub-populations like permanent and seasonal, they are all combined before the parcel allocation process. Currently, there exists an R-script the takes the synthetic population from PopGen as input and allocates households to individual parcels. The script also processes and recodes other necessary demographic attributes required by DaySim from sample data (generally Census/ACS PUMS) used in population synthesis. It then outputs a households and a persons file which can directly be read as inputs by DaySim.
+
| class="confluenceTd" | <p align="center">5</p>
 +
|  class="confluenceTd" | <p align="center">$100,000 or more</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p>Household size</p>
 +
| class="confluenceTd" | <p align="center">1</p>
 +
| class="confluenceTd" | <p align="center">1 person</p>
 +
| class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">2 persons</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">3</p>
 +
| class="confluenceTd" | <p align="center">3 persons</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">4</p>
 +
| class="confluenceTd" | <p align="center">4 persons</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">5</p>
 +
| class="confluenceTd" | <p align="center">5 persons</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-  
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">6</p>
 +
| class="confluenceTd" | <p align="center">6 persons</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">7</p>
 +
|  class="confluenceTd" | <p align="center">7 or more persons</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p>Household size and workers joint</p>
 +
| class="confluenceTd" | <p align="center">1</p>
 +
| class="confluenceTd" | <p align="center">1 person, no worker</p>
 +
| class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">1 person, 1 worker</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">3</p>
 +
| class="confluenceTd" | <p align="center">2 persons, no worker</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">4</p>
 +
|  class="confluenceTd" | <p align="center">2 persons, 1 worker</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">5</p>
 +
| class="confluenceTd" | <p align="center">2 persons, 2 workers</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">6</p>
 +
| class="confluenceTd" | <p align="center">3 persons, no worker</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-  
 +
|  class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">7</p>
 +
|  class="confluenceTd" | <p align="center">3 persons, 1 worker</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">8</p>
 +
| class="confluenceTd" | <p align="center">3 persons, 2 workers</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">9</p>
 +
| class="confluenceTd" | <p align="center">3 persons, 3 workers</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">10</p>
 +
| class="confluenceTd" | <p align="center">4 or more persons, no worker</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">11</p>
 +
| class="confluenceTd" | <p align="center">4 or more persons, 1 worker</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">12</p>
 +
|  class="confluenceTd" | <p align="center">4 or more persons, 2 workers</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">13</p>
 +
| class="confluenceTd" | <p align="center">4 or more persons, 3 workers</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|}</div><h4 id="id-3.5SYNTHETICPOPULATION-TABLE3-6PERSONCONTROLDATAFORPERMANENTHOUSEHOLDS">TABLE 3-6 PERSON CONTROL DATA FOR PERMANENT HOUSEHOLDS</h4><div class="table-wrap">
 +
{|  class="confluenceTable"
 +
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Person Attribute</strong></p>
 +
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Category Number</strong></p>
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Categories</strong></p>
 +
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Data Source</strong></p>
 +
|-  
 +
| class="confluenceTd" | <p>Gender</p>
 +
| class="confluenceTd" | <p align="center">1</p>
 +
| class="confluenceTd" | <p align="center">Male</p>
 +
| class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
 +
|-  
 +
|  class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">2</p>
 +
| class="confluenceTd" | <p align="center">Female</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-  
 +
| class="confluenceTd" | <p>Age</p>
 +
| class="confluenceTd" | <p align="center">1</p>
 +
| class="confluenceTd" | <p align="center">Under 5 years</p>
 +
| class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">2</p>
 +
| class="confluenceTd" | <p align="center">5 to 14 years</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-  
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">3</p>
 +
| class="confluenceTd" | <p align="center">15 to 17 years</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">4</p>
 +
| class="confluenceTd" | <p align="center">18 to 24 years</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">5</p>
 +
| class="confluenceTd" | <p align="center">25 to 39 years</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-  
 +
|  class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">6</p>
 +
| class="confluenceTd" | <p align="center">40 to 54 years</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">7</p>
 +
| class="confluenceTd" | <p align="center">55 to 64 years</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-  
 +
| class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">8</p>
 +
| class="confluenceTd" | <p align="center">65 to 74 years</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">9</p>
 +
| class="confluenceTd" | <p align="center">75 years and over</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|}</div><h4 id="id-3.5SYNTHETICPOPULATION-TABLE3-7HOUSEHOLDCONTROLDATAFORSEASONALHOUSEHOLDS">TABLE 3-7 HOUSEHOLD CONTROL DATA FOR SEASONAL HOUSEHOLDS</h4><div class="table-wrap">
 +
{| class="confluenceTable"
 +
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Household Attribute</strong></p>
 +
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Category Number</strong></p>
 +
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Categories</strong></p>
 +
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Data Source</strong></p>
 +
|-
 +
| class="confluenceTd" | <p>Householder unit type</p>
 +
| class="confluenceTd" | <p align="center">1</p>
 +
| class="confluenceTd" | <p align="center">Single family dwelling</p>
 +
| class="confluenceTd" | <p align="center">NHTS 2009 add-on survey for Florida</p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">2</p>
 +
| class="confluenceTd" | <p align="center">Multi family dwelling</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p>Presence of children</p>
 +
| class="confluenceTd" | <p align="center">1</p>
 +
|  class="confluenceTd" | <p align="center">Yes</p>
 +
|  class="confluenceTd" | <p align="center">NHTS 2009 add-on survey for Florida</p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">2</p>
 +
| class="confluenceTd" | <p align="center">No</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-  
 +
| class="confluenceTd" | <p>Householder age</p>
 +
| class="confluenceTd" | <p align="center">1</p>
 +
| class="confluenceTd" | <p align="center">15 to 24 years</p>
 +
| class="confluenceTd" | <p align="center">NHTS 2009 add-on survey for Florida</p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">2</p>
 +
| class="confluenceTd" | <p align="center">25 to 54 years</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">3</p>
 +
| class="confluenceTd" | <p align="center">55 to 64 years</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">4</p>
 +
|  class="confluenceTd" | <p align="center">65 to 74 years</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">5</p>
 +
| class="confluenceTd" | <p align="center">75 years and over</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p>Household income (annual)</p>
 +
| class="confluenceTd" | <p align="center">1</p>
 +
| class="confluenceTd" | <p align="center">Less than $20,000</p>
 +
| class="confluenceTd" | <p align="center">NHTS 2009 add-on survey for Florida</p>
 +
|-  
 +
|  class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">$20,000 to $39,999</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">3</p>
 +
| class="confluenceTd" | <p align="center">$40,000 to $59,999</p>
 +
| class="confluenceTd" | <p align="center"></p>
 +
|-
 +
| class="confluenceTd" | <p></p>
 +
| class="confluenceTd" | <p align="center">4</p>
 +
|  class="confluenceTd" | <p align="center">$60,000 to $99,999</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">5</p>
 +
|  class="confluenceTd" | <p align="center">$100,000 or more</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p>Household size</p>
 +
|  class="confluenceTd" | <p align="center">1</p>
 +
|  class="confluenceTd" | <p align="center">1 person</p>
 +
|  class="confluenceTd" | <p align="center">NHTS 2009 add-on survey for Florida</p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">2 persons</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">3</p>
 +
|  class="confluenceTd" | <p align="center">3 persons</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">4</p>
 +
|  class="confluenceTd" | <p align="center">4 or more persons</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-  
 +
|  class="confluenceTd" | <p>Household size and workers joint</p>
 +
|  class="confluenceTd" | <p align="center">1</p>
 +
|  class="confluenceTd" | <p align="center">1 person, no worker</p>
 +
|  class="confluenceTd" | <p align="center">NHTS 2009 add-on survey for Florida</p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">1 person, 1 worker</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">3</p>
 +
|  class="confluenceTd" | <p align="center">2 persons, no worker</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">4</p>
 +
|  class="confluenceTd" | <p align="center">2 persons, 1 worker</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">5</p>
 +
|  class="confluenceTd" | <p align="center">2 persons, 2 workers</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">6</p>
 +
|  class="confluenceTd" | <p align="center">3 persons, no worker</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">7</p>
 +
|  class="confluenceTd" | <p align="center">3 persons, 1 worker</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">8</p>
 +
|  class="confluenceTd" | <p align="center">3 persons, 2 workers</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">9</p>
 +
|  class="confluenceTd" | <p align="center">4 or more persons, no worker</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">10</p>
 +
|  class="confluenceTd" | <p align="center">4 or more persons, 1 worker</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">11</p>
 +
|  class="confluenceTd" | <p align="center">4 or more persons, 2 workers</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">12</p>
 +
|  class="confluenceTd" | <p align="center">4 or more persons, 3 workers</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|}</div><h4 id="id-3.5SYNTHETICPOPULATION-TABLE3-8PERSONCONTROLDATAFORSEASONALHOUSEHOLDS">TABLE 3-8 PERSON CONTROL DATA FOR SEASONAL HOUSEHOLDS</h4><div class="table-wrap">
 +
{|  class="confluenceTable"
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Person Attribute</strong></p>
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Category Number</strong></p>
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Categories</strong></p>
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Data Source</strong></p>
 +
|-
 +
|  class="confluenceTd" | <p>Gender</p>
 +
|  class="confluenceTd" | <p align="center">1</p>
 +
|  class="confluenceTd" | <p align="center">Male</p>
 +
|  class="confluenceTd" | <p align="center">NHTS 2009 add-on survey for Florida</p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">Female</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p>Age</p>
 +
|  class="confluenceTd" | <p align="center">1</p>
 +
|  class="confluenceTd" | <p align="center">0 to 17 years</p>
 +
|  class="confluenceTd" | <p align="center">NHTS 2009 add-on survey for Florida</p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">18 to 24 years</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">3</p>
 +
|  class="confluenceTd" | <p align="center">25 to 39 years</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">4</p>
 +
|  class="confluenceTd" | <p align="center">40 to 54 years</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">5</p>
 +
|  class="confluenceTd" | <p align="center">55 to 64 years</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">6</p>
 +
|  class="confluenceTd" | <p align="center">65 to 74 years</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">7</p>
 +
|  class="confluenceTd" | <p align="center">75 years and over</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|}</div><h4 id="id-3.5SYNTHETICPOPULATION-TABLE3-9CONTROLDATAFORGROUPQUARTERSRESIDENTS">TABLE 3-9 CONTROL DATA FOR GROUPQUARTERS RESIDENTS</h4><div class="table-wrap">
 +
{|  class="confluenceTable"
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Person Attribute</strong></p>
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Category Number</strong></p>
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Categories</strong></p>
 +
|  class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Data Source</strong></p>
 +
|-
 +
|  class="confluenceTd" | <p>Gender</p>
 +
|  class="confluenceTd" | <p align="center">1</p>
 +
|  class="confluenceTd" | <p align="center">Male</p>
 +
|  class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">Female</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p>Age</p>
 +
|  class="confluenceTd" | <p align="center">1</p>
 +
|  class="confluenceTd" | <p align="center">Under 18 years</p>
 +
|  class="confluenceTd" | <p align="center">Census 2010 and ACS 2006-10</p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">2</p>
 +
|  class="confluenceTd" | <p align="center">18 to 64 years</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|-
 +
|  class="confluenceTd" | <p></p>
 +
|  class="confluenceTd" | <p align="center">3</p>
 +
|  class="confluenceTd" | <p align="center">65 years and over</p>
 +
|  class="confluenceTd" | <p align="center"></p>
 +
|}</div><h4 id="id-3.5SYNTHETICPOPULATION-SampleData"><em>Sample Data</em></h4><p class="BodyParagraph">During population synthesis, individual household and person records are drawn from a disaggregate sample of households to match target distributions of controlled attributes. It may not be possible to control all the desired attributes and so “uncontrolled” attributes are added to the synthetic population from disaggregate sample data. It is essential that the disaggregate sample is representative of the population of the entire region.</p><p class="BodyParagraph">In most cases, the primary source of disaggregate sample data will is Public Use Microdata Sample (PUMS) data, which is now part of the ACS, and follows the same sampling framework, but provides disaggregate records for households and persons across numerous different attributes. PUMS is sampled and grouped according to geographic units, better known as PUMAs. PUMAs cover contiguous areas of roughly 100,000 population, including persons living in group quarters. For example, a metro area of 850,000 might be covered by 8 or more likely 9 PUMAs. In general, ACS-PUMS provides good representative coverage of most regions and is rigorously tested and monitored, so it is was used for creating sample data for this effort.</p><h4 id="id-3.5SYNTHETICPOPULATION-PopGenRun"><em>PopGen Run</em></h4><p class="BodyParagraph">The control totals and disaggregate sample data are input into a population synthesizer to generate a synthetic population. The joint distribution of the control attributes from the disaggregate sample is fitted to the control totals. This fitting or balancing is general done using the Iterative Proportional Fitting (IPF) algorithm or some variant of it which is at the core of most populations synthesizers. PopGen goes one step further in applying what is called an Iterative Proportional Updating (IPU) algorithm that not only matches household-level attribute totals but also person-level attribute controls simultaneously. The final step is then to draw individual household and person synthetic records from the disaggregate sample to match the fitted distribution.</p><h3 id="id-3.5SYNTHETICPOPULATION-Microzone/ParcelAllocation"><span style="color: rgb(255,102,0);">Microzone / Parcel Allocation</span></h3><p class="BodyParagraph">As stated previously, DaySim operates at the parcel level. Since population synthesizers typically synthesize households at the TAZ level, synthetics households are then required to be assigned individual parcels or microzones. The process that does this need not be very complex. Currently, synthesized households of a particular TAZ are randomly assigned to all parcels within the TAZ based on parcel capacities. The parcel capacity or the number of housing units on a parcel is a required field in the base parcel file. The following steps are involved in the allocation process:</p><ol><li>For all TAZs, parcel capacities are adjusted proportionately so that the total capacity obtained as a sum of capacities of all parcels within a TAZ is equal to the total number of households synthesized.</li><li>Each of the synthetic households within a TAZ is randomly located in one of the parcels within the TAZ.</li></ol><p>The process is the same for group quarter population and this requires group quarter capacities for each parcel. In case there are other sub-populations like permanent and seasonal, they are all combined before the parcel allocation process. Currently, there exists an R-script the takes the synthetic population from PopGen as input and allocates households to individual parcels. The script also processes and recodes other necessary demographic attributes required by DaySim from sample data (generally Census/ACS PUMS) used in population synthesis. It then outputs a households and a persons file which can directly be read as inputs by DaySim.</p>

Revision as of 21:00, 17 October 2016


Overview

In trip-based models, trip rates are applied to aggregate households grouped in Traffic Analysis Zones (TAZs) to generate trips. On the other hand, in an activity-based model (ABM), choices involving activities and trips are simulated for each of the individual persons in households. Hence, it is necessary to first develop a “synthetic population” of the regions’ residents. Synthetic population is a list of households and persons that is based on observed or forecasted distributions of socioeconomic attributes and created by sampling detailed Census microdata. This produces individual household agents and individual person agents that are subjects of the simulation.

Prior to their use in the simulation, synthetic populations are represented in data tables, often in a relational database or some equivalently structured file system. Typically there are separate tables for households and person records. The household records file provides details about various household-level socio-demographic attributes such as household income, size, number of workers, etc. Similarly, the person records file provides information about person-level attributes such as age, gender, employment status, etc. Person records are linked to household records through ID numbers.

TABLE 3-2 SAMPLE HOUSEHOLD RECORDS FILE

TAZ

HHID

Age of Household Head

Number of persons

Income Group

Presence of Children

Number Workers

143

16667

1

2

1

1

1

193

17392

1

2

4

0

1

77

232

1

3

1

1

2

18

5042

1

4

3

1

3

TABLE 3-3 SAMPLE PERSON RECORDS FILE

TAZ

HHID

Person ID

Age

Works from Home

Employment Status

Gender

Hours Worked per Week

77

232

1

22

1

1

2

9

77

232

2

24

1

0

1

45

77

232

3

1

0

1

2

0

Population synthesized by any synthetic population generator may be used with DaySim as long as the required household and person socio-demographic attributes are provided to it in the appropriate format. PopGen, the synthetic population generator developed at Arizona State University (ASU) was chosen for this effort primarily for two reasons. First, it has the ability to control for both household and person level demographic attributes simultaneously. Second, it has an easy-to-use and simple graphical user interface (GUI).

Preparing Synthetic Populations for DaySim

The design of the synthetic population should support the design of the activity-based model (DaySim in this case) and provide the variables it needs. In addition, the activity-based model should only rely on information that can be realistically provided in the synthetic population.

Population synthesis generally consists of the synthesis of two sub-populations – those living in regular households and those living in non-institutionalized group quarters such as college dormitories. For this effort, an additional segment of population was synthesized which comprised of seasonal households. These segments were established to reflect the differences in travel patterns associated with these sub-populations as well as to provide the ability to support seasonal analyses. For example, the seasonal population is generally older than the permanent population, has lower levels of workforce participation, and clusters in certain geographic areas. All of these attributes influence travel patterns and the demand for travel.

There are three major steps in creating a synthetic population:

  1. Specifying the inputs to the process—the control variables and sample households as well as the level of geographic resolution. Specifying the control variables is essential. In addition, there is often an additional step of specifying additional, uncontrolled variables to be added to the synthetic population.
  2. Actually running a program that produces the synthetic households.
  3. The third major step would be transforming the model-generated outputs into characteristics of the population that will be used throughout the rest of the model system. This could involve creating categorical variables out of continuous variables, reformulating income, or allocating households from the zonal level to a finer level of geographic resolution, such as a parcel.

DaySim Person Types

Although person are being modeled in disaggregate form in an ABM, it is often useful to create person type categories. DaySim uses 8 such person types. Person type categories may be used for various purposes:

  1. As a basic segmentation for certain models, such as daily activity pattern models
  2. To summarize and compare observed versus estimated data and calibrate models
  3. As explanatory variables in models
  4. As constraints on alternatives that are available; for example, work and school activities are only available to workers and student; and driving is restricted by age

TABLE 3-4 DAYSIM PERSON TYPES

No.

Person Type

Age

Work Status

School Status

1

Full-time worker

18 or more

Full-time

None/Part-time

2

Part-time worker

18 or more

Part-time

None/Part-time

3

Retired person

65 or more

Unemployed

4

Non-working adult

Less than 65

Unemployed

None/Part-time

5

University student

18 or more

Unemployed/Part-time

Full-time

6

High school student

16 or more

Unemployed/Part-time

Full-time

7

Primary school child

5-15

Unemployed

Full-time

8

Preschool child

0-4

Unemployed

None

Control Attributes and Target Distributions

There are three major inputs required for population synthesis of which the first step is to identify a set of control attributes and their levels. Next, target distributions of the control attributes and their levels are derived at appropriate geographic units. These target distributions are also known as marginal control totals since they represent the margins of a joint distribution of multiple attributes. Typically, the smallest level of spatial resolution that can be feasibly and reliably used to control attributes is used. If control attribute totals are not accurate at a particular spatial unit, they could be specified at a lower resolution.

The following considerations are usually important in choosing control variables:

  • The number of control variables is important. If there are too few, the synthetic population may not accurately reflect the true population. On the other hand, too many control attributes may cause sample issues. There may not be any sample households with joint attributes of the control variables and this could distort the synthetic population.
  • Control attributes may be single or multi-dimensional. Multi-dimensional attributes can be treated as single dimensional attributes with number of categories equal to the product of the numbers of categories in individual attributes. The primary advantage of multi-dimensional attributes is more precise regional control over the correlation between attributes. The disadvantage again is with sparse sample.
  • The best choices of variables, will be meaningful attributes that are somewhat “orthogonal” to each other, which means that their variance in the population is largely independent. Conversely, if there are two attributes that are highly correlated, then controlling for both may not achieve much more than controlling for just one.
  • Finally, different sets of control attributes may be used for base and forecast years, if limited by forecasting accuracy. This is not necessarily desirable, though. The ability to forecast marginal control totals should be a consideration when specifying control attributes for this base year.

Target distributions of control variables for the base year could be obtained from a variety of data sources including the following:

  • Decennial Census: ~100% sample
  • American Community Survey (ACS) summary files: 3% sample, rolling 5-year sample, yields an estimate of ~15% of population
  • Census Transportation Planning Products (CTPP)
  • Other zonal data developed locally (TAZs)

For the forecast year, regional socio-economic forecasts or outputs from a land-use model are often used.

The following tables provide the list of control attributes and their levels along with the specific data sources used to obtain corresponding target distributions. All the distributions were obtained at the TAZ level.

TABLE 3-5 HOUSEHOLD CONTROL DATA FOR PERMANENT HOUSEHOLDS

Household Attribute

Category Number

Categories

Data Source

Householder unit type

1

Single family dwelling

NERPM TAZ Data

2

Multi family dwelling

Presence of children

1

Yes

Census 2010 and ACS 2006-10

2

No

Householder age

1

15 to 24 years

Census 2010 and ACS 2006-10

2

25 to 54 years

3

55 to 64 years

4

65 to 74 years

5

75 years and over

Household income (annual)

1

Less than $20,000

Census 2010 and ACS 2006-10

2

$20,000 to $39,999

3

$40,000 to $59,999

4

$60,000 to $99,999

5

$100,000 or more

Household size

1

1 person

Census 2010 and ACS 2006-10

2

2 persons

3

3 persons

4

4 persons

5

5 persons

6

6 persons

7

7 or more persons

Household size and workers joint

1

1 person, no worker

Census 2010 and ACS 2006-10

2

1 person, 1 worker

3

2 persons, no worker

4

2 persons, 1 worker

5

2 persons, 2 workers

6

3 persons, no worker

7

3 persons, 1 worker

8

3 persons, 2 workers

9

3 persons, 3 workers

10

4 or more persons, no worker

11

4 or more persons, 1 worker

12

4 or more persons, 2 workers

13

4 or more persons, 3 workers

TABLE 3-6 PERSON CONTROL DATA FOR PERMANENT HOUSEHOLDS

Person Attribute

Category Number

Categories

Data Source

Gender

1

Male

Census 2010 and ACS 2006-10

2

Female

Age

1

Under 5 years

Census 2010 and ACS 2006-10

2

5 to 14 years

3

15 to 17 years

4

18 to 24 years

5

25 to 39 years

6

40 to 54 years

7

55 to 64 years

8

65 to 74 years

9

75 years and over

TABLE 3-7 HOUSEHOLD CONTROL DATA FOR SEASONAL HOUSEHOLDS

Household Attribute

Category Number

Categories

Data Source

Householder unit type

1

Single family dwelling

NHTS 2009 add-on survey for Florida

2

Multi family dwelling

Presence of children

1

Yes

NHTS 2009 add-on survey for Florida

2

No

Householder age

1

15 to 24 years

NHTS 2009 add-on survey for Florida

2

25 to 54 years

3

55 to 64 years

4

65 to 74 years

5

75 years and over

Household income (annual)

1

Less than $20,000

NHTS 2009 add-on survey for Florida

2

$20,000 to $39,999

3

$40,000 to $59,999

4

$60,000 to $99,999

5

$100,000 or more

Household size

1

1 person

NHTS 2009 add-on survey for Florida

2

2 persons

3

3 persons

4

4 or more persons

Household size and workers joint

1

1 person, no worker

NHTS 2009 add-on survey for Florida

2

1 person, 1 worker

3

2 persons, no worker

4

2 persons, 1 worker

5

2 persons, 2 workers

6

3 persons, no worker

7

3 persons, 1 worker

8

3 persons, 2 workers

9

4 or more persons, no worker

10

4 or more persons, 1 worker

11

4 or more persons, 2 workers

12

4 or more persons, 3 workers

TABLE 3-8 PERSON CONTROL DATA FOR SEASONAL HOUSEHOLDS

Person Attribute

Category Number

Categories

Data Source

Gender

1

Male

NHTS 2009 add-on survey for Florida

2

Female

Age

1

0 to 17 years

NHTS 2009 add-on survey for Florida

2

18 to 24 years

3

25 to 39 years

4

40 to 54 years

5

55 to 64 years

6

65 to 74 years

7

75 years and over

TABLE 3-9 CONTROL DATA FOR GROUPQUARTERS RESIDENTS

Person Attribute

Category Number

Categories

Data Source

Gender

1

Male

Census 2010 and ACS 2006-10

2

Female

Age

1

Under 18 years

Census 2010 and ACS 2006-10

2

18 to 64 years

3

65 years and over

Sample Data

During population synthesis, individual household and person records are drawn from a disaggregate sample of households to match target distributions of controlled attributes. It may not be possible to control all the desired attributes and so “uncontrolled” attributes are added to the synthetic population from disaggregate sample data. It is essential that the disaggregate sample is representative of the population of the entire region.

In most cases, the primary source of disaggregate sample data will is Public Use Microdata Sample (PUMS) data, which is now part of the ACS, and follows the same sampling framework, but provides disaggregate records for households and persons across numerous different attributes. PUMS is sampled and grouped according to geographic units, better known as PUMAs. PUMAs cover contiguous areas of roughly 100,000 population, including persons living in group quarters. For example, a metro area of 850,000 might be covered by 8 or more likely 9 PUMAs. In general, ACS-PUMS provides good representative coverage of most regions and is rigorously tested and monitored, so it is was used for creating sample data for this effort.

PopGen Run

The control totals and disaggregate sample data are input into a population synthesizer to generate a synthetic population. The joint distribution of the control attributes from the disaggregate sample is fitted to the control totals. This fitting or balancing is general done using the Iterative Proportional Fitting (IPF) algorithm or some variant of it which is at the core of most populations synthesizers. PopGen goes one step further in applying what is called an Iterative Proportional Updating (IPU) algorithm that not only matches household-level attribute totals but also person-level attribute controls simultaneously. The final step is then to draw individual household and person synthetic records from the disaggregate sample to match the fitted distribution.

Microzone / Parcel Allocation

As stated previously, DaySim operates at the parcel level. Since population synthesizers typically synthesize households at the TAZ level, synthetics households are then required to be assigned individual parcels or microzones. The process that does this need not be very complex. Currently, synthesized households of a particular TAZ are randomly assigned to all parcels within the TAZ based on parcel capacities. The parcel capacity or the number of housing units on a parcel is a required field in the base parcel file. The following steps are involved in the allocation process:

  1. For all TAZs, parcel capacities are adjusted proportionately so that the total capacity obtained as a sum of capacities of all parcels within a TAZ is equal to the total number of households synthesized.
  2. Each of the synthetic households within a TAZ is randomly located in one of the parcels within the TAZ.

The process is the same for group quarter population and this requires group quarter capacities for each parcel. In case there are other sub-populations like permanent and seasonal, they are all combined before the parcel allocation process. Currently, there exists an R-script the takes the synthetic population from PopGen as input and allocates households to individual parcels. The script also processes and recodes other necessary demographic attributes required by DaySim from sample data (generally Census/ACS PUMS) used in population synthesis. It then outputs a households and a persons file which can directly be read as inputs by DaySim.