Scenarios for validating the horizontal continuity were added. Those scenarios should be implemented in another rule, but were maintained in the commit to be evaluated, and should be altered after

…erkin-rules into IVS-137-ALB011-IfcAlignmentVerticalSegment.RadiusOfCurvature

It was created a function of comparison that considers the instance context precision tolerance. This function was added in the 'then' step that compares an attributes to an expression.

ALB010 is already in use.
Renaming this feature will allow for a new rule ALB011 to check RadiusOfCurvature
for the horizontal layout.

(IVS-137)

…gment.RadiusOfCurvature

…ature' of https://github.com/fg55b/ifc-gherkin-rules into IVS-137-ALB012-IfcAlignmentVerticalSegment.RadiusOfCurvature

(IVS-143)

ALB012 focuses solely on 'RadiusOfCurvature' design parameter and includes a scenario that fixes #241.

(IVS-137)

Co-authored-by: Thomas Krijnen <[email protected]>

- adds a Given statement for proper entity type of DesignParameters
- adds `na` unit test file to confirm this new Given statement
- adds `na` unit test file to confirm rule is not activated for alignment with horizontal layout only

(IVS-137)

(IVS-137)

(IVS-137)

…m/buildingSMART/ifc-gherkin-rules into IVS-137-ALB012-IfcAlignmentVerticalSegment.RadiusOfCurvature

The test file that raises an exception
should start with 'fail'.

(IVS-137)

…gment.RadiusOfCurvature

(IVS-137)

(IVS-137)