VU.CITY Knowledge Base logo
  1. Home
  2. VU.CITY Early Access
  3. Migration
  4. Cameras, targets and viewsheds
An icon of a circle with a information symbol insideOur Early Access platform is currently under active development. As a result, some features and functionality may be subject to change before this information is updated. Get in touch with us if you require assistance.

Cameras, targets and viewsheds

Last updated: 15 October 2026 10:04 BST

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.

  • Scene

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.

  • View collection

  • Legacy

Viewpoints

Viewpoints represent individual camera positions. Saved camera views from Legacy are migrated as viewpoints, preserving the camera position.

Camera targets are not migrated. If a Legacy camera view had a target assigned to it, the migrated viewpoint retains the camera position, but the target and its associated outline are not transferred. Targets can be recreated in the new application where needed.

  • Viewpoint

  • Legacy

Relevant links:

Target behaviour

Camera targets and their associated outlines are not migrated from Legacy. Although the camera position is preserved in the migrated viewpoint, any target assigned to the original camera view must be recreated in the new application where needed.

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.


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.