[TM24] Linear zone and typical sections#1135
Open
aothms wants to merge 8 commits into
Open
Conversation
Description: Introduced new linear zones for typical tunnel sections.
Scope: ENTITY IfcLinearZone, ENTITY IfcTunnelTypicalSection,
TYPE IfcTunnelTypicalSectionTypeEnum,
PSET Pset_GeoAspects, Pset_PreSupportCommon, Pset_SupportCommon,
Pset_ElementAssemblyTypePreSupportVault,
Pset_ElementAssemblyTypePreSupportFace,
PENUM PEnum_GroutingType, PEnum_PreSupportArrangement,
PEnum_PreSupportLocation, PEnum_PreSupportType
Explanation: Rename STDGROUTING_CEMENT to STANDARD_GROUTING_CEMENT (full word); replace USERDEFINED with OTHER, keep NOTKNOWN/UNSET tail.
Explanation: Add OTHER/NOTKNOWN/UNSET tail.
Explanation: Rename TUNNELVAULT to TUNNEL_VAULT and TUNNELFACE to TUNNEL_FACE; replace USERDEFINED with OTHER, keep NOTKNOWN/UNSET tail.
Explanation: Rename JETGROUTED to JET_GROUTED and PIPEUMBRELLA to PIPE_UMBRELLA; replace USERDEFINED with OTHER, keep NOTKNOWN/UNSET tail.
…eSupportArrangement Explanation: Aligns Pset_SupportCommon.Arrangement with Pset_PreSupportCommon.Arrangement — same property name, same enumerated values.
…Spacing to BoltHorizontalSpacing Explanation: Arrangement renamed to SupportArrangement in Pset_PreSupportCommon and Pset_SupportCommon to avoid collision with the generic Arrangement property. HorizontalSpacing renamed to BoltHorizontalSpacing in Pset_SupportCommon for specificity.
…IfcTunnelDomain packageImport
PR Validation -- schema generatorsChecks:
Detected:
📋 EXPRESS schema diff (baseline vs PR head)Express schema differences5 items Missing data3 items
Type definitions2 items
Entity definitions🎉 No issues 🎉 Constraints🎉 No issues 🎉 SHACL validation reportDefinitionForEnumLiteral
DefinitionForPropertyOrQuantity
DefinitionForResource
LeafEntityHasPredefinedType
PropertyForDefinition
SHACL report truncated -- full report in the workflow artifact bundle. See workflow run for failure details. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description: Introduced new linear zones for typical tunnel sections.
Scope: ENTITY IfcLinearZone, ENTITY IfcTunnelTypicalSection,
TYPE IfcTunnelTypicalSectionTypeEnum,
PSET Pset_GeoAspects, Pset_PreSupportCommon, Pset_SupportCommon,
Pset_ElementAssemblyTypePreSupportVault,
Pset_ElementAssemblyTypePreSupportFace,
PENUM PEnum_GroutingType, PEnum_PreSupportArrangement,
PEnum_PreSupportLocation, PEnum_PreSupportType
Documentation preview (only for new/modified entities, cross-links to other pages disabled)
https://ifc44-docs.geerthesselink.com/IFC/PREVIEW/PR-1135/