Some of the concepts used to save and organise camera views have changed in the new application. Existing visibility states, camera views and camera studies are migrated into the equivalent new structures.

Visibility state ➡ Scene

Camera study ➡ View collection

Camera view ➡ Viewpoint

Scenes

A scene replaces the legacy visibility state and stores the state of the project at a particular point in time.

A migrated scene can include:

• model visibility
• hidden or highlighted elements
• active data layers
• date and time
• sun position
• weather and atmospheric conditions
• styling settings such as edge lines

All project assets remain available within the scene, with their visibility configured according to the original visibility state.

View collections

Camera studies are replaced by view collections.

Where a legacy camera study contained multiple saved camera views, these are migrated as viewpoints within the corresponding view collection.

This allows existing groups of related views to remain organised in the new application.

Viewpoints

A viewpoint represents an individual camera position.

Where a camera view was saved in Legacy, it is migrated as a viewpoint in the new application. The camera position is preserved, and where a target location was defined, the viewpoint retains that target and can remain locked to it.

Relevant links:

• Creating viewpoints
• View collections
• Scene manager
• Scene switcher

Viewsheds

Viewshed results are not migrated because in the Legacy they exist as live line-of-sight calculations rather than saved project data.

Saved viewpoints used to create a Viewshed are migrated and remain available in the new application. This provides the same starting position for recreating the analysis. In the new application the analysis can be run again using the new Viewshed tool.

Highlighting and target behaviour

Where a legacy view was focused on a particular building or area, the associated target information is preserved where supported.

The way visual emphasis is represented may differ in the new application. Imported models and canvas-based elements may use different highlighting or representation to achieve an equivalent result.

What may look different

Although the information contained in a migrated view is preserved, its appearance may not be identical to the Legacy version. Differences may occur because scenes, viewpoints and highlighting are handled differently in the new application.