VU.CITY Logo
+44 (0)20 8432 7000
Facebook iconLinkedIn iconYouTube iconInstagram iconX (formerly Twitter) icon

Privacy policy | Cookie policy - Terms and conditions for: Private Sector | Public sector

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
© 2025 All rights reserved VU.CITY Limited.
VU.CITY Knowledge Base logo
Search...
  • VU.CITY Hub
    • Getting started
      • Introduction to VU.CITY Hub
      • Personal Drive and Project Drive
      • Purchasing a subscription
    • Account Management
      • Sign up to the Hub
      • Update account settings
      • Setting VU.CITY 3D environment
    • Organisation Management
      • Creating an organisation
      • Updating organisation settings
      • Organisation roles
      • Inviting members to join
      • Joining an organisation
      • Assigning subscriptions
      • Removing organisation member
    • Project management
      • Managing project and file access
      • Creating a project
      • Deleting a project
      • Updating project access
      • Launch a project in 3D
      • Upload files to project drive
      • Assigning a primary file
      • Update file access
    • Purchasing geometry
      • Using the coverage map
      • Formats available
      • Pricing
    • Release notes
      • Release notes - Hub
  • VU.CITY 3D
    • Getting started
      • Introduction to VU.CITY 3D
      • Navigating the VU.CITY 3D
      • Cloud session control
      • Request city model split
      • Reporting city model errors
    • Selecting your environment
      • Cloud vs Desktop
      • Network requirements and system - Cloud
      • System requirements - Desktop
      • Network configuration - Desktop
      • Network configuration - Cloud
    • Importing Models
      • Model requirements
      • Model optimisation
      • Geolocation
      • 3D model submission
      • Import workflows
    • File management
      • Merge
      • Auto and manual save files
    • Create
      • Create tool
      • Creating your first model
      • Exporting your model
    • ZTV
      • ZTV model requirements
      • ZTV analysis
      • Understanding the ZTV
    • Data
      • Data layers
      • Protected views
      • Timeline
      • Reporting missing Timeline data
      • Add your own point data
    • World scene tools
      • Measure
      • Style
      • Highlight
      • Hide
      • Tag
    • Cameras
      • Camera tool
      • Visibility states
      • Viewshed
      • Presenter
      • 180° and 360° Panoramic Views
      • Add your views from a CSV
    • Release notes
      • Release notes - VU.CITY Cloud
      • Release notes - VU.CITY Desktop
  • SiteSolve
    • Getting started
      • Introduction to SiteSolve
      • System and networking requirements
      • Data storage and file handling
    • Project management
      • Starting a project
      • Saving and loading project
      • Importing files
      • Importing settings
      • Exporting files and data
    • Setting up a site
      • Setting up a site boundary
      • Adjusting the site geometry
      • Exclusion zones
      • Managing height and zone tools
    • Create the geometry
      • Generating the geometry
      • Drawing blocks and footprints
      • Modifying existing building blocks
      • Modifying site geometry
    • The analysis
      • Navigate and analyse the project
      • Analyse data
    • Release notes
      • Release notes - SiteSolve
  • Plugins and Tools
    • VU.CITY plugins
      • Auto-Update service
      • Blender plugin
      • Revit plugin
      • SketchUp plugin
    • VU.CITY tools
      • 360 Viewer
  • FAQ
  1. Home
  2. VU.CITY 3D
  3. ZTV
  4. ZTV analysis

ZTV analysis

Last updated: 23 December 2025 16:29 BST

Ensure your model is a standalone entity (multiple buildings or clusters are not supported for ZTV analysis) and is merged into a single mesh. Only a single mesh can be selected for the analysis.

For highly detailed models, use the VU.CITY Create to create a simple massing model in place of the imported model. This ensures compatibility and optimises processing time.

  1. Launch VU.CITY and select the ZTV
    In the VU.CITY interface, navigate to the Tools and select the ZTV analysis.

  2. Name your ZTV analysis
    Input a unique name for the ZTV analysis to initiate the process.

  3. Select the target
    Click on the building you wish to analyse. The mouse cursor will change to a selection cursor, and the selected building will highlight in red, confirming your selection.

  4. Activate the analysis
    After naming the analysis and selecting the building, the ‘Next’ button on the interface will become active. Click on this button to proceed to the next step.

  5. Set grid size and resolution
    • Adjust the grid size for the analysis area. Choose between a minimum of 500 meters and a maximum of 2 kilometers. Note that a larger area will require more sample points, which may increase the processing time.
    • Set the resolution, which is the distance between each sample point. Options range from coarse (10 meters) to fine (1 meter). A finer resolution will include more points in the grid, resulting in longer processing times but more detailed results.

  6. Run the ZTV analysis
    Click the ‘Run ZTV’ button. VU.CITY will then collect data from the selected model and the surrounding buildings or terrain.

  7. Review the results
    Once the calculation is complete, the ZTV tool will display a visibility map indicating the areas from which the building is visible. Analyse the results to understand the visual impact of the proposed development on the surrounding landscape.

Optimising the process

If the ZTV analysis takes a long time due to high model detail, consider simplifying the geometry or using the VU.CITY Create Tool to generate a simplified massing model. This simplified model can then be used for a quicker and efficient ZTV analysis.

Save and share

Save the ZTV analysis results for further review and documentation.

ZTV and trees

The default ZTV tool in VU.CITY 3D does not consider tree cover when conducting its analyses.

Previous:

ZTV model requirements

Did we answer your question?

Next up:

Understanding the ZTV