household table structure#
Records the households synthesized in the simulation and all associated characteristics and metrics aggregated at the household level. Certain columns are directly obtained from the ACS, while others are synthesized through demand models executed during simulation.
Records are either a result of population synthesis or are being moved from one Demand database to the next when reading population from database.
Field |
Type |
NULL allowed |
Default Value |
Foreign key |
Description |
|---|---|---|---|---|---|
household* |
INTEGER |
NO |
The unique identifier for the household |
||
hhold |
INTEGER |
NO |
The upstream (i.e. PUMS) identifier for the household |
||
location |
INTEGER |
NO |
The location to which this household is attached (foreign key to the Location table) |
||
persons |
INTEGER |
NO |
0 |
Number of household members |
|
workers |
INTEGER |
NO |
0 |
Number of workers in the household as defined by WiF from the ACS (number of people over 15 that worked one week or more in the last year, capped at 3+) |
|
vehicles |
INTEGER |
NO |
0 |
Number of vehicles in the household |
|
type |
INTEGER |
NO |
0 |
Household type as defined by the ACS and represented the enumValues at type. |
|
income |
INTEGER |
NO |
0 |
Annual household income (ACS field HINCP) |
|
bikes |
INTEGER |
NO |
0 |
Number of bicycles in the household |
|
housing_unit_type |
INTEGER |
NO |
0 |
Type of the housing unit Values at housing_unit_type. |
|
ecom |
INTEGER |
NO |
0 |
Number of e-commerce packages received in the simulated day by the household |
|
delRat |
REAL |
YES |
0 |
Delivery ratio |
|
dispose_veh |
INTEGER |
NO |
boolean flag - were one or more vehicles disposed within the household? |
||
time_in_home |
REAL |
NO |
0 |
Time this household has been resident at this location (unit: years) |
|
Has_Residential_Charging |
INTEGER |
NO |
0 |
boolean flag - does household have an EV charging station? |
|
num_groceries |
INTEGER |
NO |
0 |
Number of grocery deliveries received in the simulated day by the household |
|
num_meals |
INTEGER |
NO |
0 |
Number of meal deliveries received in the simulation day by the household |
(* - Primary key)
The SQL statement for table and index creation is below.
CREATE TABLE "Household" (
"household" INTEGER NOT NULL PRIMARY KEY AUTOINCREMENT,
"hhold" INTEGER NOT NULL,
"location" INTEGER NOT NULL,
"persons" INTEGER NOT NULL DEFAULT 0,
"workers" INTEGER NOT NULL DEFAULT 0,
"vehicles" INTEGER NOT NULL DEFAULT 0,
"type" INTEGER NOT NULL DEFAULT 0,
"income" INTEGER NOT NULL DEFAULT 0,
"bikes" INTEGER NOT NULL DEFAULT 0,
"housing_unit_type" INTEGER NOT NULL DEFAULT 0,
"ecom" INTEGER NOT NULL DEFAULT 0,
"delRat" REAL NULL DEFAULT 0,
"dispose_veh" INTEGER NOT NULL,
"time_in_home" REAL NOT NULL DEFAULT 0,
"Has_Residential_Charging" INTEGER NOT NULL DEFAULT 0,
"num_groceries" INTEGER NOT NULL DEFAULT 0,
"num_meals" INTEGER NOT NULL DEFAULT 0
)
Enums#
The following enums are used in this table.
type#
Value |
Description |
|---|---|
1 |
HHT_OWN_FAMILY_MARRIED |
2 |
HHT_OWN_FAMILY_MALE |
3 |
HHT_OWN_FAMILY_FEMALE |
4 |
HHT_OWN_NONFAMILY_SINGLE |
5 |
HHT_OWN_NONFAMILY_OTHER |
6 |
HHT_RENT_FAMILY_MARRIED |
7 |
HHT_RENT_FAMILY_MALE |
8 |
HHT_RENT_FAMILY_FEMALE |
9 |
HHT_RENT_NONFAMILY_SINGLE |
10 |
HHT_RENT_NONFAMILY_OTHER |
11 |
HHT_GQ |
housing_unit_type#
Value |
Description |
|---|---|
1 |
HU_SINGLE_FAMILY |
2 |
HU_SMALL_APT_BLD |
3 |
HU_LARGE_APT_BLD |
4 |
HU_OTHER |
5 |
HU_GROUP_QUARTERS |