| Column Name | Data Type | Required | Description |
|---|---|---|---|
| template_id | Integer | Y | A unique identifier for the template |
| percent_land_overhead | Integer | Y | The percent of land required for purposes other than buildings, e.g. landscaping, parking |
| land_sqft_min | Integer | Y | The minimum land area needed for the template |
| land_sqft_max | Integer | Y | The maximum land area used by the template |
| density_type | String | Y | The density measure for the template. The value must be 'units_per_acre' or 'far' |
| density | Float | Y | The density of the template |
| land_use_type_id | Integer | Y | The land use type id of the template |
| development_type | String | N | A description of the development type, e.g. single-family residential, retail, office |
| is_active | Integer | N? | The possible values are 1 for active and 0 for not active. Templates with is_active=0 can be used for known future projects without an active template |
The contents of this table are roughly comparable to the development_project_proposals table, since development templates become proposals if they are determined to fit within parcel constraints. Proposals become projects if they are chosen for construction by the Development Project Proposal Regression Model. See also a sample populated table.
-- PeterMcNally - 04 Nov 2009
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.