UrbanSim\OPUS Real Estate Development model. Notes prepared by: Jesse Ayers Maricopa Association of Governments Last revised: 1/29/2009. Real Estate Developer Model.
Notes prepared by:
Maricopa Association of Governments
Last revised: 1/29/2009
Update 3/17/2009: it turns out that the development_project_proposal_components table is not a required table in the base year for a planned project proposal. The model system will construct this table automatically. For details, see the create_from_proposals_and_template_components() function in the development_project_proposal_component_dataset.py
This set of records represents one fairly dense SFR proposal that will be built by the model system starting in year 2011:
These can be 0 here because we don’t care, is_active = 0 so this template will only be used for planned proposalsColumn notes
0 = builds regardless of existing buildings, 1 = demolishes existing buildings
Cost per unit in terms of these units
(e.g. 98.7067 * 1933 = $190,800)
100 = a single free-standing building.
Multiple component records with this adding
up to 100 represent a single building w/ multiple uses.
Multiple component records each = 100 represents
multiple free-standing buildings with different uses. I honestly don’t know how extensively it is used without further research.
Update 3/18/2009: this affects the units_proposed.py variable at urbansim_parcel.development_project_proposal.
5 year plan with those percentages built per year