Skip to main content

zones

Function zones 

Source
pub fn zones(
    model: &Model,
) -> Result<(Vec<Zone>, Vec<SystemAnomaly>), SchemaResolutionError>
Expand description

Every IfcZone in the file, with WR1-valid members resolved.

Zones are found by schema ancestry so that any future subtype is included automatically, consistent with how systems and ports are discovered.

Reads against the release the model’s FILE_SCHEMA header declares: IFC2X3, IFC4 or IFC4X3 (#194), every slot by attribute name. WR1 differs by release: IFC4 and IFC4X3 admit IfcZone, IfcSpace and IfcSpatialZone; IFC2X3 admits only IfcZone and IfcSpace, because it has no IfcSpatialZone. Membership is checked by ancestry in the declared table, so an IfcSpatialZone in an IFC2X3 file is reported as ZoneMemberNotSpatial. long_name is None for every zone under IFC2X3, whose IfcZone has no LongName (issue #52). This bulk reader cannot tell that apart from a file that left it empty, because Zone::long_name predates #52 and stays Option<String>. Use long_name_of when that distinction matters.

§Errors

SchemaResolutionError when the model’s FILE_SCHEMA binds no release this crate is verified for (see crate::schema_of): no schema, several, or any release but IFC2X3, IFC4 and IFC4X3. None is read as IFC4.