Mesh data CSV files attach attribute data to individual components within a 3D mesh model. When uploaded alongside a GLB file, the CSV defines how different parts of the model should be interpreted and displayed in the 3D environment.

What the CSV is for

The CSV links data to specific parts of the 3D model by referencing individual mesh components from the GLB file. Each row represents a single component, allowing attributes to be assigned to it directly.

This enables workflows such as:

• colouring parts of a model by use or status
• filtering components based on attributes
• visualising analysis results directly on the geometry
• querying data in context within the 3D environment

Atribute data types

The CSV can include a wide range of attribute types, depending on the use case.

• text (e.g. “office”, “residential”)
• numeric (e.g. height, cost, exposure score)
• status (e.g. “complete”, “in progress”)
• categorical values used for grouping and colour coding
• timestamp values for time-based workflows

These attributes can then be used to filter, style, and analyse the mesh in the 3D environment.

• CSV example

  

Time-based data

If the CSV includes timestamp fields, these can be used for time-based visualisation. This enables workflows such as:

• construction sequencing
• phased developments
• status changes over time
• installation or delivery tracking

The platform will interpret timestamped attributes in line with existing timeline functionality.

Formatting requirements

To link data successfully, the CSV must meet the following requirements:

Mesh names

• Each row must include a mesh name that exactly matches a component name in the GLB file
• Names are case sensitive - "Floor_01" and "floor_01" will not match
• Avoid extra spaces, trailing punctuation, or inconsistent naming conventions

Structure

• Each row should represent a single mesh component
• Use consistent column headers across all rows
• Avoid merged cells, blank rows, or irregular formatting

Attribute values

• Keep values clean and consistently formatted within each column
• Use a single format for dates and timestamps throughout the file
• Avoid special characters or symbols that may not parse correctly

If any mesh names do not match, the import will still proceed, but those components will not have attributes linked.