2098 Archicad Connector geometry fidelity

[jozseflkiss]

#2098

New functions:

• Import option for parametric or mesh import
• LibpartImportManager
  • Edge status calculcation (welded, unwelded) based on vertex reusage and polygon directions
  • Transformation matrix introduced, but not currently used
  • Geometry reusage based on hash ids introduced, but not currently used
• AttributeManager
  • Attribute generation cache
• MeshModel
  • Speckle id sent to Archicad for content-based identification
  • Custom JSON serialization for Dictionaries for Graphisoft representation (e.g. "firts" and "second" props for pairs)

No Schema change.

Extra minor changes:

• Beam, column common codes moved to central place
• All hierarchical elements exported

Description & motivation

Changes:

To-do before merge:

Screenshots:

Validation of changes:

Checklist:

• My pull request follows the guidelines in the Contributing guide?
• My pull request does not duplicate any other open Pull Requests for the same update/change?
• My commits are related to the pull request and do not amend unrelated code or documentation.
• My code follows a similar style to existing code.
• [] I have added appropriate tests.
• I have updated or added relevant documentation.

References

With hard edges only:

Without edges:

[JR-Morgan]

Quick comment on performance, minor, but I'd thought I'd share my findings from other connectors.

In other connectors, we have optimised the performance of MeshToNative quite significantly by avoiding using Points and reusing the scaling factor (calling Units.GetConversionFactor once per Mesh)

Creating a Point object for each vertex leads to a lot of heap allocations,
additionally, I see, PointToNative will call Units.GetConversionFactor for each point, which has a small cost, but one that adds up, especially when you consider meshes with high vert count.

Take this with a grain of salt, you may prefer to care about performance later, I'll leave this up to you.

[JR-Morgan]

🙌 amazing