Buildings
The
buildings table in the zone version of the model system is an aggregation of the individual buildings located on parcels within a zone that are of the same building type. Note that even single-family buildings will therefore have more than 1 residential unit, since this is like representing single-family as an aggregated subdivision. There should be only one record per building_type per zone.
| Column Name |
Data Type |
Required |
Description |
| building_id |
Integer |
Y |
Unique id of building (one per zone and building type) |
| land_area |
Integer |
N |
Land area in sqft used by the aggregate building |
| non_residential_sqft |
Integer |
Y |
Total non-residential sqft in building |
| non_residential_sqft_capacity |
Integer |
Y |
Developable capacity for non-residential sqft in the zone for this building type |
| residential_units |
Integer |
Y |
Total residential units in building |
| residential_units_capacity |
Integer |
Y |
Developable capacity for residential units in the zone of this building type |
| sqft_per_unit |
Integer |
N |
Average square feet per residential unit in building |
| year_built |
Integer |
N |
Average year built of this aggregated building |
| average_value_per_unit |
Integer |
Y |
Average property value (land + building) per unit (either residential units or non-residential sqft) |
| zone_id |
Integer |
Y |
Unique id of the zone in which this building is located |
| building_type_id |
Integer |
Y |
Unique id of the building type of this building |
--
PaulWaddell - 08 Dec 2009
Changed land_area, sqft_per_unit, and year_built to be optional fields. I am able to run the entire model system sans these fields. Also, these fields do not appear to be updated by any of the models during the simulation. All of this leads me to believe that they are currently optional fields.
--
JesseAyers - 27 Jan 2010
Topic revision: r4 - 20 May 2010 - 00:42:28 -
PaulWaddell