You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried two of your sample files and uploaded them to the buildingSMART validation service. Unfortunately, they failed the validation, and I am wondering if this is negligible or not, especially in the case of an issue with the IFC schema itself.
GEM111 - No duplicated points within a polyloop or polyline
The rule verifies, that all the polyloops and polylines will have no duplicate points, unless it's the first and last point of a closed polyline.
In that case, it must be identical by reference (referencing the same instance), not just having the same coordinates.
and twice on
Feature: GEM002 - Space representation
The rule verifies that all IfcSpaces have a correct Body shape representation.
Scenario: Agreement152_1 - Agreement that all spaces must have a body shape representation
Given An IfcSpace
Then There must be one Body shape representation
And The Body shape representation has RepresentationType "SweptSolid, Clipping, Brep"
I tried two of your sample files and uploaded them to the buildingSMART validation service. Unfortunately, they failed the validation, and I am wondering if this is negligible or not, especially in the case of an issue with the IFC schema itself.
For Duplex_A_20110907.ifc the rule verification fails on a lot of case according to
GEM111 - No duplicated points within a polyloop or polyline
The rule verifies, that all the polyloops and polylines will have no duplicate points, unless it's the first and last point of a closed polyline.
In that case, it must be identical by reference (referencing the same instance), not just having the same coordinates.
and twice on
Feature: GEM002 - Space representation
Scenario: Agreement152_1 - Agreement that all spaces must have a body shape representation
In the case of Clinic_Structural.ifc we have problems with IFC schema itself:
The text was updated successfully, but these errors were encountered: