-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Test Case]: Alignment Curves #22
Draft
SergejMuhic
wants to merge
23
commits into
bSI-InfraRoom:develop
Choose a base branch
from
SergejMuhic:feature/alignmentCurves
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 14 commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
95e8278
Creating TC1.1 test instructions
SergejMuhic ab2d2d8
Initial description
SergejMuhic ae4859d
IFC entities
SergejMuhic b44fb91
Concept templates
SergejMuhic 4754c32
Adding placements
SergejMuhic 17d949f
Merge branch 'bSI-InfraRoom:develop' into develop
SergejMuhic da51b9d
Move and rename TC1.1 test instructions
SergejMuhic c8ba34d
Resolving links in readme for TC1.1
SergejMuhic 02f490a
Adding TC1.2
SergejMuhic a22b755
Alphabetical order of entities
SergejMuhic df0b10d
Updating TC1.2 description
SergejMuhic 4eb290a
Delete TC_1.2_Stationing_including_linear_positioning.md
SergejMuhic a479bc7
Addressing comments
SergejMuhic 48c7096
Update README.md
SergejMuhic 912b4af
Apply suggestions from code review
SergejMuhic b2e065f
Update the test instruction template
SergejMuhic e36f683
Updating header
SergejMuhic 96f093f
Adding dataset readme
SergejMuhic 74d5d6b
Removing leftover Variations section
SergejMuhic 3282bcf
Adding entity list
SergejMuhic d0444cf
Updating header
SergejMuhic 5bc91b0
Modification to the Test case Imports section
SergejMuhic 3daee64
Adding usage restriction for test case
SergejMuhic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,92 @@ | ||
## Summary | ||
|
||
*Include a short description of the test case.* | ||
|
||
*Optional: if your data comes from a specific Storyline or unit test of the IFC Infrastructure Deployment Project or IFC Rail Project, please include a link to the originating documentation here. so additional background information can be created.* | ||
|
||
With these instructions the baseline alignment exchange will be established between various domains. This includes basic alignment geometry featuring the common layout: | ||
- horizontal | ||
- vertical | ||
|
||
The valid geometry segment types for horizontal are the following: | ||
- Arc | ||
- Clothoid | ||
- Cubic (? has to be covered somewhere) | ||
- Linear | ||
|
||
The valid geometry segment types for vertical: | ||
- Arc | ||
- Linear | ||
- Parabolic (?does Road use it?) | ||
|
||
## Itemised Roots | ||
The Test instruction addresses the import and export of the following IFC Entities & Concept Templates: | ||
|
||
- IFC Entities | ||
- *IfcAlignment* | ||
- *IfcAlignmnetHorizontal* | ||
- *IfcAlignmentVertical* | ||
- *IfcAlignmentSegment* | ||
- *IfcAlignmentHorizontalSegment* | ||
- *IfcAlignmentVerticalSegment* | ||
- *IfcAxis2PlacementLinear* | ||
- *IfcAxis2Placement2D* | ||
- *IfcAxis2Placement3D* | ||
- *IfcCircle* | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. How do we handle the cases in ALIN where we have no requirements for geometry at all (only layout)? Can we split this in two (with/without geometry)? |
||
- *IfcClothoid* | ||
- *IfcCompositeCurve* | ||
- *IfcCurveSegment* | ||
- *IfcLine* | ||
- *IfcLinearPlacement* | ||
- *IfcLocalPlacement* | ||
- *IfcGeometricRepresentationContext* | ||
- *IfcGeometricRepresentationSubContext* | ||
- *IfcGradientCurve* | ||
- *IfcMapConversion* | ||
- *IfcPolyline* | ||
- *IfcProject* | ||
- *IfcProjectedCRS* | ||
- *IfcProductDefinitionShape* | ||
- *IfcSite* | ||
- *IfcShapeRepresentation* | ||
- Concept Templates | ||
- *Alignment Layout* | ||
- *Alignmnent Geomtry* | ||
SergejMuhic marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- *Alignmnet Geometry Gradient* | ||
SergejMuhic marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- *Project Global Positioning* | ||
- *Spatial Containment* | ||
|
||
## Variations | ||
The Following occurence variations need to be checked and certified in relation to the targetted entities and concept templates: | ||
|
||
- Entity_01 - *decription of variation* | ||
- Entity_02 - *decription of variation* | ||
|
||
|
||
## Usages | ||
The following itemised restrictions and constraints shall be placed on IFC Entities & Concept Templates: | ||
|
||
- IfcSomething | ||
- *Constraint* | ||
|
||
|
||
The Test case requires the following additional checks related to Model Geometry: | ||
|
||
- *Constraint* | ||
|
||
|
||
## Model Dataset | ||
This test case utilises the attached dataset documented by the following drawings and data schedule. | ||
|
||
*This is a later step tha involved the detailed documentation of the certification dataset (model)* | ||
|
||
|
||
## Drawings (Visualisations) | ||
The following Drawings and visualisations describe the test case dataset to be modelled and certified. | ||
|
||
|
||
## Supporting files | ||
|
||
| Filename | Description | | ||
|-----------------------------------|-------------------------------------------| | ||
| *filename* | *short description* | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More specific more better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaving as Arc for now. Has to be changed in the partial template name also.