``GRF007`` valid vertical datum crs type - v1
========================================================================================================================================================================================================

.. parsed-literal::

   001 | \@implementer-agreement
   002 | \@GRF
   003 | \@version1
   004 | Feature: GRF007 - Valid vertical datum CRS type
   005 | The rule verifies that any coordinate reference system (CRS) assigned as a vertical datum is either a vertical CRS or a compound CRS containing a vertical component, to ensure valid height referencing.
   006 | https://pyproj4.github.io/pyproj/stable/api/crs/crs.html
   007 | 
   008 | 
   009 |   Scenario: WKT specification for missing EPSG in the name
   010 | 
   011 |       :doc:`Given A model with Schema 'IFC4' or 'IFC4.3' </steps/givensattributespy_Afile_or_modelwithfieldvalues>`
   012 |       :doc:`Given an .IfcProjectedCRS. </steps/stepsentity_selectionpy_Anentity_opt_stmt>`
   013 |       :doc:`Given Its attribute .VerticalDatum. </steps/stepsattribute_selectionpy_Itsattributeattribute>`
   014 |       :doc:`Given The value refers to a valid EPSG code </steps/stepscrspy_ThevaluereferstoavalidEPSGcode>`
   015 | 
   016 |       :doc:`Then The CRS should define a vertical component </steps/stepscrspy_TheCRSshoulddefineaverticalcomponent>`

.. rubric:: Version history

.. list-table::
   :header-rows: 1

   * - Version
     - Tag
     - Date
     - Commit
     - Rule link
   * - v1
     - :tag:`v0.7.7`
     - 2025-06-16
     - :commit:`af8dc3d8f6d7873a07ef394a6a64c3b99111e74d`
     - `view <https://github.com/buildingSMART/ifc-gherkin-rules/blob/release/0.7.7/features/rules/GRF/GRF007_valid-vertical-datum-crs-type.feature>`_