Skip to content

BC003 ALX1 - improving documentation#76

Open
pjanck wants to merge 11 commits intobuildingSMART:mainfrom
bSI-RailwayRoom:bc003-alx1
Open

BC003 ALX1 - improving documentation#76
pjanck wants to merge 11 commits intobuildingSMART:mainfrom
bSI-RailwayRoom:bc003-alx1

Conversation

@pjanck
Copy link
Copy Markdown
Contributor

@pjanck pjanck commented Aug 21, 2023

Small improvements to

  • readability
  • structure
  • content

|RI 300 | Signals reused geometries | Signal parts geometries shall be mapped (IfcMappedItem) to their matching type geometry | Every signal sharing the same type shall reuse shared geometry defined for the signal type|
|RI 301 | Signals as assemblies| Signals shall be modeled as an IfcElementAssembly with aggregated post, foundation, mast and signal port| Signal posts shall use parametric/lighweight geometry and avoid heavy tessalated or BRep geometry |
|RI 302 | Signals reused types| Signal parts shall be using IfcElementAssemblyType entities| Signals shall be defined by their type with their characteristics |
|RI 304 | Stationing address | IfcReferents (typed POSITION or STATION) linked to IfcAlignments need a IfcRelPositions relationship | A Linear address shall be known from the alignment it relates to |
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is preventing the business requirement to be answered via the nesting relationship between an alignment and its referents?
Also, the current IFC documentation does not specify how and when to use IfcRelPositions between an alignment and referents.

Please clarify the requirement or put forward a proposal to modify the current IFC documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants