“eHeritage Dunedin is a virtual 3D walkthrough of Dunedin, allowing users to view the city at various stages of its history.”

“eHeritage Dunedin is a virtual 3D model of Dunedin, allowing users to view the city at various stages of its history.”

“eHeritage Dunedin is an interactive 3D model of Dunedin, allowing museum visitors to view the city at various stages of its history.”

As the bulk of our project is 3D modelling and texturing, which are both time-consuming, manual tasks, we focussed on developing a system that would:Store resources in such a way that they can

easily be accessed for modelling or texturing.Organize geo-data according to year, including

GIS-data, aerial photographs, parcel/building information.

Be scalable, allowing for extra years to be added easily, or extra data to be added to any existing years.

A significant lack of data: building heights.But data being collected over the next few

years...So what should we do? Two options:

Populate the system with inaccurate test data.Use other data to demonstrate the capability of

the system, although not within our initial spec.

The system shall store data from each year in separate layers, allowing for isolated editing.

The system shall link layers to allow for relationship queries.

The system shall georeference historical town maps to present land parcel data from the DCC.

The system shall plot building footprints over land parcels.

The system shall extrude building footprints to 3D models.

The system shall render 3D buildings using texture maps.

The system shall catalogue existing resources (photos, articles, etc.) into a database.

The user can navigate the 3D environment. The user can change time period. The user can interact with 3D environment

(additional information about buildings, sites).The client can update database as required.

Database (April):The system shall catalogue existing resources

(photos, articles, etc.) into a database. The client can update database as required.

Front-End (April):The user can navigate the 3D environment. The user can change time period. The user can interact with 3D environment

(additional information about buildings, sites).

Database updates – checks put in place to ensure data quality.

Front-End display – whole city or specific areas? Load-time considerations...

Map viewer as separate deliverable?Open source IDE development – TSQL vs

MySQL; Flash vs FlashDevelop – budgeting.Technical complexity – client technical

competence.