Vectorworks Data Visualization Guide: Communicate Model Data with Color and Visibility

Official Vectorworks Help documentation for versions 2026 and 2027 explains that Data Visualization can turn embedded data in a model or drawing into visual rules. The feature can change the attributes of objects that meet specific criteria or hide those objects. This guide covers the basic setup steps for classification, comparison, and presentation in architecture and interior design projects. Menu names and options are described as they appear in the documentation for those versions.

What does Data Visualization change?

A visualization definition has two parts. Object criteria determine which elements are included; display criteria define which data will be used to color objects differently, change their attributes, or hide them. For example, object parameters, record fields, IFC entities, or object-specific functions such as area can be selected as display criteria. The data available to use depends on the information present in the model objects.

The 2026 documentation shows that you can start a new visualization from the View bar, the Manage Data Visualizations dialog box, or while creating or editing a viewport. The 2027 documentation also lists additional ways to create one, including through Resource Manager and a saved view. Access through the View bar is documented when a design layer is active. Therefore, consult the Help page for the version you are using to find the command.

Create a visualization step by step

1. Start a new definition. In 2026, use New Data Visualization from the View bar or while creating/editing a viewport. In 2027, you can also select Data Visualization through New Resource in Resource Manager. The visualization name must be unique. In 2027, you can also add a description.

2. Choose how objects will be displayed. Use Change Attributes to change object attributes, or Hide to remove objects from view. This choice matters: subsequent lists show options related to applying attributes or controlling visibility. Using colors to distinguish categories on a sheet and hiding specific elements serve different purposes; deciding on the intended result up front helps prevent setting up the wrong type of rule.

3. Define which objects are included. Open the criteria dialog with Define Criteria; here, specify the object types and other conditions to evaluate. The selection formula and the number of objects that meet the conditions may be displayed in the definition. This is an essential check to avoid applying the visualization to far too many or too few elements.

4. Select the display data. From the object category, choose the appropriate option: All Objects, Objects using Parameter, Objects using Record, Objects using IFC Entity, or Objects using Function. When you select a parameter, record field, or IFC property, the values are listed accordingly. For example, area and material are given in the documentation as object-specific function examples. Verify that the data field you want to use exists in the project objects.

5. Edit values or numeric ranges. By values handles text or numeric values individually; By ranges divides numeric values into ranges. Add ranges with Add and edit them with Edit. You can choose whether each row applies attributes or hides objects. Check that the Apply or Hide checkbox next to each row is enabled: the documentation identifies these checkboxes as among the first things to inspect when troubleshooting.

6. Assign colors and other attributes. If you use Change Attributes, you can select available attributes for each row, such as fill, line, texture, and shadow; the available options depend on the selected attribute. Auto-Color assigns colors automatically. The 2026 and 2027 documentation describes creating a gradient with start and end colors, while the 2027 documentation also lists ordering colors from a palette. If you are not using automatic colors, you can set row colors manually. The documentation also includes an option to preserve original attributes.

7. Review the behavior of other objects and tags. Objects unaffected by the visualization can display normally, be grayed out, or be hidden. In 2027, Apply attributes to associated data tags lets data tags follow the attribute or visibility behavior of their associated objects. The documentation also warns that class overrides cannot be applied when the graying option is used on a viewport.

8. Save and verify the result. Save the definition with OK. Depending on the context in which it was created, the visualization can be applied to the relevant layer, saved view, or viewport. If objects in the drawing have changed, you can remove values that no longer appear in the list with Clear Unavailable Values, or update the current values with Refresh Values. Read the confirmation carefully when choosing a new display criterion, as it warns that the value list may change.

Impact on architectural and visualization workflows

Architects and interior designers can use this feature to turn information already stored in a model into a readable visual distinction in a drawing. Rules based on a record field, IFC property, or parameter make it possible to see which objects contain the data and how the selected values are distinguished in the drawing. The same method can also simplify a view for a particular presentation by hiding objects. It does not create new data; the result depends on the accuracy of the existing model criteria and values.

For definitions to be used across multiple files in an office, the 2027 documentation states that Data Visualization resources can be shared with other files and users, and that visualizations used together can be saved as a set. When preparing an office standard, therefore, keep naming, the data fields used, and the meaning of colors consistent across the team. If class overrides are used in a viewport, take note of the graying warning; if sheet annotations are important, check the associated data tag option. The documentation does not specify particular hardware requirements or performance gains, so it is not possible to make a specific hardware recommendation for this feature.

Common mistakes

• Defining the included objects incorrectly, causing the visualization to affect different elements than expected.

• Forgetting to enable the Apply or Hide checkbox for a value or range row.

• Failing to refresh the value list after model data changes, or to remove values that are no longer in use.

• Missing the compatibility warning in the documentation when using the graying option together with class overrides in a viewport.

Checking the criteria and results on a few objects after setup can help confirm that the rule works as intended before applying it to the entire drawing.