IFC4.3.x-development icon indicating copy to clipboard operation
IFC4.3.x-development copied to clipboard

Repository to collect updates to the IFC4.3 Specification

Results 284 IFC4.3.x-development issues
Sort by recently updated
recently updated
newest added

Want to share here https://github.com/buildingSMART/IFC4.3.x-output/issues/619

I think we should provide a short definition of a polynomial curve in IFC beyond `Polynomial Curve`. How should the coefficients be applied? should it be:` IFCPOLYNOMIALCURVE([#], (0.0,1.0,3.14), [y], [z])...

Check Status on https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/Pset_ActuatorPHistory.htm https://standards.buildingsmart.org/IFC/RELEASE/IFC4/ADD2_TC1/HTML/schema/ifcbuildingcontrolsdomain/pset/pset_actuatorphistory.htm

e.g. Ifc4.Pset_BuildingElementProxyProvisionForVoid.Shape => Ifc4x3.Pset_ProvisionForVoid.VoidShape. This is really annoying for implementers. Please provide a flatlisted changelog.

In the validation service, the types of topological representation (https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcTopologyRepresentation.htm) must be added to the valid_representation_type csv file, because for structural members (that are related to topological representations), the service...

In [5.4.3.1](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcAlignment.htm) IfcOffsetCurveByDistances is described as `IfcOffsetCurveByDistances as a 2D or 3D curve defined relative to an IfcGradientCurve or another IfcOffsetCurveByDistances.` IfcGradientCurve is 3D so 2D doesn't make sense. Suggest...

The [element nesting concept](https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/concepts/Object_Composition/Nesting/Element_Nesting/content.html) describes this: > The hosted component should not be contained in the spatial hierarchy, i.e. the concept Spatial Containment shall not be used at the level...

allocated-core
proposal

The default value of IfcAxis2PlacementLinear.Axis is not defined. Using IfcAxis2Placement3D for inspiration, you could say that the default Axis is (0,0,1). However, IfcAxis2PlacementLinear.RefDirection, when omitted, is taken from the curve...

IfcAxis2Placement3D is clear that either both Axis and RefDirection are either both provided or neither are provided. IfcAxis2PlacementLinear does not state such a requirement. Should it?

This is a bit of a minor thing, but should IfcSegmentedReferenceCurve be a subtype of IfcGradientCurve? It's a backwards compatible change to make. It would make things more consistent, and...