Meshes in displayValue have area and volume as zero.

[ks-cph]

Prerequisites

• I read the contribution guidelines
• I checked the documentation and found no answer.
• I checked existing issues and found no similar issue.
• I checked the community forum for related discussions and found no answer.
• I'm reporting the issue to the correct repository (see also speckle-server, speckle-sharp, specklepy, speckle-docs, and others)

What package are you referring to?

The problem occurs when converting objects from Revit and ArchiCAD. I expect the same for other connectors.

Describe the bug

The Meshes in displayValue have the properties area and volume. However, the Revit connector does not add the correct information and instead sets them to 0.

To Reproduce

Check the area or volume property of any element in the displayValue array.

Expected behavior

We would expect the correct area and volume of the meshes.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Failure Logs

Additional context

Proposed Solution (if any)

From Revit, it should be rather straightforward to add the information. When converting the geometry from Revit into speckle objects, we could add the volume and area for Revit.DB.Solid and the area for Revit.DB.Mesh. This information is already part of the corresponding Revit elements. Hence, it should not require a lot of computational power.

Optional: Affected Projects

[jsdbroughton]

@ks-cph What is the correct interpretation of Area for the Mesh?

Let's say a CLT Floor Slab or a Drywall Wall - is this Plan Area, Face area?

[ks-cph]

Hey @jsdbroughton,

thanks for your response.
In my opinion, this property should address the surface of the Mesh without interpreting the domain knowledge such as using the plan area for a slab and the side area for a wall. This area property should aggregate all faces of the Mesh into one value.

Now we could argue that all information is stored in the vertices and faces arrays. But then again, why is there an Area property? And this is what I hoped to find out. I guess there is a reason why the area property was added, and I guess there is also a good reason to set it to zero. For me as a user, however, it would be very beneficial to get the numbers directly without computing each individual face area.