#[non_exhaustive]pub struct SpaceBoundary {
pub id: EntityId,
pub type_name: String,
pub space: Option<EntityId>,
pub element: Option<EntityId>,
pub physicality: BoundaryPhysicality,
pub exposure: BoundaryExposure,
pub parent: Option<EntityId>,
pub corresponding: Option<EntityId>,
}Expand description
One space boundary as the file states it.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.id: EntityIdThe relationship entity itself.
type_name: StringConcrete STEP type, e.g. IFCRELSPACEBOUNDARY2NDLEVEL.
space: Option<EntityId>RelatingSpace: the space being bounded.
element: Option<EntityId>RelatedBuildingElement: the element forming the boundary.
physicality: BoundaryPhysicalityPhysicalOrVirtualBoundary.
exposure: BoundaryExposureInternalOrExternalBoundary.
parent: Option<EntityId>ParentBoundary, on 1st-level boundaries and above.
An inner boundary – a window within a wall boundary – names the
wall’s boundary here. None on a plain IfcRelSpaceBoundary, which
has no such slot at all.
corresponding: Option<EntityId>CorrespondingBoundary, on 2nd-level boundaries only.
The boundary on the OTHER side of the same fabric. This pairing is what makes second-level boundaries usable for heat transfer: each side’s area is known and the two are linked.
Implementations§
Source§impl SpaceBoundary
impl SpaceBoundary
Sourcepub fn physical_matches_element(&self, model: &Model) -> Option<bool>
pub fn physical_matches_element(&self, model: &Model) -> Option<bool>
Does physicality agree with the related element’s type?
The schema’s CorrectPhysOrVirt rule: a Physical boundary must not
name an IfcVirtualElement, and a Virtual one must name either an
IfcVirtualElement or an IfcOpeningElement. NotDefined is always
admissible.
Returns None when the element is absent or unresolvable, since
agreement is then unknowable rather than false.
Sourcepub fn connection_geometry(
&self,
model: &Model,
) -> Result<Option<EntityId>, ConnectionGeometryAnomaly>
pub fn connection_geometry( &self, model: &Model, ) -> Result<Option<EntityId>, ConnectionGeometryAnomaly>
ConnectionGeometry: the boundary’s shape, if the file gives one.
The coordinates are in the object placement of the relating space
(space): IFC4 ADD2 TC1 states the connection
geometry is “given within the local placement of each space”, and
that SurfaceOnRelatingElement / CurveOnRelatingElement are in the
space’s local coordinate system while the ...OnRelatedElement
counterparts, rarely exported, are in the element’s. Placing the
shape in the model therefore needs the space’s placement, not the
element’s.
The slot is OPTIONAL in IFC2x3, IFC4 and IFC4X3 and sits at the same
position on IfcRelSpaceBoundary1stLevel and 2ndLevel. The target
is normally an IfcConnectionSurfaceGeometry (3D) or
IfcConnectionCurveGeometry (2D); any concrete
IfcConnectionGeometry subtype is returned, since which ones a
boundary may use is a validation question.
model must be the model the boundary was read from: the slot is
read from it on each call rather than stored on the struct.
§Errors
Returns a ConnectionGeometryAnomaly when the slot names a missing
entity or a non-connection-geometry entity, holds something other
than one reference, or when the boundary is not in model. An absent
($) or missing slot is Ok(None): the boundary is then stated
logically, without a shape.
Trait Implementations§
Source§impl Clone for SpaceBoundary
impl Clone for SpaceBoundary
Source§fn clone(&self) -> SpaceBoundary
fn clone(&self) -> SpaceBoundary
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more