Integrating Versions, History, and Levels-of-Detail within a 3D Geodatabase

The sustainable management and continuation of virtual 3D city models puts specific demands on 3D geodatabases. These demands result from the need to manage three different dimensions of multiple representation: Levels-of-detail, concurrent planning versions, and history over time. In this paper we propose a concept for the integration of all three aspects in the framework of spatial relational database management systems. User applications need to see resp. work with different states of the database content, e.g.. the current state “as-built” or the current state plus certain approved plannings. It is shown how the workspace manager of the RDBMS can be extended by structures, which allow to combine these versions in so called City Model Aspects. Specific spatial integrity checks are introduced in order to avoid conflicts between spatially disconnected concurrent plannings.     «

The sustainable management and continuation of virtual 3D city models puts specific demands on 3D geodatabases. These demands result from the need to manage three different dimensions of multiple representation: Levels-of-detail, concurrent planning versions, and history over time. In this paper we propose a concept for the integration of all three aspects in the framework of spatial relational database management systems. User applications need to see resp. work with different states of the dat...     »