``SPS002`` Correct spatial breakdown - v3 ======================================================================================================================================================================================================== .. parsed-literal:: 001 | \@implementer-agreement 002 | \@SPS 003 | \@version3 004 | Feature: SPS002 - Correct spatial breakdown 005 | The rule verifies that spatial elements are aggregated as per the Spatial Composition Table. 006 | The possible allowed breakdown can be found in the csv file in the folder 'features/resources/spatial\_CompositionTable.csv' 007 | 008 | Scenario: Agreement on each IfcSpatialElement being aggregated as per spatial composition table. 009 | 010 | :doc:`Given A model with Schema 'IFC4' or 'IFC4.3' ` 011 | :doc:`Given An .IfcSpatialElement. ` 012 | 013 | :doc:`Then It must be aggregated as per spatial\_CompositionTable.csv ` 014 | 015 | Scenario: Agreement on the IfcProject being aggregated as per spatial composition table. 016 | 017 | :doc:`Given A model with Schema 'IFC4' or 'IFC4.3' ` 018 | :doc:`Given An .IfcProject. ` 019 | 020 | :doc:`Then It must be aggregated as per spatial\_CompositionTable.csv ` .. rubric:: Version history .. list-table:: :header-rows: 1 * - Version - Tag - Date - Commit - Rule link * - v1 - :tag:`v0.6.6` - 2023-09-21 - :commit:`2cf129562fc83bc63cf30b159d240da7120b5070` - `view `_ * - v2 - :tag:`v0.6.6` - 2024-07-11 - :commit:`7686282999419c5449e15dd5b8f2e843e83287c9` - `view `_ * - v3 - :tag:`v0.6.11` - 2025-02-01 - :commit:`4e1884be5d3315a5f1b7d4fd2b4d309f211d2411` - `view `_