Update IfcRelInterferesElement DocEntity & Documentation #40

MatthieuPERIN · 2021-05-20T15:01:06Z

Update Interferences Type Doc
Update ImpliedOrder Doc
Update general doc

Linked to issue #39 and #111

* Update Interferences Type Doc * Update ImpliedOrder Doc * Update general doc

AlexBrad1eyCT

Just a few language suggestions/corrections. see comments.

Only other point is around handling the spatial-spatial physical-physical question are we adding an informal propersition or defining a restrictive where rule?

...ore data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/DocEntity.xml

... data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md

...ore data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/DocEntity.xml

MatthieuPERIN · 2021-07-01T08:19:58Z

Solution to be implemented (followed in #111)

…Elements_update

AlexBrad1eyCT

All looks as per discussions, will create a back log issue to possibly add some tidy diagrams some where

…Elements_update # Conflicts: # IFC4x3/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md

AlexBrad1eyCT · 2021-07-02T16:11:13Z

Merging, as meets resolution for SCTE review, open issues address open discussion points.

SergejMuhic

A few questions to resolve and a few proposals.

...ore data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/DocEntity.xml

SergejMuhic · 2021-07-02T16:21:59Z

... data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md

@@ -1,12 +1,24 @@
-The _IfcRelInterferesElements_ objectified relationship indicates that two elements interfere. Interference is a spatial overlap between the two elements. It is a 1 to 1 relationship. The concept of two elements interfering physically or logically is described independently from the elements. The interference may be related to the shape representation of the entities by providing an interference geometry.  
+The _IfcRelInterferesElements_ objectified relationship indicates that two elements interfere. Interference is a spatial and/or shape interaction between the two elements. It is a 1 to 1 relationship. The concept of two elements interfering physically or logically is described independently from the elements. The interference may be related to the shape representation of the entities by providing an interference geometry.  


What is a spatial interaction and how is it different from a shape interaction?

This change have being lost/reverted in actual version of the develop branch.

SergejMuhic · 2021-07-02T16:27:07Z

... data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md


-* When the interference geometry is available it can be passed by the optional attribute _InterferenceGeometry_ pointing to _IfcConnectionGeometry_. The connection geometry is provided as a point, curve, surface, or solid within the placement coordinate systems of the connecting elements. The _IfcConnectionVolumeGeometry_ is the default type to be used for interference in 3D space, as indicated in e.g. clash detections.  
+* When the interference geometry is available it can be passed by the optional attribute _InterferenceGeometry_ pointing to _IfcConnectionGeometry_. The connection geometry is provided as a point, curve, surface, or volume within the local placement coordinate systems of the connecting elements. The _IfcConnectionVolumeGeometry_ is the default type to be used for interference in 3D space, as indicated in e.g. clash detections.  


Volume is not a term in geometry items. Volume is a measurement type. Solid is the proper terminology.

Not sure why I cannot add a suggestion here but this "coordinate systems of the connecting elements" is ambiguous. Which element? Only one local placement can serve as the basis. I guess Implied order should influence this also?

Suggested change

* When the interference geometry is available it can be passed by the optional attribute _InterferenceGeometry_ pointing to _IfcConnectionGeometry_. The connection geometry is provided as a point, curve, surface, or volume within the local placement coordinate systems of the connecting elements. The _IfcConnectionVolumeGeometry_ is the default type to be used for interference in 3D space, as indicated in e.g. clash detections.

* When the interference geometry is available it can be passed by the optional attribute _InterferenceGeometry_ pointing to _IfcConnectionGeometry_. The connection geometry is provided as a point, curve, surface, or solid within the placement coordinate systems of the connecting elements. The _IfcConnectionVolumeGeometry_ is the default type to be used for interference in 3D space, as indicated in e.g. clash detections.

@SergejMuhic amusingly your are wrong and right at the same time! :D

you are correct in the sense the term is solid, but amusingly the subtype is called IfcConnectionVolumeGeometry so theres that !

it sounds ambiguous but is correct IfcConnectionGeometry subtypes are made up of 2 geometries one for the overlapping zone on RelatingElement (in its placement) and the same for RelatedElement (in its placement). so...! :p

Solid was kept is the actual version

@SergejMuhic amusingly your are wrong and right at the same time! :D

1. you are correct in the sense the term is solid, but amusingly the subtype is called _IfcConnectionVolumeGeometry_ so theres that ! 2. it sounds ambiguous but is correct IfcConnectionGeometry subtypes are made up of 2 geometries one for the overlapping zone on _RelatingElement_ (in its placement) and the same for _RelatedElement_ (in its placement). so...! :p

You have to read my comments carefully. And I would appreciate that you refrain from labeling them wrong. Thank you.

Volume is not a term in geometry items.

That is a fact. IfcConnectionGeometry is by no means a geometric item. It has been introduced specifically to not be a geometric item (or a representation item) but to "describe the geometric and topological constraints that facilitate the physical connection of two objects". Semantics.

SergejMuhic · 2021-07-02T16:49:15Z

... data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md

 * _ImpliedOrder_=FALSE The _RelatingElement_ and _RelatedElement_ have no priority among each other. If the interference is to be resolved then no information about whether the _InterferenceGeometry_ should be subtracted from the _RelatingElement_ or the _RelatedElement_ can be traced. This would be the case for clash detection results.  
 * _ImpliedOrder_=UNKNOWN No information about the priorities is provided.  
-
+
+The _IfcConnectionGeometry_ property is used to define the interference shape, it can be part of the shape of one of the elements of the relationship (in the case of clash, overlapping and crossing interference types) or define the interface between the two shapes (in the case of along, over and under interference types).


Suggested change

The _IfcConnectionGeometry_ property is used to define the interference shape, it can be part of the shape of one of the elements of the relationship (in the case of clash, overlapping and crossing interference types) or define the interface between the two shapes (in the case of along, over and under interference types).

The _InterferenceGeometry_ attribute is used to define the interference shape, it can be part of the shape of one of the elements of the relationship (in the case of clash, overlapping and crossing interference types) or define the interface between the two shapes (in the case of along, over and under interference types).

This section was lost/reverted in actual devellop version ...should it be back ?

SergejMuhic · 2021-07-02T16:53:21Z

... data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md

+  * Crosses: the _RelatingElement_ is crossing the _RelatedElement_ (e.g. Railway crossing a road)
+  * PassesThrough: the _RelatingElement_ is passing through the _RelatedElement_ (e.g. a Road passing inside a tunnel)
+  * PassesOver: the _RelatingElement_ is passing over the _RelatedElement_ (e.g a bridge passing over a water canal)
+  * PassesUnder: the _RelatingElement_ is passing under the _RelatedElement_ (e.g a Pipe passing under a road)


Do we allow a mix of spatial and physical concepts? I do not like this at all. @TLiebich what do you think?

That is an excellent question, to be solved by IFC TUNNEL project 😄

SergejMuhic · 2021-07-02T16:54:06Z

... data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md

+  * PassesThrough: the _RelatingElement_ is passing through the _RelatedElement_ (e.g. a Road passing inside a tunnel)
+  * PassesOver: the _RelatingElement_ is passing over the _RelatedElement_ (e.g a bridge passing over a water canal)
+  * PassesUnder: the _RelatingElement_ is passing under the _RelatedElement_ (e.g a Pipe passing under a road)
+* **Non oriented interferences types** do not imply specific values of _ImpliedOrder_ (but can still be set to precise shape interference calculation)


Suggested change

* **Non oriented interferences types** do not imply specific values of _ImpliedOrder_ (but can still be set to precise shape interference calculation)

* **Non oriented interferences types** do not imply specific values of _ImpliedOrder_ (but can still be set to for a precise shape interference calculation)

SergejMuhic · 2021-07-02T16:56:16Z

... data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md

+  * PassesOver: the _RelatingElement_ is passing over the _RelatedElement_ (e.g a bridge passing over a water canal)
+  * PassesUnder: the _RelatingElement_ is passing under the _RelatedElement_ (e.g a Pipe passing under a road)
+* **Non oriented interferences types** do not imply specific values of _ImpliedOrder_ (but can still be set to precise shape interference calculation)
+  * Clash: The _RelatingElement_ and _RelatedElement_ have a spatial or shape-based clash


Spatial clash has to be defined somewhere. I am having problems understanding the difference that is implied.

…esElements_update Update IfcRelInterferesElement DocEntity & Documentation

Update IfcRelInterferesElement DocEntity & Documentation

f26122f

* Update Interferences Type Doc * Update ImpliedOrder Doc * Update general doc

MatthieuPERIN mentioned this pull request May 20, 2021

IfcRelInterferesElements new usage in IFC Infra project #39

Closed

AlexBrad1eyCT added the documentation Issues or pull requests relating to documentation label May 21, 2021

AlexBrad1eyCT assigned MatthieuPERIN May 21, 2021

AlexBrad1eyCT requested review from AlexBrad1eyCT and SergejMuhic May 21, 2021 10:11

MatthieuPERIN marked this pull request as ready for review May 25, 2021 07:01

AlexBrad1eyCT linked an issue May 25, 2021 that may be closed by this pull request

IfcRelInterferesElements new usage in IFC Infra project #39

Closed

AlexBrad1eyCT requested changes May 25, 2021

View reviewed changes

Update to respond the first review

f9d31c2

MatthieuPERIN requested a review from AlexBrad1eyCT May 25, 2021 13:20

SergejMuhic reviewed May 26, 2021

View reviewed changes

...ore data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/DocEntity.xml Outdated Show resolved Hide resolved

...ore data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/DocEntity.xml Show resolved Hide resolved

Clarify doc on InterferenceType in IfcRelInterferesElements

5876dcb

pjanck added the IFC4x3_RC4 To be resolved before IFC4x3_RC4 label Jun 11, 2021

AlexBrad1eyCT added the EXPRESS Issues or pull requests relating to EXPRESS schema label Jun 16, 2021

AlexBrad1eyCT added this to Review in progress in IFC4x3 Jun 21, 2021

AlexBrad1eyCT removed the EXPRESS Issues or pull requests relating to EXPRESS schema label Jun 30, 2021

AlexBrad1eyCT approved these changes Jun 30, 2021

View reviewed changes

IFC4x3 automation moved this from Review in progress to Reviewer approved Jun 30, 2021

AlexBrad1eyCT added the EXPRESS Issues or pull requests relating to EXPRESS schema label Jul 1, 2021

MatthieuPERIN mentioned this pull request Jul 1, 2021

Intereference of spatial structure elements #111

Closed

AlexBrad1eyCT linked an issue Jul 1, 2021 that may be closed by this pull request

Intereference of spatial structure elements #111

Closed

matthieu.perin added 4 commits July 1, 2021 11:21

Merge remote-tracking branch 'upstream/develop' into IfcRelInterferes…

1709db8

…Elements_update

Review MD version of IfcRelInterferesElements Documentation

bd0834e

Add .INTERFERENCE. Predefined Type for IfcSpatialZone

7da9c37

Update IfcRElInterferesElement to have InterferenceSpace attribute

0788c2d

MatthieuPERIN requested a review from SergejMuhic July 1, 2021 17:09

AlexBrad1eyCT approved these changes Jul 2, 2021

View reviewed changes

Merge remote-tracking branch 'upstream/develop' into IfcRelInterferes…

abe6940

…Elements_update # Conflicts: # IFC4x3/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcRelInterferesElements/Documentation.md

AlexBrad1eyCT removed a link to an issue Jul 2, 2021

Intereference of spatial structure elements #111

Closed

AlexBrad1eyCT merged commit a2ebf86 into bSI-InfraRoom:develop Jul 2, 2021

IFC4x3 automation moved this from Reviewer approved to Done Jul 2, 2021

SergejMuhic requested changes Jul 2, 2021

View reviewed changes

IFC4x3 automation moved this from Done to Review in progress Jul 2, 2021

SergejMuhic mentioned this pull request Jul 2, 2021

Revert "Update IfcRelInterferesElement DocEntity & Documentation" #124

Merged

SergejMuhic moved this from Review in progress to In progress in IFC4x3 Jul 2, 2021

MatthieuPERIN pushed a commit to MatthieuPERIN/IFC-Specification that referenced this pull request Jul 6, 2021

Merge pull request bSI-InfraRoom#40 from MatthieuPERIN/IfcRelInterfer…

559cbdb

…esElements_update Update IfcRelInterferesElement DocEntity & Documentation

MatthieuPERIN mentioned this pull request Jul 6, 2021

Update Spatial Description needed by IFC Rail #139

Merged

MatthieuPERIN pushed a commit to MatthieuPERIN/IFC-Specification that referenced this pull request Jul 6, 2021

Updated to take into account remarks on bSI-InfraRoom#40

d10be43

AlexBrad1eyCT moved this from In progress to Done in IFC4x3 Nov 29, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update IfcRelInterferesElement DocEntity & Documentation #40

Update IfcRelInterferesElement DocEntity & Documentation #40

MatthieuPERIN commented May 20, 2021 •

edited

AlexBrad1eyCT left a comment

MatthieuPERIN commented Jul 1, 2021

AlexBrad1eyCT left a comment

AlexBrad1eyCT commented Jul 2, 2021

SergejMuhic left a comment

SergejMuhic Jul 2, 2021

MatthieuPERIN Jul 5, 2021

SergejMuhic Jul 2, 2021

SergejMuhic Jul 2, 2021

AlexBrad1eyCT Jul 2, 2021 •

edited

AlexBrad1eyCT Jul 2, 2021

MatthieuPERIN Jul 5, 2021

SergejMuhic Jul 6, 2021

SergejMuhic Jul 2, 2021

MatthieuPERIN Jul 5, 2021

SergejMuhic Jul 2, 2021

MatthieuPERIN Jul 5, 2021

SergejMuhic Jul 2, 2021

SergejMuhic Jul 2, 2021

		@@ -1,12 +1,24 @@
		The _IfcRelInterferesElements_ objectified relationship indicates that two elements interfere. Interference is a spatial overlap between the two elements. It is a 1 to 1 relationship. The concept of two elements interfering physically or logically is described independently from the elements. The interference may be related to the shape representation of the entities by providing an interference geometry.
		The _IfcRelInterferesElements_ objectified relationship indicates that two elements interfere. Interference is a spatial and/or shape interaction between the two elements. It is a 1 to 1 relationship. The concept of two elements interfering physically or logically is described independently from the elements. The interference may be related to the shape representation of the entities by providing an interference geometry.


		* When the interference geometry is available it can be passed by the optional attribute _InterferenceGeometry_ pointing to _IfcConnectionGeometry_. The connection geometry is provided as a point, curve, surface, or solid within the placement coordinate systems of the connecting elements. The _IfcConnectionVolumeGeometry_ is the default type to be used for interference in 3D space, as indicated in e.g. clash detections.
		* When the interference geometry is available it can be passed by the optional attribute _InterferenceGeometry_ pointing to _IfcConnectionGeometry_. The connection geometry is provided as a point, curve, surface, or volume within the local placement coordinate systems of the connecting elements. The _IfcConnectionVolumeGeometry_ is the default type to be used for interference in 3D space, as indicated in e.g. clash detections.

	The _IfcConnectionGeometry_ property is used to define the interference shape, it can be part of the shape of one of the elements of the relationship (in the case of clash, overlapping and crossing interference types) or define the interface between the two shapes (in the case of along, over and under interference types).
	The _InterferenceGeometry_ attribute is used to define the interference shape, it can be part of the shape of one of the elements of the relationship (in the case of clash, overlapping and crossing interference types) or define the interface between the two shapes (in the case of along, over and under interference types).

	* Non oriented interferences types do not imply specific values of _ImpliedOrder_ (but can still be set to precise shape interference calculation)
	* Non oriented interferences types do not imply specific values of _ImpliedOrder_ (but can still be set to for a precise shape interference calculation)

Update IfcRelInterferesElement DocEntity & Documentation #40

Update IfcRelInterferesElement DocEntity & Documentation #40

Conversation

MatthieuPERIN commented May 20, 2021 • edited

AlexBrad1eyCT left a comment

Choose a reason for hiding this comment

MatthieuPERIN commented Jul 1, 2021

AlexBrad1eyCT left a comment

Choose a reason for hiding this comment

AlexBrad1eyCT commented Jul 2, 2021

SergejMuhic left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AlexBrad1eyCT Jul 2, 2021 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

MatthieuPERIN commented May 20, 2021 •

edited

AlexBrad1eyCT Jul 2, 2021 •

edited