Skip to content

IfcSectionedSolidHorizontal issues #4501

@RickBrice

Description

@RickBrice

On the v0.8.0 branch, I'm having some trouble with IfcSectionedSolidHorizontal.

I have two files (attached) of the same bridge. The first and last segment of each girder is a cross section that transitions over a distance.

The file named 26122_Mismatch_Polygon_Points.ifc models the cross sections with a different number of points. I think this is generally incorrect. All the sections should have the same number of points, but IfcConvert doesn't specifically indicate this as an error.

[Error] [2024-04-02 09:14:22] Failed to convert:
#872=IfcSectionedSolidHorizontal(#787,(#805,#825,#847,#869),(#807,#827,#849,#871))
[Error] [2024-04-02 09:14:22] No operation defined for:
#872=IfcSectionedSolidHorizontal(#787,(#805,#825,#847,#869),(#807,#827,#849,#871))
[Error] [2024-04-02 09:14:22] Failed to convert:
#888=IfcShapeRepresentation(#98,'Body','AdvancedSweptSolid',(#872))
[Error] [2024-04-02 09:14:22] No operation defined for:
#888=IfcShapeRepresentation(#98,'Body','AdvancedSweptSolid',(#872))

The file named 26122_Duplicate_Polygon_Points.ifc has the same cross sections but this time defined with the same number of points. Some of the points within a single cross section are duplicated. This results in a different error from IfcConvert

[Debug] [2024-04-02 09:23:15] {2SZbvXgv56HR_q_$6U$esO} Progress 3
[Debug] [2024-04-02 09:23:15] {2SZbvXgv56HR_q_$6U$esO} Begin processing
#902=IfcBeam('36tHTk9tLAOegAmxon79W6',$,'Segment 1',$,$,#889,#901,$,.GIRDER_SEGMENT.)
[Error] [2024-04-02 09:23:15] {36tHTk9tLAOegAmxon79W6} BRep_API: command not done

The attached Excel workbook plots the two different beam cross-sections.

  1. Where to add an error message so IfcConvert notifies that the polygons have different number of points?
  2. Why doesn't the duplicate point method work?
  3. If duplicate points can't be used, how can this type of beam be modeled?

GirderSections.xlsx
26122_Duplicate_Polygon_Points.ifc.txt
26122_Mismatch_Polygon_Points.ifc.txt

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions