There is an issue with the representation of openings in gbXML files when the opening polyloop collides or overlaps with the parent surface polyloop. Some openings are not displayed correctly due to failed boolean subtraction operations.
Key points:
The issue was identified when a user exported a gbXML file from DesignBuilder and loaded it into Spider Viewer.
Some openings were not displayed correctly in Spider Viewer.
The boolean subtraction operation fails when the opening polyloop collides/overlaps with the parent surface polyloop.
Questions to address:
Does the gbXML schema define whether opening edges can or cannot collide with parent surface edges?
Should this be addressed on the export side (DesignBuilder) or the import side (Spider Viewer)?
Possible solutions to consider:
Export side: Modify DesignBuilder to avoid exporting geometry with colliding edges. This would mean that models after export import would not be the same.
Import side: Enhance Spider to handle cutting openings even when edges collide or overlap.
There is an issue with the representation of openings in gbXML files when the opening polyloop collides or overlaps with the parent surface polyloop. Some openings are not displayed correctly due to failed boolean subtraction operations.
Key points:
Questions to address:
Possible solutions to consider:
Attachment: gb.zip