Disaggregate models with aggregate data: Two UrbanSim applications

Abstract

UrbanSim has significant data requirements. In particular, it requires disaggregate data (traditionally at the 150 meter by 150 meter gridcell level) for employment, households, and buildings. While such data are not always easily available, most regions have readily available data in a more aggregate form, often at the level of traffic analysis zone (TAZ) or other municipal divisions. This paper describes two UrbanSim applications for the cities of Brussels, Belgium and Lyon, France that adopted different approaches of using aggregate data. In Brussels, aggregate zonal data were disaggregated to the gridcell level. In the Lyon application, the zone was used as the unit of analysis and as such, each zone corresponds to one gridcell. The objectives of this paper are: 1) establish whether an UrbanSim model can be developed using aggregate data; 2) describe two different approaches to using aggregate data with UrbanSim and evaluate; and 3) evaluate the advantages and disadvantages of using aggregate data, as well as the two different approaches described. In doing so, it advances knowledge in the field of transportation and land use modeling by helping modelers evaluate the use of an increasingly popular integrated transportation land use modeling option. Several conclusions flow from this work. First, aggregate data can be used to develop UrbanSim models. Second, only a limited amount of disaggregate information can be drawn from aggregate data. In the context of UrbanSim, this is manifested in models with relatively few variables and dubious simulation results—in other words, while it is possible to develop an UrbanSim application with aggregate data, it should not be used for applied analysis. Finally, the development of such models can be a relatively low-cost exercise to gain familiarity with UrbanSim’s functioning and data requirements. As a result, it can also be seen as an important first step to developing or evaluating UrbanSim for application in a new region.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 33 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.