Expand description
IfcConic subtypes: IfcCircle and IfcEllipse.
§Shared shape
IfcConic contributes exactly one attribute, Position, which is an
IfcAxis2Placement select: an IfcAxis2Placement2D for a planar conic
or an IfcAxis2Placement3D for one in space. Both subtypes therefore read
Position from slot 0 and their own radii from slot 1 onwards.
§Why radii are validated here
IfcPositiveLengthMeasure is a constrained type, not a Rust type: STEP
parsers do not enforce it and real exporters emit zero-radius circles for
degenerate sweeps. A zero radius reaches a kernel as a division by zero or
a NaN vertex thousands of entities later. Rejecting it at the view boundary
turns an unfindable numerical bug into a located crate::GeometryError.
Note that IFC constrains the two ellipse semi-axes only to be positive. It
does not require SemiAxis1 >= SemiAxis2, so a “prolate” ellipse whose
major axis is the local Y direction is legal and must not be normalised
away: the placement’s RefDirection fixes which axis is which.