<?phpxml version="1.0" encoding="ISO-8859-1"?>
 <collection>
  

 
<record>
 <datafield tag="088" ind1="" ind2="">
  <subfield code="a">ZP-STRC-07</subfield> 
  </datafield>
<datafield tag="909" ind1="C" ind2="0">
<subfield code="p">TRANSP-OR</subfield>
</datafield>
<datafield tag="980" ind1="" ind2="">
<subfield code="a">TALK</subfield>
</datafield>
 <datafield tag="700" ind1="" ind2="">
  <subfield code="a">Patterson, Zachary</subfield> 
  </datafield>
 <datafield tag="700" ind1="" ind2="">
  <subfield code="a">Bierlaire, Michel</subfield> 
  </datafield>
<datafield tag="245" ind1="" ind2="">
<subfield code="a">
An UrbanSim Model of Brussels in a Short Timeline</subfield>
</datafield>
<datafield tag="260" ind1="" ind2="">
<subfield code="c">2007</subfield>
</datafield>
<datafield tag="711" ind1="2" ind2="">
<subfield code="a">
Swiss Transport Research Conference</subfield>
<subfield code="c">
Monte Verita</subfield>
<subfield code="d">September 13, 2007</subfield>
</datafield>
<datafield tag="520" ind1="" ind2="">
<subfield code="a">
UrbanSim is an increasingly popular integrated transportation land-use model. A particularly
attractive feature of UrbanSim is its disaggregate frame of analysis. This characteristic means it requires much land-use and socio-economic data at a fine scale. This research was conceived as a feasibility study. In particular, it asked ‘Is it possible to mount an UrbanSim model with relatively aggregate data (from a TRANUS application) and limited human resources in three to four months?’ The conclusions are as follows. It was possible to mount an UrbanSim model with the limited resources and data available. The UrbanSim sub-models estimated were not very robust, compromising simulation results. Weaknesses of the sub-models were not due to the use of disaggregate data. The weaknesses were due to insufficient exploitation of existing
data and the lack of some critical data. It was not possible to mount a travel model AND an
UrbanSim model given the time and resource constraints.</subfield>
</datafield>
  </record>



  </collection>
