``GRF006`` WKT specification for missing EPSG - v2 ======================================================================================================================================================================================================== .. parsed-literal:: 001 | \@implementer-agreement 002 | \@GRF 003 | \@version2 004 | Feature: GRF006 - WKT specification for missing EPSG 005 | The rule verifies that if an ESPG code does not exist for the coordinate reference system, this CRS shall be further speciied using the IfcWellKnownText entity 006 | https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcCoordinateReferenceSystem.htm#8.18.3.2.3-Attributes 007 | 008 | Background: 009 | :doc:`Given a Model with Schema 'IFC4.3' ` 010 | :doc:`Given an .IfcCoordinateReferenceSystem. ` 011 | 012 | 013 | Scenario: WKT specification for missing ESPG in the name 014 | 015 | :doc:`Given Its .Name. attribute ^does not start^ with 'EPSG:' ` 016 | 017 | :doc:`Then The value of attribute .WellKnownText. must be ^not empty^ ` 018 | :doc:`Then The value of attribute .Name. must be 'WKT' ` 019 | 020 | 021 | Scenario: WKT specification linked to 'WKT' in CRS name 022 | 023 | :doc:`Given .Name. ^is^ 'WKT' ` 024 | 025 | :doc:`Then The value of attribute .WellKnownText. must be ^not empty^ ` 026 | 027 | 028 | Scenario: WKT attribute linked to specification 029 | 030 | :doc:`Given .WellKnownText. ^is not^ empty ` 031 | 032 | :doc:`Then The value of attribute .Name. must be 'WKT' ` .. rubric:: Version history .. list-table:: :header-rows: 1 * - Version - Tag - Date - Commit - Rule link * - v1 - :tag:`v0.7.7` - 2025-06-16 - :commit:`bcfd8342fddf79fc73858ce6aeb76c70f9761873` - `view `_ * - v2 - :tag:`v0.8.2` - 2025-10-28 - :commit:`f332af51b676186e001ed8ddc2370c9dde301815` - `view `_