diff --git a/ChangeSets/IFC2x3 to IFC4/DocChangeSet.xml b/ChangeSets/4.0.0.0/DocChangeSet.xml similarity index 52% rename from ChangeSets/IFC2x3 to IFC4/DocChangeSet.xml rename to ChangeSets/4.0.0.0/DocChangeSet.xml index 3f2b0f123..503e89a74 100644 --- a/ChangeSets/IFC2x3 to IFC4/DocChangeSet.xml +++ b/ChangeSets/4.0.0.0/DocChangeSet.xml @@ -1,390 +1,390 @@  - + - + - + - - - - - - - - - - + + + + + + + + + + - + - - - + + + - + - - + + - + - + - + - - + + - + - - - - + + + + - + - - + + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - + + + - + - + - + - - + + - + - + - + - + - - + + - + - + - - + + - + - + - - - + + + - + - - + + - + - + - - + + - + - + - + - + - + - + - + - + - + - - - + + + - - - - - - - + + + + + + + - + - + - + - + @@ -392,522 +392,522 @@ - - + + - + - + - + - + - + - + - + - + - + - + - + - - - + + + - - - + + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - - - - + + + + - - - + + + - - - + + + - - - - - + + + + + - - + + - - + + - - + + - + - + - + - + - + - + - + - - - + + + - + - + - + - + - + - + - + - - + + - + - - - + + + - + - + - + - + - - - + + + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - - - + + + - + - + - + - + - + - + - + - + @@ -916,111 +916,111 @@ - + - + - + - + - - - - - + + + + + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - - - + + + - + @@ -1029,87 +1029,87 @@ - + - + - + - - + + - + - - - + + + - + - + - - - + + + - + - - + + - - - - + + + + - - - + + + - + - + - - + + - + - + - + - + - + @@ -1117,199 +1117,199 @@ - + - + - + - - - - + + + + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - + + + - - - + + + - + - + - - + + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + @@ -1317,87 +1317,87 @@ - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + @@ -1405,42 +1405,42 @@ - - - - + + + + - + - - - + + + - + - + - + - + - + @@ -1448,463 +1448,463 @@ - + - + - + - + - + - + - - + + - + - + - - + + - + - + - + - + - + - + - + - - - + + + - - - + + + - + - + - + - + - + - + - - - + + + - + - + - + - + - + - - + + - + - + - + - + - + - + - - + + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - - - - + + + + + + - + - - - - - + + + + + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - + + + - - - + + + - + - - - + + + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + @@ -1912,534 +1912,534 @@ - + - + - + - - + + - + - + - + - - - + + + - + - - - - + + + + - + - + - - - + + + - + - + - - - - + + + + - + - + - + - + - + - + - + - - - + + + - + - + - + - - - + + + - + - + - + - + - + - - - - + + + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - - - + + + - + - + - + - + - + - - + + - + - + - - - - - + + + + + - + - - - - - - - - - + + + + + + + + + - - - + + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - - - - - - - + + + + + + + - + - + - + - + - + - - + + - - + + - + - + - + - + - + - + - + @@ -2447,159 +2447,159 @@ - - + + - + - + - + - + - + - - + + - - - + + + - + - + - + - + - + - - + + - - + + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + @@ -2607,955 +2607,955 @@ - + - + - - - + + + - - + + - - + + - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - + + - - - + + + - + - - + + - + - - - + + + - + - + - + - - + + - - + + - - - + + + - - + + - - - - + + + + - + - - + + - - - - + + + + - + - + - - + + - + - + - - - - + + + + - + - + - - - - + + + + - + - + - - - - + + + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - - - + + + + - + - + - - - - + + + + - + - + - - + + - + - + - - - + + + - + - + - - - - - + + + + + - - + + - + - + - + - - + + - + - + - + - + - - + + - - + + - + - + - - + + - + - - - - - - - + + + + + + + - + - - - - - - - + + + + + + + - + - + - - - + + + - + - + - + - + - + - - + + - + - + - - + + - + - + - - - - + + + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - - - + + + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - - - + + + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - - + + - + - + - + - + - - + + - - - + + + - - + + - + - + - - - - + + + + - + - + - - + + - + - + - - + + - + - + @@ -3564,115 +3564,115 @@ - + - + - + - - - - - + + + + + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + @@ -3680,35 +3680,35 @@ - - + + - + - + - + - + - + - + @@ -3716,173 +3716,173 @@ - + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - - + + - - - - - + + + + + - + - + - + - + - - - + + + - - - - - - - + + + + + + + - + - + - - + + - + - + - - + + - + - + - + - + - + - + @@ -3891,110 +3891,110 @@ - - - + + + - + - + - + - + - + - + - + - + - - - + + + - + - + - + - + - + - + - + - - - - - + + + + + - + - - + + - - - - - - - + + + + + + + @@ -4003,131 +4003,131 @@ - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - + @@ -4136,71 +4136,71 @@ - - - + + + - + - + - - - - + + + + - + - - - + + + - + - - - - - + + + + + - + - - - - - - + + + + + + - + - + - + - + - + - + - + @@ -4208,313 +4208,313 @@ - - - - - - + + + + + + - + - + - - - - + + + + - + - + - + - - - - + + + + - + - + - + - + - + - - + + - + - + - + - + - + - + - - + + - - - + + + - + - - - - - - + + + + + + - + - - - + + + - - - + + + - + - + - + - + - - - + + + - + - + - - - - - - + + + + + + - + - - - - - + + + + + - + - - - - - - + + + + + + - + - + - + - - - + + + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + @@ -4522,334 +4522,334 @@ - + - - + + - + - + - + - - + + - - - + + + - + - + - + - + - + - + - + - - - + + + - - - - - - + + + + + + - + - - - - + + + + - + - + - + - - - - - + + + + + - + - - - + + + - + - - + + - + - + - + - + - + - + - - - - + + + + - + - - - - - + + + + + - - - - - - - - - - - - + + + + + + + + + + + + - + - + - + - - - + + + - + - - + + - - - - - - + + + + + + - + - - + + - + - + - - - - + + + + - + - - - - + + + + - + - + - + - + - - - - - - - + + + + + + + - + - - - + + + - - + + - + - - - - - - + + + + + + - - - - + + + + - + - - - - - + + + + + - + - + - + - - - - - + + + + + - - + + - + @@ -4858,198 +4858,198 @@ - + - + - + - + - + - + - + - + - - + + - + - + - - + + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - - + + + + - + - + @@ -5057,184 +5057,184 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - - - - - - + + + + + + - + - + - + - - - - - - - - - - - - + + + + + + + + + + + + - + - + - + - + - + - + - + @@ -5243,345 +5243,345 @@ - + - + - + - + - + - + - + - + - + - + - + - - - + + + - + - + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - - + + - - + + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - - + + - - - - - - - - + + + + + + + + - - - - + + + + - + - + - + - + - + - + @@ -5590,115 +5590,115 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - - - - + + + + + + - - + + - + - + - + @@ -5708,66 +5708,66 @@ - + - - - - - - - + + + + + + + - + - + - + - + - + - + - + - + - + - + @@ -5775,157 +5775,157 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - + + + - + - + - + - + - + - + - + - + - - - + + + - + - + - + - + - + - + - - + + - + - + @@ -5934,218 +5934,218 @@ - + - - - - - + + + + + - - - - - - - - + + + + + + + + - + - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - - + + - - + + - + - - + + - + - - + + - + - + - + - + - + - + - + - - + + diff --git a/ChangeSets/IFC2x3 to IFC4/Documentation.md b/ChangeSets/4.0.0.0/Documentation.md similarity index 100% rename from ChangeSets/IFC2x3 to IFC4/Documentation.md rename to ChangeSets/4.0.0.0/Documentation.md diff --git a/ChangeSets/4.0.1.0/DocChangeSet.xml b/ChangeSets/4.0.1.0/DocChangeSet.xml new file mode 100644 index 000000000..00b8ef8f1 --- /dev/null +++ b/ChangeSets/4.0.1.0/DocChangeSet.xml @@ -0,0 +1,1598 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/ChangeSets/IFC4 Addendum 1/Documentation.md b/ChangeSets/4.0.1.0/Documentation.md similarity index 100% rename from ChangeSets/IFC4 Addendum 1/Documentation.md rename to ChangeSets/4.0.1.0/Documentation.md diff --git a/ChangeSets/4.0.2.0/DocChangeSet.xml b/ChangeSets/4.0.2.0/DocChangeSet.xml new file mode 100644 index 000000000..7def85e82 --- /dev/null +++ b/ChangeSets/4.0.2.0/DocChangeSet.xml @@ -0,0 +1,463 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/ChangeSets/IFC4 Addendum 2/Documentation.md b/ChangeSets/4.0.2.0/Documentation.md similarity index 100% rename from ChangeSets/IFC4 Addendum 2/Documentation.md rename to ChangeSets/4.0.2.0/Documentation.md diff --git a/ChangeSets/4.0.2.1/DocChangeSet.xml b/ChangeSets/4.0.2.1/DocChangeSet.xml new file mode 100644 index 000000000..9f5e67cc4 --- /dev/null +++ b/ChangeSets/4.0.2.1/DocChangeSet.xml @@ -0,0 +1,878 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/ChangeSets/4.0.2.1/Documentation.md b/ChangeSets/4.0.2.1/Documentation.md new file mode 100644 index 000000000..f055552ec --- /dev/null +++ b/ChangeSets/4.0.2.1/Documentation.md @@ -0,0 +1,2 @@ +{ .std} +The Technical Corrigendum to IFC4 Addendum 2 includes fixes and improvements to documentation, property sets, and examples based on implementer feedback. There are no changes to the schema, however all StandardCase and ElementedCase classes have been deprecated, with supertypes now supporting the same functionality. diff --git a/ChangeSets/IFC4 Addendum 1/DocChangeSet.xml b/ChangeSets/IFC4 Addendum 1/DocChangeSet.xml deleted file mode 100644 index c2545c6e0..000000000 --- a/ChangeSets/IFC4 Addendum 1/DocChangeSet.xml +++ /dev/null @@ -1,1598 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/ChangeSets/IFC4 Addendum 2/DocChangeSet.xml b/ChangeSets/IFC4 Addendum 2/DocChangeSet.xml deleted file mode 100644 index d149bf672..000000000 --- a/ChangeSets/IFC4 Addendum 2/DocChangeSet.xml +++ /dev/null @@ -1,463 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Constants/c/COMPLEX_3anFklXRj86BhMEVsDqIdj.xml b/Constants/c/COMPLEX_3anFklXRj86BhMEVsDqIdj.xml index 189517cf2..640a536e1 100644 --- a/Constants/c/COMPLEX_3anFklXRj86BhMEVsDqIdj.xml +++ b/Constants/c/COMPLEX_3anFklXRj86BhMEVsDqIdj.xml @@ -1,5 +1,5 @@  - + Not used - kept for upward compatibility. diff --git a/Constants/e/ELEMENTEDWALL_17wGJl8PD2suSmzoMiGpGq.xml b/Constants/e/ELEMENTEDWALL_17wGJl8PD2suSmzoMiGpGq.xml index c68286e6a..59d64ac59 100644 --- a/Constants/e/ELEMENTEDWALL_17wGJl8PD2suSmzoMiGpGq.xml +++ b/Constants/e/ELEMENTEDWALL_17wGJl8PD2suSmzoMiGpGq.xml @@ -1,7 +1,5 @@  - A stud wall framed with studs and faced with sheetings, sidings, wallboard, or plasterwork. -{ .deprecated} -> The value is deprecated, it is expressed by choosing the subtype _IfcWallElementedCase_. + A stud wall framed with studs and faced with sheetings, sidings, wallboard, or plasterwork. diff --git a/Constants/e/ELEMENT_2D6JmXdjHBQhjZ2o7Bv$fp.xml b/Constants/e/ELEMENT_2D6JmXdjHBQhjZ2o7Bv$fp.xml index c92a77313..0ca6cb304 100644 --- a/Constants/e/ELEMENT_2D6JmXdjHBQhjZ2o7Bv$fp.xml +++ b/Constants/e/ELEMENT_2D6JmXdjHBQhjZ2o7Bv$fp.xml @@ -1,5 +1,5 @@  - + Not used - kept for upward compatibility. diff --git a/Constants/l/LOAD_COMBINATION_1nghqo8HX7zQoeue7IbCQn.xml b/Constants/l/LOAD_COMBINATION_1nghqo8HX7zQoeue7IbCQn.xml index 4babceb03..88032d805 100644 --- a/Constants/l/LOAD_COMBINATION_1nghqo8HX7zQoeue7IbCQn.xml +++ b/Constants/l/LOAD_COMBINATION_1nghqo8HX7zQoeue7IbCQn.xml @@ -1,5 +1,5 @@  - + An intermediate level between LOAD_CASE and LOAD_COMBINATION. This level is obsolete and deprecated. Before the introduction of _IfcRelAssignsToGroupByFactor_, the purpose of this level was to provide a factor with which one or more LOAD_CASEs occur in a LOAD_COMBINATION. diff --git a/Constants/p/PARTIAL_02mpBiXF5B090xF$ZbUf7F.xml b/Constants/p/PARTIAL_02mpBiXF5B090xF$ZbUf7F.xml index 7b17190fe..217b4f1ee 100644 --- a/Constants/p/PARTIAL_02mpBiXF5B090xF$ZbUf7F.xml +++ b/Constants/p/PARTIAL_02mpBiXF5B090xF$ZbUf7F.xml @@ -1,5 +1,5 @@  - + Not used - kept for upward compatibility. diff --git a/Constants/p/POLYGONAL_1Z2uEUEwX2KBJpQFW__Qch.xml b/Constants/p/POLYGONAL_1Z2uEUEwX2KBJpQFW__Qch.xml index 645bc1360..cc85b5861 100644 --- a/Constants/p/POLYGONAL_1Z2uEUEwX2KBJpQFW__Qch.xml +++ b/Constants/p/POLYGONAL_1Z2uEUEwX2KBJpQFW__Qch.xml @@ -1,5 +1,7 @@  - - A polygonal wall, extruded vertically, where the wall thickness varies along the wall path. + + A polygonal wall, extruded vertically, where the wall thickness varies along the wall path. +{ .deprecated} +> IFC4 DEPRECATION&nbsp; The enumerator POLYGONAL is deprecated and shall no longer be used. diff --git a/Constants/s/STANDARD_3$tRl5c9X3d9115$P5AxjJ.xml b/Constants/s/STANDARD_3$tRl5c9X3d9115$P5AxjJ.xml index 405aef7b4..0d55f2036 100644 --- a/Constants/s/STANDARD_3$tRl5c9X3d9115$P5AxjJ.xml +++ b/Constants/s/STANDARD_3$tRl5c9X3d9115$P5AxjJ.xml @@ -1,7 +1,5 @@  - - A standard wall, extruded vertically with a constant thickness along the wall path. -{ .deprecated} -> The value is deprecated, it is expressed by choosing the subtype _IfcWallStandardCase_. + + A standard wall, extruded vertically with a constant thickness along the wall path. diff --git a/Constants/w/WCSEAT_2uhRm$O6v1hepYfS5j9VCs.xml b/Constants/w/WCSEAT_2uhRm$O6v1hepYfS5j9VCs.xml index e368f3b9e..7a0d8aab5 100644 --- a/Constants/w/WCSEAT_2uhRm$O6v1hepYfS5j9VCs.xml +++ b/Constants/w/WCSEAT_2uhRm$O6v1hepYfS5j9VCs.xml @@ -1,5 +1,7 @@  - - [Deprecated] Hinged seat that fits on the top of a water closet (WC) pan. + + Hinged seat that fits on the top of a water closet (WC) pan. +{ .deprecated} +> DEPRECATION&nbsp; Enumerator shall not be used in IFC4. diff --git a/Examples/Additional test cases/Examples/Beam varying cardinal points/DocExample.xml b/Examples/Additional test cases/Examples/Beam varying cardinal points/DocExample.xml index f75bf7f9e..e992e46e4 100644 --- a/Examples/Additional test cases/Examples/Beam varying cardinal points/DocExample.xml +++ b/Examples/Additional test cases/Examples/Beam varying cardinal points/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Additional test cases/Examples/Beam varying cardinal points/File.ifc b/Examples/Additional test cases/Examples/Beam varying cardinal points/File.ifc index c485ae16b..0153dd577 100644 --- a/Examples/Additional test cases/Examples/Beam varying cardinal points/File.ifc +++ b/Examples/Additional test cases/Examples/Beam varying cardinal points/File.ifc @@ -44,7 +44,7 @@ DATA; #207= IFCBEAMTYPE('32b2OtzCP30umNyY5LsCfN',#56,'IPE200',$,$,$,$,$,$,.JOIST.); #208= IFCRELDEFINESBYTYPE('3s_DqAVvb3LguudTShJHVo',#56,$,$,(#210,#227,#243,#260),#207); #209= IFCRELDECLARES('18K3qwA9fCieEg2L2UiuR_',#56,$,$,#100,(#207)); -#210= IFCBEAMSTANDARDCASE('2YX3YEaA13qOf$B1iBgAf6',#56,'TopMid',$,$,#211,#226,$,$); +#210= IFCBEAM('2YX3YEaA13qOf$B1iBgAf6',#56,'TopMid',$,$,#211,#226,$,$); #211= IFCLOCALPLACEMENT($,#212); #212= IFCAXIS2PLACEMENT3D(#2,#213,#214); #213= IFCDIRECTION((0.0,1.0,0.0)); @@ -61,7 +61,7 @@ DATA; #224= IFCCARTESIANPOINT((0.0,-100.0,0.0)); #225= IFCSHAPEREPRESENTATION(#5,'Body','SweptSolid',(#222)); #226= IFCPRODUCTDEFINITIONSHAPE($,$,(#218,#225)); -#227= IFCBEAMSTANDARDCASE('39IDqhhC14BxCj_Ryk$esj',#56,'BotMid',$,$,#228,#242,$,$); +#227= IFCBEAM('39IDqhhC14BxCj_Ryk$esj',#56,'BotMid',$,$,#228,#242,$,$); #228= IFCLOCALPLACEMENT($,#229); #229= IFCAXIS2PLACEMENT3D(#2,#230,#231); #230= IFCDIRECTION((0.0,1.0,0.0)); @@ -77,7 +77,7 @@ DATA; #240= IFCCARTESIANPOINT((0.0,100.0,0.0)); #241= IFCSHAPEREPRESENTATION(#5,'Body','SweptSolid',(#238)); #242= IFCPRODUCTDEFINITIONSHAPE($,$,(#234,#241)); -#243= IFCBEAMSTANDARDCASE('17CqI$IjrDARuaYNcWcoRH',#56,'BotLeft',$,$,#244,#259,$,$); +#243= IFCBEAM('17CqI$IjrDARuaYNcWcoRH',#56,'BotLeft',$,$,#244,#259,$,$); #244= IFCLOCALPLACEMENT($,#245); #245= IFCAXIS2PLACEMENT3D(#246,#247,#248); #246= IFCCARTESIANPOINT((500.0,0.0,0.0)); @@ -94,7 +94,7 @@ DATA; #257= IFCCARTESIANPOINT((-50.0,100.0,0.0)); #258= IFCSHAPEREPRESENTATION(#5,'Body','SweptSolid',(#255)); #259= IFCPRODUCTDEFINITIONSHAPE($,$,(#251,#258)); -#260= IFCBEAMSTANDARDCASE('3TOzuh11rACgRkioYYOjj5',#56,'TopRight',$,$,#261,#276,$,$); +#260= IFCBEAM('3TOzuh11rACgRkioYYOjj5',#56,'TopRight',$,$,#261,#276,$,$); #261= IFCLOCALPLACEMENT($,#262); #262= IFCAXIS2PLACEMENT3D(#263,#264,#265); #263= IFCCARTESIANPOINT((500.0,0.0,0.0)); diff --git a/Examples/Additional test cases/Examples/Beam varying extrusion paths/DocExample.xml b/Examples/Additional test cases/Examples/Beam varying extrusion paths/DocExample.xml index 59ed3de91..7c3f6090a 100644 --- a/Examples/Additional test cases/Examples/Beam varying extrusion paths/DocExample.xml +++ b/Examples/Additional test cases/Examples/Beam varying extrusion paths/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Additional test cases/Examples/Beam varying extrusion paths/File.ifc b/Examples/Additional test cases/Examples/Beam varying extrusion paths/File.ifc index f1dd6466c..f3c95222d 100644 --- a/Examples/Additional test cases/Examples/Beam varying extrusion paths/File.ifc +++ b/Examples/Additional test cases/Examples/Beam varying extrusion paths/File.ifc @@ -44,7 +44,7 @@ DATA; #207= IFCBEAMTYPE('32b2OtzCP30umNyY5LsCfN',#56,'IPE200',$,$,$,$,$,$,.JOIST.); #208= IFCRELDEFINESBYTYPE('3s_DqAVvb3LguudTShJHVo',#56,$,$,(#210,#227),#207); #209= IFCRELDECLARES('2tgfGrMZ15PQOp9j9EqeaR',#56,$,$,#100,(#207)); -#210= IFCBEAMSTANDARDCASE('0a_qfeQLDA8e5qT$Do6J_t',#56,'Extrusion',$,$,#211,#226,$,$); +#210= IFCBEAM('0a_qfeQLDA8e5qT$Do6J_t',#56,'Extrusion',$,$,#211,#226,$,$); #211= IFCLOCALPLACEMENT($,#212); #212= IFCAXIS2PLACEMENT3D(#2,#213,#214); #213= IFCDIRECTION((0.0,1.0,0.0)); @@ -61,7 +61,7 @@ DATA; #224= IFCCARTESIANPOINT((0.0,-100.0,0.0)); #225= IFCSHAPEREPRESENTATION(#5,'Body','SweptSolid',(#222)); #226= IFCPRODUCTDEFINITIONSHAPE($,$,(#218,#225)); -#227= IFCBEAMSTANDARDCASE('1zqFh80l11VgfEm3ZWh6Xv',#56,'Revolution',$,$,#228,#249,$,$); +#227= IFCBEAM('1zqFh80l11VgfEm3ZWh6Xv',#56,'Revolution',$,$,#228,#249,$,$); #228= IFCLOCALPLACEMENT($,#229); #229= IFCAXIS2PLACEMENT3D(#230,#231,#232); #230= IFCCARTESIANPOINT((0.0,0.0,400.0)); diff --git a/Examples/Additional test cases/Examples/Beam varying profiles/DocExample.xml b/Examples/Additional test cases/Examples/Beam varying profiles/DocExample.xml index 0674b9a84..d8ac945cb 100644 --- a/Examples/Additional test cases/Examples/Beam varying profiles/DocExample.xml +++ b/Examples/Additional test cases/Examples/Beam varying profiles/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Additional test cases/Examples/Beam varying profiles/File.ifc b/Examples/Additional test cases/Examples/Beam varying profiles/File.ifc index 4726ecb0f..761204fad 100644 --- a/Examples/Additional test cases/Examples/Beam varying profiles/File.ifc +++ b/Examples/Additional test cases/Examples/Beam varying profiles/File.ifc @@ -44,7 +44,7 @@ DATA; #207= IFCBEAMTYPE('32b2OtzCP30umNyY5LsCfN',#56,'IPE200',$,$,$,$,$,$,.JOIST.); #208= IFCRELDEFINESBYTYPE('3s_DqAVvb3LguudTShJHVo',#56,$,$,(#210),#207); #209= IFCRELDECLARES('2DvxT2XND9fesX3CV34ZPl',#56,$,$,#100,(#207,#305)); -#210= IFCBEAMSTANDARDCASE('0uo2yx7G19uwCu9sIjn6DQ',#56,'IPE200',$,$,#211,#224,$,$); +#210= IFCBEAM('0uo2yx7G19uwCu9sIjn6DQ',#56,'IPE200',$,$,#211,#224,$,$); #211= IFCLOCALPLACEMENT($,#212); #212= IFCAXIS2PLACEMENT3D(#2,#213,#214); #213= IFCDIRECTION((0.0,1.0,0.0)); @@ -65,7 +65,7 @@ DATA; #304= IFCRELASSOCIATESMATERIAL('3aZa8DE_z84uP2gdbcb_UP',#56,'MatAssoc','Material Associates',(#305),#303); #305= IFCBEAMTYPE('3l_OKNTJr4yBOR5rYl6b9w',#56,'CHS219.1x6.3',$,$,$,$,$,$,.BEAM.); #306= IFCRELDEFINESBYTYPE('3LrutsCpn4DPF9Zt4YdIEU',#56,$,$,(#307),#305); -#307= IFCBEAMSTANDARDCASE('3_NFDdmqr7mxekvlvcgwa7',#56,'CHS219.1x6.3',$,$,#308,#321,$,$); +#307= IFCBEAM('3_NFDdmqr7mxekvlvcgwa7',#56,'CHS219.1x6.3',$,$,#308,#321,$,$); #308= IFCLOCALPLACEMENT($,#309); #309= IFCAXIS2PLACEMENT3D(#310,#311,#312); #310= IFCCARTESIANPOINT((500.0,0.0,0.0)); diff --git a/Examples/Additional test cases/Examples/Reinforcing assembly/File.ifc b/Examples/Additional test cases/Examples/Reinforcing assembly/File.ifc index a0007e0f6..1acd4ee90 100644 --- a/Examples/Additional test cases/Examples/Reinforcing assembly/File.ifc +++ b/Examples/Additional test cases/Examples/Reinforcing assembly/File.ifc @@ -56,7 +56,7 @@ DATA; #219= IFCRELASSOCIATESMATERIAL('2ZEgyI2v184hwa$_diRqS9',#56,'MatAssoc','Material Associates',(#220),#218); #220= IFCBEAMTYPE('3bdpqVuWTCbxJ2S3ODYv6q',#56,'400x200RC',$,$,$,$,$,$,.BEAM.); #221= IFCRELDEFINESBYTYPE('2oaQVVf79BrwRouvtRuQVg',#56,$,$,(#222),#220); -#222= IFCBEAMSTANDARDCASE('1yjQ2DwLnCC8k3i3X6D_ut',#56,$,$,$,#223,#238,$,$); +#222= IFCBEAM('1yjQ2DwLnCC8k3i3X6D_ut',#56,$,$,$,#223,#238,$,$); #223= IFCLOCALPLACEMENT($,#224); #224= IFCAXIS2PLACEMENT3D(#2,#225,#226); #225= IFCDIRECTION((0.0,1.0,0.0)); diff --git a/Examples/Additional test cases/Examples/Reinforcing stirrup/DocExample.xml b/Examples/Additional test cases/Examples/Reinforcing stirrup/DocExample.xml index a8f85251f..2882f7eb8 100644 --- a/Examples/Additional test cases/Examples/Reinforcing stirrup/DocExample.xml +++ b/Examples/Additional test cases/Examples/Reinforcing stirrup/DocExample.xml @@ -1,7 +1,7 @@  - + diff --git a/Examples/Additional test cases/Examples/Slab openings/DocExample.xml b/Examples/Additional test cases/Examples/Slab openings/DocExample.xml index e44e962ee..588608d11 100644 --- a/Examples/Additional test cases/Examples/Slab openings/DocExample.xml +++ b/Examples/Additional test cases/Examples/Slab openings/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Additional test cases/Examples/Slab openings/File.ifc b/Examples/Additional test cases/Examples/Slab openings/File.ifc index 1eaca871a..6f6a45754 100644 --- a/Examples/Additional test cases/Examples/Slab openings/File.ifc +++ b/Examples/Additional test cases/Examples/Slab openings/File.ifc @@ -42,7 +42,7 @@ DATA; #205= IFCRELASSOCIATESMATERIAL('2l_enLhI93reVwnim9gXUq',#56,'MatAssoc','Material Associates',(#300),#204); #300= IFCSLABTYPE('0RSW$KKbzCZ9QaSm3GoEan',#56,'200mm Concrete',$,$,$,$,$,$,.FLOOR.); #302= IFCRELDECLARES('1oXuN5qJ93Eggy5n3jcluj',#56,$,$,#100,(#300)); -#303= IFCSLABSTANDARDCASE('1wAj$J2Az2V8wnBiVYd3bU',#56,$,$,$,#304,#315,$,$); +#303= IFCSLAB('1wAj$J2Az2V8wnBiVYd3bU',#56,$,$,$,#304,#315,$,$); #304= IFCLOCALPLACEMENT($,#316); #305= IFCAXIS2PLACEMENT3D(#306,$,$); #306= IFCCARTESIANPOINT((0.0,0.0,-200.0)); @@ -64,7 +64,7 @@ DATA; #322= IFCEXTRUDEDAREASOLID(#318,#319,#321,200.0); #323= IFCSHAPEREPRESENTATION(#5,'Body','SweptSolid',(#322)); #324= IFCPRODUCTDEFINITIONSHAPE($,$,(#323)); -#325= IFCOPENINGSTANDARDCASE('15RSTHd8nFVQWMRE7og7sd',#56,'Opening',$,$,#327,#324,$,$); +#325= IFCOPENINGELEMENT('15RSTHd8nFVQWMRE7og7sd',#56,'Opening',$,$,#327,#324,$,$); #326= IFCAXIS2PLACEMENT3D(#2,$,$); #327= IFCLOCALPLACEMENT($,#326); #328= IFCRELVOIDSELEMENT('0gqEDsyEzFXvY$fc_rUxyO',#56,$,$,#303,#325); diff --git a/Examples/Placements and GIS referencing/Examples/Geographic referencing/DocExample.xml b/Examples/Advanced geometric shape/Examples/Curve parameters in degrees/DocExample.xml similarity index 65% rename from Examples/Placements and GIS referencing/Examples/Geographic referencing/DocExample.xml rename to Examples/Advanced geometric shape/Examples/Curve parameters in degrees/DocExample.xml index 4677d1841..ef218f5f8 100644 --- a/Examples/Placements and GIS referencing/Examples/Geographic referencing/DocExample.xml +++ b/Examples/Advanced geometric shape/Examples/Curve parameters in degrees/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Advanced geometric shape/Examples/Curve parameters in degrees/Documentation.md b/Examples/Advanced geometric shape/Examples/Curve parameters in degrees/Documentation.md new file mode 100644 index 000000000..a2ce50a03 --- /dev/null +++ b/Examples/Advanced geometric shape/Examples/Curve parameters in degrees/Documentation.md @@ -0,0 +1,3 @@ +This example illustrates extruded solids based on trimmed arcs using degrees. The resulting solid is identical to the corresponding example in radians. + +!["Trimmed curve extrusions"](../../../../figures/examples/trimmedcurve.png "Figure 1 — Trimmed curve representation") diff --git a/Examples/Advanced geometric shape/Examples/Curve parameters in degrees/File.ifc b/Examples/Advanced geometric shape/Examples/Curve parameters in degrees/File.ifc new file mode 100644 index 000000000..6654200ae --- /dev/null +++ b/Examples/Advanced geometric shape/Examples/Curve parameters in degrees/File.ifc @@ -0,0 +1,154 @@ +ISO-10303-21; +HEADER; +FILE_DESCRIPTION(('ViewDefinition [DesignTransferView_V1]'),'2;1'); +FILE_NAME( +/* name */ 'C:\\My Work\\Geometry Gym\\documents\\building smart\\github\\ifcscript\\examples\\CurveParametersDegrees.ifc', +/* time_stamp */ '2017-06-28T23:09:53', +/* author */ ('jonm'), +/* organization */ ('Geometry Gym'), +/* preprocessor_version */ 'GeometryGymIFC v0.0.15.0 by Geometry Gym Pty Ltd built 2017-06-28T13:09:05', +/* originating_system */ 'IFCExamples v0.0.1.0', +/* authorization */ 'None'); + +FILE_SCHEMA (('IFC4')); +ENDSEC; + +DATA; +#10= IFCCARTESIANPOINT((0.0,0.0,0.0)); +#11= IFCAXIS2PLACEMENT3D(#10,$,$); +#12= IFCLOCALPLACEMENT($,#11); +/* defines the default building (as required as the minimum spatial element) */ +/* These profile curves are intentionally expressed in a more complicated manner than possible to test parameterization */ +#13= IFCBUILDING('39t4Pu3nTC4ekXYRIHJB9W',$,'IfcBuilding',$,$,#12,$,$,$,$,$,#18); +#14= IFCRELCONTAINEDINSPATIALSTRUCTURE('3Sa3dTJGn0H8TQIGiuGQd5',$,'Building','Building Container for Elements',(#77,#131,#180),#13); +#15= IFCCARTESIANPOINT((0.0,0.0,0.0)); +#16= IFCAXIS2PLACEMENT3D(#15,$,$); +#18= IFCPOSTALADDRESS($,$,$,$,('Unknown'),$,'Unknown',$,'Unknown','Unknown'); +/* general entities required for all IFC sets, defining the context for the exchange */ +#20= IFCPROJECT('0$WU4A9R19$vKWO$AdOnKA',$,'IfcProject',$,$,$,$,(#31),#21); +#21= IFCUNITASSIGNMENT((#22,#23,#24,#27,#29)); +#22= IFCSIUNIT(*,.LENGTHUNIT.,.MILLI.,.METRE.); +#23= IFCSIUNIT(*,.AREAUNIT.,$,.SQUARE_METRE.); +#24= IFCSIUNIT(*,.VOLUMEUNIT.,$,.CUBIC_METRE.); +#25= IFCSIUNIT(*,.PLANEANGLEUNIT.,$,.RADIAN.); +#26= IFCMEASUREWITHUNIT(IFCPLANEANGLEMEASURE(0.0174532925199433),#25); +#27= IFCCONVERSIONBASEDUNIT(#28,.PLANEANGLEUNIT.,'DEGREE',#26); +#28= IFCDIMENSIONALEXPONENTS(0,0,0,0,0,0,0); +#29= IFCSIUNIT(*,.TIMEUNIT.,$,.SECOND.); +#30= IFCRELAGGREGATES('091a6ewbvCMQ2Vyiqspa7a',$,'Project Container','Project Container for Buildings',#20,(#13)); +#31= IFCGEOMETRICREPRESENTATIONCONTEXT($,'Model',3,0.0001,#33,#34); +#32= IFCCARTESIANPOINT((0.0,0.0,0.0)); +#33= IFCAXIS2PLACEMENT3D(#32,$,$); +#34= IFCDIRECTION((0.0,1.0)); +#35= IFCGEOMETRICREPRESENTATIONSUBCONTEXT('Body','Model',*,*,*,*,#31,$,.MODEL_VIEW.,$); +/* Example data for CurveParametersDegrees */ +#50= IFCMATERIAL('Steel',$,$); +#52= IFCCARTESIANPOINT((-1000.0,1000.0)); +#53= IFCDIRECTION((0.70710678,-0.70710678)); +#54= IFCVECTOR(#53,1414.2135623731); +#55= IFCLINE(#52,#54); +#56= IFCTRIMMEDCURVE(#55,(IFCPARAMETERVALUE(0.292893218813453)),(IFCPARAMETERVALUE(1.70710678118655)),.T.,.PARAMETER.); +#57= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#56); +#58= IFCCARTESIANPOINT((0.0,0.0)); +#59= IFCAXIS2PLACEMENT2D(#58,$); +#60= IFCCIRCLE(#59,1000.0); +#61= IFCTRIMMEDCURVE(#60,(IFCPARAMETERVALUE(315.0)),(IFCPARAMETERVALUE(135.0)),.T.,.PARAMETER.); +#62= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#61); +#63= IFCCOMPOSITECURVE((#57,#62),.U.); +#64= IFCARBITRARYCLOSEDPROFILEDEF(.AREA.,'SemiCircle',#63); +#65= IFCMATERIALPROFILE('SemiCircle',$,#50,#64,$,$); +#67= IFCMATERIALPROFILESET('SemiCircle',$,(#65),$); +#68= IFCRELASSOCIATESMATERIAL('1gdVo5TjPETPZlW8HSRupM',$,'MatAssoc','Material Associates',(#69),#67); +#69= IFCCOLUMNTYPE('24mq0gwVr7bgEMXPmo$TrF',$,'SemiCircle',$,$,$,$,$,$,.COLUMN.); +#70= IFCRELDEFINESBYTYPE('0devdSRyf3uBEQbSqWTDjo',$,'NameNotAssigned',$,(#77),#69); +#71= IFCRELDECLARES('1Cjr05W9T0fx0M3_mdVqMd',$,$,$,#20,(#69,#124,#173)); +#72= IFCMATERIALPROFILESETUSAGE(#67,5,$); +#73= IFCRELASSOCIATESMATERIAL('35z8gDFbb6gvrCOz$24tUJ',$,'MatAssoc','Material Associates',(#77),#72); +#74= IFCCARTESIANPOINT((0.0,0.0,0.0)); +#75= IFCAXIS2PLACEMENT3D(#74,$,$); +#76= IFCLOCALPLACEMENT(#12,#75); +#77= IFCCOLUMN('0RGc8lepr7BRF_EtHrWJ45',$,'SemiCircle',$,$,#76,#85,$,$); +#78= IFCCARTESIANPOINT((0.0,0.0,2000.0)); +#79= IFCPOLYLINE((#15,#78)); +#80= IFCGEOMETRICREPRESENTATIONSUBCONTEXT('Axis','Model',*,*,*,*,#31,$,.MODEL_VIEW.,$); +#81= IFCSHAPEREPRESENTATION(#80,'Axis','Curve3D',(#79)); +#82= IFCEXTRUDEDAREASOLID(#64,$,#83,2000.0); +#83= IFCDIRECTION((0.0,0.0,1.0)); +#84= IFCSHAPEREPRESENTATION(#35,'Body','SweptSolid',(#82)); +#85= IFCPRODUCTDEFINITIONSHAPE($,$,(#81,#84)); +#100= IFCCARTESIANPOINT((0.0,1000.0)); +#101= IFCAXIS2PLACEMENT2D(#100,#102); +#102= IFCDIRECTION((-1.0,0.0)); +#103= IFCCIRCLE(#101,1732.05081); +#104= IFCTRIMMEDCURVE(#103,(IFCPARAMETERVALUE(60.0)),(IFCPARAMETERVALUE(120.0)),.T.,.PARAMETER.); +#105= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#104); +#106= IFCCARTESIANPOINT((-866.0254,-500.0)); +#107= IFCAXIS2PLACEMENT2D(#106,#108); +#108= IFCDIRECTION((0.0,-1.0)); +#109= IFCCIRCLE(#107,1732.05081); +#110= IFCTRIMMEDCURVE(#109,(IFCPARAMETERVALUE(90.0)),(IFCPARAMETERVALUE(150.0)),.T.,.PARAMETER.); +#111= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#110); +#112= IFCCARTESIANPOINT((866.0254,-500.0)); +#113= IFCAXIS2PLACEMENT2D(#112,#114); +#114= IFCDIRECTION((0.0,1.0)); +#115= IFCCIRCLE(#113,1732.05081); +#116= IFCTRIMMEDCURVE(#115,(IFCPARAMETERVALUE(30.0)),(IFCPARAMETERVALUE(90.0)),.T.,.PARAMETER.); +#117= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#116); +#118= IFCCOMPOSITECURVE((#105,#111,#117),.U.); +#119= IFCARBITRARYCLOSEDPROFILEDEF(.AREA.,'CurviLinearTriangle',#118); +#120= IFCMATERIALPROFILE('CurviLinearTriangle',$,#50,#119,$,$); +#122= IFCMATERIALPROFILESET('CurviLinearTriangle',$,(#120),$); +#123= IFCRELASSOCIATESMATERIAL('1qSyS$HSb8TRu4PVnIUzZM',$,'MatAssoc','Material Associates',(#124),#122); +#124= IFCCOLUMNTYPE('0JgmY6eGLC9AwX_nMFf5CT',$,'CurviLinearTriangle',$,$,$,$,$,$,.COLUMN.); +#125= IFCRELDEFINESBYTYPE('1N1PpBCJLB4QMrIjidnGaj',$,'NameNotAssigned',$,(#131),#124); +#126= IFCMATERIALPROFILESETUSAGE(#122,5,$); +#127= IFCRELASSOCIATESMATERIAL('00Bah4pIPCa9jB2F34kUX_',$,'MatAssoc','Material Associates',(#131),#126); +#128= IFCCARTESIANPOINT((2500.0,0.0,0.0)); +#129= IFCAXIS2PLACEMENT3D(#128,$,$); +#130= IFCLOCALPLACEMENT(#12,#129); +#131= IFCCOLUMN('3vcm8ZmFfDwhpgzzT7EP8n',$,'CurviLinearTriangle',$,$,#130,#137,$,$); +#132= IFCCARTESIANPOINT((0.0,0.0,2000.0)); +#133= IFCPOLYLINE((#15,#132)); +#134= IFCSHAPEREPRESENTATION(#80,'Axis','Curve3D',(#133)); +#135= IFCEXTRUDEDAREASOLID(#119,$,#83,2000.0); +#136= IFCSHAPEREPRESENTATION(#35,'Body','SweptSolid',(#135)); +#137= IFCPRODUCTDEFINITIONSHAPE($,$,(#134,#136)); +#150= IFCCARTESIANPOINT((0.0,0.0)); +#151= IFCAXIS2PLACEMENT2D(#150,$); +#152= IFCELLIPSE(#151,1000.0,500.0); +#153= IFCTRIMMEDCURVE(#152,(IFCPARAMETERVALUE(0.0)),(IFCPARAMETERVALUE(45.0)),.T.,.PARAMETER.); +#154= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#153); +#155= IFCCARTESIANPOINT((0.0,0.0)); +#156= IFCDIRECTION((0.89442719,0.4472136)); +#157= IFCVECTOR(#156,1.0); +#158= IFCLINE(#155,#157); +#159= IFCTRIMMEDCURVE(#158,(IFCPARAMETERVALUE(0.0)),(IFCPARAMETERVALUE(790.569415042095)),.F.,.PARAMETER.); +#160= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#159); +#161= IFCCARTESIANPOINT((0.0,0.0)); +#162= IFCDIRECTION((1.0,0.0)); +#163= IFCVECTOR(#162,1.0); +#164= IFCLINE(#161,#163); +#165= IFCTRIMMEDCURVE(#164,(IFCPARAMETERVALUE(0.0)),(IFCPARAMETERVALUE(1000.0)),.T.,.PARAMETER.); +#166= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#165); +#167= IFCCOMPOSITECURVE((#154,#160,#166),.U.); +#168= IFCARBITRARYCLOSEDPROFILEDEF(.AREA.,'PartialEllipse',#167); +#169= IFCMATERIALPROFILE('PartialEllipse',$,#50,#168,$,$); +#171= IFCMATERIALPROFILESET('PartialEllipse',$,(#169),$); +#172= IFCRELASSOCIATESMATERIAL('2V$PMUw5f3PgVGq_LG8lb7',$,'MatAssoc','Material Associates',(#173),#171); +#173= IFCCOLUMNTYPE('32anvmJgjFPOL650_UAlfM',$,'PartialEllipse',$,$,$,$,$,$,.COLUMN.); +#174= IFCRELDEFINESBYTYPE('1YdxXK2rrC6RnMj56iAUZG',$,'NameNotAssigned',$,(#180),#173); +#175= IFCMATERIALPROFILESETUSAGE(#171,5,$); +#176= IFCRELASSOCIATESMATERIAL('1k_RZ6rAPBe92Lvj8VqnvM',$,'MatAssoc','Material Associates',(#180),#175); +#177= IFCCARTESIANPOINT((5000.0,0.0,0.0)); +#178= IFCAXIS2PLACEMENT3D(#177,$,$); +#179= IFCLOCALPLACEMENT(#12,#178); +#180= IFCCOLUMN('0gw7Zq2jn3b91J9aZCStsR',$,'PartialEllipse',$,$,#179,#186,$,$); +#181= IFCCARTESIANPOINT((0.0,0.0,2000.0)); +#182= IFCPOLYLINE((#15,#181)); +#183= IFCSHAPEREPRESENTATION(#80,'Axis','Curve3D',(#182)); +#184= IFCEXTRUDEDAREASOLID(#168,$,#83,2000.0); +#185= IFCSHAPEREPRESENTATION(#35,'Body','SweptSolid',(#184)); +#186= IFCPRODUCTDEFINITIONSHAPE($,$,(#183,#185)); +ENDSEC; + +END-ISO-10303-21; diff --git a/Examples/Advanced geometric shape/Examples/Curve parameters in radians/DocExample.xml b/Examples/Advanced geometric shape/Examples/Curve parameters in radians/DocExample.xml new file mode 100644 index 000000000..a5c198521 --- /dev/null +++ b/Examples/Advanced geometric shape/Examples/Curve parameters in radians/DocExample.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/Examples/Advanced geometric shape/Examples/Curve parameters in radians/Documentation.md b/Examples/Advanced geometric shape/Examples/Curve parameters in radians/Documentation.md new file mode 100644 index 000000000..d728928c8 --- /dev/null +++ b/Examples/Advanced geometric shape/Examples/Curve parameters in radians/Documentation.md @@ -0,0 +1,3 @@ +This example illustrates extruded solids based on trimmed arcs using radians. The resulting solid is identical to the corresponding example in degrees. + +!["Trimmed curve extrusions"](../../../../figures/examples/trimmedcurve.png "Figure 1 — Trimmed curve representation") diff --git a/Examples/Advanced geometric shape/Examples/Curve parameters in radians/File.ifc b/Examples/Advanced geometric shape/Examples/Curve parameters in radians/File.ifc new file mode 100644 index 000000000..a179038a2 --- /dev/null +++ b/Examples/Advanced geometric shape/Examples/Curve parameters in radians/File.ifc @@ -0,0 +1,151 @@ +ISO-10303-21; +HEADER; +FILE_DESCRIPTION(('ViewDefinition [DesignTransferView_V1]'),'2;1'); +FILE_NAME( +/* name */ 'C:\\My Work\\Geometry Gym\\documents\\building smart\\github\\ifcscript\\examples\\CurveParametersRadians.ifc', +/* time_stamp */ '2017-06-28T23:09:53', +/* author */ ('jonm'), +/* organization */ ('Geometry Gym'), +/* preprocessor_version */ 'GeometryGymIFC v0.0.15.0 by Geometry Gym Pty Ltd built 2017-06-28T13:09:05', +/* originating_system */ 'IFCExamples v0.0.1.0', +/* authorization */ 'None'); + +FILE_SCHEMA (('IFC4')); +ENDSEC; + +DATA; +#10= IFCCARTESIANPOINT((0.0,0.0,0.0)); +#11= IFCAXIS2PLACEMENT3D(#10,$,$); +#12= IFCLOCALPLACEMENT($,#11); +/* defines the default building (as required as the minimum spatial element) */ +/* These profile curves are intentionally expressed in a more complicated manner than possible to test parameterization */ +#13= IFCBUILDING('39t4Pu3nTC4ekXYRIHJB9W',$,'IfcBuilding',$,$,#12,$,$,$,$,$,#18); +#14= IFCRELCONTAINEDINSPATIALSTRUCTURE('3Sa3dTJGn0H8TQIGiuGQd5',$,'Building','Building Container for Elements',(#77,#131,#180),#13); +#15= IFCCARTESIANPOINT((0.0,0.0,0.0)); +#16= IFCAXIS2PLACEMENT3D(#15,$,$); +#18= IFCPOSTALADDRESS($,$,$,$,('Unknown'),$,'Unknown',$,'Unknown','Unknown'); +/* general entities required for all IFC sets, defining the context for the exchange */ +#20= IFCPROJECT('0$WU4A9R19$vKWO$AdOnKA',$,'IfcProject',$,$,$,$,(#28),#21); +#21= IFCUNITASSIGNMENT((#22,#23,#24,#25,#26)); +#22= IFCSIUNIT(*,.LENGTHUNIT.,.MILLI.,.METRE.); +#23= IFCSIUNIT(*,.AREAUNIT.,$,.SQUARE_METRE.); +#24= IFCSIUNIT(*,.VOLUMEUNIT.,$,.CUBIC_METRE.); +#25= IFCSIUNIT(*,.PLANEANGLEUNIT.,$,.RADIAN.); +#26= IFCSIUNIT(*,.TIMEUNIT.,$,.SECOND.); +#27= IFCRELAGGREGATES('091a6ewbvCMQ2Vyiqspa7a',$,'Project Container','Project Container for Buildings',#20,(#13)); +#28= IFCGEOMETRICREPRESENTATIONCONTEXT($,'Model',3,0.0001,#30,#31); +#29= IFCCARTESIANPOINT((0.0,0.0,0.0)); +#30= IFCAXIS2PLACEMENT3D(#29,$,$); +#31= IFCDIRECTION((0.0,1.0)); +#32= IFCGEOMETRICREPRESENTATIONSUBCONTEXT('Body','Model',*,*,*,*,#28,$,.MODEL_VIEW.,$); +/* Example data for CurveParametersRadians */ +#50= IFCMATERIAL('Steel',$,$); +#52= IFCCARTESIANPOINT((-1000.0,1000.0)); +#53= IFCDIRECTION((0.70710678,-0.70710678)); +#54= IFCVECTOR(#53,1414.2135623731); +#55= IFCLINE(#52,#54); +#56= IFCTRIMMEDCURVE(#55,(IFCPARAMETERVALUE(0.292893218813453)),(IFCPARAMETERVALUE(1.70710678118655)),.T.,.PARAMETER.); +#57= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#56); +#58= IFCCARTESIANPOINT((0.0,0.0)); +#59= IFCAXIS2PLACEMENT2D(#58,$); +#60= IFCCIRCLE(#59,1000.0); +#61= IFCTRIMMEDCURVE(#60,(IFCPARAMETERVALUE(5.49778714378214)),(IFCPARAMETERVALUE(2.35619449019234)),.T.,.PARAMETER.); +#62= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#61); +#63= IFCCOMPOSITECURVE((#57,#62),.U.); +#64= IFCARBITRARYCLOSEDPROFILEDEF(.AREA.,'SemiCircle',#63); +#65= IFCMATERIALPROFILE('SemiCircle',$,#50,#64,$,$); +#67= IFCMATERIALPROFILESET('SemiCircle',$,(#65),$); +#68= IFCRELASSOCIATESMATERIAL('1gdVo5TjPETPZlW8HSRupM',$,'MatAssoc','Material Associates',(#69),#67); +#69= IFCCOLUMNTYPE('24mq0gwVr7bgEMXPmo$TrF',$,'SemiCircle',$,$,$,$,$,$,.COLUMN.); +#70= IFCRELDEFINESBYTYPE('0devdSRyf3uBEQbSqWTDjo',$,'NameNotAssigned',$,(#77),#69); +#71= IFCRELDECLARES('1Cjr05W9T0fx0M3_mdVqMd',$,$,$,#20,(#69,#124,#173)); +#72= IFCMATERIALPROFILESETUSAGE(#67,5,$); +#73= IFCRELASSOCIATESMATERIAL('35z8gDFbb6gvrCOz$24tUJ',$,'MatAssoc','Material Associates',(#77),#72); +#74= IFCCARTESIANPOINT((0.0,0.0,0.0)); +#75= IFCAXIS2PLACEMENT3D(#74,$,$); +#76= IFCLOCALPLACEMENT(#12,#75); +#77= IFCCOLUMN('0RGc8lepr7BRF_EtHrWJ45',$,'SemiCircle',$,$,#76,#85,$,$); +#78= IFCCARTESIANPOINT((0.0,0.0,2000.0)); +#79= IFCPOLYLINE((#15,#78)); +#80= IFCGEOMETRICREPRESENTATIONSUBCONTEXT('Axis','Model',*,*,*,*,#28,$,.MODEL_VIEW.,$); +#81= IFCSHAPEREPRESENTATION(#80,'Axis','Curve3D',(#79)); +#82= IFCEXTRUDEDAREASOLID(#64,$,#83,2000.0); +#83= IFCDIRECTION((0.0,0.0,1.0)); +#84= IFCSHAPEREPRESENTATION(#32,'Body','SweptSolid',(#82)); +#85= IFCPRODUCTDEFINITIONSHAPE($,$,(#81,#84)); +#100= IFCCARTESIANPOINT((0.0,1000.0)); +#101= IFCAXIS2PLACEMENT2D(#100,#102); +#102= IFCDIRECTION((-1.0,0.0)); +#103= IFCCIRCLE(#101,1732.05081); +#104= IFCTRIMMEDCURVE(#103,(IFCPARAMETERVALUE(1.0471975511966)),(IFCPARAMETERVALUE(2.0943951023932)),.T.,.PARAMETER.); +#105= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#104); +#106= IFCCARTESIANPOINT((-866.0254,-500.0)); +#107= IFCAXIS2PLACEMENT2D(#106,#108); +#108= IFCDIRECTION((0.0,-1.0)); +#109= IFCCIRCLE(#107,1732.05081); +#110= IFCTRIMMEDCURVE(#109,(IFCPARAMETERVALUE(1.5707963267949)),(IFCPARAMETERVALUE(2.61799387799149)),.T.,.PARAMETER.); +#111= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#110); +#112= IFCCARTESIANPOINT((866.0254,-500.0)); +#113= IFCAXIS2PLACEMENT2D(#112,#114); +#114= IFCDIRECTION((0.0,1.0)); +#115= IFCCIRCLE(#113,1732.05081); +#116= IFCTRIMMEDCURVE(#115,(IFCPARAMETERVALUE(0.523598775598299)),(IFCPARAMETERVALUE(1.5707963267949)),.T.,.PARAMETER.); +#117= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#116); +#118= IFCCOMPOSITECURVE((#105,#111,#117),.U.); +#119= IFCARBITRARYCLOSEDPROFILEDEF(.AREA.,'CurviLinearTriangle',#118); +#120= IFCMATERIALPROFILE('CurviLinearTriangle',$,#50,#119,$,$); +#122= IFCMATERIALPROFILESET('CurviLinearTriangle',$,(#120),$); +#123= IFCRELASSOCIATESMATERIAL('1M5oofzjD3IOM43brXW6wT',$,'MatAssoc','Material Associates',(#124),#122); +#124= IFCCOLUMNTYPE('3N_qc_BjX1hvEgwfRvVcb_',$,'CurviLinearTriangle',$,$,$,$,$,$,.COLUMN.); +#125= IFCRELDEFINESBYTYPE('3tGocD1N51oOvSvHbJI_qD',$,'NameNotAssigned',$,(#131),#124); +#126= IFCMATERIALPROFILESETUSAGE(#122,5,$); +#127= IFCRELASSOCIATESMATERIAL('0gnTzVmkbE9hPsJDxOUOL3',$,'MatAssoc','Material Associates',(#131),#126); +#128= IFCCARTESIANPOINT((2500.0,0.0,0.0)); +#129= IFCAXIS2PLACEMENT3D(#128,$,$); +#130= IFCLOCALPLACEMENT(#12,#129); +#131= IFCCOLUMN('0bmIILAwj8$PLHK1jcmad0',$,'CurviLinearTriangle',$,$,#130,#137,$,$); +#132= IFCCARTESIANPOINT((0.0,0.0,2000.0)); +#133= IFCPOLYLINE((#15,#132)); +#134= IFCSHAPEREPRESENTATION(#80,'Axis','Curve3D',(#133)); +#135= IFCEXTRUDEDAREASOLID(#119,$,#83,2000.0); +#136= IFCSHAPEREPRESENTATION(#32,'Body','SweptSolid',(#135)); +#137= IFCPRODUCTDEFINITIONSHAPE($,$,(#134,#136)); +#150= IFCCARTESIANPOINT((0.0,0.0)); +#151= IFCAXIS2PLACEMENT2D(#150,$); +#152= IFCELLIPSE(#151,1000.0,500.0); +#153= IFCTRIMMEDCURVE(#152,(IFCPARAMETERVALUE(0.0)),(IFCPARAMETERVALUE(0.785398163397448)),.T.,.PARAMETER.); +#154= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#153); +#155= IFCCARTESIANPOINT((0.0,0.0)); +#156= IFCDIRECTION((0.89442719,0.4472136)); +#157= IFCVECTOR(#156,1.0); +#158= IFCLINE(#155,#157); +#159= IFCTRIMMEDCURVE(#158,(IFCPARAMETERVALUE(0.0)),(IFCPARAMETERVALUE(790.569415042095)),.F.,.PARAMETER.); +#160= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#159); +#161= IFCCARTESIANPOINT((0.0,0.0)); +#162= IFCDIRECTION((1.0,0.0)); +#163= IFCVECTOR(#162,1.0); +#164= IFCLINE(#161,#163); +#165= IFCTRIMMEDCURVE(#164,(IFCPARAMETERVALUE(0.0)),(IFCPARAMETERVALUE(1000.0)),.T.,.PARAMETER.); +#166= IFCCOMPOSITECURVESEGMENT(.CONTINUOUS.,.T.,#165); +#167= IFCCOMPOSITECURVE((#154,#160,#166),.U.); +#168= IFCARBITRARYCLOSEDPROFILEDEF(.AREA.,'PartialEllipse',#167); +#169= IFCMATERIALPROFILE('PartialEllipse',$,#50,#168,$,$); +#171= IFCMATERIALPROFILESET('PartialEllipse',$,(#169),$); +#172= IFCRELASSOCIATESMATERIAL('2OfhB1Dcz2cAdV$CDh9PHV',$,'MatAssoc','Material Associates',(#173),#171); +#173= IFCCOLUMNTYPE('0dtemVu1P2682BcO3CPWAy',$,'PartialEllipse',$,$,$,$,$,$,.COLUMN.); +#174= IFCRELDEFINESBYTYPE('0rNx6sqCH2mOt1cWOT6zSU',$,'NameNotAssigned',$,(#180),#173); +#175= IFCMATERIALPROFILESETUSAGE(#171,5,$); +#176= IFCRELASSOCIATESMATERIAL('3bTNkVsf9099xrALHA6WhF',$,'MatAssoc','Material Associates',(#180),#175); +#177= IFCCARTESIANPOINT((5000.0,0.0,0.0)); +#178= IFCAXIS2PLACEMENT3D(#177,$,$); +#179= IFCLOCALPLACEMENT(#12,#178); +#180= IFCCOLUMN('1JCvykjKH71R7_uck4n6hN',$,'PartialEllipse',$,$,#179,#186,$,$); +#181= IFCCARTESIANPOINT((0.0,0.0,2000.0)); +#182= IFCPOLYLINE((#15,#181)); +#183= IFCSHAPEREPRESENTATION(#80,'Axis','Curve3D',(#182)); +#184= IFCEXTRUDEDAREASOLID(#168,$,#83,2000.0); +#185= IFCSHAPEREPRESENTATION(#32,'Body','SweptSolid',(#184)); +#186= IFCPRODUCTDEFINITIONSHAPE($,$,(#183,#185)); +ENDSEC; + +END-ISO-10303-21; diff --git a/Examples/Basic context information/DocExample.xml b/Examples/Basic context information/DocExample.xml index 366e08cdf..e75781efc 100644 --- a/Examples/Basic context information/DocExample.xml +++ b/Examples/Basic context information/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Basic geometric shape/DocExample.xml b/Examples/Basic geometric shape/DocExample.xml index 231c21789..ced955321 100644 --- a/Examples/Basic geometric shape/DocExample.xml +++ b/Examples/Basic geometric shape/DocExample.xml @@ -3,6 +3,7 @@ + diff --git a/Examples/Basic geometric shape/Examples/Extruded solid/DocExample.xml b/Examples/Basic geometric shape/Examples/Extruded solid/DocExample.xml index 393084c5f..c1b01f582 100644 --- a/Examples/Basic geometric shape/Examples/Extruded solid/DocExample.xml +++ b/Examples/Basic geometric shape/Examples/Extruded solid/DocExample.xml @@ -6,6 +6,7 @@ + diff --git a/Examples/Building element configuration/Examples/Wall with opening and window/File.ifc b/Examples/Building element configuration/Examples/Wall with opening and window/File.ifc index 3bcf5bb23..77f161a30 100644 --- a/Examples/Building element configuration/Examples/Wall with opening and window/File.ifc +++ b/Examples/Building element configuration/Examples/Wall with opening and window/File.ifc @@ -81,7 +81,7 @@ DATA; #44 = IFCRELCONTAINEDINSPATIALSTRUCTURE('0w_L$jTK98v8wOzKFGjTuo', #2, 'Default Building', 'Contents of Building Storey', (#45, #102), #38); /* the wall itself ----------------------------------------------------------------------------- */ -#45 = IFCWALLSTANDARDCASE('3ZYW59sxj8lei475l7EhLU', #2, 'Wall for Test Example', 'Description of Wall', $, #46, #48, $, $); +#45 = IFCWALL('3ZYW59sxj8lei475l7EhLU', #2, 'Wall for Test Example', 'Description of Wall', $, #46, #48, $, $); #46 = IFCLOCALPLACEMENT(#39, #47); /* no rotation - z and x axes set to '$' are therefore identical to "world coordinate system" -- */ #47 = IFCAXIS2PLACEMENT3D(#24, $, $); diff --git a/Examples/Building element elemented case/Examples/Slab elemented case/DocExample.xml b/Examples/Building element elemented case/Examples/Slab elemented case/DocExample.xml index 1e9a96d84..f796d8971 100644 --- a/Examples/Building element elemented case/Examples/Slab elemented case/DocExample.xml +++ b/Examples/Building element elemented case/Examples/Slab elemented case/DocExample.xml @@ -1,3 +1,3 @@  - + diff --git a/Examples/Building element elemented case/Examples/Wall elemented case/DocExample.xml b/Examples/Building element elemented case/Examples/Wall elemented case/DocExample.xml index 1bfa8c29b..e88a776e9 100644 --- a/Examples/Building element elemented case/Examples/Wall elemented case/DocExample.xml +++ b/Examples/Building element elemented case/Examples/Wall elemented case/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Building element elemented case/Examples/Wall elemented case/File.ifc b/Examples/Building element elemented case/Examples/Wall elemented case/File.ifc index a9ce62acf..1ec45d5bb 100644 --- a/Examples/Building element elemented case/Examples/Wall elemented case/File.ifc +++ b/Examples/Building element elemented case/Examples/Wall elemented case/File.ifc @@ -173,7 +173,7 @@ DATA; #122= IFCRELDEFINESBYTYPE('0b7wBKEN98nvtgUGavkVDu',$,$,$,(#123),#49); /* The wall occurrence is an instance of the wall type, and aggregates instantiations of all components */ -#123= IFCWALLELEMENTEDCASE('2ucZRLBGP4uxZW$9i1VAZ8',$,'Wall #1',$,$,#153,#154,$,.MOVABLE.); +#123= IFCWALL('2ucZRLBGP4uxZW$9i1VAZ8',$,'Wall #1',$,$,#153,#154,$,.MOVABLE.); #153= IFCLOCALPLACEMENT(#50,#159); #154= IFCPRODUCTDEFINITIONSHAPE($,$,(#160,#161)); #159= IFCAXIS2PLACEMENT3D(#162,#163,#164); diff --git a/Examples/Building element standard case/Examples/Beam extruded solid/DocExample.xml b/Examples/Building element standard case/Examples/Beam extruded solid/DocExample.xml index 443f32304..0cc9c205a 100644 --- a/Examples/Building element standard case/Examples/Beam extruded solid/DocExample.xml +++ b/Examples/Building element standard case/Examples/Beam extruded solid/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Building element standard case/Examples/Beam revolved solid/DocExample.xml b/Examples/Building element standard case/Examples/Beam revolved solid/DocExample.xml index 34743b630..338892daf 100644 --- a/Examples/Building element standard case/Examples/Beam revolved solid/DocExample.xml +++ b/Examples/Building element standard case/Examples/Beam revolved solid/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Building element standard case/Examples/Beam revolved solid/File.ifc b/Examples/Building element standard case/Examples/Beam revolved solid/File.ifc index 0f22539bb..091b6889b 100644 --- a/Examples/Building element standard case/Examples/Beam revolved solid/File.ifc +++ b/Examples/Building element standard case/Examples/Beam revolved solid/File.ifc @@ -85,7 +85,7 @@ DATA; /* defines the beam as a standard case element with revolved solid geometry */ /* the profile set usage indicated the cardinal point */ /* ---------------------------------------------------------------------------------------------- */ -#70= IFCBEAMSTANDARDCASE('3v1174zor6w9secwnbuYk1',#6,$,$,$,#73,#90,$,$); +#70= IFCBEAM('3v1174zor6w9secwnbuYk1',#6,$,$,$,#73,#90,$,$); #71= IFCMATERIALPROFILESETUSAGE(#66,5,$); #72= IFCRELASSOCIATESMATERIAL('09XSzlrVbBaPJrUqRqW_4D',#6,'MatAssoc','Material Associates',(#70),#71); #73= IFCLOCALPLACEMENT($,#74); diff --git a/Examples/Building element standard case/Examples/Beam standard case/DocExample.xml b/Examples/Building element standard case/Examples/Beam standard case/DocExample.xml index be406a931..ccd79d89e 100644 --- a/Examples/Building element standard case/Examples/Beam standard case/DocExample.xml +++ b/Examples/Building element standard case/Examples/Beam standard case/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Building element standard case/Examples/Beam standard case/File.ifc b/Examples/Building element standard case/Examples/Beam standard case/File.ifc index c7bee83bb..45d2c60e5 100644 --- a/Examples/Building element standard case/Examples/Beam standard case/File.ifc +++ b/Examples/Building element standard case/Examples/Beam standard case/File.ifc @@ -45,7 +45,7 @@ DATA; /* beam A-1 - beam axis along global x axis -------------------------------- */ /* cardinal point = 1 - bottom left */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1000= IFCBEAMSTANDARDCASE('0juf4qyggSI8rxA20Qwnsj',$,'A-1','IPE220','Beam',#1001,#1010,'A-1',$); +#1000= IFCBEAM('0juf4qyggSI8rxA20Qwnsj',$,'A-1','IPE220','Beam',#1001,#1010,'A-1',$); #1001= IFCLOCALPLACEMENT(#100025,#1002); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -76,7 +76,7 @@ DATA; /* beam A-2 - beam axis along global x axis -------------------------------- */ /* cardinal point = 2 - bottom center */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1100= IFCBEAMSTANDARDCASE('0juf4qyggSI8rxA20sznsj',$,'A-2','IPE220','Beam',#1101,#1110,'A-2',$); +#1100= IFCBEAM('0juf4qyggSI8rxA20sznsj',$,'A-2','IPE220','Beam',#1101,#1110,'A-2',$); #1101= IFCLOCALPLACEMENT(#100025,#1102); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -107,7 +107,7 @@ DATA; /* beam A-3 - beam axis along global x axis -------------------------------- */ /* cardinal point = 3 - bottom right */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1200= IFCBEAMSTANDARDCASE('0juf4qyggSI8s4A20sznsj',$,'A-3','IPE220','Beam',#1201,#1210,'A-3',$); +#1200= IFCBEAM('0juf4qyggSI8s4A20sznsj',$,'A-3','IPE220','Beam',#1201,#1210,'A-3',$); #1201= IFCLOCALPLACEMENT(#100025,#1202); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -138,7 +138,7 @@ DATA; /* beam A-4 - beam axis along global x axis -------------------------------- */ /* cardinal point = 3 - bottom right */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1300= IFCBEAMSTANDARDCASE('0juf4qyggSI8s4A20sznw6',$,'A-4','IPE220','Beam',#1301,#1310,'A-4',$); +#1300= IFCBEAM('0juf4qyggSI8s4A20sznw6',$,'A-4','IPE220','Beam',#1301,#1310,'A-4',$); #1301= IFCLOCALPLACEMENT(#100025,#1302); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -169,7 +169,7 @@ DATA; /* beam A-5 - beam axis along global x axis -------------------------------- */ /* cardinal point = 5 - mid-depth center */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1400= IFCBEAMSTANDARDCASE('0juf4qyggSI8rxA20Qwnab',$,'A-5','IPE220','Beam',#1401,#1410,'A-5',$); +#1400= IFCBEAM('0juf4qyggSI8rxA20Qwnab',$,'A-5','IPE220','Beam',#1401,#1410,'A-5',$); #1401= IFCLOCALPLACEMENT(#100025,#1402); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -200,7 +200,7 @@ DATA; /* beam A-6 - beam axis along global x axis -------------------------------- */ /* cardinal point = 6 - mid-depth right */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1500= IFCBEAMSTANDARDCASE('0juf4qyggSI8rxA20Qwng1',$,'A-6','IPE220','Beam',#1501,#1510,'A-6',$); +#1500= IFCBEAM('0juf4qyggSI8rxA20Qwng1',$,'A-6','IPE220','Beam',#1501,#1510,'A-6',$); #1501= IFCLOCALPLACEMENT(#100025,#1502); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -231,7 +231,7 @@ DATA; /* beam A-7 - beam axis along global x axis -------------------------------- */ /* cardinal point = 7 - top left */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1600= IFCBEAMSTANDARDCASE('0juf4qyggSI8rxA20Qwn3s',$,'A-7','IPE220','Beam',#1601,#1610,'A-7',$); +#1600= IFCBEAM('0juf4qyggSI8rxA20Qwn3s',$,'A-7','IPE220','Beam',#1601,#1610,'A-7',$); #1601= IFCLOCALPLACEMENT(#100025,#1602); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -262,7 +262,7 @@ DATA; /* beam A-8 - beam axis along global x axis -------------------------------- */ /* cardinal point = 8 - top center */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1700= IFCBEAMSTANDARDCASE('0juf4qyggSI8rxA20Qwnlq',$,'A-8','IPE220','Beam',#1701,#1710,'A-8',$); +#1700= IFCBEAM('0juf4qyggSI8rxA20Qwnlq',$,'A-8','IPE220','Beam',#1701,#1710,'A-8',$); #1701= IFCLOCALPLACEMENT(#100025,#1702); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -293,7 +293,7 @@ DATA; /* beam A-9 - beam axis along global x axis -------------------------------- */ /* cardinal point = 9 - top right */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#1800= IFCBEAMSTANDARDCASE('0juf4qyggSI8s4A20sznrt',$,'A-9','IPE220','Beam',#1801,#1810,'A-9',$); +#1800= IFCBEAM('0juf4qyggSI8s4A20sznrt',$,'A-9','IPE220','Beam',#1801,#1810,'A-9',$); #1801= IFCLOCALPLACEMENT(#100025,#1802); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -325,7 +325,7 @@ DATA; /* beam B-1 - beam axis along global x axis -------------------------------- */ /* cardinal point = 1 - bottom left */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2000=IFCBEAMSTANDARDCASE('3QbcAsYoB7Hvx$4VHzijYi',$,'B-1','1/2IPE300','Beam',#2001,#2010,'B-1',$); +#2000=IFCBEAM('3QbcAsYoB7Hvx$4VHzijYi',$,'B-1','1/2IPE300','Beam',#2001,#2010,'B-1',$); #2001=IFCLOCALPLACEMENT(#100025,#2002); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -355,7 +355,7 @@ DATA; /* beam B-2 - beam axis along global x axis -------------------------------- */ /* cardinal point = 2 - bottom center */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2100=IFCBEAMSTANDARDCASE('3Qb5gsYoB7Hvx$4VHzijYi',$,'B-2','1/2IPE300','Beam',#2101,#2110,'B-2',$); +#2100=IFCBEAM('3Qb5gsYoB7Hvx$4VHzijYi',$,'B-2','1/2IPE300','Beam',#2101,#2110,'B-2',$); #2101=IFCLOCALPLACEMENT(#100025,#2102); /* set local placement so that the z-axis is co-linear to the beam axis ---- */ /* the y-axis (cross product of x & z axis) is up direction of profile ----- */ @@ -385,7 +385,7 @@ DATA; /* beam B-3 - beam axis along global x axis -------------------------------- */ /* cardinal point = 3 - bottom right */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2200=IFCBEAMSTANDARDCASE('3QbcAsYsg7Hvx$4VHzijYi',$,'B-3','1/2IPE300','Beam',#2201,#2210,'B-3',$); +#2200=IFCBEAM('3QbcAsYsg7Hvx$4VHzijYi',$,'B-3','1/2IPE300','Beam',#2201,#2210,'B-3',$); #2201=IFCLOCALPLACEMENT(#100025,#2202); #2202=IFCAXIS2PLACEMENT3D(#2203,#2204,#2205); #2203=IFCCARTESIANPOINT((0.,3000.,1500.)); @@ -413,7 +413,7 @@ DATA; /* beam B-4 - beam axis along global x axis -------------------------------- */ /* cardinal point = 4 - mid-depth left */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2300=IFCBEAMSTANDARDCASE('3QbcAsYsg7Hvx$4VHzijGT',$,'B-4','1/2IPE300','Beam',#2301,#2310,'B-4',$); +#2300=IFCBEAM('3QbcAsYsg7Hvx$4VHzijGT',$,'B-4','1/2IPE300','Beam',#2301,#2310,'B-4',$); #2301=IFCLOCALPLACEMENT(#100025,#2302); #2302=IFCAXIS2PLACEMENT3D(#2303,#2304,#2305); #2303=IFCCARTESIANPOINT((0.,4500.,1500.)); @@ -441,7 +441,7 @@ DATA; /* beam B-5 - beam axis along global x axis -------------------------------- */ /* cardinal point = 5 - mid-depth centre */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2400=IFCBEAMSTANDARDCASE('3QbcAsYsg7Hvx$4VHzijdF',$,'B-5','1/2IPE300','Beam',#2401,#2410,'B-5',$); +#2400=IFCBEAM('3QbcAsYsg7Hvx$4VHzijdF',$,'B-5','1/2IPE300','Beam',#2401,#2410,'B-5',$); #2401=IFCLOCALPLACEMENT(#100025,#2402); #2402=IFCAXIS2PLACEMENT3D(#2403,#2404,#2405); #2403=IFCCARTESIANPOINT((0.,6000.,1500.)); @@ -469,7 +469,7 @@ DATA; /* beam B-6 - beam axis along global x axis -------------------------------- */ /* cardinal point = 6 - mid-depth right */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2500=IFCBEAMSTANDARDCASE('3QbcAsYsg7Hvx$4VHzij3V',$,'B-6','1/2IPE300','Beam',#2501,#2510,'B-6',$); +#2500=IFCBEAM('3QbcAsYsg7Hvx$4VHzij3V',$,'B-6','1/2IPE300','Beam',#2501,#2510,'B-6',$); #2501=IFCLOCALPLACEMENT(#100025,#2502); #2502=IFCAXIS2PLACEMENT3D(#2503,#2504,#2505); #2503=IFCCARTESIANPOINT((0.,7500.,1500.)); @@ -497,7 +497,7 @@ DATA; /* beam B-7 - beam axis along global x axis -------------------------------- */ /* cardinal point = 7 - top left */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2600=IFCBEAMSTANDARDCASE('3QbcAsYsg7Hvx$4VHzij71',$,'B-7','1/2IPE300','Beam',#2601,#2610,'B-7',$); +#2600=IFCBEAM('3QbcAsYsg7Hvx$4VHzij71',$,'B-7','1/2IPE300','Beam',#2601,#2610,'B-7',$); #2601=IFCLOCALPLACEMENT(#100025,#2602); #2602=IFCAXIS2PLACEMENT3D(#2603,#2604,#2605); #2603=IFCCARTESIANPOINT((0.,9000.,1500.)); @@ -525,7 +525,7 @@ DATA; /* beam B-8 - beam axis along global x axis -------------------------------- */ /* cardinal point = 3 - top center */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2700=IFCBEAMSTANDARDCASE('3QbcAsYsg7Hvx$4VHzijvb',$,'B-8','1/2IPE300','Beam',#2701,#2710,'B-8',$); +#2700=IFCBEAM('3QbcAsYsg7Hvx$4VHzijvb',$,'B-8','1/2IPE300','Beam',#2701,#2710,'B-8',$); #2701=IFCLOCALPLACEMENT(#100025,#2702); #2702=IFCAXIS2PLACEMENT3D(#2703,#2704,#2705); #2703=IFCCARTESIANPOINT((0.,10500.,1500.)); @@ -553,7 +553,7 @@ DATA; /* beam B-9 - beam axis along global x axis -------------------------------- */ /* cardinal point = 9 - top right */ /* enhanced definitions intruduced in IFC2x4 - IfcBeamStandardCase --------- */ -#2800=IFCBEAMSTANDARDCASE('3QbcAsYsg7Hvx$4VHzijp1',$,'B-9','1/2IPE300','Beam',#2801,#2810,'B-9',$); +#2800=IFCBEAM('3QbcAsYsg7Hvx$4VHzijp1',$,'B-9','1/2IPE300','Beam',#2801,#2810,'B-9',$); #2801=IFCLOCALPLACEMENT(#100025,#2802); #2802=IFCAXIS2PLACEMENT3D(#2803,#2804,#2805); #2803=IFCCARTESIANPOINT((0.,12000.,1500.)); diff --git a/Examples/Building element standard case/Examples/Column extruded solid/DocExample.xml b/Examples/Building element standard case/Examples/Column extruded solid/DocExample.xml index 3aaa395d1..000224a55 100644 --- a/Examples/Building element standard case/Examples/Column extruded solid/DocExample.xml +++ b/Examples/Building element standard case/Examples/Column extruded solid/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Building element standard case/Examples/Column extruded solid/File.ifc b/Examples/Building element standard case/Examples/Column extruded solid/File.ifc index 270be33ce..acc555e03 100644 --- a/Examples/Building element standard case/Examples/Column extruded solid/File.ifc +++ b/Examples/Building element standard case/Examples/Column extruded solid/File.ifc @@ -44,7 +44,7 @@ DATA; #207= IFCCOLUMNTYPE('3qJDCKcPj1tgEHrIL1MUed',#56,'IPE200',$,$,$,$,$,$,.COLUMN.); #208= IFCRELDEFINESBYTYPE('0QSJIMj99DcOpmktgECZT7',#56,$,$,(#210),#207); #209= IFCRELDECLARES('2RA6m5trr5aOD9rZCp3GjP',#56,$,$,#100,(#207)); -#210= IFCCOLUMNSTANDARDCASE('3S1GK_wA565RDoiWQEJc_l',#56,'IPE200',$,$,#211,#224,$,$); +#210= IFCCOLUMN('3S1GK_wA565RDoiWQEJc_l',#56,'IPE200',$,$,#211,#224,$,$); #211= IFCLOCALPLACEMENT($,#212); #212= IFCAXIS2PLACEMENT3D(#2,#214,#213); #213= IFCDIRECTION((0.0,-1.0,0.0)); diff --git a/Examples/Building element standard case/Examples/Element standard case/DocExample.xml b/Examples/Building element standard case/Examples/Element standard case/DocExample.xml index 1757f6794..d2b94fcca 100644 --- a/Examples/Building element standard case/Examples/Element standard case/DocExample.xml +++ b/Examples/Building element standard case/Examples/Element standard case/DocExample.xml @@ -1,3 +1,3 @@  - + diff --git a/Examples/Building element standard case/Examples/Element standard case/File.ifc b/Examples/Building element standard case/Examples/Element standard case/File.ifc index 790e750bd..3ee29d4a8 100644 --- a/Examples/Building element standard case/Examples/Element standard case/File.ifc +++ b/Examples/Building element standard case/Examples/Element standard case/File.ifc @@ -113,7 +113,7 @@ DATA; #133= IFCPOLYLINE((#131,#132)); #134= IFCPRODUCTDEFINITIONSHAPE($,$,(#136,#286)); #136= IFCSHAPEREPRESENTATION(#40,'Axis','Curve2D',(#133)); -#139= IFCWALLSTANDARDCASE('1T_lQ6m$P4qR0KcAT3YY$I',$,'Wall #1',$,$,#144,#165,$,.NOTDEFINED.); +#139= IFCWALL('1T_lQ6m$P4qR0KcAT3YY$I',$,'Wall #1',$,$,#144,#165,$,.NOTDEFINED.); #140= IFCRELCONNECTSELEMENTS('1RLsKjckj3fQdtZ0vyuAxn',$,$,$,$,#103,#139); #141= IFCCARTESIANPOINT((0.,0.,0.)); #142= IFCDIRECTION((0.,0.,1.)); @@ -145,7 +145,7 @@ DATA; #182= IFCPOLYLINE((#180,#181)); #183= IFCPRODUCTDEFINITIONSHAPE($,$,(#185,#337)); #185= IFCSHAPEREPRESENTATION(#40,'Axis','Curve2D',(#182)); -#188= IFCWALLSTANDARDCASE('2OY2$2dm1A$ftGfWeKdPP2',$,'Wall #2',$,$,#194,#201,$,.NOTDEFINED.); +#188= IFCWALL('2OY2$2dm1A$ftGfWeKdPP2',$,'Wall #2',$,$,#194,#201,$,.NOTDEFINED.); #189= IFCRELCONNECTSELEMENTS('3U6qRI2g1DrOShTLfYzu5s',$,$,$,$,#171,#188); #190= IFCRELCONNECTSPATHELEMENTS('3Yt2yKZ0PC78sihBJOqhfw',$,$,$,$,#139,#188,$,$,.ATSTART.,.ATEND.); #191= IFCCARTESIANPOINT((0.,144.,0.)); @@ -169,7 +169,7 @@ DATA; #218= IFCPOLYLINE((#216,#217)); #219= IFCPRODUCTDEFINITIONSHAPE($,$,(#221,#388)); #221= IFCSHAPEREPRESENTATION(#40,'Axis','Curve2D',(#218)); -#224= IFCWALLSTANDARDCASE('1Jt9WM93TEKgG1CuXB5nF1',$,'Wall #3',$,$,#230,#237,$,.NOTDEFINED.); +#224= IFCWALL('1Jt9WM93TEKgG1CuXB5nF1',$,'Wall #3',$,$,#230,#237,$,.NOTDEFINED.); #225= IFCRELCONNECTSELEMENTS('0GfQAclJ5BJQT2Hu49TMTq',$,$,$,$,#207,#224); #226= IFCRELCONNECTSPATHELEMENTS('3SYt_qPBvAfRJ7IfZwkFOq',$,$,$,$,#188,#224,$,$,.ATSTART.,.ATEND.); #227= IFCCARTESIANPOINT((192.,144.,0.)); @@ -193,7 +193,7 @@ DATA; #254= IFCPOLYLINE((#252,#253)); #255= IFCPRODUCTDEFINITIONSHAPE($,$,(#257,#439)); #257= IFCSHAPEREPRESENTATION(#40,'Axis','Curve2D',(#254)); -#260= IFCWALLSTANDARDCASE('16erZEKXDAiO2lt6Zda1bd',$,'Wall #4',$,$,#266,#273,$,.NOTDEFINED.); +#260= IFCWALL('16erZEKXDAiO2lt6Zda1bd',$,'Wall #4',$,$,#266,#273,$,.NOTDEFINED.); #261= IFCRELCONNECTSELEMENTS('1jETcAvxPDR9$Imjb25xzq',$,$,$,$,#243,#260); #262= IFCRELCONNECTSPATHELEMENTS('1j1GYReHLAMRWdpGDWIQMI',$,$,$,$,#224,#260,$,$,.ATSTART.,.ATEND.); #263= IFCCARTESIANPOINT((192.,0.,0.)); @@ -395,7 +395,7 @@ DATA; #485= IFCAXIS2PLACEMENT3D(#484,$,$); #486= IFCLOCALPLACEMENT(#78,#485); #487= IFCPRODUCTDEFINITIONSHAPE($,$,(#99,#498)); -#488= IFCSLABSTANDARDCASE('1UgW18Bgn5vhtOjA_a4Gfj',$,'Slab #1',$,$,#486,#487,$,$); +#488= IFCSLAB('1UgW18Bgn5vhtOjA_a4Gfj',$,'Slab #1',$,$,#486,#487,$,$); #489= IFCMATERIALLAYERWITHOFFSETS(#110,4.,.F.,'Body',$,$,$,.AXIS3.,(0.,0.)); #490= IFCMATERIALLAYERSET((#489),'Slab (Standard)',''); #491= IFCMATERIALLAYERSETUSAGE(#490,.AXIS1.,.POSITIVE.,0.,$); @@ -591,7 +591,7 @@ DATA; #761= IFCCARTESIANPOINT((48.,48.,0.)); #762= IFCAXIS2PLACEMENT3D(#761,#753,#754); #768= IFCOWNERHISTORY($,$,$,.DELETED.,1410987024,$,#1,0); -#777= IFCDOORSTANDARDCASE('3mlAgYRGHBfwVOt_pMmUph',$,'Door #1',$,$,#2249,#806,$,80.,32.,.NOTDEFINED.,.SINGLE_SWING_LEFT.); +#777= IFCDOOR('3mlAgYRGHBfwVOt_pMmUph',$,'Door #1',$,$,#2249,#806,$,80.,32.,.NOTDEFINED.,.SINGLE_SWING_LEFT.); #781= IFCMEASUREWITHUNIT(IFCAREAMEASURE(12.),#15); #782= IFCCONVERSIONBASEDUNIT(#14,.LENGTHUNIT.,'foot',#781); #783= IFCQUANTITYLENGTH('Width',$,#782,2.66666666666667,$); diff --git a/Examples/Building element standard case/Examples/Slab standard case/DocExample.xml b/Examples/Building element standard case/Examples/Slab standard case/DocExample.xml index 78c4291d6..3da2974fd 100644 --- a/Examples/Building element standard case/Examples/Slab standard case/DocExample.xml +++ b/Examples/Building element standard case/Examples/Slab standard case/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Building element standard case/Examples/Slab standard case/File.ifc b/Examples/Building element standard case/Examples/Slab standard case/File.ifc index 9e15b44e4..6b36a9c40 100644 --- a/Examples/Building element standard case/Examples/Slab standard case/File.ifc +++ b/Examples/Building element standard case/Examples/Slab standard case/File.ifc @@ -42,7 +42,7 @@ DATA; #205= IFCRELASSOCIATESMATERIAL('2l_enLhI93reVwnim9gXUq',#56,'MatAssoc','Material Associates',(#300),#204); #300= IFCSLABTYPE('0RSW$KKbzCZ9QaSm3GoEan',#56,'200mm Concrete',$,$,$,$,$,$,.FLOOR.); #302= IFCRELDECLARES('2Gpvcy0aXF0wUU3skbKo0s',#56,$,$,#100,(#300)); -#303= IFCSLABSTANDARDCASE('1wAj$J2Az2V8wnBiVYd3bU',#56,$,$,$,#304,#315,$,$); +#303= IFCSLAB('1wAj$J2Az2V8wnBiVYd3bU',#56,$,$,$,#304,#315,$,$); #304= IFCLOCALPLACEMENT($,#316); #305= IFCAXIS2PLACEMENT3D(#306,$,$); #306= IFCCARTESIANPOINT((0.0,0.0,-200.0)); diff --git a/Examples/Building element standard case/Examples/Wall standard case/DocExample.xml b/Examples/Building element standard case/Examples/Wall standard case/DocExample.xml index c936fc1dc..d1800ae73 100644 --- a/Examples/Building element standard case/Examples/Wall standard case/DocExample.xml +++ b/Examples/Building element standard case/Examples/Wall standard case/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Construction scheduling/Examples/Construction scheduling task/DocExample.xml b/Examples/Construction scheduling/Examples/Construction scheduling task/DocExample.xml index 6f71f4970..5da476bce 100644 --- a/Examples/Construction scheduling/Examples/Construction scheduling task/DocExample.xml +++ b/Examples/Construction scheduling/Examples/Construction scheduling task/DocExample.xml @@ -1,5 +1,5 @@  - + diff --git a/Examples/Construction scheduling/Examples/Construction scheduling task/File.ifc b/Examples/Construction scheduling/Examples/Construction scheduling task/File.ifc index f29e2c4ed..b5341e266 100644 --- a/Examples/Construction scheduling/Examples/Construction scheduling task/File.ifc +++ b/Examples/Construction scheduling/Examples/Construction scheduling task/File.ifc @@ -116,7 +116,7 @@ DATA; #289= IFCCARTESIANPOINT((0.,192.)); #290= IFCCARTESIANPOINT((0.,0.)); #291= IFCPOLYLINE((#286,#287,#288,#289,#290)); -#292= IFCSLABSTANDARDCASE('20WrgxqpbDtferON_k1P2X',#201,'Slab #1',$,$,#352,#302,$,.BASESLAB.); +#292= IFCSLAB('20WrgxqpbDtferON_k1P2X',#201,'Slab #1',$,$,#352,#302,$,.BASESLAB.); #300= IFCGEOMETRICCURVESET((#291)); #302= IFCPRODUCTDEFINITIONSHAPE($,$,(#304,#346)); #304= IFCSHAPEREPRESENTATION(#204,'FootPrint','GeometricCurveSet',(#300)); @@ -148,7 +148,7 @@ DATA; /* Standard case walls #1 with axis and body geometry and material layer set defined ----------- */ /* --------------------------------------------------------------------------------------------- */ -#356= IFCWALLSTANDARDCASE('26tmERtwL8G8UQn5BoglEh',#201,'Wall #1',$,$,#362,#379,$,.NOTDEFINED.); +#356= IFCWALL('26tmERtwL8G8UQn5BoglEh',#201,'Wall #1',$,$,#362,#379,$,.NOTDEFINED.); #358= IFCRELCONNECTSELEMENTS('2ZHJEGFvL98QhEDnQsGNrK',#201,$,$,$,#292,#356); #359= IFCCARTESIANPOINT((0.,0.,6.)); #360= IFCDIRECTION((0.,0.,1.)); @@ -180,7 +180,7 @@ DATA; /* Standard case walls #2 with axis and body geometry and material layer set defined ----------- */ /* --------------------------------------------------------------------------------------------- */ -#385= IFCWALLSTANDARDCASE('2qqyx9mIf27vQuEGt7ts8$',#201,'Wall #2',$,$,#394,#401,$,.NOTDEFINED.); +#385= IFCWALL('2qqyx9mIf27vQuEGt7ts8$',#201,'Wall #2',$,$,#394,#401,$,.NOTDEFINED.); #387= IFCRELCONNECTSELEMENTS('04lBS8dRv8082xho3Ve2L0',#201,$,$,$,#292,#385); #388= IFCRELCONNECTSPATHELEMENTS('2aU84ph_f2iwRK7mEx6APn',#201,$,$,$,#356,#385,(),(),.ATSTART.,.ATEND.); #391= IFCCARTESIANPOINT((0.,192.,6.)); @@ -207,7 +207,7 @@ DATA; /* Standard case walls #3 with axis and body geometry and material layer set defined ----------- */ /* --------------------------------------------------------------------------------------------- */ -#407= IFCWALLSTANDARDCASE('0edwXkNgP03AySQjQQlat2',#201,'Wall #3',$,$,#416,#423,$,.NOTDEFINED.); +#407= IFCWALL('0edwXkNgP03AySQjQQlat2',#201,'Wall #3',$,$,#416,#423,$,.NOTDEFINED.); #409= IFCRELCONNECTSELEMENTS('1_c3omXFD7UPfF9thiXwlM',#201,$,$,$,#292,#407); #410= IFCRELCONNECTSPATHELEMENTS('3cHo0l0vT7YecRcCZH80A_',#201,$,$,$,#385,#407,(),(),.ATSTART.,.ATEND.); #413= IFCCARTESIANPOINT((288.,192.,6.)); @@ -234,7 +234,7 @@ DATA; /* Standard case walls #4 with axis and body geometry and material layer set defined ----------- */ /* --------------------------------------------------------------------------------------------- */ -#429= IFCWALLSTANDARDCASE('27D5wuD5z86hr07xvbZLKW',#201,'Wall #4',$,$,#438,#445,$,.NOTDEFINED.); +#429= IFCWALL('27D5wuD5z86hr07xvbZLKW',#201,'Wall #4',$,$,#438,#445,$,.NOTDEFINED.); #431= IFCRELCONNECTSELEMENTS('2GwDyB_Xb1mBzqynA5hpmk',#201,$,$,$,#292,#429); #432= IFCRELCONNECTSPATHELEMENTS('0N2CJ8VSz1yx6iStYDzqLN',#201,$,$,$,#407,#429,(),(),.ATSTART.,.ATEND.); #435= IFCCARTESIANPOINT((288.,0.,6.)); diff --git a/Examples/Mapped geometric shape/DocExample.xml b/Examples/Mapped geometric shape/DocExample.xml index e55b50d84..885ec0b08 100644 --- a/Examples/Mapped geometric shape/DocExample.xml +++ b/Examples/Mapped geometric shape/DocExample.xml @@ -3,6 +3,7 @@ + diff --git a/Examples/Mapped geometric shape/Examples/Mapped shape with multiple items/DocExample.xml b/Examples/Mapped geometric shape/Examples/Mapped shape with multiple items/DocExample.xml index 8d72cda03..dab1eac76 100644 --- a/Examples/Mapped geometric shape/Examples/Mapped shape with multiple items/DocExample.xml +++ b/Examples/Mapped geometric shape/Examples/Mapped shape with multiple items/DocExample.xml @@ -6,6 +6,7 @@ + diff --git a/Examples/Mapped geometric shape/Examples/Mapped shape with transformation/DocExample.xml b/Examples/Mapped geometric shape/Examples/Mapped shape with transformation/DocExample.xml index 90e0394a5..8c78d998a 100644 --- a/Examples/Mapped geometric shape/Examples/Mapped shape with transformation/DocExample.xml +++ b/Examples/Mapped geometric shape/Examples/Mapped shape with transformation/DocExample.xml @@ -6,6 +6,7 @@ + diff --git a/Examples/Mapped geometric shape/Examples/Mapped shape without transformation/DocExample.xml b/Examples/Mapped geometric shape/Examples/Mapped shape without transformation/DocExample.xml index 6e74da368..02bdb266d 100644 --- a/Examples/Mapped geometric shape/Examples/Mapped shape without transformation/DocExample.xml +++ b/Examples/Mapped geometric shape/Examples/Mapped shape without transformation/DocExample.xml @@ -6,6 +6,7 @@ + diff --git a/Examples/Placements and GIS referencing/DocExample.xml b/Examples/Placements and GIS referencing/DocExample.xml index 09627ae3f..7a65b61df 100644 --- a/Examples/Placements and GIS referencing/DocExample.xml +++ b/Examples/Placements and GIS referencing/DocExample.xml @@ -1,7 +1,9 @@  + + diff --git a/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/DocExample.xml b/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/DocExample.xml new file mode 100644 index 000000000..920e88668 --- /dev/null +++ b/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/DocExample.xml @@ -0,0 +1,8 @@ + + + + + + + + diff --git a/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/Documentation.md b/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/Documentation.md new file mode 100644 index 000000000..3fd67d74c --- /dev/null +++ b/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/Documentation.md @@ -0,0 +1,3 @@ +This example illustrates 3D placement based on geographic referencing. + +!["Geographic referencing"](../../../../figures/examples/georeference_tessellation_gk_v1.png "Figure 1 — Geographic referencing") diff --git a/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/File.ifc b/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/File.ifc new file mode 100644 index 000000000..e24e37da0 --- /dev/null +++ b/Examples/Placements and GIS referencing/Examples/Geographic referencing GK/File.ifc @@ -0,0 +1,81 @@ +ISO-10303-21; +HEADER; + +FILE_DESCRIPTION( +/* description */ ('GeoReference'), +/* implementation level */ '2;1'); + +FILE_NAME( +/* name */ 'GeoReference.ifc', +/* time_stamp */ '2017-07-10T15:03:00', +/* author */ ('Geiger'), +/* organization */ ('KIT'), +/* preprocessor_version */ 'Handmade', +/* originating_system */ '', +/* authorisation */ 'none'); + +FILE_SCHEMA (('IFC4')); +ENDSEC; + +DATA; +/* Geographic reference*/ +#1= IFCPROJECTEDCRS('EPSG:31467','DHDN / 3-Degree Gauss-Krueger Zone 3','ETRS89',$,'Gaus-Krueger','3',#3); +#2= IFCMAPCONVERSION(#100011,#1,3458715.92,5439966.65,113.7,0.270600445976,0.962691746426,$); +#3= IFCSIUNIT(*,.LENGTHUNIT.,$,.METRE.); + +/* BuildingElementProxy */ +#149= IFCBUILDINGELEMENTPROXY('0rBru4syGxGOZb$M8kVJuS',#100005,'Geographic Position',$,$,#121,#5037,$,$); +#121= IFCLOCALPLACEMENT(#5044,#243); +#243= IFCAXIS2PLACEMENT3D(#173,#217,#218); +#173= IFCCARTESIANPOINT((0.,0.,0.)); +#217= IFCDIRECTION((0.,0.,1.)); +#218= IFCDIRECTION((1.,0.,0.)); + +#5037= IFCPRODUCTDEFINITIONSHAPE('',$,(#5038)); +#5038= IFCSHAPEREPRESENTATION(#100011,'Body','Tessellation',(#5000)); + +/* Tesselated geometry */ +#5000= IFCTRIANGULATEDFACESET(#5001,$,.T.,((1,3,2),(1,4,3),(1,5,4),(1,2,5),/*(2,3,4),(4,5,2),*/(2,3,6),(3,7,6),(3,4,7),(4,8,7),(4,5,8),(5,9,8),(5,2,9),(2,6,9),(6,7,8),(6,8,9)),$); +#5001= IFCCARTESIANPOINTLIST3D(((0.0,0.0,0.0),(-500.0,-500.0,2000.0),(500.0,-500.0,2000.0),(500.0,500.0,2000.0),(-500.0,500.0,2000.0),(-500.0,-500.0,4000.0),(500.0,-500.0,4000.0),(500.0,500.0,4000.0),(-500.0,500.0,4000.0))); + +/* BuildingStorey */ +#5043= IFCBUILDINGSTOREY('3_fv_WeK63IPclwapZa9MD',#100005,'Storey 1',$,$,#5044,$,$,.ELEMENT.,-1.6); +#5044= IFCLOCALPLACEMENT(#100025,#100040); +#5045= IFCRELCONTAINEDINSPATIALSTRUCTURE('2lLFgu3KhSGw4jMC3$Ak50',#100005,'Storey 1',$,(#149),#5043); +#5046= IFCRELAGGREGATES('3INy2PAPGPJ8Dpwhrq610o',#100005,'All stories',$,#100023,(#5043)); + +/* Person, Org, App, Project */ +#100001= IFCPERSON($,'AGeiger',$,$,$,$,$,$); +#100002= IFCORGANIZATION($,'KIT',$,$,$); +#100003= IFCPERSONANDORGANIZATION(#100001,#100002,$); +#100004= IFCAPPLICATION(#100002,'Unknown','IFCExplorer','Unknown'); +#100005= IFCOWNERHISTORY(#100003,#100004,$,.NOTDEFINED.,$,$,$,1122650864); +#100010= IFCPROJECT('01JwSt5ycUHvKFlMZUleKS',#100005,'Notch',$,$,$,$,(#100011),#100060); +#100011= IFCGEOMETRICREPRESENTATIONCONTEXT($,'Model',3,1.0E-5,#100040,$); + +/* Site */ +#100020= IFCSITE('1BPCQAtTW7GhKrUF$Sytrr',#100005,'Site',$,$,#100022,$,$,.ELEMENT.,(49,5,43,983700),(8,26,1,247300),113.7,$,$); +#100021= IFCRELAGGREGATES('2vOmTZNmbvJAJRbSGMMNrC',#100005,$,$,#100010,(#100020)); +#100022= IFCLOCALPLACEMENT($,#100040); + +/* Building */ +#100023= IFCBUILDING('0cVTYHAI3nGeTXA2X4Gxyo',#100005,'Building',$,$,#100025,$,$,.ELEMENT.,$,$,$); +#100024= IFCRELAGGREGATES('1F_GRhxz1GJgGgcJgzjvKX',#100005,$,$,#100020,(#100023)); +#100025= IFCLOCALPLACEMENT(#100022,#100040); + +/* Placement */ +#100040= IFCAXIS2PLACEMENT3D(#100041,#100044,#100042); +#100041= IFCCARTESIANPOINT((0.,0.,0.)); +#100042= IFCDIRECTION((1.,0.,0.)); +#100044= IFCDIRECTION((0.,0.,1.)); + +/* Units */ +#100060= IFCUNITASSIGNMENT((#100061,#100062,#100063,#100064)); +#100061= IFCSIUNIT(*,.LENGTHUNIT.,.MILLI.,.METRE.); +#100062= IFCSIUNIT(*,.AREAUNIT.,$,.SQUARE_METRE.); +#100063= IFCSIUNIT(*,.VOLUMEUNIT.,$,.CUBIC_METRE.); +#100064= IFCSIUNIT(*,.PLANEANGLEUNIT.,$,.RADIAN.); + +ENDSEC; + +END-ISO-10303-21; diff --git a/Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/DocExample.xml b/Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/DocExample.xml new file mode 100644 index 000000000..51b0ca1af --- /dev/null +++ b/Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/DocExample.xml @@ -0,0 +1,8 @@ + + + + + + + + diff --git a/Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/Documentation.md b/Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/Documentation.md new file mode 100644 index 000000000..73a25658d --- /dev/null +++ b/Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/Documentation.md @@ -0,0 +1,3 @@ +This example illustrates 3D placement based on geographic referencing. + +!["Geographic referencing"](../../../../figures/examples/georeference_tessellation_utm_v1.png "Figure 1 — Geographic referencing") diff --git a/Examples/Placements and GIS referencing/Examples/Geographic referencing/File.ifc b/Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/File.ifc similarity index 78% rename from Examples/Placements and GIS referencing/Examples/Geographic referencing/File.ifc rename to Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/File.ifc index 3acac392e..aa2f7c205 100644 --- a/Examples/Placements and GIS referencing/Examples/Geographic referencing/File.ifc +++ b/Examples/Placements and GIS referencing/Examples/Geographic referencing UTM/File.ifc @@ -7,7 +7,7 @@ FILE_DESCRIPTION( FILE_NAME( /* name */ 'GeoReference.ifc', -/* time_stamp */ '2014-08-22T15:03:00', +/* time_stamp */ '2017-07-10T15:03:00', /* author */ ('Geiger'), /* organization */ ('KIT'), /* preprocessor_version */ 'Handmade', @@ -20,7 +20,7 @@ ENDSEC; DATA; /* Geographic reference*/ #1= IFCPROJECTEDCRS('EPSG:25832','UTM in band 32','ETRS89',$,'UTM','UTM32',#3); -#2= IFCMAPCONVERSION(#100011,#1,458658.78,5438232.79,113.7,0.270600445976,0.962691746426,$); +#2= IFCMAPCONVERSION(#100011,#1,458657.30,5438232.25,113.7,0.270600445976,0.962691746426,$); #3= IFCSIUNIT(*,.LENGTHUNIT.,$,.METRE.); /* BuildingElementProxy */ @@ -32,23 +32,11 @@ DATA; #218= IFCDIRECTION((1.,0.,0.)); #5037= IFCPRODUCTDEFINITIONSHAPE('',$,(#5038)); -#5038= IFCSHAPEREPRESENTATION(#100011,'Body','CSG',(#5000,#6000)); +#5038= IFCSHAPEREPRESENTATION(#100011,'Body','Tessellation',(#5000)); -/* Cone geometry */ -#5000= IFCCSGSOLID(#5001); -#5001= IFCRIGHTCIRCULARCONE(#5002, 500., 150.); -#5002= IFCAXIS2PLACEMENT3D(#5003,#5005,#5004); -#5003= IFCCARTESIANPOINT((0.,0.,500.)); -#5004= IFCDIRECTION((-1.,0.,0.)); -#5005= IFCDIRECTION((0.,0.,-1.)); - -/* Cylinder geometry */ -#6000= IFCCSGSOLID(#6001); -#6001= IFCRIGHTCIRCULARCYLINDER(#6002, 500., 50.); -#6002= IFCAXIS2PLACEMENT3D(#6003,#6005,#6004); -#6003= IFCCARTESIANPOINT((0.,0.,500.)); -#6004= IFCDIRECTION((1.,0.,0.)); -#6005= IFCDIRECTION((0.,0.,1.)); +/* Tesselated geometry */ +#5000= IFCTRIANGULATEDFACESET(#5001,$,.T.,((1,3,2),(1,4,3),(1,5,4),(1,2,5),/*(2,3,4),(4,5,2),*/(2,3,6),(3,7,6),(3,4,7),(4,8,7),(4,5,8),(5,9,8),(5,2,9),(2,6,9),(6,7,8),(6,8,9)),$); +#5001= IFCCARTESIANPOINTLIST3D(((0.0,0.0,0.0),(-500.0,-500.0,2000.0),(500.0,-500.0,2000.0),(500.0,500.0,2000.0),(-500.0,500.0,2000.0),(-500.0,-500.0,4000.0),(500.0,-500.0,4000.0),(500.0,500.0,4000.0),(-500.0,500.0,4000.0))); /* BuildingStorey */ #5043= IFCBUILDINGSTOREY('3_fv_WeK63IPclwapZa9MD',#100005,'Storey 1',$,$,#5044,$,$,.ELEMENT.,-1.6); @@ -66,7 +54,7 @@ DATA; #100011= IFCGEOMETRICREPRESENTATIONCONTEXT($,'Model',3,1.0E-5,#100040,$); /* Site */ -#100020= IFCSITE('1BPCQAtTW7GhKrUF$Sytrr',#100005,'Site',$,$,#100022,$,$,.ELEMENT.,(49,5,44,124),(8,26,1,320000),113.7,$,$); +#100020= IFCSITE('1BPCQAtTW7GhKrUF$Sytrr',#100005,'Site',$,$,#100022,$,$,.ELEMENT.,(49,5,43,983700),(8,26,1,247300),113.7,$,$); #100021= IFCRELAGGREGATES('2vOmTZNmbvJAJRbSGMMNrC',#100005,$,$,#100010,(#100020)); #100022= IFCLOCALPLACEMENT($,#100040); diff --git a/Examples/Placements and GIS referencing/Examples/Geographic referencing/Documentation.md b/Examples/Placements and GIS referencing/Examples/Geographic referencing/Documentation.md deleted file mode 100644 index 22083fa9a..000000000 --- a/Examples/Placements and GIS referencing/Examples/Geographic referencing/Documentation.md +++ /dev/null @@ -1 +0,0 @@ -This example illustrates 3D placement based on geographic referencing. diff --git a/Examples/Tessellated shape with style/DocExample.xml b/Examples/Tessellated shape with style/DocExample.xml index ace0e6ed8..e8e674e58 100644 --- a/Examples/Tessellated shape with style/DocExample.xml +++ b/Examples/Tessellated shape with style/DocExample.xml @@ -1,7 +1,9 @@  + + diff --git a/Examples/Tessellated shape with style/Examples/Tessellation with image texture/File.ifc b/Examples/Tessellated shape with style/Examples/Tessellation with image texture/File.ifc index fe525b956..f9099f8a4 100644 --- a/Examples/Tessellated shape with style/Examples/Tessellation with image texture/File.ifc +++ b/Examples/Tessellated shape with style/Examples/Tessellation with image texture/File.ifc @@ -65,7 +65,7 @@ DATA; #54= IFCSURFACESTYLERENDERING(#56,$,$,$,$,$,$,$,.NOTDEFINED.); #55= IFCSURFACESTYLEWITHTEXTURES((#57)); #56= IFCCOLOURRGB($,1.,1.,1.); -#57= IFCIMAGETEXTURE(.T.,.T.,'TEXTURE',#58,$,'C:\\dev\\Constructivity\\Constructivity.Renderer.Mono\\Textures\\diagnostic.png'); +#57= IFCIMAGETEXTURE(.T.,.T.,'TEXTURE',#58,$,'texture.png'); #58= IFCCARTESIANTRANSFORMATIONOPERATOR2D(#59,$,#60,48.); #59= IFCDIRECTION((1.,0.)); #60= IFCCARTESIANPOINT((0.,0.)); diff --git a/Examples/Tessellated shape with style/Examples/Tessellation with individual colors/DocExample.xml b/Examples/Tessellated shape with style/Examples/Tessellation with individual colors/DocExample.xml index 2afed6b96..80b4d447d 100644 --- a/Examples/Tessellated shape with style/Examples/Tessellation with individual colors/DocExample.xml +++ b/Examples/Tessellated shape with style/Examples/Tessellation with individual colors/DocExample.xml @@ -6,6 +6,7 @@ + diff --git a/ModelViews/Design Transfer View/DocModelView.xml b/ModelViews/Design Transfer View/DocModelView.xml index 1235af4c8..137f7fb21 100644 --- a/ModelViews/Design Transfer View/DocModelView.xml +++ b/ModelViews/Design Transfer View/DocModelView.xml @@ -8,16 +8,16 @@ - + - The _IfcBeamStandardCase_ defines in addition that the _IfcBeamType_ should have a unique _IfcMaterialProfileSet_, that is referenced by the _IfcMaterialProfileSetUsage_ that is assigned to all occurrences of this _IfcBeamType_. + An _IfcBeam_ may be defined parametrically according to its cross section where the _IfcBeamType_ should have a unique _IfcMaterialProfileSet_, that is referenced by the _IfcMaterialProfileSetUsage_ that is assigned to all occurrences of this _IfcBeamType_. <table> <tr> <td><img src="../../figures/ifcbeamstandardcase-01.png" height="500" width="500" alt="Material profile set and usage"></td> - <td><blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates assignment of <em>IfcMaterialProfileSetUsage</em> and <em>IfcMaterialProfileSet</em> to the <em>IfcBeamStandardCase</em> as the beam occurrence and to the <em>IfcBeamType</em>. The same <em>IfcMaterialProfileSet</em> shall be shared by many occurrences of <em>IfcMaterialProfileSetUsage</em>. This relationship shall be consistent to the relationship between the <em>IfcBeamType</em> and the <em>IfcBeamStandardCase</em>.</blockquote> + <td><blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates assignment of <em>IfcMaterialProfileSetUsage</em> and <em>IfcMaterialProfileSet</em> to the <em>IfcBeam</em> as the beam occurrence and to the <em>IfcBeamType</em>. The same <em>IfcMaterialProfileSet</em> shall be shared by many occurrences of <em>IfcMaterialProfileSetUsage</em>. This relationship shall be consistent to the relationship between the <em>IfcBeamType</em> and the <em>IfcBeam</em>.</blockquote> </td> </tr> @@ -153,7 +153,7 @@ The following interpretation of dimension parameter applies for circular beams: * **Solid Position** : The _IfcSweptAreaSolid.Position_ shall exclusively been used to correspond to the cardinal point. The x/y offset of the _Position_ represents the cardinal point offset of the profile against the axis. No rotation shall be allowed. * **Profile**: all subtypes of _IfcProfileDef_ (with exception of _IfcArbitraryOpenProfileDef_) * **Profile Position** : For all single profiles, the _IfcParameterizedProfileDef.Position_ shall be NIL, or having _Location_ = 0.,0. and _RefDirection_ = 1.,0. - + The following additional constraints apply to the 'AdvancedSweptSolid' representation type: @@ -164,7 +164,7 @@ The following interpretation of dimension parameter applies for circular beams: * **Profile Position** : For all single profiles, the _IfcParameterizedProfileDef.Position_ shall be NIL, or having _Location_ = 0.,0. and _RefDirection_ = 1.,0. > NOTE&nbsp; Using _IfcExtrudedAreaSolidTapered_, or _IfcRevolvedAreaSolidTapered_ requires the use of two _IfcMaterialProfile_'s within the _IfcMaterialProfileSetUsageTapering_ assinged to the _IfcBeamStandardCase_ - + The following constraints apply to the 'Clipping' representation: @@ -182,38 +182,8 @@ Figure 1 illustrates a 'Clipping' geometric representation with use of !["clipped beam"](../../figures/ifcbeamstandardcase_clipping-01.png "Figure 1 &mdash; Beam body clipping") - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + @@ -221,10 +191,6 @@ Figure 1 illustrates a 'Clipping' geometric representation with use of The material of the _IfcBeamType_ is defined by the _IfcMaterialProfileSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. -> NOTE&nbsp; It is illegal to assign an _IfcMaterial_ to an _IfcBeamType_, if there is at least one occurrence of _IfcBeamStandardCase_ for this type. - -The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ (see material use definition above). The _IfcMaterialProfile_ refers to the subtype of _IfcProfileDef_ that is the common profile for all beam occurrence, if used. It is only applicable if the _IfcBeamType_ has only occurrences of type _IfcBeamStandardCase_ (see definition of _IfcBeamStandardCase_ for further information). - > NOTE&nbsp; The attribute _ProfileName_ of the _IfcProfileDef_ subtype, referenced in _IfcMaterialProfile_ should contain a standardized profile name according to local standards. However, an additional geometric representation of the profile is necessary (such as _IfcExtrudedAreaSolid_). An importing application is allowed to check for the existence of the profile name: in case of identifying it as a standardized name, the corresponding profile geometry and possibly other cross sectional properties can be read from a library. Otherwise the geometric representation and possible non geometric _IfcProfileProperties_ have to be used. @@ -274,12 +240,12 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - + - The _IfcColumnStandardCase_ defines in addition that the _IfcColumnType_ should have a unique _IfcMaterialProfileSet_, that is referenced by the _IfcMaterialProfileSetUsage_ assigned to all occurrences of this _IfcColumnType_. Composite profile columns can be represented by refering to several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ that is referenced from the _IfcMaterialProfileSetUsage_. + An _IfcColumn_ may be defined parametrically according to its cross section where the _IfcColumnType_ should have a unique _IfcMaterialProfileSet_, that is referenced by the _IfcMaterialProfileSetUsage_ assigned to all occurrences of this _IfcColumnType_. Composite profile columns can be represented by refering to several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ that is referenced from the _IfcMaterialProfileSetUsage_. -Figure 1 illustrates assignment of _IfcMaterialProfileSetUsage_ and _IfcMaterialProfileSet_ to the _IfcColumnStandardCase_ as the column occurrence and to the _IfcColumnType_. The same _IfcMaterialProfileSet_ shall be shared by many occurrences of _IfcMaterialProfileSetUsage_. This relationship shall be consistent to the relationship between the _IfcColumnType_ and the _IfcColumnStandardCase_. +Figure 1 illustrates assignment of _IfcMaterialProfileSetUsage_ and _IfcMaterialProfileSet_ to the _IfcColumn_ as the column occurrence and to the _IfcColumnType_. The same _IfcMaterialProfileSet_ shall be shared by many occurrences of _IfcMaterialProfileSetUsage_. This relationship shall be consistent to the relationship between the _IfcColumnType_ and the _IfcColumn_. !["Material profile set and usage"](../../figures/ifccolumnstandardcase-01.png "Figure 1 &mdash; Column profile usage") @@ -389,7 +355,7 @@ The following interpretation of dimension parameter applies for circular columns * **Solid**: _IfcSurfaceCurveSweptAreaSolid_, _IfcFixedReferenceSweptAreaSolid_, shall be supported. * **Profile**: all subtypes of _IfcProfileDef_ (with exception of _IfcArbitraryOpenProfileDef_) * **Profile Position** : For all single profiles, the _IfcParameterizedProfileDef.Position_ shall be NIL, or having _Location_ = 0.,0. and _RefDirection_ = 1.,0. - + The following additional constraints apply to the 'AdvancedSweptSolid' representation type: @@ -399,7 +365,7 @@ The following interpretation of dimension parameter applies for circular columns * **Profile Position** : For all single profiles, the _IfcParameterizedProfileDef.Position_ shall be NIL, or having _Location_ = 0.,0. and _RefDirection_ = 1.,0. > NOTE&nbsp; Using _IfcExtrudedAreaSolidTapered_, or _IfcRevolvedAreaSolidTapered_ requires the use of two _IfcMaterialProfile_'s within the _IfcMaterialProfileSetUsageTapering_ assinged to the _IfcColumnStandardCase_ - + The following constraints apply to the 'Clipping' representation: @@ -416,38 +382,8 @@ Figure 1 illustrates a 'Clipping' geometric representation with use of !["clipped column"](../../figures/ifccolumnstandardcase_clipping-01.png "Figure 1 &mdash; Column body clipping") - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + @@ -455,10 +391,6 @@ Figure 1 illustrates a 'Clipping' geometric representation with use of The material of the _IfcColumnType_ is defined by the _IfcMaterialProfileSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. -> NOTE&nbsp; It is illegal to assign an _IfcMaterial_ to an _IfcColumnType_, if there is at least one occurrences of _IfcColumnStandardCase_ for this type. - -The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ (see material use definition above). The _IfcMaterialProfile_ refers to the subtype of _IfcProfileDef_ that is the common profile for all column occurrence, if used. It is only applicable if the _IfcColumnType_ has only occurrences of type _IfcColumnStandardCase_ (see definition of _IfcColumnStandardCase_ for further information). - > NOTE&nbsp; The attribute _ProfileName_ of the _IfcProfileDef_ subtype, referenced in _IfcMaterialProfile_ should contain a standardized profile name according to local standards. However, an additional geometric representation of the profile is necessary (e.g. as _IfcExtrudedAreaSolid_). An importing application is allowed to check for the existence of the profile name: in case of identifying it as a standardized name, the corresponding profile geometry and possibly other cross sectional properties can be read from a library. Otherwise the geometric representation and possible non geometric _IfcProfileProperties_ have to be used. @@ -515,7 +447,7 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - + The door profile is represented by a three-dimensional closed curve within a particular shape representation. The profile is used to apply the parameter of the parametric door representation. The following attribute values for the _IfcShapeRepresentation_ holding this geometric representation shall be used: @@ -585,7 +517,7 @@ height. Distance to the centre line of the transom.</li> - + @@ -823,10 +755,10 @@ The material is attached by the _RelatingMaterial_ attribute on the [IfcRelAssoc - + - Figure 1 illustrates assignment of _IfcMaterialProfileSetUsage_ and _IfcMaterialProfileSet_ to the _IfcMemberStandardCase_ as the member occurrence and to the _IfcMemberType_. The same _IfcMaterialProfileSet_ shall be shared by many occurrences of _IfcMaterialProfileSetUsage_. This relationship shall be consistent to the relationship between the _IfcMemberType_ and the _IfcMemberStandardCase_. + Figure 1 illustrates assignment of _IfcMaterialProfileSetUsage_ and _IfcMaterialProfileSet_ to the _IfcMember_ as the member occurrence and to the _IfcMemberType_. The same _IfcMaterialProfileSet_ shall be shared by many occurrences of _IfcMaterialProfileSetUsage_. This relationship shall be consistent to the relationship between the _IfcMemberType_ and the _IfcMember_. !["Material profile set and usage"](../../figures/ifcmemberstandardcase-01.png "Figure 1 &mdash; Member profile usage") @@ -834,7 +766,7 @@ Figure 2 illustrates assignment of a composite profile by using _IfcCompositePro !["Material profile set and usage"](../../figures/ifcmemberstandardcase-02.png "Figure 2 &mdash; Member composite profiles") -The material of the _IfcMemberStandardCase_ is defined by _IfcMaterialProfileSetUsage_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. Composite profile members can be represented by refering to several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ that is referenced from the _IfcMaterialProfileSetUsage_. +The material of the _IfcMember_ is defined by _IfcMaterialProfileSetUsage_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. Composite profile members can be represented by refering to several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ that is referenced from the _IfcMaterialProfileSetUsage_. Material information can also be given at the _IfcMemberType_, defining the common attribute data for all occurrences of the same type. It is then accessible by the inverse _IsDefinedBy_ relationship pointing to _IfcMemberType.HasAssociations_ and via _IfcRelAssociatesMaterial.RelatingMaterial_. See **Type Use Definition** for additional agreements for standard members. @@ -934,7 +866,7 @@ The following interpretation of dimension parameter applies for circular members * **Profile Position** : For all single profiles, the _IfcParameterizedProfileDef.Position_ shall be NIL, or having _Location_ = 0.,0. and _RefDirection_ = 1.,0. > NOTE&nbsp; Using _IfcExtrudedAreaSolidTapered_, or _IfcRevolvedAreaSolidTapered_ requires the use of two _IfcMaterialProfile_'s within the _IfcMaterialProfileSetUsageTapering_ assinged to the _IfcMemberStandardCase_ - + The following additional constraints apply to the 'AdvancedSweptSolid' representation type: @@ -944,7 +876,7 @@ The following interpretation of dimension parameter applies for circular members * **Profile Position** : For all single profiles, the _IfcParameterizedProfileDef.Position_ shall be NIL, or having _Location_ = 0.,0. and _RefDirection_ = 1.,0. > NOTE&nbsp; Using _IfcExtrudedAreaSolidTapered_, or _IfcRevolvedAreaSolidTapered_ requires the use of two _IfcMaterialProfile_'s within the _IfcMaterialProfileSetUsageTapering_ assinged to the _IfcMemberStandardCase_ - + The following constraints apply to the advanced representation: @@ -960,38 +892,8 @@ Figure 1 illustrates an advanced geometric representation with use of _IfcBoolea !["clipped beam"](../../figures/ifcbeamstandardcase_clipping-01.png "Figure 1 &mdash; Member body clipping") - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + @@ -999,10 +901,6 @@ Figure 1 illustrates an advanced geometric representation with use of _IfcBoolea The material of the _IfcMemberType_ is defined by the _IfcMaterialProfileSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. -> NOTE&nbsp; It is illegal to assign an _IfcMaterial_ to an _IfcMemberType_, if there is at least one occurrences of _IfcMemberStandardCase_ for this type. - -The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ (see material use definition above). The _IfcMaterialProfile_ refers to the subtype of _IfcProfileDef_ that is the common profile for all member occurrence, if used. It is only applicable if the _IfcMemberType_ has only occurrences of type _IfcMemberStandardCase_ (see definition of _IfcMemberStandardCase_ for further information). - > NOTE&nbsp; The attribute _ProfileName_ of the _IfcProfileDef_ subtype, referenced in _IfcMaterialProfile_ should contain a standardized profile name according to local standards. However, an additional geometric representation of the profile is necessary (e.g. as _IfcExtrudedAreaSolid_). An importing application is allowed to check for the existence of the profile name: in case of identifying it as a standardized name, the corresponding profile geometry and possibly other cross sectional properties can be read from a library. Otherwise the geometric representation and possible non geometric _IfcProfileProperties_ have to be used. @@ -1019,10 +917,6 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - - - - @@ -1051,7 +945,7 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - + @@ -1086,7 +980,7 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - + The material of the _IfcPlateStandardCase_ is defined by _IfcMaterialLayerSetUsage_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. Multi-layer plates can be represented by refering to several _IfcMaterialLayer_'s within the _IfcMaterialLayerSet_ that is referenced from the _IfcMaterialLayerSetUsage_.&nbsp; @@ -1198,38 +1092,8 @@ As shown in Figure 106, the following conventions shall be met: </table> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + @@ -1292,6 +1156,15 @@ The shared material layer set definition is defined by assigning an _IfcMaterial + + + + + + + + + @@ -1315,47 +1188,7 @@ The shared material layer set definition is defined by assigning an _IfcMaterial - Elemented slabs extend the concepts of standard slabs with the following features, as shown in Figure 234: - -* The slab has a type (_IfcSlabType_) that indicates material layers and corresponding elements to be placed parametrically. -* The slab is decomposed into elements for part occurrences, each corresponding to parts defined at the slab type. -* The relationship _IfcRelConnectsWithRealizingElements_ indicates how parts are connected. - -!["voiding"](../../figures/ifcslabelementedcase-floor.png "Figure 1 &mdash; Slab elemented case") - - - - An elemented slab is decomposed into parts for particular components such as headers, joists, deck/subfloor, insulation, fasteners, and sealants. There must be an object corresponding to each type of part, however there may be single object instance indicating multiple placements (via mapping geometry) for each part, or multiple instances corresponding to each placement. For minimizing file size, it is recommended to use a single object with multiple placement unless there are specific connectivity relationships indicated (e.g. a duct connected to specific joists). - - - - Plywood for subfloor above. - - - Frame containing headers, joists, and possibly insulation. - - - Panels such as gypsum board for ceiling underneath. - - - - - - - - - - - - - Similar to standard slabs (_IfcSlabStandardCase_), elemented slabs are defined parametrically with _IfcMaterialLayerSetUsage_, but go into further detail, where each material layer corresponds to an aggregated part of a particular type, where such parts may be further decomposed and/or use parametric material definitions. - - - - - - - + Multi-layer slabs can be represented by refering to several _IfcMaterialLayer_'s within the _IfcMaterialLayerSet_ that is referenced from the _IfcMaterialLayerSetUsage_.&nbsp; @@ -1480,38 +1313,23 @@ Figure 2 illustrates slab material usage, where the following conventions shall </table> - - - - + + An slab may be decomposed into parts for particular components such as headers, joists, deck/subfloor, insulation, fasteners, and sealants. If a material layer set is defined, each _IfcElement_.Name shall match the corresponding _IfcMaterialLayer_.Name. - - - - - - - - - - - - - - - - - - - - - - - - + + + Plywood for subfloor above. + + + Frame containing headers, joists, and possibly insulation. + + + Panels such as gypsum board for ceiling underneath. + + - + Slab types may be described at several levels of detail to support the following slab occurrences: @@ -1531,13 +1349,7 @@ As shown in Figure 1, each material layer may be elaborated into an element (whe - The material of the _IfcSlabType_ is defined by the _IfcMaterialLayerSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. - -> NOTE&nbsp; It is illegal to assign an _IfcMaterial_ to an _IfcSlabType_, if there is at least one occurrences. of _IfcSlabStandardCase_ for this type. - -The shared material layer set definition is defined by assigning an _IfcMaterialLayerSet_ (see material use definition above). The _IfcMaterialLayer_ refers to one or several of _IfcMaterial_ that is the common for all slab occurrence, if used. It is only applicable if the _IfcSlabType_ has only occurrences of type _IfcSlabStandardCase_ (see definition of _IfcSlabStandardCase_ for further information). - -> NOTE&nbsp; Since each individual instance of _IfcSlabStandardCase_ defines its own _IfcMaterialLayerSetUsage_ including the offset from the reference plane, the same _IfcSlabType_ can be used independently of the reference plane alignment of its occurrences. + The material of the _IfcSlabType_ is defined by the _IfcMaterialLayerSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. @@ -1562,106 +1374,6 @@ The shared material layer set definition is defined by assigning an _IfcMaterial - - - > NOTE&nbsp; The 'Axis' is not used to locate the material layer set, only the subtype _IfcWallStandardCase_ provides this capability. - - - - The wall axis of the wall. - - - - - - - - Walls with equal or lower priority are connected at RelatedElement. - - - - - - - - - - - An elemented wall is decomposed into parts for particular components such as framing and panels on each side. There must be an object corresponding to each type of part, however there may be single object instance indicating multiple placements (via mapping geometry) for each part, or multiple instances corresponding to each placement. For minimizing file size, it is recommended to use a single object with multiple placement unless there are specific connectivity relationships indicated (e.g. a junction box connected to a specific stud). - - - - Frame containing studs, tracks, and possibly insulation - - - Panels on each side such as gypsum (drywall) or cement board (tile backing) with fasteners - - - - - - - - - - - - - Similar to standard walls (_IfcWallStandardCase_), elemented walls are defined parametrically with _IfcMaterialLayerSetUsage_, but go into further detail, where each material layer corresponds to an aggregated part of a particular type, where such parts may be further decomposed and/or use parametric material definitions. - - - - The wall axis is represented by a two-dimensional open curve within a particular shape representation. The wall axis is used to apply the material layer set usage parameter to the wall geometry. - -* _Axis_ - * _IfcPolyline_ having two _Points_, or _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcLine_ for the 'SweptSolid' provided as _IfcExtrudedAreaSolid_. The axis curve lies on the x/y plane and is parallel to the x-axis of the object coordinate system. - * _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcCircle_ for 'SweptSolid' provided as _IfcExtrudedAreaSolid_. The axis curve lies on the x/y plane of the object coordinate system, the tangent at the start is along the positive x-axis. - -&nbsp; - -<table cellpadding="2" cellspacing="2"> - - <tr> - - <td align="left" valign="top"><img src="../../figures/ifcwallstandard_straigthwall_01-layout1.gif" alt="straight wall axis" border="0" height="299" width="393"></td> - - <td><blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates an axis representation for a straight wall. In case of a straight wall, the set of items shall -include a single geometric representation item of type <em>IfcPolyline</em> or <em>IfcTrimmedCurve</em> with the <em>BasisCurve</em> being an <em>IfcLine</em>. The <em>IfcPolyline</em> or <em>IfcTrimmedCurve</em> shall be parallel (here in a special case co-linear) to the x-axis -of the object coordinate system. The direction shall be identical to the direction of the x-axis.</blockquote> - - </td> - </tr> - <tr> - <td width="393"><p class="figure">Figure 1 &mdash; Wall axis straight</p></td> - - <td>&nbsp;</td> - </tr> -</table> - -<table cellpadding="2" cellspacing="2"> - - <tr> - - <td align="left" valign="top"><img src="../../figures/ifcwallstandard_curvedwall_01-layout1.gif" alt="curved wall axis" border="0" height="299" width="393"></td> - - <td><blockquote class="example">EXAMPLE&nbsp; Figure 2 illustrates an axis representation for a curved wall. In case of a curved wall, the set of items shall include -a single geometric representation item of type <em>IfcTrimmedCurve</em>. The curve shall have a <em>BasisCurve</em> of type <em>IfcCircle</em>. The tangent of the <em>IfcTrimmedCurve</em> shall be parallel at start to the x-axis of the object coordinate system. The direction shall be identical to the direction of the x-axis.</blockquote> - </td></tr> - -<tr> - <td width="393"><p class="figure">Figure 2 &mdash; Wall axis curved</p></td> - <td>&nbsp;</td> - -</tr> - -</table> - - - - - - - Multi-layer walls can be represented by refering to several _IfcMaterialLayer_'s within the _IfcMaterialLayerSet_ that is referenced from the _IfcMaterialLayerSetUsage_.&nbsp; @@ -1815,32 +1527,43 @@ Figure 2 illustrates a clipping for a curved wall using an _IfcHalfSpaceSolid_ a </table> - - - - - - - - - - - - - - - - + + A wall may be decomposed into parts for particular components such as framing and panels on each side. If a material layer set is defined, each _IfcElement_.Name shall match the corresponding _IfcMaterialLayer_.Name. + + + Frame containing studs, tracks, and possibly insulation + + + Panels on each side such as gypsum (drywall) or cement board (tile backing) with fasteners + + - - + + + + + + + + > NOTE&nbsp; The 'Axis' is not used to locate the material layer set, only the subtype _IfcWallStandardCase_ provides this capability. + + + + The wall axis of the wall. + + - - + + + + + Walls with equal or lower priority are connected at RelatedElement. + + - + Wall types may be described at several levels of detail to support the following wall occurrences: @@ -1862,31 +1585,9 @@ As shown in Figure 1, each material layer may be elaborated into an element (whe The material of the _IfcWallType_ is defined by the _IfcMaterialLayerSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. -> NOTE&nbsp; It is illegal to assign an _IfcMaterial_ to an _IfcWallType_, if there is at least one occurrence of _IfcWallStandardCase_ for this type. +The shared material layer set definition is defined by assigning an _IfcMaterialLayerSet_ (see material use definition above). The _IfcMaterialLayer_ refers to one or several of _IfcMaterialLayer_ that is the common for all wall occurrence, if used. -The shared material layer set definition is defined by assigning an _IfcMaterialLayerSet_ (see material use definition above). The _IfcMaterialLayer_ refers to one or several of _IfcMaterialLayer_ that is the common for all wall occurrence, if used. It is only applicable if the _IfcWallType_ has only occurrences of type _IfcWallStandardCase_ (see definition of _IfcWallStandardCase_ for further information). - -> NOTE&nbsp; Since each individual instance of _IfcWallStandardCase_ defines its own _IfcMaterialLayerSetUsage_ including the offset from the wall axis, the same _IfcWallType_ can be used independently of the axis alignment of its occurrences. - -If a wall type is decomposed into parts, then material layers of the _IfcWallType_ may be driven by corresponding material layers and profiles of components, where _IfcMaterialLayer_.Name refers to _IfcElement_.Name. The ordering of layers is preserved by the layer set, while the thicknesses of each layer are calculated according to the material layer/profile geometry of the parts. - -The following is an example of a framed wall composition, where layers are ordered in the direction away from the viewer facing the right side of the wall: - -{ .gridtable} -<table class="gridtable"> -<tr><th>#</th><th>Layer/Element Name</th><th>Element Type</th><th>Description</th></tr> -<tr><td>1</td><td>Forward Panels</td><td><i>IfcPlate</i></td><td>Panels on right side of wall (looking in direction of axis) such as gypsum board or cement board.</td></tr> -<tr><td>2</td><td>Frame</td><td><i>IfcElementAssembly</i></td><td>Framing, which is decomposed into tracks, studs, and insulation. The thickness of the layer is determined according to the greatest extent by superimposing the material layers and profiles of all aggregated objects (in the absense of this <i>IfcElementAssembly</i> having its own <i>IfcMaterialLayerSet</i> defining sequential positioning of elements).<br> -<table class="gridtable"> -<tr><th>Element Name</th><th>Element Type</th><th>Material</th><th>Description</th></tr> -<tr><td>Track</td><td><i>IfcMemberStandardCase</i></td><td><i>IfcMaterialProfileSetUsage</i></td><td>Track at base and top of frame.</td></tr> -<tr><td>Stud</td><td><i>IfcMemberStandardCase</i></td><td><i>IfcMaterialProfileSetUsage</i></td><td>Studs, where <i>IfcMaterialProfileSetUsage</i>.ReferenceExtent defines the maximum height and <i>IfcMaterialProfileWithOffsets</i>.Offsets defines the stud spacing.</td></tr> -<tr><td>Insulation</td><td><i>IfcBuildingElementPart</i></td><td><i>IfcMaterialLayerSet</i></td><td>Insulation.</td></tr> -</table> - -</td></tr> -<tr><td>3</td><td>Reverse Panels</td><td><i>IfcPlate</i></td><td>Panels on left side of wall (looking in direction of axis) such as gypsum board or cement board.</td></tr> -</table> +If a wall type is decomposed into parts, then material layers of the _IfcWallType_ may be driven by corresponding material layers and profiles of components, where _IfcMaterialLayer_.Name refers to _IfcElement_.Name. The ordering of layers is preserved by the layer set, while the thicknesses of each layer are calculated according to the material layer/profile geometry of the parts. @@ -1901,7 +1602,7 @@ The following is an example of a framed wall composition, where layers are order - + The following additional constraints apply to the 'Profile' representation type: @@ -1929,7 +1630,7 @@ As shown in Figure 1, the profile defines the outer boundary to which the window - + "089504E470D0A1A0A0000000D4948445200000010000000100802000000909168360000000467414D410000B18F0BFC6105000000097048597300000EC300000EC301C76FA8640000008749444154384F9552DB1180200CA3AEA493E91C6EE64E5A2E5C89A520FA8531AF5624AD7BFAF3880AEEEB94ED3095BEE26C20230BBE196432B6E07311388D32D8822B944AA13178AE704D68BBB56CE554413B22E676E3BD12C61A287DA5CF1C2F08D7CFADEA9678D9BC65870709BDDF0CBC2B08BB65107769E6FAA1DB28C1B9C03727CCD81BE7010F395301E94440CD0000000049454E44AE426082" diff --git a/ModelViews/Design Transfer View/Documentation.md b/ModelViews/Design Transfer View/Documentation.md index 7325fdfa7..7cb24a9a5 100644 --- a/ModelViews/Design Transfer View/Documentation.md +++ b/ModelViews/Design Transfer View/Documentation.md @@ -44,28 +44,28 @@ All geometry is supported in the Design Transfer View, including Constructive So The Design Transfer View derives from the Reference View, such that it is a superset of the Reference View. It is valid to include geometry defined within the Design Transfer View (e.g. CSG) along with geometry defined within the Reference View (e.g. tessellation). Reference View geometry may also be omitted, as it is defined as optional. -The IFC data model provides constructs for implicit and explicit parametric modeling. Explicit parametric behavior may be represented with the IFC constraint model (_IfcRelAssociatesConstraint_) to indicate product configuration tables and geometric formulas, which is out of scope for this model view. Implicit parametric behavior is based on defined rules for common elements defined by an axis path or footprint area, and may be modelled by _standard-case_ and _elemented-case_ entities. +The IFC data model provides constructs for implicit and explicit parametric modeling. Explicit parametric behavior may be represented with the IFC constraint model (_IfcRelAssociatesConstraint_) to indicate product configuration tables and geometric formulas, which is out of scope for this model view. Implicit parametric behavior is based on defined rules for common elements defined by an axis path or footprint area. -_Standard-case_ entities are defined by material configuration at type definitions (either _IfcMaterialLayerSet_, _IfcMaterialProfileSet_, or _IfcMaterialConstituentSet_, which are applied to an axis path or footprint area. Material profiles define cross sections of materials that are swept along a curve. Material layers define thicknesses of materials that fill a bounded area. _Standard-case_ entities include the following: +Elements may have parametric behaviors defined by material configuration at type definitions (either _IfcMaterialLayerSet_, _IfcMaterialProfileSet_, or _IfcMaterialConstituentSet_, which are applied to an axis path or footprint area. Material profiles define cross sections of materials that are swept along a curve. Material layers define thicknesses of materials that fill a bounded area. Applicable entities include the following: { .gridtable} Entity | Material | Representation ------ | -------- | -------------- -_IfcSlabStandardCase_ | _IfcMaterialLayerSetUsage_ | 'Footprint' -_IfcPlateStandardCase_ | _IfcMaterialLayerSetUsage_ | 'Footprint' -_IfcWallStandardCase_ | _IfcMaterialLayerSetUsage_ | 'Axis' -_IfcColumnStandardCase_ | _IfcMaterialProfileSetUsage_ | 'Axis' -_IfcBeamStandardCase_ | _IfcMaterialProfileSetUsage_ | 'Axis' -_IfcMemberStandardCase_ | _IfcMaterialProfileSetUsage_ | 'Axis' -_IfcDoorStandardCase_ | _IfcMaterialConstituentSet_ | 'Profile' -_IfcWindowStandardCase_ | _IfcMaterialConstituentSet_ | 'Profile' -_IfcOpeningStandardCase_ | _IfcMaterialConstituentSet_ | 'Profile' +_IfcSlab_ | _IfcMaterialLayerSetUsage_ | 'Footprint' +_IfcPlate_ | _IfcMaterialLayerSetUsage_ | 'Footprint' +_IfcWall_ | _IfcMaterialLayerSetUsage_ | 'Axis' +_IfcColumn_ | _IfcMaterialProfileSetUsage_ | 'Axis' +_IfcBeam_ | _IfcMaterialProfileSetUsage_ | 'Axis' +_IfcMember_ | _IfcMaterialProfileSetUsage_ | 'Axis' +_IfcDoor_ | _IfcMaterialConstituentSet_ | 'Profile' +_IfcWindow_ | _IfcMaterialConstituentSet_ | 'Profile' +_IfcOpeningElement_ | - | 'Profile' -_Elemented-case_ entities are defined by compositions of elements, where each composed element is defined by material configuration at type definitions. _Elemented-case_ entities include the following: +Elements may be further described by compositions of parts, where each composed element is defined by material configuration at type definitions. Applicable entities include the following: { .gridtable} Entity | Components ------ | ---------- -_IfcSlabElementedCase_ | _IfcPlateStandardCase_ (subfloor)
_IfcElementAssembly_ (joists)
_IfcBuildingElementPart_ (ceiling drywall) -_IfcWallElementedCase_ | _IfcBuildingElementPart_ (panels on forward side)
_IfcElementAssembly_ (studs, track, insulation)
_IfcBuildingElementPart_ (panels on reverse side) +_IfcSlab_ | _IfcPlate_ (subfloor)
_IfcElementAssembly_ (joists)
_IfcBuildingElementPart_ (ceiling drywall) +_IfcWall_ | _IfcBuildingElementPart_ (panels on forward side)
_IfcElementAssembly_ (studs, track, insulation)
_IfcBuildingElementPart_ (panels on reverse side) diff --git a/ModelViews/General Usage/DocModelView.xml b/ModelViews/General Usage/DocModelView.xml index 63a5c1954..4a37d8a91 100644 --- a/ModelViews/General Usage/DocModelView.xml +++ b/ModelViews/General Usage/DocModelView.xml @@ -256,8 +256,8 @@ The **IfcActionRequest** may have assignments of its own using the [IfcRelAssign - - + + @@ -333,10 +333,10 @@ The **IfcActionRequest** may have assignments of its own using the [IfcRelAssign - - - - + + + + @@ -402,9 +402,9 @@ The **IfcActionRequest** may have assignments of its own using the [IfcRelAssign - - - + + + @@ -562,7 +562,7 @@ The **IfcActionRequest** may have assignments of its own using the [IfcRelAssign The operating function of an asset within an organization may be particularly valuable in situations where one organization provides and maintains core services and another organization adds and maintains terminal services. It can classify who owns and is responsible for the asset. Operating function can be designated through the use of one or more classification references. - + @@ -987,15 +987,104 @@ The **IfcActionRequest** may have assignments of its own using the [IfcRelAssign - The material of the _IfcBeam_ is defined by the _IfcMaterialProfileSet_ or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcBeamType_. - -> NOTE&nbsp; It is illegal to assign an _IfcMaterialProfileSetUsage_ to an _IfcBeam_. Only the subtype _IfcBeamStandardCase_ supports this concept. + The material information of the _IfcBeam_ is defined by _IfcMaterialProfileSet_ or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcBeamType_. In this case, the material information does not allow to construct a shape by applying the profile definition to the axis representation, to enable this parametric definition, the _IfcMaterialProfileSetUsage_ has to be used instead. + + The _Material Profile Set Usage_ defines the assignment of an _IfcMaterialProfileSetUsage_ to the _IfcBeamType_ providing a common profile definition to all occurrences of this _IfcBeamType_. Beams with composite profile can be represented by refering to several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ that is referenced from the _IfcMaterialProfileSetUsage_. + +<table> + + <tr> + <td><img src="../../figures/ifcbeam-01.png" height="500" width="500" alt="Material profile set and usage"></td> + <td><blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates assignment of <em>IfcMaterialProfileSetUsage</em> and <em>IfcMaterialProfileSet</em> to the <em>IfcBeam</em> as the beam occurrence and to the <em>IfcBeamType</em>. The same <em>IfcMaterialProfileSet</em> shall be shared by many occurrences of <em>IfcMaterialProfileSetUsage</em>. This relationship shall be consistent to the relationship between the <em>IfcBeamType</em> and the <em>IfcBeam</em>.</blockquote> + + </td> + </tr> + +<tr> + <td><p class="figure">Figure 1 &mdash; Beam profile usage</p></td> + <td>&nbsp;</td> + </tr> + +</table> + +<table> + + <tr> + <td><img src="../../figures/ifcbeam_cardinalpoint.png" height="250" width="500" alt="Cardinal point usage"></td> + <td> + + <blockquote class="example">EXAMPLE&nbsp; Figure 2 illustrates alignment of cardinal points.</blockquote> + +<blockquote class="note">NOTE&nbsp; It has to be guaranteed that the use of <em>IfcCardinalPointEnum</em> is consistent to the placement of the extrusion body provided by <em>IfcExtrudedAreaSolid.Position</em></blockquote> + +<blockquote class="note">NOTE&nbsp; The cardinal points <b>8</b> (top centre) and <b>6</b> (mid-depth right) are assigned according to the definition at <em>IfcCardinalPointReference</em></blockquote> </td> + </tr> + +<tr> + <td><p class="figure">Figure 2 &mdash; Beam cardinal points</p></td> + <td>&nbsp;</td> + </tr> + +</table> + +<table> + +<tr> + <td><img src="../../figures/ifcbeam-02.png" height="550" width="500" alt="Material profile set and usage"></td> + <td> +<blockquote class="example">EXAMPLE&nbsp; Figure 3 illustrates assignment of a composite profile by using <em>IfcCompositeProfile</em> for geometric representation and several <em>IfcMaterialProfile</em>'s within the <em>IfcMaterialProfileSet</em>.</blockquote> + + </td> + </tr> + + <tr> + <td><p class="figure">Figure 3 &mdash; Beam composite profiles</p></td> + </tr> + +</table> + + - The 'Axis' 'Curve 3D' geometry can be used to represent the system axis and length of a beam that may extent the body length. + The axis representation can be used to represent the system length of a beam that may extent the body length of the beam. + +> NOTE&nbsp; The 'Axis' is used to locate the material profile set, if the material association is of type _IfcMaterialProfileSetUsage_. + +The following additional constraints apply to the 'Axis' representation, if an _IfcMaterialProfileSetUsage_ is provided and the 'Body' shape representation has the _RepresentationType_: 'SweptSolid': + +* _Axis_ + * _IfcPolyline_ having two _Points_, or _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcLine_ for 'SweptSolid' provided as _IfcExtrudedAreaSolid_. The axis curve lies on the z axis of the object coordinate system. + * _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcCircle_ for 'SweptSolid' provided as _IfcRevolvedAreaSolid_. The axis curve lies on the x/z plane of the object coordinate system, the tangent at the start is along the positive z-axis. + +&nbsp; + +<table border="0" cellpadding="2" cellspacing="2" summary="Axis"> + +<tr><td align="left" valign="top" width="350"> +<img src="../../figures/ifcbeamstandardcase_axis-01.png" alt="Axis" height="300" width="400" border="1"></td> +<td><blockquote class="example">EXAMPLE&nbsp; As shown in Figure 76, the axis shall be defined along the z axis of the object coordinate system. The axis representation can be used to represent the system length of a beam that may extent the body length of the beam.</blockquote> + +</td> +</tr> + +<tr><td><p class="figure">Figure 1 &mdash; Beam axis representation</p></td><td>&nbsp;</td></tr> + +</table> + +<table> + +<tr><td align="left" valign="top" width="350"> +<img src="../../figures/ifcbeamstandardcase_axis-02.png" alt="Axis" height="300" width="400" border="1"></td> +<td><blockquote class="example">EXAMPLE&nbsp; As shown in Figure 77, the axis representation shall be used to represent the cardinal point as the offset between the 'Axis' and the extrusion path of the beam. The extrusion path is provided as <em>IfcExtrudedAreaSolid.ExtrudedDirection</em> and should be parallel to the 'Axis' and the z axis. It has to be guaranteed that the value provided by +<em>IfcMaterialProfileSetUsage.CardinalPoint</em> is consistent to the <em>IfcExtrudedAreaSolid.Position</em>.</blockquote> + +</td> +</tr> + +<tr><td><p class="figure">Figure 2 &mdash; Beam axis cardinal point</p></td><td>&nbsp;</td></tr> -> NOTE&nbsp; The 'Axis' is not used to locate the material profile set, only the subtype _IfcBeamStandardCase_ provides this capability. +</table> @@ -1041,14 +1130,6 @@ Figure 1 illustrates use of _IfcBooleanClippingResult_ between an _IfcExtrudedAr !["clipped beam"](../../figures/ifcbeam_advanced-2-layout1.gif "Figure 1 &mdash; Beam clipping") - - - - - An idealized structural member corresponding to the beam. - - - @@ -1274,9 +1355,9 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - - - + + + @@ -1416,8 +1497,8 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - - + + @@ -2113,7 +2194,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2531,7 +2612,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2579,8 +2660,8 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - - + + @@ -2590,7 +2671,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2805,11 +2886,29 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - The material of the _IfcColumn_ is defined by the _IfcMaterialProfileSet_ or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcColumnType_. - -> NOTE&nbsp; It is illegal to assign an _IfcMaterialProfileSetUsage_ to an _IfcColumn_. Only the subtype _IfcColumnStandardCase_ supports this concept. + The material information of the _IfcColumn_ is defined by the _IfcMaterialProfileSet_ or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcColumnType_. In this case, the material information does not allow to construct a shape by applying the profile definition to the axis representation, to enable this parametric definition, the _IfcMaterialProfileSetUsage_ has to be used instead. + + The _Material Profile Set Usage_ defines the assignment of an _IfcMaterialProfileSetUsage_ to the _IfcColumnType_ providing a common profile definition to all occurrences of this _IfcColumnType_. Columns with composite profile can be represented by refering to several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ that is referenced from the _IfcMaterialProfileSetUsage_. + +Figure 1 illustrates assignment of _IfcMaterialProfileSetUsage_ and _IfcMaterialProfileSet_ to the _IfcColumn_ as the column occurrence and to the _IfcColumnType_. The same _IfcMaterialProfileSet_ shall be shared by many occurrences of _IfcMaterialProfileSetUsage_. This relationship shall be consistent to the relationship between the _IfcColumnType_ and the _IfcColumnStandardCase_. + +!["Material profile set and usage"](../../figures/ifccolumn-01.png "Figure 1 &mdash; Column profile usage") + +Figure 2 illustrates cardinal point alignment. + +> NOTE  It has to be guaranteed that the use of _IfcCardinalPointEnum_ is consistent to the placement of the extrusion body provided by _IfcExtrudedAreaSolid_._Position_ + +> NOTE  The cardinal points **7** (top left), and **6** (mid-depth right) are assigned according to the definition at _IfcCardinalPointReference_ + +!["Cardinal point usage"](../../figures/ifccolumn_cardinalpoint.png "Figure 2 &mdash; Column cardinal points") + +Figure 3 illustrates assignment of a composite profile by using _IfcCompositeProfile_ for geometric representation and several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_. The number of _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ is restricted to maximal 2 and requires the use of _IfcExtrudedAreaSolidTapered_, or _IfcRevolvedAreaSolidTapered_ for the correct 'Body' shape representation. + +!["Material profile set and usage"](../../figures/ifccolumn-02.png "Figure 3 &mdash; Column composite profiles") + + The _IfcColumn_, as any subtype of _IfcBuildingElement_, may participate alternatively in one of the two different containment relationships: @@ -2831,7 +2930,50 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they The axis representation can be used to represent the system length of a column that may extent the body length of the column. -> NOTE&nbsp; The 'Axis' is not used to locate the material profile set, only the subtype _IfcColumnStandardCase_ provides this capability. +> NOTE&nbsp; The 'Axis' is used to locate the material profile set, if the material association is of type _IfcMaterialProfileSetUsage_. + +The following additional constraints apply to the 'Axis' representation, if an _IfcMaterialProfileSetUsage_ is provided and the 'Body' shape representation has the _RepresentationType_: 'SweptSolid': + +* _Axis_ + * _IfcPolyline_ having two _Points_, or _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcLine_ for 'SweptSolid' provided as _IfcExtrudedAreaSolid_. The axis curve lies on the z axis of the object coordinate system. + * _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcCircle_ for 'SweptSolid' provided as _IfcRevolvedAreaSolid_. The axis curve lies on the x/z plane of the object coordinate system, the tangent at the start is along the positive z-axis. + +&nbsp; + +<table border="0" cellpadding="2" cellspacing="2" summary="Axis"> + + <tr> + <td align="left" valign="top" width="300"><img src="../../figures/ifccolumnstandardcase_axis-01.png" alt="Axis" border="1"></td> + <td> +<blockquote class="example">EXAMPLE&nbsp; As shown in Figure 1, the axis shall be defined along the z axis of +the object coordinate system. The axis representation can be used to +represent the system length of a column that may extent the body +length of the column.</blockquote> + +</td> + </tr> + +<tr> + <td><p class="figure">Figure 1 &mdash; Column axis representation</p></td> + <td>&nbsp;</td> + </tr> + +</table> + +<table border="0" cellpadding="2" cellspacing="2" summary="Axis"> + +<tr> + <td align="left" valign="top" width="300"><img src="../../figures/ifccolumnstandardcase_axis-02.png" alt="Axis" border="1"></td> + + <td><blockquote class="example">EXAMPLE&nbsp; As shown in Figure 2, the axis representation shall be used to represent the cardinal point as the offset between the 'Axis' and the extrusion path of the column. The extrusion path is provided as <em>IfcExtrudedAreaSolid.ExtrudedDirection</em> and should be parallel to the 'Axis'. It has to be guaranteed that the value provided by <em>IfcMaterialProfileSetUsage.CardinalPoint</em> is consistent to the <em>IfcExtrudedAreaSolid.Position</em>.</blockquote> + </td></tr> + + <tr> + <td><p class="figure">Figure 2 &mdash; Column axis cardinal point</p></td> + <td>&nbsp;</td> + </tr> + +</table> @@ -2877,17 +3019,6 @@ Figure 1 illustrates a 'Clipping' geometric representation with use of !["advanced column"](../../figures/ifccolumn_advanced-2-layout1.png "Figure 1 &mdash; Column clipping") - - - - - An idealized structural member corresponding to the column. - - - A task for operating on the column. - - - @@ -3515,7 +3646,7 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ Constraints may be applied to a resource to indicate fixed work (such as total person-hours) or fixed usage (such as simultaneous workers). - + Indicate fixed usage (such as simultaneous workers) such that changes to ScheduleWork should impact the assigned IfcTask.TaskTime.ScheduleDuration and vice-versa. @@ -3728,7 +3859,7 @@ A common scenario is two nesting levels where the first-level resources have no - + @@ -3853,7 +3984,7 @@ A common scenario is two nesting levels where the first-level resources have no Instances of _IfcCostItem_ are used for cost estimates, budgets, and other forms, where a variety of identification codes are used extensively to identify the meaning of the cost. Examples include project phase codes, CSI codes, takeoff sequence numbers, and cost accounts. The model allows for all classes that are ultimately subtypes of _IfcObject_ to inherit the ability to have one or more instances of _IfcClassificationReference_ to be assigned. Where identification codes are required, the generic _IfcRelAssociatesClassification_ facility should be used. - + An _IfcCostItem_ can nest other instances of _IfcCostItem_ through its relationships to _IfcRelNests_. This can be used to enable the development of complex groups of costs as may be found in cost schedules through to pages, sections and complete cost schedules. @@ -4315,7 +4446,7 @@ parameter of the <em>IfcSurfaceOfLinearExtrusion</em>.</li> - + @@ -4458,7 +4589,7 @@ parameter of the <em>IfcSurfaceOfLinearExtrusion</em>.</li> Figure 1 illustrates classification usage. !["Classification Use Definition"](../../figures/ifcdistributioncontrolelement-classification.png "Figure 1 &mdash; Distribution control classification") - + 32-bit decimal BACnetObjectIdentifier indicating type ID and instance ID (e.g.'12.15' for Digital Input #15). @@ -4544,9 +4675,9 @@ The assignment of types to distribution element occurrences is vital for providi - - - + + + @@ -4680,8 +4811,8 @@ Upon connecting elements through ports with rigid connections, each object shall - - + + @@ -4691,30 +4822,30 @@ Upon connecting elements through ports with rigid connections, each object shall - - - + + + - - + + - - - + + + - + @@ -4724,26 +4855,26 @@ Upon connecting elements through ports with rigid connections, each object shall - + - - - - + + + + - - - - - + + + + + @@ -4753,27 +4884,27 @@ Upon connecting elements through ports with rigid connections, each object shall - + - - - - + + + + - - - - - - + + + + + + @@ -4875,6 +5006,8 @@ Figure 1 illustrates a distribution system for an electrical circuit. The opening direction is determined by the local placement of _IfcDoor_ and the _OperationType_ of the _IfcDoorType_ as shown in Figure 1. +The _IfcDoorTypeOperationEnum_ defines the general layout of the door type and its symbolic presentation. Depending on the enumerator, the appropriate instances of _IfcDoorLiningProperties_ and _IfcDoorPanelProperties_ are attached in the list of _HasPropertySets_. The _IfcDoorTypeOperationEnum_ mainly determines the hinge side (left hung, or right hung), the operation (swinging, sliding, folding, etc.) and the number of panels. + > NOTE&nbsp; There are different definitions in various countries on what a left opening or left hung or left swing door is (same for right). Therefore the IFC definition may derivate from the local standard and need to be mapped appropriately. <table><tr><td> @@ -4995,7 +5128,7 @@ pictures).</small></td> - + @@ -5067,8 +5200,16 @@ pictures).</small></td> - - The material of the _IfcDoor_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_ relationship. + + The material of the _IfcDoor_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_ relationship. It is accessible by the inverse _HasAssociations_ relationship. + +The following keywords for _IfcMaterialConstituentSet.MaterialConstituents[n].Name_ shall be used: + +* 'Lining' - to indicate that the material constituent applies to to the door lining +* 'Framing' - to indicate that the material constituent applies to to the door framing, if not provided, the 'Lining' material information applied to frams as well +* 'Glazing' - to indicate that the material constituent applies to to the glazing as well + +If the fall back single _IfcMaterial_ is referenced, it applies to the lining and framing of the door. @@ -5082,6 +5223,83 @@ pictures).</small></td> + + The following restriction is imposed: + +1. The _PlacementRelTo_ relationship of _IfcLocalPlacement_ shall point to the local placement of the same element (if given), in which the _IfcDoor_ is used as a filling (normally an _IfcOpeningElement_), as provided by the _IfcRelFillsElement_ relationship; +2. If the _IfcDoor_ is part of an assembly, e.g. an _IfcCurtainWall_, then the _PlacementRelTo_ relationship of _IfcLocalPlacement_ shall point (if given) to the local placement of that assembly; +3. If the _IfcDoor_ is not inserted into an _IfcOpeningElement_, then the _PlacementRelTo_ relationship of _IfcLocalPlacement_ shall point (if given) to the local placement of the same _IfcSpatialStructureElement_ that is used in the _ContainedInStructure_ inverse attribute or to a referenced spatial structure element at a higher level. + +> NOTE&nbsp; The product placement is used to determine the opening direction of the door. + + + + The door profile is represented by a three-dimensional closed curve within a particular shape representation. The profile is used to apply the parameter of the parametric door representation. The following attribute values for the _IfcShapeRepresentation_ holding this geometric representation shall be used: + +* _RepresentationIdentifier_ : 'Profile' +* _RepresentationType_ : 'Curve3D' or 'GeometricCurveSet', in case of 'GeometricCurveSet' only a single closed curve shall be contained in the set of _IfcShapeRepresentation.Items_. + +The following additional constraints apply to the 'Profile' representation type: + +* **Curve**: being an _IfcPolyline_ defining a rectangle. +* **Position**: The curve shall lie in the xz plane of the object placement coordinate (the y coordinate values of the _IfcCartesianPoint_'s shall be 0.). + +&nbsp; + +<table summary=""> + +<tr valign="top"> + + <td><img src="../../figures/ifcdoorstandardcase-01.png" alt="standard door" border="0" width="500" height="500"></td> + + <td> +<blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates applying the door lining parameters to the +door profile shape representation. The profile defines the outer +boundary to which the door lining parameters relate as:</blockquote> + <blockquote> +<ul> + + <li class="small"><em>IfcDoorLiningProperties.LiningDepth</em> starting at distance +defined by <em>LiningOffset</em> going into the positive y +direction.</li> + + <li class="small"><em>IfcDoorLiningProperties.LiningThickness</em> offset into the +inner side of the rectangle.</li> + <li class="small"><em>IfcDoorLiningProperties.LiningOffset</em> distance along the +positive y direction to where the <em>LiningDepth</em> applies.</li> + +<li class="small"><em>IfcDoorLiningProperties.ThresholdThickness</em> starting at +the bottom edge of the rectangle into the inner side of the +rectangle</li> + + <li class="small"><em>IfcDoorLiningProperties.ThresholdDepth</em> starting at +distance defined by <em>LiningOffset</em> going into the positive y +direction.</li> + + <li class="small"><em>IfcDoorLiningProperties.TransomOffset</em> starting at the +bottom edge of the rectangle (along local x axis) into the inner +side of the rectangle, distance provided as percentage of overall +height. Distance to the centre line of the transom.</li> + +</ul></blockquote> + +</td> + + </tr> + + <tr valign="top"> + +<td> +<p class="figure">Figure 1 &mdash; Door profile</p> +</td> + +<td>&nbsp;</td> + + </tr> + +</table> + + The _IfcDoor_, as any subtype of _IfcBuildingElement_, may participate alternatively in one of the two different containment relationships: @@ -5135,22 +5353,6 @@ structure by - - The following restriction is imposed: - -1. The _PlacementRelTo_ relationship of _IfcLocalPlacement_ shall point to the local placement of the same element (if given), in which the _IfcDoor_ is used as a filling (normally an _IfcOpeningElement_), as provided by the _IfcRelFillsElement_ relationship; -2. If the _IfcDoor_ is part of an assembly, e.g. an _IfcCurtainWall_, then the _PlacementRelTo_ relationship of _IfcLocalPlacement_ shall point (if given) to the local placement of that assembly; -3. If the _IfcDoor_ is not inserted into an _IfcOpeningElement_, then the _PlacementRelTo_ relationship of _IfcLocalPlacement_ shall point (if given) to the local placement of the same _IfcSpatialStructureElement_ that is used in the _ContainedInStructure_ inverse attribute or to a referenced spatial structure element at a higher level. - -> NOTE&nbsp; The product placement is used to determine the opening direction of the door. - - - - The door profile is represented by a three-dimensional closed curve within a particular shape representation. The profile is used to apply the parameter of the parametric door representation. Only a single closed curve shall be contained in the set of _IfcShapeRepresentation.Items_. - -A 'Profile' representation has to be provided if a parametric representation is applied to the door. - - @@ -5285,8 +5487,8 @@ height. Distance to the centre line of the transom.</li> - - + + @@ -5405,8 +5607,8 @@ height. Distance to the centre line of the transom.</li> - - + + @@ -5483,9 +5685,9 @@ height. Distance to the centre line of the transom.</li> - - - + + + @@ -5760,7 +5962,7 @@ height. Distance to the centre line of the transom.</li> - + @@ -6109,7 +6311,7 @@ height. Distance to the centre line of the transom.</li> - + @@ -6267,6 +6469,12 @@ representation</p> The same constraints, as given for 'SurfaceOrSolidModel', 'SurfaceModel', 'Tessellation', 'Brep', and 'AdvancedBrep' geometric representation, shall apply to the _IfcRepresentationMap_. + + + + + + @@ -6463,7 +6671,7 @@ Representation identifier and type are the same as in single mapped representati - + @@ -6696,7 +6904,7 @@ Representation identifier and type are the same as in single mapped representati - + @@ -6802,8 +7010,8 @@ Representation identifier and type are the same as in single mapped representati - - + + @@ -7351,7 +7559,7 @@ The material is attached by the _RelatingMaterial_ attribute on the [IfcRelAssoc * Catalog : _IfcClassification.Name_ * Identity: _IfcClassificationReference.Identification_ * ElementName: _IfcClassificationReference.Name_ - + @@ -8318,11 +8526,21 @@ The following constraints apply to the 2D representation: - The material of the _IfcMember_ is defined by the _IfcMaterialProfileSet_ or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcMemberType_. - -> NOTE&nbsp; It is illegal to assign an _IfcMaterialProfileSetUsage_ to an _IfcMember_. Only the subtype _IfcMemberStandardCase_ supports this concept. + The material information of the _IfcMember_ is defined by the _IfcMaterialProfileSet_ or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcMemberType_. In this case, the material information does not allow to construct a shape by applying the profile definition to the axis representation, to enable this parametric definition, the _IfcMaterialProfileSetUsage_ has to be used instead. + + The material of the _IfcMember_ is defined by _IfcMaterialProfileSetUsage_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. Composite profile members can be represented by refering to several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ that is referenced from the _IfcMaterialProfileSetUsage_. + +Figure 1 illustrates assignment of _IfcMaterialProfileSetUsage_ and _IfcMaterialProfileSet_ to the _IfcMember_ as the member occurrence and to the _IfcMemberType_. The same _IfcMaterialProfileSet_ shall be shared by many occurrences of _IfcMaterialProfileSetUsage_. This relationship shall be consistent to the relationship between the _IfcMemberType_ and the _IfcMember_. + +!["Material profile set and usage"](../../figures/ifcmember-01.png "Figure 1 &mdash; Member profile usage") + +Figure 2 illustrates assignment of a composite profile by using _IfcCompositeProfile_ for geometric representation and several _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_. The number of _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ is restricted to maximal 2 and requires the use of _IfcExtrudedAreaSolidTapered_, or _IfcRevolvedAreaSolidTapered_ for the correct 'Body' shape representation. + +!["Material profile set and usage"](../../figures/ifcmember-02.png "Figure 2 &mdash; Member composite profiles") + + The _IfcMember_, as any subtype of _IfcBuildingElement_, may participate alternatively in one of the two different containment relationships: @@ -8344,7 +8562,49 @@ The following constraints apply to the 2D representation: The axis representation can be used to represent the system length of a member that may extent the body length of the member. -> NOTE&nbsp; The 'Axis' is not used to locate the material profile set, only the subtype _IfcMemberStandardCase_ provides this capability. +> NOTE&nbsp; The 'Axis' is used to locate the material profile set, if the material association is of type _IfcMaterialProfileSetUsage_. + +The following additional constraints apply to the 'Axis' representation, if an _IfcMaterialProfileSetUsage_ is provided and the 'Body' shape representation has the _RepresentationType_: 'SweptSolid': + +* _Axis_ + * _IfcPolyline_ having two _Points_, or _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcLine_ for 'SweptSolid' provided as _IfcExtrudedAreaSolid_. The axis curve lies on the z axis of the object coordinate system. + * _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcCircle_ for 'SweptSolid' provided as _IfcRevolvedAreaSolid_. The axis curve lies on the x/z plane of the object coordinate system, the tangent at the start is along the positive z-axis. + +&nbsp; + +<table border="0" cellpadding="2" cellspacing="2" summary="Axis"> + +<tr> + <td align="left" valign="top" width="350"><img src="../../figures/ifcmemberstandardcase_axis-01.png" alt="Axis" border="1"></td> + <td> + +<blockquote class="example">EXAMPLE&nbsp; As shown in Figure 101, the axis representation can be used to represent the system length of a member that may extent the body length of the member.</blockquote> + + </td> + </tr> + + <tr> + <td><p class="figure">Figure 1 &mdash; Member axis representation</p></td> + <td>&nbsp;</td> + </tr> + +</table> + +<table border="0" cellpadding="2" cellspacing="2" summary="Axis"> + +<tr> + <td align="left" valign="top" width="350"><img src="../../figures/ifcmemberstandardcase_axis-02.png" alt="Axis" border="1"></td> + <td align="left" valign="top"><blockquote class="example">EXAMPLE&nbsp; As shown in Figure 102, the axis representation shall be used to represent the cardinal point as the offset between the 'Axis' and the extrusion path of the member. The extrusion path is provided as <em>IfcExtrudedAreaSolid.ExtrudedDirection</em> and should be parallel to the 'Axis'. It has to be guaranteed that the value provided by <em>IfcMaterialProfileSetUsage.CardinalPoint</em> is consistent to the <em>IfcExtrudedAreaSolid.Position</em>.</blockquote> + +</td> + </tr> + +<tr> + <td><p class="figure">Figure 2 &mdash; Member axis cardinal point</p></td> + <td>&nbsp;</td> + </tr> + +</table> @@ -8353,26 +8613,50 @@ The following constraints apply to the 2D representation: - The following additional constraints apply to the 'SweptSolid' representation: + The following constraints apply to the 'SweptSolid' representation: -* **Solid**: _IfcExtrudedAreaSolid_, _IfcRevolvedAreaSolid_ shall be supported -* **Profile**: all subtypes of _IfcProfileDef_ (with exception of _IfcArbitraryOpenProfileDef_)  -* **Extrusion**: All extrusion directions shall be supported. +* Solid: IfcExtrudedAreaSolid, IfcRevolvedAreaSolid shall be supported +* Profile: all subtypes of IfcProfileDef (with exception of _IfcArbitraryOpenProfileDef_) +* Extrusion: All extrusion directions shall be supported. -Figure 1 illustrates a 'SweptSolid' geometric representation. There are no restrictions or conventions on how to use the local placement (black), solid of extrusion placement (red) and profile placement (green). -!["standard member"](../../figures/ifcmember_sweptsolid-01.png "Figure 1 &mdash; Member swept solid") +<>The following additional constraints apply to the 'SweptSolid' +representation, when an _IfcMaterialProfileSetUsage_ is assigned to the _IfcMember_:* **Solid**: _IfcExtrudedAreaSolid_, _IfcRevolvedAreaSolid_ shall be supported +* **Profile**: all subtypes of _IfcProfileDef_ (with exception of _IfcArbitraryOpenProfileDef_) +* **Profile Position** : For all single profiles, the _IfcParameterizedProfileDef_.Position shall be NIL, or having _Location_ = 0.,0. and _RefDirection_ = 1.,0. +* **Extrusion**: perpendicular to the profile direction. +* **Orientation**: The y-axis of the profile, as determined by _IfcSweptAreaSolid.Position.P[2]_ shall point to the Z-Axis. It indicates the "role" of the column, a role=0&deg; means y-axis of profile = Z-axis of reference coordinate system. In the exception of a vertical member, the y-axis shall point to the Y-axis. + +Figure 1 illustrates a 'SweptSolid' geometric representation with cardinal point applied as **1** (bottom left). + +The following interpretation of dimension parameter applies for rectangular members: + +* <small><em>IfcRectangleProfileDef.YDim</em> interpreted as member width</small> +* <small><em>IfcRectangleProfileDef.XDim</em> interpreted as member depth</small> + +The following interpretation of dimension parameter applies for circular members: + +* <small><em>IfcCircleProfileDef.Radius</em> interpreted as beam radius.</small> + +!["standard member"](../../figures/ifcbeamstandardcase_sweptsolid-01.png "Figure 1 &mdash; Member body extrusion") - The following additional constraints apply to the 'AdvancedSweptSolid' representation type: + The following constraints apply to the 'AdvancedSweptSolid' representation type: * **Solid**: _IfcSurfaceCurveSweptAreaSolid_, _IfcFixedReferenceSweptAreaSolid_, _IfcExtrudedAreaSolidTapered_, _IfcRevolvedAreaSolidTapered_ shall be supported. >> NOTE&nbsp; View definitions and implementer agreements can further constrain the allowed swept solid types. * **Profile**: see 'SweptSolid' geometric representation * **Extrusion**: not applicable -_MappedRepresentation Representation Type_ +The following additional constraints apply to the 'AdvancedSweptSolid' representation type, when an _IfcMaterialProfileSetUsage_ is assigned to the _IfcMember_: + +* **Solid**: _IfcSurfaceCurveSweptAreaSolid_, _IfcFixedReferenceSweptAreaSolid_, _IfcExtrudedAreaSolidTapered_, _IfcRevolvedAreaSolidTapered_ shall be supported. +>> NOTE&nbsp; View definitions and implementer agreement can further constrain the allowed swept solid types. +>> NOTE&nbsp; Using _IfcExtrudedAreaSolidTapered_, or _IfcRevolvedAreaSolidTapered_ requires the use of two _IfcMaterialProfile_'s within the _IfcMaterialProfileSet_ assinged to the _IfcBeamStandardCase_ +* **Profile**: see 'SweptSolid' geometric representation +* **Profile Position** : see 'SweptSolid' geometric representation +* **Extrusion**: not applicable @@ -8385,20 +8669,21 @@ _MappedRepresentation Representation Type_ Figure 1 illustrates a 'Clipping' geometric representation with use of _IfcBooleanClippingResult_ between an _IfcExtrudedAreaSolid_ and an _IfcHalfSpaceSolid_ to create a clipped body. -!["clipped member"](../../figures/ifcmember_clipping-01.png "Figure 1 &mdash; Member clipping") +!["clipped member"](../../figures/ifcmember_clipping-01.png "Figure 1 &mdash; Member clipping") + +The following constraints apply to the 'Clipping' representation, when an _IfcMaterialProfileSetUsage_ is assigned to the _IfcMember_: + +* **Solid**: see 'SweptSolid' geometric representation +* **Profile**: see 'SweptSolid' geometric representation +* **Profile Position** : see 'SweptSolid' geometric representation +* **Extrusion**: see 'SweptSolid' geometric representation +* **Boolean result**: The _IfcBooleanClippingResult_ shall be supported, allowing for Boolean differences between the swept solid (here _IfcExtrudedAreaSolid_) and one or several _IfcHalfSpaceSolid_ (or its subtypes). + +Figure 2 illustrates an advanced geometric representation with use of _IfcBooleanClippingResult_ between an _IfcExtrudedAreaSolid_ and an _IfcHalfSpaceSolid_ to create a clipped body, with cardinal point applied as **4** (mid-depth left). + +!["clipped beam"](../../figures/ifcbeamstandardcase_clipping-01.png "Figure 2 &mdash; Member body clipping") - - - - - An idealized structural member corresponding to the member. - - - A task for operating on the member. - - - @@ -8615,12 +8900,38 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - + + An attribute _Name_ and optionally _Description_ can be used for all subypes of _IfcObject_. For those subtypes, that have an object type definition, such as ifcBeam - IfcBeamType, the common _Name_ and optionally _Description_ is associated with the object type. + + + + + Any object occurrence can be typed by being assigned to a common object type utilizing this concept. A particular rule, restricting the applicable subtypes of _IfcTypeObject_ that can be assigned, is introduced by overriding this concept at the level of subtypes of _IfcObject_. + + + + Any object occurrence can hold property sets, each being a set of individual properties having name, description, value(s) and unit(s). A reference to applicable property sets, being part of this specification, is introduced at the level of sub types of _IfcObject_. + + + + Any object occurrence can hold property sets, either directly at the object occurrence as element specific property sets, or at the object type, as type property sets. In this case, the properties that are provided to the object occurrence are the combinations of element specific and type properties. In case, that the same property (within the same property set, is defined both, in occurrence and type properties, the property value of the occurrence property overrides the property value of the type property. + + + + + + + Any object occurrence or object type can have a reference to a specific classification reference, i.e. to a particular facet within a classification system. + + + + + @@ -8646,16 +8957,16 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - - - - + + + + - + @@ -8670,21 +8981,21 @@ The shared profile definition is defined by assigning an _IfcMaterialProfileSet_ - - - + + + - + - + @@ -8911,7 +9222,7 @@ In addition to standard property sets defined within this specification, if the _IfcPerformanceHistory_ may be classified using _IfcRelAssociatesClassification_ where _RelatingClassification_ refers to an _IfcClassificationReference_ indicating a classification notation. Such classification notation may be used to identify the information such as an address within a building automation system, a work breakdown structure code for tasks, or a cost code for resource allocation. - + _IfcPerformanceHistory_ may be decomposed into components using _IfcRelNests_ where _RelatingObject_ refers to the enclosing _IfcPerformanceHistory_ and _RelatedObjects_ contains one or more _IfcPerformanceHistory_ components. Composition indicates breakdown of further detail and may correspond to the hierarchy of objects it represents. @@ -9171,8 +9482,8 @@ The **IfcPermit** may have assignments of its own using the [IfcRelAssignsToCont - - + + @@ -9306,8 +9617,8 @@ The **IfcPermit** may have assignments of its own using the [IfcRelAssignsToCont - - + + @@ -9458,11 +9769,37 @@ The **IfcPermit** may have assignments of its own using the [IfcRelAssignsToCont - The material of the _IfcPlate_ is defined by _IfcMaterialLayerSet_, or by _IfcMaterial_, and it is attached either directly or at the _IfcPlateType_. - -> NOTE&nbsp; It is illegal to assign an _IfcMaterialLayerSetUsage_ to an _IfcPlate_. Only the subtype _IfcPlateStandardCase_ supports this concept. + The material information of the _IfcPlate_ is defined by _IfcMaterialLayerSet_, or by _IfcMaterial_, and it is attached either directly or at the _IfcPlateType_. In this case, the material information does not allow to construct a shape by applying the layer definition to the plane of the shape representation, to enable this parametric definition, the _IfcMaterialLayerSetUsage_ has to be used instead. + + The material of _IfcPlate_ can be defined by _IfcMaterialLayerSetUsage_ and attached by _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. Multi-layer plates can be represented by refering to several _IfcMaterialLayer_'s within the _IfcMaterialLayerSet_ that is referenced from the _IfcMaterialLayerSetUsage_. + +When assigning an _IfcMaterialLayerSetUsage_ to _IfcPlate_ it shall imply that the _IfcPlateType_ should have a unique _IfcMaterialLayerSet_, that is referenced by _IfcMaterialLayerSetUsage_ assigned to all occurrences of this _IfcPlateType_. + +Figure 1 illustrates assignment of _IfcMaterialLayerSetUsage_ and _IfcMaterialLayerSet_ to the _IfcPlate_ as the plate occurrence and to the _IfcPlateType_. The same _IfcMaterialLayerSet_ shall be shared by many occurrences of _IfcMaterialLayerSetUsage_. This relationship shall be consistent to the relationship between the _IfcPlateType_ and the _IfcPlateStandardCase_. + +<table border="0" cellpadding="2" cellspacing="2"> + +<tr><td width="610" align="left" valign="top"> +<p><img src="../../figures/ifcplate_materialusage-01.png" alt="Material layer set and usage" height="220" width="500">&nbsp;</p></td></tr> + +<tr><td><p class="figure">Figure 1 &mdash; Plate type definition</p></td></tr> + +</table> + +As shown in Figure 106, the following conventions shall be met: + +* The reference coordinate system is the coordinate system established by the _IfcExtrudedAreaSolid.Position_. +* The reference plane is the plane defined by the extruded profile of _IfcExtrudedAreaSolid.SweptSolid_. The _IfcMaterialLayerSetUsage.OffsetFromReferenceLine_ is given as a distance from this plane. +* The _IfcMaterialLayerSetUsage.DirectionSense_ defines how the _IfcMaterialLayer_'s are assigned to the reference plane. POSITIVE means in direction to the positive z-axis of the reference coordinate system. +* The _IfcMaterialLayerSetUsage.OffsetFromReferenceLine_ is the distance parallel to the reference plane and always perpendicular to the base (XY) plane of the reference coordinate system. This is independent of a potential non-perpendicular extrusion given by _IfcExtrudedAreaSolid.ExtrudedDirection_ &lt;&gt; 0.,0.,1. A positive value of _IfcMaterialLayerSetUsage.OffsetFromReferenceLine_ would then point into the positive z-axis of the reference coordinate system. +* The _Thickness_ of each _IfcMaterialLayer_ shall be the parallel distance (measured perpendicular to the base plane). The _TotalThickness_ of the _IfcMaterialLayerSet_ is the sum of all layer thicknesses and in case of a perpendicular extrusion identical with _IfcExtrudedAreaSolid.Depth_ +* The _IfcMaterialLayerSetUsage.LayerSetDirection_ i always AXIS3. + +!["plate material layer set"](../../figures/ifcmateriallayersetusage_slab-01.png "Figure 2 &mdash; Plate material layers") + + The _IfcPlate_, as any subtype of _IfcBuildingElement_, may participate alternatively in one of the two different containment relationships: @@ -9490,23 +9827,65 @@ The **IfcPermit** may have assignments of its own using the [IfcRelAssignsToCont * **Solid**: _IfcExtrudedAreaSolid_ is required, * **Profile**: _IfcArbitraryClosedProfileDef, IfcArbitraryProfileDefWithVoids, IfcRectangleProfileDef, IfcCircleProfileDef, IfcEllipseProfileDef_ shall be supported. -* **Extrusion**: The profile can be extruded perpendicularly or non-perpendicularly to the plane of the swept profile. +* **Extrusion**: The profile can be extruded perpendicularly or non-perpendicularly to the plane of the swept profile. + +The following additional constraints apply to the 'SweptSolid' representation, when an _IfcMaterialLayerSetUsage_ is assigned to the _IfcPlate_: + +* **Solid**: _IfcExtrudedAreaSolid_ is required, +* **Profile**: _IfcArbitraryClosedProfileDef, IfcRectangleProfileDef, IfcRoundedRectangleProfileDef, IfcCircleProfileDef, IfcEllipseProfileDef_ shall be supported. +* **Extrusion**: The profile can be extruded perpendicularly or non-perpendicularly to the plane of the swept profile. +* **Material**: The definition of the _IfcMaterialLayerSetUsage_, particularly of the _OffsetFromReferenceLine_ and the _ForLayerSet.TotalThickness_, has to be consistent to the 'SweptSolid' representation. + +&nbsp; + +<table> + + <tr> + <td><img src="../../figures/ifcslab_standard-layout1.gif" alt="standard plate" border="0" height="274" width="399"></td> + <td> + +<blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates a 'SweptSolid' geometric representation. The following interpretation of dimension parameter applies for polygonal plates (in ground floor view): <em>IfcArbitraryClosedProfileDef.OuterCurve</em> being a closed bounded curve is interpreted as area (or foot print) of the plate.</blockquote> + + + </td> + </tr> + + <tr> + <td><p class="figure">Figure 1 &mdash; Plate body extrusion</p></td> + <td>&nbsp;</td> + </tr> + +</table> + The following constraints apply to the 'Clipping' representation when an _IfcMaterialLayerSetUsage_ is assigned to the _IfcPlate_: + +* **Solid**: see 'SweptSolid' shape representation, +* **Profile**:&nbsp;see 'SweptSolid' shape representation, +* **Extrusion**:&nbsp;see 'SweptSolid' shape representation, +* **Material**:&nbsp;see 'SweptSolid' shape representation, +* **Boolean result**: The _IfcBooleanClippingResult_ shall be supported, allowing for Boolean differences between the swept solid (here _IfcExtrudedAreaSolid_) and one or several _IfcHalfSpaceSolid_. + +&nbsp; + +<table> + + <tr> + <td><img src="../../figures/ifcslab_advanced-layout1.gif" alt="advanced plate" border="0" height="274" width="399"></td> + <td><blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates a 'Clipping' geometric representation with definition of a plate using advanced geometric representation. The profile is extruded non-perpendicular and the plate body is clipped at the eave.</blockquote> + +</td> + </tr> + + <tr> + <td><p class="figure">Figure 1 &mdash; Plate body clipping</p></td> + <td>&nbsp;</td> + </tr> + +</table> - - - - - An idealized structural member corresponding to the plate. - - - A task for operating on the plate. - - - @@ -9766,32 +10145,41 @@ The shared material layer set definition is defined by assigning an _IfcMaterial - - The _IfcProject_ is used to reference the root of the spatial structure of a building or other construction project (that serves as the primary project breakdown and is required to be hierarchical). The spatial structure elements are linked together, and to the _IfcProject_, by using the objectified relationship _IfcRelAggregates_. - -The following constraints are applied to using the relationshio _IfcRelAggregates_ in context of _IfcProject_ - -> NOTE&nbsp; The anomaly to use the composition structure through _IfcRelAggregates_ for assigning the uppermost spatial container to _IfcProject_ is due to upward compatibility reasons with earlier releases of this standard. - -* _IfcProject_.Decomposes -- it shall be NIL, i.e. the _IfcProject_ shall be on top of the root of the spatial structure tree. -* _IfcProject_.IsDecomposedBy -- referencing (_IfcSite_ || _IfcBuilding_ || _IfcSpatialZone_) by using _IfcRelAggregates_.RelatedObjects. The _IfcSite_, _IfcBuilding_, or _IfcSpatialZone_ being referenced shall be the root of the spatial structure. - -Figure 1 illustrates project relationships with spatial structures, elements, and element type libraries. - -!["spatial decomposition relationships"](../../figures/ifcproject_fig-2.png "Figure 1 &mdash; Project spatial structure, products and product type library") - + + - - If referenced, the site is the root of the spatial structure. + + Length unit as meters, millimeters, or inches. - - If referenced, the building is the root of the spatial structure (no explicit site information included). + + Angle unit as degrees or radians. - - If referenced, the spatial zone is the root of the spatial structure (to be used as a stub for non-building related projects). + + + + + + + Context for all 3D geometry. + + + Context for all 2D annotations. + + The representation context of the project refers to a global positioning, i.e. the local engineering coordinate system of the project has a mapping to a defined projected coordinate system (a rectangular map coordinate system, as used in GIS systems) + + + + + + + + + + + The _IfcProject_ is also the context for other information about the construction project such as a work plan. Non-product structures are assigned by their first level object to _IfcProject_ using the _IfcRelDeclares_ relationship. The _IfcProject_ provides the context for work plans (or other non-product based) descriptions of the construction project. It is handled by the objectified relationship _IfcRelDeclares_. @@ -9832,37 +10220,32 @@ Figure 1 illustrates the use of _IfcProject_ as context for work plans or work s - - + + The _IfcProject_ is used to reference the root of the spatial structure of a building or other construction project (that serves as the primary project breakdown and is required to be hierarchical). The spatial structure elements are linked together, and to the _IfcProject_, by using the objectified relationship _IfcRelAggregates_. + +The following constraints are applied to using the relationshio _IfcRelAggregates_ in context of _IfcProject_ + +> NOTE&nbsp; The anomaly to use the composition structure through _IfcRelAggregates_ for assigning the uppermost spatial container to _IfcProject_ is due to upward compatibility reasons with earlier releases of this standard. + +* _IfcProject_.Decomposes -- it shall be NIL, i.e. the _IfcProject_ shall be on top of the root of the spatial structure tree. +* _IfcProject_.IsDecomposedBy -- referencing (_IfcSite_ || _IfcBuilding_ || _IfcSpatialZone_) by using _IfcRelAggregates_.RelatedObjects. The _IfcSite_, _IfcBuilding_, or _IfcSpatialZone_ being referenced shall be the root of the spatial structure. + +Figure 1 illustrates project relationships with spatial structures, elements, and element type libraries. + +!["spatial decomposition relationships"](../../figures/ifcproject_fig-2.png "Figure 1 &mdash; Project spatial structure, products and product type library") + - - Length unit as meters, millimeters, or inches. - - - Angle unit as degrees or radians. + + If referenced, the site is the root of the spatial structure. - - - - - - - Context for all 3D geometry. + + If referenced, the building is the root of the spatial structure (no explicit site information included). - - Context for all 2D annotations. + + If referenced, the spatial zone is the root of the spatial structure (to be used as a stub for non-building related projects). - - - - - - - - - @@ -10248,7 +10631,7 @@ The **IfcProjectOrder** may have assignments of its own using the _IfcRelAssigns - + @@ -10272,7 +10655,7 @@ The **IfcProjectOrder** may have assignments of its own using the _IfcRelAssigns - + @@ -10374,9 +10757,9 @@ The **IfcProjectOrder** may have assignments of its own using the _IfcRelAssigns - - - + + + @@ -11644,10 +12027,48 @@ The representation identifier and type of this representation of _IfcSite_ is: - The material of the _IfcSlab_ is defined by _IfcMaterialLayerSet_, or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcSlabType_. + The material information of the _IfcSlab_ is defined by _IfcMaterialLayerSet_, or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcSlabType_. In this case, the material information does not allow to construct a shape by applying the layer definition to the plane of the shape representation, to enable this parametric definition, the _IfcMaterialLayerSetUsage_ has to be used instead. + + + + The material of _IfcSlab_ can be defined by _IfcMaterialLayerSetUsage_ and attached by _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. Multi-layer slabs can be represented by refering to several _IfcMaterialLayer_'s within the _IfcMaterialLayerSet_ that is referenced from th e _IfcMaterialLayerSetUsage_. + +When assigning an _IfcMaterialLayerSetUsage_ to _IfcSlab_ it shall imply that the _IfcSlabType_ should have a unique _IfcMaterialLayerSet_, that is referenced by _IfcMaterialLayerSetUsage_ assigned to all occurrences of this _IfcSlabType_. + +<table> + + <tr> + <td><img src="../../figures/ifcslab_materialusage-01.png" alt="Material layer set and usage" height="220" width="501"></td> + +<td><blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates assignment of <em>IfcMaterialLayerSetUsage</em> and <em>IfcMaterialLayerSet</em> to the <em>IfcSlab</em> as the slab occurrence and to the <em>IfcSlabType</em>. The same <em>IfcMaterialLayerSet</em> shall be shared by many occurrences of <em>IfcMaterialLayerSetUsage</em>. This relationship shall be consistent to the relationship between the <em>IfcSlabType</em> and the <em>IfcSlabStandardCase</em>.</blockquote></td> + </tr> + +<tr><td><p class="figure">Figure 1 &mdash; Slab type definition</p></td> + <td>&nbsp;</td> + </tr> -> NOTE&nbsp; It is illegal to assign an _IfcMaterialLayerSetUsage_ to an _IfcSlab_. Only the subtype _IfcSlabStandardCase_ supports this concept. - +</table> + +Figure 2 illustrates slab material usage, where the following conventions shall be met: + +* The reference coordinate system is the coordinate system established by the _IfcExtrudedAreaSolid.Position_. +* The reference plane is the plane defined by the extruded profile of _IfcExtrudedAreaSolid.SweptSolid_. The _IfcMaterialLayerSetUsage.OffsetFromReferenceLine_ is given as a distance from this plane. +* The _IfcMaterialLayerSetUsage.DirectionSense_ defines how the _IfcMaterialLayer_'s are assigned to the reference plane. POSITIVE means in direction to the positive z-axis of the reference coordinate system. +* The _IfcMaterialLayerSetUsage.OffsetFromReferenceLine_ is the distance parallel to the reference plane and always perpendicular to the base (XY) plane of the reference coordinate system. This is independent of a potential non-perpendicular extrusion given by _IfcExtrudedAreaSolid.ExtrudedDirection_ &lt;&gt; 0.,0.,1. A positive value of _IfcMaterialLayerSetUsage.OffsetFromReferenceLine_ would then point into the positive z-axis of the reference coordinate system. +* The _Thickness_ of each _IfcMaterialLayer_ shall be the parallel distance (measured perpendicular to the base plane). The _TotalThickness_ of the _IfcMaterialLayerSet_ is the sum of all layer thicknesses and in case of a perpendicular extrusion identical with _IfcExtrudedAreaSolid.Depth_ +* The _IfcMaterialLayerSetUsage.LayerSetDirection_ is always AXIS3. + +<table summary="material use definition for standard slabs"> + + <tr> + <td align="left" valign="top" width="610"> +<img src="../../figures/ifcmateriallayersetusage_slab-01.png" alt="slab material layer set" width="601" height="321" border="0"> +</td></tr> +<tr><td align="left" valign="top" width="610"> +<img src="../../figures/ifcmateriallayersetusage_roofslab-01.png" alt="roof slab material layer set" width="600" height="400" border="0"></td></tr> +<tr><td><p class="figure">Figure 2 &mdash; Slab material layers</p></td></tr> +</table> + The _IfcSlab_, as any subtype of _IfcBuildingElement_, may participate alternatively in one of the two different containment relationships: @@ -11672,17 +12093,45 @@ The representation identifier and type of this representation of _IfcSite_ is: - The following additional constraints apply to the swept solid representation: + The following constraints apply to the 'SweptSolid' representation: * **Solid**: _IfcExtrudedAreaSolid_ is required, -* **Profile**: _IfcArbitraryClosedProfileDef, IfcRectangleProfileDef, IfcCircleProfileDef, IfcEllipseProfileDef_ shall be supported. +* **Profile**: _IfcArbitraryClosedProfileDef, IfcRectangleProfileDef, IfcCircleProfileDef , IfcEllipseProfileDef_ shall be supported. * **Extrusion**: The profile can be extruded perpendicularly or non-perpendicularly to the plane of the swept profile. Figure 1 illustrates a 'SweptSolid' geometric representation. > NOTE&nbsp; The following interpretation of dimension parameter applies for polygonal slabs (in ground floor view): > * _IfcArbitraryClosedProfileDef.OuterCurve_: closed bounded curve interpreted as area (or foot print) of the slab. -!["standard slab"](../../figures/ifcslab_standard-layout1.gif "Figure 1 &mdash; Slab body extrusion") +!["standard slab"](../../figures/ifcslab_standard-layout1.gif "Figure 1 &mdash; Slab body extrusion") + +The following additional constraints apply to the 'SweptSolid' representation, when an _IfcMaterialLayerSetUsage_ is assigned to the _IfcSlab_: + +* **Solid**: _IfcExtrudedAreaSolid_ is required, +* **Profile**: _IfcArbitraryClosedProfileDef_, _IfcRectangleProfileDef_, _IfcCircleProfileDef_, _IfcEllipseProfileDef_ shall be supported. +* **Extrusion**: The profile can be extruded perpendicularly or non-perpendicularly to the plane of the swept profile. +* **Material**: The definition of the _IfcMaterialLayerSetUsage_, particularly of the _OffsetFromReferenceLine_ and the _ForLayerSet.TotalThickness_, has to be consistent to the 'SweptSolid' representation. + +&nbsp; + +<table> + +<tr> + <td><img src="../../figures/ifcslab_standard-layout1.gif" alt="standard slab" border="0" height="274" width="399"></td> + <td> + +<blockquote class="example">EXAMPLE&nbsp; Figure 2 illustrates a 'SweptSolid' geometric representation. The following interpretation of dimension parameter applies for polygonal slabs (in ground floor view): + <em>IfcArbitraryClosedProfileDef.OuterCurve</em>: closed bounded curve interpreted as area (or foot print) of the slab.</blockquote> + +</td> + </tr> + + <tr> + <td><p class="figure">Figure 2 &mdash; Slab body extrusion</p></td> + <td>&nbsp;</td> + </tr> + +</table> @@ -11695,28 +12144,37 @@ Figure 1 illustrates a 'SweptSolid' geometric representation. Figure 1 illustrates a 'Clipping' geometric representation with definition of a roof slab using advanced geometric representation. The profile is extruded non-perpendicular and the slab body is clipped at the eave. -!["advanced slab"](../../figures/ifcslab_advanced-layout1.gif "Figure 1 &mdash; Slab body clipping") +!["advanced slab"](../../figures/ifcslab_advanced-layout1.gif "Figure 1 &mdash; Slab body clipping") + +The following constraints apply to the 'Clipping' representation, when an _IfcMaterialLayerSetUsage_ is assigned to the _IfcSlab_: + +* **Solid**: see 'SweptSolid' shape representation, +* **Profile**:&nbsp;see 'SweptSolid' shape representation, +* **Extrusion**:&nbsp;see 'SweptSolid' shape representation, +* **Material**:&nbsp;see 'SweptSolid' shape representation, +* **Boolean result**: The _IfcBooleanClippingResult_ shall be supported, allowing for Boolean differences between the swept solid (here _IfcExtrudedAreaSolid_) and one or several _IfcHalfSpaceSolid_. + +&nbsp; + +<table> + + <tr> + <td><img src="../../figures/ifcslab_advanced-layout1.gif" alt="advanced slab" border="0" height="274" width="399"></td> + <td> + +<blockquote class="example">EXAMPLE&nbsp; Figure 2 illustrates a 'Clipping' geometric representation with definition of a roof slab using advanced geometric representation. The profile is extruded non-perpendicular and the slab body is clipped at the eave.</blockquote> + +</td> + </tr> + + <tr> + <td><p class="figure">Figure 2 &mdash; Slab body clipping</p></td> + <td>&nbsp;</td> + </tr> + +</table> - - - - - Indicates a partial recess or full opening that may or may not be filled by another element. - - - - - - - - An idealized structural member corresponding to the slab. - - - A task for operating on the slab. - - - @@ -12136,20 +12594,20 @@ The shared material layer set definition is defined by assigning an _IfcMaterial - - - - - - - - - - - - - - + + + + + + + + + + + + + + @@ -12162,10 +12620,13 @@ The shared material layer set definition is defined by assigning an _IfcMaterial - + - + + + + The local placement for _IfcSpace_ is defined at its supertype _IfcProduct_. It is defined by the _IfcLocalPlacement_, which defines the local coordinate system that is referenced by all geometric representations. * The _PlacementRelTo_ relationship of _IfcLocalPlacement_ shall point to the local placement of the _IfcSpatialStructureElement_ of type _IfcBuildingStorey_ or _IfcSite_ if relative placement is used. @@ -13222,13 +13683,13 @@ The local coordinate system is established by the reference surface given by top - - - - - - - + + + + + + + @@ -13428,11 +13889,11 @@ A top-level task is declared within the _IfcProject_ using the _IfcRelDeclares_ An _IfcTask_ may be assigned a Work Breakdown Structure (WBS) code. A WBS code is dealt with as a classification of task and is associated to a task occurrence using the _IfcRelAssociatesClassification_ relationship class. As well as being to designate the code, the classification structure also enables the source of the work breakdown structure classification to be identified. - + Constraints may be applied to a task to indicate fixed task duration, fixed start or fixed finish, where _IfcMetric_.ReferencePath is set to the corresponding attribute on the _IfcTaskTime_ entity. - + Indicate fixed duration of task with ConstraintGrade=HARD and Benchmark=EQUALTO such that changes to an assigned _IfcConstructionResource.ResourceTime.ScheduleWork_ should impact _IfcConstructionResource.ResourceTime.ScheduleUsage_, and vice-versa. @@ -14313,11 +14774,41 @@ shown above.</li> - The material of the _IfcWall_ is defined by _IfcMaterialLayerSet_, or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcWallType_. - -> NOTE&nbsp; It is illegal to assign an _IfcMaterialLayerSetUsage_ to an _IfcWall_. Only the subtype _IfcWallStandardCase_ supports this concept. + The material information of the _IfcWall_ is defined by _IfcMaterialLayerSet_, or as fallback by _IfcMaterial_, and it is attached either directly or at the _IfcWallType_. In this case, the material information does not allow to construct a shape by applying the layer definition to the axis representation, to enable this parametric definition, the _IfcMaterialLayerSetUsage_ has to be used instead. + + The material of _IfcWall_ can be defined by _IfcMaterialLayerSetUsage_ and attached by _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. Multi-layer walls can be represented by refering to several _IfcMaterialLayer_'s within the _IfcMaterialLayerSet_ that is referenced from the _IfcMaterialLayerSetUsage_. + +When assigning an _IfcMaterialLayerSetUsage_ to _IfcWall_ it shall imply that the _IfcWallType_ should have a unique _IfcMaterialLayerSet_, that is referenced by _IfcMaterialLayerSetUsage_ assigned to all occurrences of this _IfcWallType_. + +<table> + +<tr> + <td><img src="../../figures/ifcwall_materialusage-01.png" alt="Material layer set and usage" height="220" width="501"></td> + <td><blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates assignment of <em>IfcMaterialLayerSetUsage</em> and <em>IfcMaterialLayerSet</em> to the wall type and the wall occurrence.</blockquote></td> + </tr> + + <tr> + <td><p class="figure">Figure 1 &mdash; Wall Standard Object Typing</p></td> + <td>&nbsp;</td> + </tr> + +</table> + +Figure 2 illustrates material layer usage, where the following conventions shall be met: + +* The reference coordinate system is the local coordinate system established by the _ObjectPlacement_ of the _IfcWallStandardCase_. +* The reference axis is the axis defined by the _IfcShapeRepresentation_ with _RepresentationType_='Axis' as one of the _Representation.Representations_ of the _IfcWallStandardCase_. +* The _IfcMaterialLayerSetUsage.OffsetFromReferenceLine_ is given as a distance from this axis. +* The _IfcMaterialLayerSetUsage.OffsetFromReferenceLine_ is the distance parallel to the reference axis and always within the base (XY) plane of the reference coordinate system. A positve value of _IfcMaterialLayerSetUsage_.OffsetFromReferenceLine would then point into the positive y-axis of the reference coordinate system. +* The _IfcMaterialLayerSetUsage_.DirectionSense defines how the _IfcMaterialLayer_'s are assigned to the reference axis. POSITIVE means in direction to the positive y-axis of the reference coordinate system. +* The _Thickness_ of each _IfcMaterialLayer_ is provided starting from the _OffsetFromReferenceLine_ and in the direction given by _DirectionSense_. It is applied without any gap or overlap between two consecutive layers. The _TotalThickness_ of the _IfcMaterialLayerSet_ is the sum of all layer thicknesses. +* The _IfcMaterialLayerSetUsage.LayerSetDirection_ is always AXIS2. + +!["wall material layer set"](../../figures/ifcmateriallayersetusage_wall-01.png "Figure 2 &mdash; Wall material layers") + + @@ -14345,7 +14836,50 @@ shown above.</li> - > NOTE&nbsp; The 'Axis' is not used to locate the material layer set, only the subtype _IfcWallStandardCase_ provides this capability. + The wall axis is represented by a two-dimensional open curve within a particular shape representation. The 'Axis' shape representation is only used to locate the material layer set along the axis, if the _IfcMaterialLayerSetUsgae_ is applied to the _IfcWall_. In this case, the wall axis is used to apply the material layer set usage parameter to the wall geometry. + +* _Axis_ + * _IfcPolyline_ having two _Points_, or _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcLine_ for the 'SweptSolid' provided as _IfcExtrudedAreaSolid_. The axis curve lies on the x/y plane and is parallel to the x-axis of the object coordinate system. + * _IfcTrimmedCurve_ with _BasisCurve_ of Type _IfcCircle_ for 'SweptSolid' provided as _IfcExtrudedAreaSolid_. The axis curve lies on the x/y plane of the object coordinate system, the tangent at the start is along the positive x-axis. + +&nbsp; + +<table cellpadding="2" cellspacing="2"> + + <tr> + + <td align="left" valign="top"><img src="../../figures/ifcwallstandard_straigthwall_01-layout1.gif" alt="straight wall axis" border="0" height="299" width="393"></td> + + <td><blockquote class="example">EXAMPLE&nbsp; Figure 1 illustrates an axis representation for a straight wall. In case of a straight wall, the set of items shall +include a single geometric representation item of type <em>IfcPolyline</em> or <em>IfcTrimmedCurve</em> with the <em>BasisCurve</em> being an <em>IfcLine</em>. The <em>IfcPolyline</em> or <em>IfcTrimmedCurve</em> shall be parallel (here in a special case co-linear) to the x-axis +of the object coordinate system. The direction shall be identical to the direction of the x-axis.</blockquote> + + </td> + </tr> + <tr> + <td width="393"><p class="figure">Figure 1 &mdash; Wall axis straight</p></td> + + <td>&nbsp;</td> + </tr> +</table> + +<table cellpadding="2" cellspacing="2"> + + <tr> + + <td align="left" valign="top"><img src="../../figures/ifcwallstandard_curvedwall_01-layout1.gif" alt="curved wall axis" border="0" height="299" width="393"></td> + + <td><blockquote class="example">EXAMPLE&nbsp; Figure 2 illustrates an axis representation for a curved wall. In case of a curved wall, the set of items shall include +a single geometric representation item of type <em>IfcTrimmedCurve</em>. The curve shall have a <em>BasisCurve</em> of type <em>IfcCircle</em>. The tangent of the <em>IfcTrimmedCurve</em> shall be parallel at start to the x-axis of the object coordinate system. The direction shall be identical to the direction of the x-axis.</blockquote> + </td></tr> + +<tr> + <td width="393"><p class="figure">Figure 2 &mdash; Wall axis curved</p></td> + <td>&nbsp;</td> + +</tr> + +</table> @@ -14364,31 +14898,72 @@ shown above.</li> * **Profile**: _IfcArbitraryClosedProfileDef_ is required. * **Extrusion**: All extrusion directions shall be supported. -> NOTE&nbsp; If the wall body can be described by a vertical extrusion of a polygonal footprint with constant thickness along the axis (where vertical = into the direction of the global Z axis), the subtype _IfcWallStandardCase_ should be used. If the extrusion is not equal to global Z, then the _IfcWall_ should be used. +The following additional constraints apply to the 'SweptSolid' representation, when an _IfcMaterialLayerSetUsage_ is assigned to the _IfcSlab_: + +* **Solid**: _IfcExtrudedAreaSolid_ is required, +* **Profile**: _IfcArbitraryClosedProfileDef_ and _IfcRectangleProfileDef_ shall be supported. +* **Extrusion**: The profile shall be extruded vertically, i.e., in the direction of the z-axis of the co-ordinate system of the referred spatial structure element. It might be further constraint to be in the direction of the global z-axis in implementers agreements. The extrusion axis shall be perpendicular to the swept profile, i.e. pointing into the direction of the z-axis of the Position of the _IfcExtrudedAreaSolid_. + +The profile of a wall is described in the ground view and extruded vertically. The profile (also identical with the foot print of the wall) is defined by the _IfcArbitraryClosedProfileDef_ (excluding its subtypes). The profile is given with all wall connections already resolved. + +Figure 1 illustrates a body representation for a straight wall. In case of a straight wall, the two sides of the profile shall be parallel to the wall axis, that is, the wall has a single unchanged thickness. + +Figure 2 illustrates a body representation for a curved wall. In case of a curved wall, the two sides of the profile shall be parallel (with defined offset) to the wall axis, that is, the wall has a single unchanged thickness. + +<table cellpadding="2" cellspacing="2"> + +<tr> + + <td align="left" valign="top"><img src="../../figures/ifcwallstandard_straigthwall_02-layout1.gif" alt="straight wall body" border="0" height="299" width="393"></td> + + <td align="left" valign="top"><img src="../../figures/ifcwallstandard_curvedwall_02-layout1.gif" alt="curved wall body" border="0" height="299" width="393"></td> + + </tr> + + <tr> + +<td width="393"><p class="figure">Figure 1 &mdash; Wall body extrusion straight</p></td> + + <td width="393"><p class="figure">Figure 2 &mdash; Wall body extrusion curved</p></td> + +</tr> + +</table> + The following additional constraints apply to the 'SweptSolid' representation, when an _IfcMaterialLayerSetUsage_ is assigned to the _IfcSlab_: + +* **Solid**: see standard geometric representation +* **Profile**: see standard geometric representation +* **Extrusion**: see standard geometric representation +* **Boolean result**: The _IfcBooleanClippingResult_ shall be supported, allowing for Boolean differences between the swept solid (here _IfcExtrudedAreaSolid_) and one or several _IfcHalfSpaceSolid_ (or subtypes). + +Figure 1 illustrates a clipping for a straight wall using an _IfcPolygonalBoundedHalfSpace_ as _SecondOperand_ in the _IfcBooleanClippingResult_. + +Figure 2 illustrates a clipping for a curved wall using an _IfcHalfSpaceSolid_ as _SecondOperand_ in the _IfcBooleanClippingResult_. + +<table cellpadding="2" cellspacing="2"> + + <tr> + + <td><img src="../../figures/ifcwallstandard_straigthwall_03-layout1.gif" alt="straight wall clipping" border="0" height="299" width="397"></td> + +<td><img src="../../figures/ifcwallstandard_curvedwall_03-layout1.gif" alt="curved wall clipping" border="0" height="300" width="400"></td> + + </tr> + +<tr> + +<td width="397"><p class="figure">Figure 1 &mdash; Wall body clipping straight</p></td> + +<td width="400"><p class="figure">Figure 2 &mdash; Wall body clipping curved</p></td> + +</tr> + +</table> - - - - - Indicates a partial recess or full opening, which may or may not be filled by another element. - - - - - - - - An idealized structural member corresponding to the wall. - - - A task for operating on the wall. - - - @@ -14686,11 +15261,11 @@ The shared material layer set definition is defined by assigning an _IfcMaterial - - - - - + + The _IfcWindowTypePartitioningEnum_ defines the general layout of the window type and its symbolic presentation. Depending on the enumerator, the appropriate instances of _IfcWindowLiningProperties_ and _IfcWindowPanelProperties_ are attached in the list of _HasPropertySets_. The _IfcWindowTypePartitioningEnum_ mainly determines the way of partitioning the window into individual window panels and thereby number and position of window panels. + +See _IfcWindowTypePartitioningEnum_ for the correct usage of panel partitioning and _IfcWindowPanelProperties_ for the opening symbols for different panel operation types. + @@ -14728,14 +15303,25 @@ The shared material layer set definition is defined by assigning an _IfcMaterial + + + + + + - - The material of the _IfcWindow_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. + + The material of the _IfcWindow_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial__. +It is accessible by the inverse _HasAssociations_ relationship. The following keywords for _IfcMaterialConstituentSet.MaterialConstituents[n].Name_ shall be used:_ + +* 'Lining' - to indicate that the material constituent applies to to the window lining +* 'Framing' - to indicate that the material constituent applies to to the window panels, if not provided, the 'Lining' material information applied to panels as well +* 'Glazing' - to indicate that the material constituent applies to to the glazing part If the fall back single _IfcMaterial_ is referenced, it applies to the lining and framing of the window. @@ -14781,7 +15367,7 @@ The _IfcWindow_ may also be connected to the _IfcOpeningElement_ in which it is - + The following restriction is imposed: 1. The _PlacementRelTo_ relationship of _IfcLocalPlacement_ shall point to the local placement of the same element (if given), in which the _IfcWindow_ is used as a filling (normally an _IfcOpeningElement_), as provided by the _IfcRelFillsElement_ relationship. @@ -14791,7 +15377,7 @@ The _IfcWindow_ may also be connected to the _IfcOpeningElement_ in which it is > NOTE&nbsp; The product placement is used to determine the opening direction of the window. - + The window profile is represented by a three-dimensional closed curve within a particular shape representation. The profile is used to apply the parameter of the parametric window representation. The following attribute values for the _IfcShapeRepresentation_ holding this geometric representation shall be used: * _RepresentationIdentifier_ : 'Profile' @@ -14802,13 +15388,22 @@ A 'Profile' representation has to be provided if: * a parametric representation shall be applied to the window AND * * the window is 'free standing', or - * the opening into which the window is inserted is not extruded horizontally (i.e. where the opening profile does not match the window profile) - - - - - - + * the opening into which the window is inserted is not extruded horizontally (i.e. where the opening profile does not match the window profile) + +The following additional constraints apply to the 'Profile' representation type: + +* **Curve**: being an _IfcPolyline_ defining a rectangle. +* **Position**: The curve shall lie in the xz plane of the object placement coordinate (the y coordinate values of the _IfcCartesianPoint_'s shall be 0.). + +As shown in Figure 1, the profile defines the outer boundary to which the window lining parameters relate as: + +* _IfcWindowLiningProperties.LiningDepth_ starting at distance defined by _LiningOffset_ going into the positive y direction. +* _IfcWindowLiningProperties.LiningThickness_ offset into the inner side of the rectangle. +* _IfcWindowLiningProperties.LiningOffset_ distance along the positive y direction to where the _LiningDepth_ applies. +* _IfcWindowLiningProperties.FirstTransomOffset_ starting at the bottom edge of the rectangle (along local x axis) into the inner side of the rectangle, distance provided as percentage of overall height. Distance to the centre line of the transom. _SecondTransomOffset_ defined accordingly. +* _IfcWindowLiningProperties.FirstMullionOffset_ starting at the left edge of the rectangle (along local z-axis) into the inner side of the rectangle, distance provided as percentage of overall width. Distance to the centre line of the mullion. _SecondMullionOffset_ defined accordingly. + +!["standard window"](../../figures/ifcwindowstandardcase-01.png "Figure 1 &mdash; Window profile") diff --git a/ModelViews/Reference View/DocModelView.xml b/ModelViews/Reference View/DocModelView.xml index 01dfbfb00..9f65c1403 100644 --- a/ModelViews/Reference View/DocModelView.xml +++ b/ModelViews/Reference View/DocModelView.xml @@ -1,7 +1,8 @@  - + + Data exchange requirements indicate required and optional values that may be set on object attributes, organized into concepts. The table that follows lists each entity, concepts applicable to each entity (and any subtypes within scope), and requirements of the concept for import (I) or export (E). Requirements for import and export are indicated using one of the following flags: @@ -27,6 +28,7 @@ General requirements of software implementing the Reference Exchange: * If an application supports both Reference View and Design Transfer View, then it must provide the user an option to choose which to export and display the following text to the user (localized accordingly): "Reference View contains simplified geometry designed for viewing within the widest range of applications. Design Transfer View contains higher-level geometry designed for editing within design applications.". There is no requirement where such choice may be made; i.e. such option could be available every time the user exports a file, or such option could be a general application setting. "089504E470D0A1A0A0000000D4948445200000010000000100802000000909168360000000467414D410000B18F0BFC6105000000097048597300000EC300000EC301C76FA8640000006049444154384F95D2D10D00100C0450B512933187CDEC4485A4D150C7779F6B93231792FB799E875B2D3819E0CB2C801B01A0D900620450CCC83D5B0262F44A4FA3016F659B03B0CD1918E60A6E86B87C6097E66D56826AE4FC7724E055E5C90E4E1D281D264C695B0000000049454E44AE426082" + @@ -39,53 +41,53 @@ General requirements of software implementing the Reference Exchange: - + - + - + - + - - + + - + - - - + + + - + - + - - + + - + - + - - + + @@ -100,7 +102,7 @@ General requirements of software implementing the Reference Exchange: - + @@ -120,79 +122,79 @@ General requirements of software implementing the Reference Exchange: - + - + - + - + - - + + - + - + - + - + - - - - - - - - - - - - - - + + + + + + + + + + + + + + - + - - - - - - - - - + + + + + + + + + - + - - + + - + - + @@ -207,19 +209,19 @@ General requirements of software implementing the Reference Exchange: - + - + - + @@ -239,46 +241,46 @@ General requirements of software implementing the Reference Exchange: - + - + - + - + - - - - - - - - + + + + + + + + - + - - - + + + - + - - - - + + + + @@ -293,7 +295,7 @@ General requirements of software implementing the Reference Exchange: - + @@ -313,38 +315,38 @@ General requirements of software implementing the Reference Exchange: - + - + - + - + - - + + - + - - + + - + - - - + + + @@ -359,7 +361,7 @@ General requirements of software implementing the Reference Exchange: - + @@ -379,34 +381,34 @@ General requirements of software implementing the Reference Exchange: - + - + - + - + - + - + - + - + - + @@ -421,7 +423,7 @@ General requirements of software implementing the Reference Exchange: - + @@ -431,52 +433,6 @@ General requirements of software implementing the Reference Exchange: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -487,35 +443,35 @@ General requirements of software implementing the Reference Exchange: - + - + - + - + - + - + - + - + - - + + @@ -530,7 +486,7 @@ General requirements of software implementing the Reference Exchange: - + @@ -546,38 +502,38 @@ General requirements of software implementing the Reference Exchange: - + - + - - - - - - - - + + + + + + + + - + - + - + - + - - - - + + + + @@ -592,30 +548,30 @@ General requirements of software implementing the Reference Exchange: - + - - - - + + + + - - + + - - + + @@ -623,10 +579,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -637,10 +593,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -661,49 +617,49 @@ General requirements of software implementing the Reference Exchange: - + - + - + - + - - - - - - + + + + + + - + - - - + + + - + - - - + + + - + - + @@ -718,14 +674,14 @@ General requirements of software implementing the Reference Exchange: - - + + - + @@ -743,10 +699,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -778,10 +734,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -795,10 +751,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -806,94 +762,94 @@ General requirements of software implementing the Reference Exchange: The following standard property sets are defined for _IfcBuilding_. - + - + - - - - - - - - - - - - - - + + + + + + + + + + + + + + - + - + - - - - - - + + + + + + - + - - - - + + + + - + - - + + - + - + - - - - + + + + - + - + - - - - - - - - - - + + + + + + + + + + - + - + @@ -909,23 +865,23 @@ General requirements of software implementing the Reference Exchange: - - + + - - - + + + - - + + @@ -933,10 +889,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -956,10 +912,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -988,10 +944,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -999,10 +955,10 @@ General requirements of software implementing the Reference Exchange: - + - + @@ -1015,22 +971,22 @@ General requirements of software implementing the Reference Exchange: - + - + - - - - - + + + + + - + - + @@ -1045,8 +1001,8 @@ General requirements of software implementing the Reference Exchange: - - + + @@ -1101,10 +1057,10 @@ _IfcBuildingStorey_ needs to have a different and higher - + - + @@ -1120,29 +1076,29 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - - - - - - - - + + + + + + + + @@ -1157,23 +1113,23 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - - - + + + - - + + - - + + @@ -1181,10 +1137,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -1199,10 +1155,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -1224,12 +1180,12 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + @@ -1252,29 +1208,29 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - - + + @@ -1289,7 +1245,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -1309,28 +1265,28 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - + @@ -1345,7 +1301,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -1365,28 +1321,28 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - + @@ -1401,20 +1357,20 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - - + + @@ -1434,28 +1390,28 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - + @@ -1470,7 +1426,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -1490,61 +1446,61 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - - - - - - - - - - - + + + + + + + + + + + - + - - + + - + - + - + - + - + @@ -1559,20 +1515,20 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - - + + @@ -1592,42 +1548,42 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - - - - - - - + + + + + + + - + - + - + - - - + + + @@ -1642,7 +1598,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -1658,23 +1614,23 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - - - - - - + + + + + + - + - + @@ -1689,7 +1645,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -1697,10 +1653,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -1711,10 +1667,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -1749,86 +1705,86 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - + - - - - + + + + - + - - + + - + - - + + - + - + - + - + - - - + + + - + - - - - - - - + + + + + + + - + - - + + @@ -1843,7 +1799,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -1859,46 +1815,46 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - - - - - - - + + + + + + + - + - + - + - + - - - - - - - + + + + + + + - + - + @@ -1913,30 +1869,30 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - - - - + + + + - - + + - - + + @@ -1944,10 +1900,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -1958,10 +1914,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -1982,28 +1938,28 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - + @@ -2018,7 +1974,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2038,38 +1994,38 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - - - - - - - - - + + + + + + + + + - + - - - + + + @@ -2084,7 +2040,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2104,34 +2060,35 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - - - - - - - + + + + + + + - + - + + @@ -2146,7 +2103,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2166,28 +2123,28 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - + @@ -2202,7 +2159,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2222,52 +2179,52 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - + - - - - + + + + - + - + @@ -2282,7 +2239,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2302,41 +2259,41 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - - - - - - - - - + + + + + + + + + - + - - - - - - + + + + + + @@ -2351,7 +2308,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2367,27 +2324,27 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - - - - - - - - - - + + + + + + + + + + - + - + @@ -2402,14 +2359,14 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - - + + @@ -2417,10 +2374,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -2431,10 +2388,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -2450,24 +2407,24 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - - - - - - - + + + + + + + - + - + @@ -2482,16 +2439,16 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - - - + + + - - + + @@ -2499,10 +2456,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -2513,10 +2470,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -2533,70 +2490,70 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + - + - + - - - - - - - - - - - - - - + + + + + + + + + + + + + + - + - - - - - - + + + + + + - + - + - + - - - + + + @@ -2611,7 +2568,7 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + @@ -2631,10 +2588,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -2645,10 +2602,10 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + @@ -2667,18 +2624,18 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - + - + - + - + - + @@ -2693,15 +2650,15 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - - + + - - + + @@ -2718,50 +2675,54 @@ Elements can also be referenced in an _IfcBuildingStorey_, for example, if they - - - - - - - - - - - - + - + - - - + + + - + - - - - + + + + + - + - - + + + + + + + + + + + + + + + + @@ -2801,23 +2762,23 @@ Figure 1 illustrates distribution port connectivity. - + - + - + - + - - + + @@ -2841,12 +2802,12 @@ Figure 1 illustrates distribution port connectivity. - + - + - + @@ -2884,46 +2845,8 @@ Figure 1 illustrates a distribution system for an electrical circuit. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The opening direction is determined by the local placement of _IfcDoor_ and the _OperationType_ of the _IfcDoorType_ as shown in Figure 1. + The opening direction is determined by the local placement of _IfcDoor_ and the _OperationType_ of the _IfcDoorType_ as shown in Figure 1. The _IfcDoorTypeOperationEnum_ defines the general layout of the door type and its symbolic presentation. Depending on the enumerator, the appropriate instances of _IfcDoorLiningProperties_ and _IfcDoorPanelProperties_ are attached in the list of _HasPropertySets_. The _IfcDoorTypeOperationEnum_ mainly determines the hinge side (left hung, or right hung), the operation (swinging, sliding, folding, etc.) and the number of panels. > NOTE&nbsp; There are different definitions in various countries on what a left opening or left hung or left swing door is (same for right). Therefore the IFC definition may derivate from the local standard and need to be mapped appropriately. @@ -3036,6 +2959,44 @@ pictures).</small></td> > NOTE&nbsp; The _OverallWidth_ and _OverallHeight_ parameters are for informational purpose only. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3044,15 +3005,15 @@ pictures).</small></td> - - - + + + - + @@ -3060,10 +3021,10 @@ pictures).</small></td> - + - + @@ -3074,15 +3035,23 @@ pictures).</small></td> - + - + - The material of the _IfcDoor_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_ relationship. + The material of the _IfcDoor_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_ relationship. It is accessible by the inverse _HasAssociations_ relationship. + +The following keywords for _IfcMaterialConstituentSet.MaterialConstituents[n].Name_ shall be used: + +* 'Lining' - to indicate that the material constituent applies to to the door lining +* 'Framing' - to indicate that the material constituent applies to to the door framing, if not provided, the 'Lining' material information applied to frams as well +* 'Glazing' - to indicate that the material constituent applies to to the glazing as well + +If the fall back single _IfcMaterial_ is referenced, it applies to the lining and framing of the door. @@ -3098,48 +3067,48 @@ pictures).</small></td> - + - + - + - + - - - + + + - + - + - - + + - + - + - + - - + + @@ -3154,21 +3123,21 @@ pictures).</small></td> - + - - - + + + - + @@ -3188,54 +3157,54 @@ pictures).</small></td> - + - + - + - + - - - + + + - + - + - - - - - - - + + + + + + + - + - - + + - + - - + + @@ -3250,21 +3219,21 @@ pictures).</small></td> - + - - - + + + - + @@ -3284,40 +3253,40 @@ pictures).</small></td> - + - + - + - + - - - - - + + + + + - + - + - + - - - + + + @@ -3332,7 +3301,7 @@ pictures).</small></td> - + @@ -3352,28 +3321,28 @@ pictures).</small></td> - + - + - + - + - + - + - + @@ -3388,7 +3357,7 @@ pictures).</small></td> - + @@ -3408,39 +3377,39 @@ pictures).</small></td> - + - + - + - + - - + + - + - + - + - + - + @@ -3455,13 +3424,13 @@ pictures).</small></td> - + - + @@ -3481,49 +3450,53 @@ pictures).</small></td> - + - + - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + - - + + - + - + @@ -3538,7 +3511,7 @@ pictures).</small></td> - + @@ -3558,31 +3531,31 @@ pictures).</small></td> - + - + - + - + - - - - + + + + - + - + @@ -3597,7 +3570,7 @@ pictures).</small></td> - + @@ -3617,38 +3590,38 @@ pictures).</small></td> - + - + - + - + - - - - - - - - - - + + + + + + + + + + - + - - + + @@ -3663,7 +3636,7 @@ pictures).</small></td> - + @@ -3683,28 +3656,28 @@ pictures).</small></td> - + - + - + - + - + - + - + @@ -3719,7 +3692,7 @@ pictures).</small></td> - + @@ -3736,134 +3709,146 @@ pictures).</small></td> - + - + - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + - + - + - + - + - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + - + - + - - - - + + + - + + + + + + + + + + + + + + - + - + - + - - - - - - + + + + + + - + - + - + - + - + - + - + - + - + - - - - - - - - + + + + + + + + @@ -3871,33 +3856,39 @@ pictures).</small></td> - + - + - Placement of elements is defined by a local placement (a transformation matrix relative to: + Placement of elements is defined by a local placement (a transformation matrix relative to): -* the spatial container (_IfcRelContainedInSpatialStructure_._RelatingSpatialStructure_) -* the parent aggregation element (_IfcRelAggregates_._RelatingObject_), if it is an aggregated part +* the spatial container (if not part of an assembly) + * provided by the relationship _IfcRelContainedInSpatialStructure_._RelatingSpatialStructure_ + * being a subtype of _IfcSpatialElement_, in most cases, _IfcBuildingStorey_ +* the parent aggregation element (if it is an aggregated part) + * provided by the relationship _IfcRelAggregates_._RelatingObject_ + * being a subtype of _IfcElement_ + +The local placement shall always be relative. - - Placement relative to the position and rotation of the container. + + Placement relative to the position and rotation of the spatial element. - - Absolute placement in the engineering coordinate system of the project. + + Placement relative to the position and rotation of the container element. - + - + @@ -3920,6 +3911,9 @@ pictures).</small></td> </table> + + + The default geometric representation of any _IfcElement_ within this model view is a single or multiple tessellated item. The supported tessellation is a triangulated face set, defined by indices into a Cartesian point list. Optionally normals per vertex can be included as well. @@ -3939,13 +3933,19 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + + + + + + + @@ -3956,10 +3956,10 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + @@ -3967,10 +3967,10 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + @@ -4006,29 +4006,29 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - + - + - - + + @@ -4054,45 +4054,45 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - - - + + + - + - - + + - + - + - + - - - + + + @@ -4107,7 +4107,7 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + @@ -4127,37 +4127,37 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - - - - - - - + + + + + + + - + - - - - + + + + @@ -4172,7 +4172,7 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + @@ -4192,70 +4192,70 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - - - - - + + + + + - + - - + + - + - + - - - - - - - + + + + + + + - + - - - + + + - + - + - + - - + + @@ -4270,7 +4270,7 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + @@ -4290,10 +4290,10 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + @@ -4304,10 +4304,10 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + @@ -4324,44 +4324,44 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - - - - - - - - - - + + + + + + + + + + - + - + - + - - + + @@ -4376,7 +4376,7 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + @@ -4396,28 +4396,28 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - + - + - + @@ -4432,7 +4432,7 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + @@ -4452,28 +4452,28 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - + - + - + @@ -4488,7 +4488,7 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + @@ -4508,40 +4508,40 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - + - + - + - - + + - + - - + + @@ -4556,7 +4556,7 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + @@ -4576,57 +4576,57 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - - + + - + - + - + - + - - - - - - + + + + + + - + - + - - - - + + + + @@ -4641,31 +4641,31 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - - - + + + - - - + + + - - + + - - + + @@ -4689,28 +4689,34 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + - + - + - - - - - - - + + + + + + + + + + + + + @@ -4721,10 +4727,10 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + @@ -4741,10 +4747,10 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + @@ -4752,10 +4758,10 @@ The same constraints, as given for 'Tessellation', 'SweptSolid&ap - + - + @@ -4862,29 +4868,29 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - + - + - - + + @@ -4899,7 +4905,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -4919,41 +4925,41 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - + + + + + - + - - - + + + - + - - + + @@ -4968,7 +4974,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -4988,36 +4994,36 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - - - - - + + + + + + + + + - + - + @@ -5032,7 +5038,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -5052,35 +5058,35 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - + + + + + - + - - - - + + + + @@ -5095,13 +5101,13 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -5121,42 +5127,42 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - - - + + + + + + + - + - - - + + + - + - + @@ -5171,7 +5177,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -5191,36 +5197,36 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - - - + + + + + + + - + - - - + + + @@ -5235,7 +5241,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -5248,34 +5254,74 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - - - - - + + + + + - + - + - - - - - + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + - + @@ -5292,28 +5338,28 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - + - + - + @@ -5339,35 +5385,35 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - - - - + + + + + + + + - + - + @@ -5382,30 +5428,30 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - - - - + + + + - - + + - - + + @@ -5413,10 +5459,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -5436,28 +5482,28 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - + - + - + @@ -5472,7 +5518,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -5482,7 +5528,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -5494,10 +5540,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -5629,6 +5675,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a + + Any object occurrence can hold property sets, either directly at the object occurrence as element specific property sets, or at the object type, as type property sets. In this case, the properties that are provided to the object occurrence are the combinations of element specific and type properties. In case, that the same property (within the same property set, is defined both, in occurrence and type properties, the property value of the occurrence property overrides the property value of the type property. + + @@ -5637,7 +5687,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a Any object occurrence or object type can have a reference to a specific classification reference, i.e. to a particular facet within a classification system. - + @@ -5645,39 +5695,48 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - - The local placement for _IfcOpeningElement_ is defined in its supertype _IfcProduct_. It is defined by the _IfcLocalPlacement_, which defines the local coordinate system that is referenced by all geometric representations. - -* The _PlacementRelTo_ relationship of _IfcLocalPlacement_ should point to the local placement of the same element, which is voided by the opening, i.e. referred to by _VoidsElement_._RelatingBuildingElement_. - - - - - - + - + - - - - + + + + - + - + + + Placement of elements is defined by a local placement (a transformation matrix relative to): + +* the element that is voided (if it is an aggregated part) + * provided by the relationship _VoidsElement_._RelatingBuildingElement_ + * being a subtype of _IfcElement_ + +The local placement shall always be relative. + + + + Placement relative to the position and rotation of the element being voided. + + + + + + Since there are no Boolean operations, either as _IfcBooleanResult_ or implicitly by _IfcRelVoidsElement_ the geometry of the _IfcOpeningElement_ shall not be used to subtract the opening from the 'Body' shape representation of the voided element. @@ -5694,27 +5753,54 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - - - + + + - + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -5728,30 +5814,30 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - + + + - + - + @@ -5766,7 +5852,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -5786,29 +5872,29 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - + + - + - + @@ -5823,29 +5909,29 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - - - + + + - - + + - - + + @@ -5869,48 +5955,48 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - + + - + - + - - - + + + - + - + - + - - + + @@ -5925,22 +6011,22 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - - - + + + - - + + @@ -5960,69 +6046,69 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - - - - + + + + + + + + - + - + - - - - + + + + - + - + - - - - - + + + + + - + - + - + - - + + @@ -6037,22 +6123,22 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - - - + + + - - + + @@ -6072,33 +6158,33 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - - + + + + + + - + - + @@ -6113,29 +6199,29 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - - + + - - + + - - + + - - + + @@ -6143,10 +6229,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -6157,15 +6243,6 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - - - - - - - - - @@ -6181,10 +6258,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -6195,31 +6272,32 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a Main representation context for all sub contexts defining geometric representations in 3D coordinate space. - + Main representation subcontext for all 3D body geometry of model elements - + Representation subcontext for curve-based axis representation of model elements (wall axis, beam axis, etc.) - + - + - - - - - + + The representation context of the project refers to a global positioning, i.e. the local engineering coordinate system of the project has a mapping to a defined projected coordinate system (a rectangular map coordinate system, as used in GIS systems) + + + + The _IfcProject_ is used to reference the root of the spatial structure of a building or other construction project (that serves as the primary project breakdown and is required to be hierarchical). The spatial structure elements are linked together, and to the _IfcProject_, by using the objectified relationship _IfcRelAggregates_. @@ -6239,136 +6317,16 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -6379,158 +6337,158 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - + - + - + - + - + - + - + - + - + - - + + - + - + - + - + - + - + - + - + - + - + - + - + - + - - - - + + + + - + - + - + - + - - - - - - - - - - - - - + + + + + + + + + + + + + - + - + - + - + - + - + - + - + - + - + @@ -6545,7 +6503,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -6565,186 +6523,186 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + - + - + - - - - - - - - - - - - - - + + + + + + + + + + + + + + - + - + - - - - - - - - - + + + + + + + + + - + - + - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + - + - + - + - + - + - + - - + + - + - + - + - + - - + + - + - + - + - - - + + + - + - + - + - + - - - - - - + + + + + + - + - + @@ -6759,7 +6717,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -6779,56 +6737,56 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - + - + - - + + - + - + - - - - + + + + - + - + - + - - - + + + @@ -6843,7 +6801,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -6863,31 +6821,31 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - + + + + - + - + @@ -6902,7 +6860,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + @@ -6910,10 +6868,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -6934,35 +6892,37 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - - - - + + + + + + + + + + - + - + @@ -6973,10 +6933,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -7001,32 +6961,32 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - + + + + + - + - + @@ -7041,22 +7001,22 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - - + + - - + + - - + + @@ -7064,10 +7024,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -7097,22 +7057,45 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - - + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - @@ -7121,7 +7104,7 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a The default geometric item to exchange the body shape representation of reinforcing elements is the _IfcSweptDiskSolid_ using the _IfcIndexedPolyCurve_ to describe the _Directrix_. - + The various subtypes of _IfcReinforcingElement_ do not support the concept of voiding - there shall no voids (openings, cut-outs, recesses) being defined as shape features for reinforcing elements. @@ -7135,21 +7118,24 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + + + + @@ -7167,22 +7153,49 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - - + + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - @@ -7196,32 +7209,33 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + - + - + - - - - - + + + + + + - + - + @@ -7236,9 +7250,9 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - - - + + + @@ -7246,10 +7260,10 @@ As shown in Figure 31, the <em>IfcGrid</em> defines a - + - + @@ -7279,10 +7293,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7299,22 +7313,32 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + - + - + - + + + + + + + + + + + @@ -7329,7 +7353,7 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + @@ -7349,28 +7373,28 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + - + - + - + - + - + @@ -7385,7 +7409,7 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + @@ -7405,38 +7429,38 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + - + - + - - - - - - - - - - + + + + + + + + + + - + - - + + @@ -7447,10 +7471,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7464,10 +7488,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7499,10 +7523,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7515,39 +7539,39 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + - + - + - - - + + + - + - + - - - - - - + + + + + + @@ -7562,13 +7586,13 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7576,10 +7600,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7590,10 +7614,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7619,77 +7643,77 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + - + - + - - - - - - - - - - + + + + + + + + + + - + - + - + - + - - - - - - - - + + + + + + + + - + - + - - - - - - - - - - - - - - + + + + + + + + + + + + + + @@ -7704,31 +7728,31 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - - - - + + + + - - + + - - + + - - + + @@ -7736,10 +7760,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7760,28 +7784,30 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + - + - + - + + + - + - + @@ -7796,13 +7822,13 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7827,83 +7853,85 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + - - - - - - + + + + + + - + - + - - - - - - - - - - - - + + + + + + + + + + + + + + - + - + - - - - - - - - - - - - - + + + + + + + + + + + + + - + - + - - - - - - - - - - - - - - + + + + + + + + + + + + + + @@ -7918,29 +7946,29 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - - - - - + + + + + - - - - - - + + + + + + - - + + @@ -7948,10 +7976,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -7971,10 +7999,10 @@ Figure 1 illustrates roof placement, with an _IfcRoof_ defining the local placem - + - + @@ -8017,10 +8045,10 @@ foot print of <em>IfcSpace</em>.</blockquote></td> - + - + @@ -8060,39 +8088,39 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - - - - - - - + + + + + + + - + - - - - - - + + + + + + @@ -8107,14 +8135,14 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - - + + @@ -8133,33 +8161,33 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - - - - - - - + + + + + + + - + - + - - - - - - + + + + + + @@ -8175,28 +8203,28 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - - - - - - - - - - - + + + + + + + + + + + @@ -8246,28 +8274,28 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - + - + - + @@ -8282,7 +8310,7 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + @@ -8302,43 +8330,45 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + - + - + @@ -8349,10 +8379,10 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + @@ -8377,38 +8407,38 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - - - - - - - - - - - + + + + + + + + + + + - + - + @@ -8423,14 +8453,14 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - - + + @@ -8438,10 +8468,10 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + @@ -8456,15 +8486,6 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - - - - - - - - - @@ -8475,39 +8496,39 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - - - - - + + + + + - + - - + + - + - + @@ -8522,7 +8543,7 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + @@ -8532,6 +8553,33 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -8542,26 +8590,26 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - - - - - + + + + + @@ -8572,10 +8620,10 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + @@ -8592,58 +8640,58 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - + - + - - + + - + - + - - - - - - - - - - + + + + + + + + + + - + - - - - - + + + + + @@ -8658,14 +8706,14 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - - + + - + @@ -8685,22 +8733,36 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - - + + - + + + + + + + + + + + + + + + + + + - - - @@ -8714,17 +8776,32 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - - + + - + + + + + + + + + + + + + + + + @@ -8740,44 +8817,51 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + - + - + - + - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - + - - - + + + + + + + + + @@ -8792,7 +8876,7 @@ Figure 1 shows an extrusion of an arbitrary profile definition with voids into t - + @@ -8815,31 +8899,31 @@ If no _IfcTransportElementType_ is attached&nbsp;(i.e. if only occurrence in - + - + - + - + - - - - + + + + - + - + @@ -8850,10 +8934,10 @@ If no _IfcTransportElementType_ is attached&nbsp;(i.e. if only occurrence in - + - + @@ -8870,42 +8954,42 @@ If no _IfcTransportElementType_ is attached&nbsp;(i.e. if only occurrence in - + - + - + - + - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + - + - + @@ -8920,8 +9004,8 @@ If no _IfcTransportElementType_ is attached&nbsp;(i.e. if only occurrence in - - + + @@ -8933,20 +9017,6 @@ If no _IfcTransportElementType_ is attached&nbsp;(i.e. if only occurrence in - - - The _RepresentationMaps_ define the type product shape and multiple geometric representations can be assigned. If a product occurrence is assigned to the type by using the _IfcRelDefinesByType_ relationship, then these occurrences have to reference the representation maps. The reference is created by one or multiple _IfcShapeRepresentation_'s having an _IfcMappedItem_ as _Items_, that places the _IfcRepresentationMap_ of the type product into the spatial contexts, i.e. by using an Cartesian transformation operator to transform the _IfcRepresentationMap_ into the object coordinate system of the product occurrence. - -Figure 1 illustrates an example of referencing a representation map by the shape representation of a product occurrence. Here the Cartesian transformation operator only uses translation, but no rotation, mirroring, or scaling. - -!["representation map"](../../figures/ifctypeproduct_representationmap-1.png "Figure 1 &mdash; Product type geometry with single placement") - -Figure 2 illustrates an example of referencing a representation multiple times map by the shape representation of a product occurrence. Here the Cartesian transformation operator only uses translation, but no rotation, mirroring, or scaling. The different translation values determine the pattern of the multiple placement. - -!["representation map"](../../figures/ifctypeproduct_representationmap-2.png "Figure 2 &mdash; Product type geometry with multiple placement") - - - @@ -8959,34 +9029,34 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + - + - + - + - + - + - + - + @@ -9001,7 +9071,7 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + @@ -9021,28 +9091,28 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + - + - + - + - + - + @@ -9057,7 +9127,7 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + @@ -9077,35 +9147,36 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + - + - + - - - - - - + + + + + + - + - - - + + + + @@ -9120,7 +9191,7 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + @@ -9140,27 +9211,33 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + - + - + - - - - - - + + + + + + + + + + + + @@ -9175,7 +9252,7 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + @@ -9191,12 +9268,42 @@ Figure 2 illustrates an example of referencing a representation multiple times m + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -9210,57 +9317,57 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + - + - + - - - - - - - - - - + + + + + + + + + + - + - + - + - + - - - - - + + + + + - + - + @@ -9275,32 +9382,32 @@ Figure 2 illustrates an example of referencing a representation multiple times m - - - + + + - - - - + + + + - - + + - - + + @@ -9308,10 +9415,10 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + @@ -9328,28 +9435,28 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + - + - + - + - + - + @@ -9364,7 +9471,7 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + @@ -9377,45 +9484,48 @@ Figure 2 illustrates an example of referencing a representation multiple times m + + The _IfcWindowTypePartitioningEnum_ defines the general layout of the window type and its symbolic presentation. Depending on the enumerator, the appropriate instances of _IfcWindowLiningProperties_ and _IfcWindowPanelProperties_ are attached in the list of _HasPropertySets_. The _IfcWindowTypePartitioningEnum_ mainly determines the way of partitioning the window into individual window panels and thereby number and position of window panels. + +See _IfcWindowTypePartitioningEnum_ for the correct usage of panel partitioning and _IfcWindowPanelProperties_ for the opening symbols for different panel operation types. + + - + - + - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - + - + - - - @@ -9423,10 +9533,10 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + @@ -9438,15 +9548,15 @@ Figure 2 illustrates an example of referencing a representation multiple times m - - - + + + - + @@ -9454,15 +9564,23 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + - The material of the _IfcWindow_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_ relationship. + The material of the _IfcWindow_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_ relationship. It is accessible by the inverse _HasAssociations_ relationship. + +The following keywords for _IfcMaterialConstituentSet.MaterialConstituents[n].Name_ shall be used: + +* 'Lining' - to indicate that the material constituent applies to to the window lining +* 'Framing' - to indicate that the material constituent applies to to the window panels, if not provided, the 'Lining' material information applied to panels as well +* 'Glazing' - to indicate that the material constituent applies to to the glazing part + +If the fall back single _IfcMaterial_ is referenced, it applies to the lining and framing of the window. @@ -9474,17 +9592,17 @@ Figure 2 illustrates an example of referencing a representation multiple times m - + - + - - - - - - + + + + + + diff --git a/ModelViews/Reference View/Documentation.md b/ModelViews/Reference View/Documentation.md index f4a2fe2eb..7baa41b93 100644 --- a/ModelViews/Reference View/Documentation.md +++ b/ModelViews/Reference View/Documentation.md @@ -356,7 +356,7 @@ In scope of presentation capabilities for the appearance of model element shapes * "_Surface Style Shading_", applying a single coloring for each solid; * "_Surface Style Rendering_", applying a single rendering (color, transparency, reflection, etc.) for each solid; -* "_Surface Style textures_", applying a single texture for each solid according to a texture mapping based on the solid type; +* "_Surface_", applying a single texture for each solid according to a texture mapping based on the solid type; * "_Suface Style Tessellation_", applying a color and/or texture for each face of a tessellated solid. The visually adaquate presentation of model elements is constraint by the shape representation diff --git a/Properties/a/ActiveCellSurfaceAreaFraction_2QcZNIbVXDLekiPbViU_nz/DocProperty.xml b/Properties/a/ActiveCellSurfaceAreaFraction_2QcZNIbVXDLekiPbViU_nz/DocProperty.xml new file mode 100644 index 000000000..d09d0b1e5 --- /dev/null +++ b/Properties/a/ActiveCellSurfaceAreaFraction_2QcZNIbVXDLekiPbViU_nz/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/a/ActiveCellSurfaceAreaFraction_2QcZNIbVXDLekiPbViU_nz/Documentation.md b/Properties/a/ActiveCellSurfaceAreaFraction_2QcZNIbVXDLekiPbViU_nz/Documentation.md new file mode 100644 index 000000000..c1e75dfc8 --- /dev/null +++ b/Properties/a/ActiveCellSurfaceAreaFraction_2QcZNIbVXDLekiPbViU_nz/Documentation.md @@ -0,0 +1 @@ +The percentage of surface area containing active solar cells. Note: the surface area may be provided at Qto_SolarDeviceBaseQuantities.GrossArea. diff --git a/Properties/b/BarLength_3IWtxiBfL3dvVCxlV83MM0/DocProperty.xml b/Properties/b/BarLength_3IWtxiBfL3dvVCxlV83MM0/DocProperty.xml new file mode 100644 index 000000000..0dc661d8e --- /dev/null +++ b/Properties/b/BarLength_3IWtxiBfL3dvVCxlV83MM0/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/b/BarLength_3IWtxiBfL3dvVCxlV83MM0/Documentation.md b/Properties/b/BarLength_3IWtxiBfL3dvVCxlV83MM0/Documentation.md new file mode 100644 index 000000000..f81117a53 --- /dev/null +++ b/Properties/b/BarLength_3IWtxiBfL3dvVCxlV83MM0/Documentation.md @@ -0,0 +1 @@ +The total length of the reinforcing bar. The total length of bended bars are calculated according to local standards with corrections for the bends. diff --git a/Properties/b/BarSpacing_00B12bISHCqw0gVJfym_Sc/DocProperty.xml b/Properties/b/BarSpacing_00B12bISHCqw0gVJfym_Sc/DocProperty.xml new file mode 100644 index 000000000..2884c96f1 --- /dev/null +++ b/Properties/b/BarSpacing_00B12bISHCqw0gVJfym_Sc/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/b/BarSpacing_00B12bISHCqw0gVJfym_Sc/Documentation.md b/Properties/b/BarSpacing_00B12bISHCqw0gVJfym_Sc/Documentation.md new file mode 100644 index 000000000..d0766dbf3 --- /dev/null +++ b/Properties/b/BarSpacing_00B12bISHCqw0gVJfym_Sc/Documentation.md @@ -0,0 +1 @@ +The spacing between bars if constant. diff --git a/Properties/b/BarSurface_2qkJc4Qq9Blec78Vl$3MoE/DocProperty.xml b/Properties/b/BarSurface_2qkJc4Qq9Blec78Vl$3MoE/DocProperty.xml new file mode 100644 index 000000000..57117217c --- /dev/null +++ b/Properties/b/BarSurface_2qkJc4Qq9Blec78Vl$3MoE/DocProperty.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/Properties/b/BarSurface_2qkJc4Qq9Blec78Vl$3MoE/Documentation.md b/Properties/b/BarSurface_2qkJc4Qq9Blec78Vl$3MoE/Documentation.md new file mode 100644 index 000000000..9ff08f4db --- /dev/null +++ b/Properties/b/BarSurface_2qkJc4Qq9Blec78Vl$3MoE/Documentation.md @@ -0,0 +1 @@ +Indicator for whether the bar surface is plain or textured. diff --git a/Properties/b/BendingParameters_1sRVDIkIP8QepwvE87UG0J/DocProperty.xml b/Properties/b/BendingParameters_1sRVDIkIP8QepwvE87UG0J/DocProperty.xml new file mode 100644 index 000000000..db0983cff --- /dev/null +++ b/Properties/b/BendingParameters_1sRVDIkIP8QepwvE87UG0J/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/b/BendingParameters_1sRVDIkIP8QepwvE87UG0J/Documentation.md b/Properties/b/BendingParameters_1sRVDIkIP8QepwvE87UG0J/Documentation.md new file mode 100644 index 000000000..4de74b343 --- /dev/null +++ b/Properties/b/BendingParameters_1sRVDIkIP8QepwvE87UG0J/Documentation.md @@ -0,0 +1 @@ +If this mesh type is bent rather than planar, this attribute provides bending shape parameters. Their meaning is defined by the bending shape code and the respective standard. diff --git a/Properties/b/BendingShapeCode_2udkp8mjH5yw9fEAvfSOcg/DocProperty.xml b/Properties/b/BendingShapeCode_2udkp8mjH5yw9fEAvfSOcg/DocProperty.xml new file mode 100644 index 000000000..d22096351 --- /dev/null +++ b/Properties/b/BendingShapeCode_2udkp8mjH5yw9fEAvfSOcg/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/b/BendingShapeCode_2udkp8mjH5yw9fEAvfSOcg/Documentation.md b/Properties/b/BendingShapeCode_2udkp8mjH5yw9fEAvfSOcg/Documentation.md new file mode 100644 index 000000000..59aba4dcc --- /dev/null +++ b/Properties/b/BendingShapeCode_2udkp8mjH5yw9fEAvfSOcg/Documentation.md @@ -0,0 +1 @@ +Shape code per a standard like ACI 315, ISO 3766, or a similar standard. It is presumed that a single standard for defining the bar bending is used throughout the project and that this standard is referenced from the _IfcProject_ object through the _IfcDocumentReference_ mechanism. diff --git a/Properties/c/CellEfficiency_03JspggTX8tub0GPwCT481/DocProperty.xml b/Properties/c/CellEfficiency_03JspggTX8tub0GPwCT481/DocProperty.xml new file mode 100644 index 000000000..af54891ba --- /dev/null +++ b/Properties/c/CellEfficiency_03JspggTX8tub0GPwCT481/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/c/CellEfficiency_03JspggTX8tub0GPwCT481/Documentation.md b/Properties/c/CellEfficiency_03JspggTX8tub0GPwCT481/Documentation.md new file mode 100644 index 000000000..a8e26701c --- /dev/null +++ b/Properties/c/CellEfficiency_03JspggTX8tub0GPwCT481/Documentation.md @@ -0,0 +1 @@ +The ratio of power generated divided by incident solar power. diff --git a/Properties/e/EfficiencyCurve_2aEBZ2UfnEdPbsufO9yZqy/DocProperty.xml b/Properties/e/EfficiencyCurve_2aEBZ2UfnEdPbsufO9yZqy/DocProperty.xml new file mode 100644 index 000000000..036d1a93a --- /dev/null +++ b/Properties/e/EfficiencyCurve_2aEBZ2UfnEdPbsufO9yZqy/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/e/EfficiencyCurve_2aEBZ2UfnEdPbsufO9yZqy/Documentation.md b/Properties/e/EfficiencyCurve_2aEBZ2UfnEdPbsufO9yZqy/Documentation.md new file mode 100644 index 000000000..9058a7a84 --- /dev/null +++ b/Properties/e/EfficiencyCurve_2aEBZ2UfnEdPbsufO9yZqy/Documentation.md @@ -0,0 +1 @@ +The ratio of power transformed according to fractional load, where the first value indicates the load percentage and the second value indicates the efficiency of power transformation. diff --git a/Properties/h/HeatTransferTypeEnum_2eawM0qS0HuO00025QrE$V/DocProperty.xml b/Properties/h/HeatTransferType_2eawM0qS0HuO00025QrE$V/DocProperty.xml similarity index 68% rename from Properties/h/HeatTransferTypeEnum_2eawM0qS0HuO00025QrE$V/DocProperty.xml rename to Properties/h/HeatTransferType_2eawM0qS0HuO00025QrE$V/DocProperty.xml index 7b77c5c30..330546cdf 100644 --- a/Properties/h/HeatTransferTypeEnum_2eawM0qS0HuO00025QrE$V/DocProperty.xml +++ b/Properties/h/HeatTransferType_2eawM0qS0HuO00025QrE$V/DocProperty.xml @@ -1,5 +1,5 @@  - + @@ -10,7 +10,7 @@ - + diff --git a/Properties/h/HeatTransferTypeEnum_2eawM0qS0HuO00025QrE$V/Documentation.md b/Properties/h/HeatTransferType_2eawM0qS0HuO00025QrE$V/Documentation.md similarity index 100% rename from Properties/h/HeatTransferTypeEnum_2eawM0qS0HuO00025QrE$V/Documentation.md rename to Properties/h/HeatTransferType_2eawM0qS0HuO00025QrE$V/Documentation.md diff --git a/Properties/l/Level_2FfK7VEQ18bfS6UW5bjDs3/DocProperty.xml b/Properties/l/Level_2FfK7VEQ18bfS6UW5bjDs3/DocProperty.xml new file mode 100644 index 000000000..7f7a6c4ac --- /dev/null +++ b/Properties/l/Level_2FfK7VEQ18bfS6UW5bjDs3/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/l/Level_2FfK7VEQ18bfS6UW5bjDs3/Documentation.md b/Properties/l/Level_2FfK7VEQ18bfS6UW5bjDs3/Documentation.md new file mode 100644 index 000000000..32cb2be9d --- /dev/null +++ b/Properties/l/Level_2FfK7VEQ18bfS6UW5bjDs3/Documentation.md @@ -0,0 +1 @@ +The level of the tank as a fraction of its available capacity. diff --git a/Properties/l/Level_2YT$iVpSfFp9mfXZHHYn1c/DocProperty.xml b/Properties/l/Level_2YT$iVpSfFp9mfXZHHYn1c/DocProperty.xml new file mode 100644 index 000000000..6e00a4d19 --- /dev/null +++ b/Properties/l/Level_2YT$iVpSfFp9mfXZHHYn1c/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/l/Level_2YT$iVpSfFp9mfXZHHYn1c/Documentation.md b/Properties/l/Level_2YT$iVpSfFp9mfXZHHYn1c/Documentation.md new file mode 100644 index 000000000..25f5b9930 --- /dev/null +++ b/Properties/l/Level_2YT$iVpSfFp9mfXZHHYn1c/Documentation.md @@ -0,0 +1 @@ +The fraction of usable energy stored. diff --git a/Properties/l/LongitudinalBarNominalDiameter_217XYJrM132RcHgHGWOKKm/DocProperty.xml b/Properties/l/LongitudinalBarNominalDiameter_217XYJrM132RcHgHGWOKKm/DocProperty.xml new file mode 100644 index 000000000..9a51a817d --- /dev/null +++ b/Properties/l/LongitudinalBarNominalDiameter_217XYJrM132RcHgHGWOKKm/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/l/LongitudinalBarSpacing_0zQBvuVW98lQnxrINKc$Sn/DocProperty.xml b/Properties/l/LongitudinalBarSpacing_0zQBvuVW98lQnxrINKc$Sn/DocProperty.xml new file mode 100644 index 000000000..30c9ad6c6 --- /dev/null +++ b/Properties/l/LongitudinalBarSpacing_0zQBvuVW98lQnxrINKc$Sn/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/l/LongitudinalBarSurface_3RS_y7y2n1RPrkDG$xtLOH/DocProperty.xml b/Properties/l/LongitudinalBarSurface_3RS_y7y2n1RPrkDG$xtLOH/DocProperty.xml new file mode 100644 index 000000000..53161b7c4 --- /dev/null +++ b/Properties/l/LongitudinalBarSurface_3RS_y7y2n1RPrkDG$xtLOH/DocProperty.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/Properties/l/LongitudinalBarSurface_3RS_y7y2n1RPrkDG$xtLOH/Documentation.md b/Properties/l/LongitudinalBarSurface_3RS_y7y2n1RPrkDG$xtLOH/Documentation.md new file mode 100644 index 000000000..9ff08f4db --- /dev/null +++ b/Properties/l/LongitudinalBarSurface_3RS_y7y2n1RPrkDG$xtLOH/Documentation.md @@ -0,0 +1 @@ +Indicator for whether the bar surface is plain or textured. diff --git a/Properties/m/MeshLength_08AQo8cYP6PROJADN7$tya/DocProperty.xml b/Properties/m/MeshLength_08AQo8cYP6PROJADN7$tya/DocProperty.xml new file mode 100644 index 000000000..07192bb6c --- /dev/null +++ b/Properties/m/MeshLength_08AQo8cYP6PROJADN7$tya/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/m/MeshWidth_2HI9158knE_gLETqt1OCJx/DocProperty.xml b/Properties/m/MeshWidth_2HI9158knE_gLETqt1OCJx/DocProperty.xml new file mode 100644 index 000000000..df784afb0 --- /dev/null +++ b/Properties/m/MeshWidth_2HI9158knE_gLETqt1OCJx/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/m/ModuleCapacity_1u4zdKW6XFUQoYarMQLbtq/DocProperty.xml b/Properties/m/ModuleCapacity_1u4zdKW6XFUQoYarMQLbtq/DocProperty.xml new file mode 100644 index 000000000..911f67fee --- /dev/null +++ b/Properties/m/ModuleCapacity_1u4zdKW6XFUQoYarMQLbtq/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/m/ModuleCapacity_1u4zdKW6XFUQoYarMQLbtq/Documentation.md b/Properties/m/ModuleCapacity_1u4zdKW6XFUQoYarMQLbtq/Documentation.md new file mode 100644 index 000000000..5a8677755 --- /dev/null +++ b/Properties/m/ModuleCapacity_1u4zdKW6XFUQoYarMQLbtq/Documentation.md @@ -0,0 +1 @@ +The capacity for each battery module. diff --git a/Properties/m/ModulesInParallel_1aH6j1SE99_fngHMIHVC$P/DocProperty.xml b/Properties/m/ModulesInParallel_1aH6j1SE99_fngHMIHVC$P/DocProperty.xml new file mode 100644 index 000000000..168ac8a31 --- /dev/null +++ b/Properties/m/ModulesInParallel_1aH6j1SE99_fngHMIHVC$P/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/m/ModulesInParallel_1aH6j1SE99_fngHMIHVC$P/Documentation.md b/Properties/m/ModulesInParallel_1aH6j1SE99_fngHMIHVC$P/Documentation.md new file mode 100644 index 000000000..f5c80cfba --- /dev/null +++ b/Properties/m/ModulesInParallel_1aH6j1SE99_fngHMIHVC$P/Documentation.md @@ -0,0 +1 @@ +The number of modules in parallel, where the total number of modules equals the number in parallel multiplied by the number in series. diff --git a/Properties/m/ModulesInSeries_2SCdldRMz1EQkVMCQbp7gQ/DocProperty.xml b/Properties/m/ModulesInSeries_2SCdldRMz1EQkVMCQbp7gQ/DocProperty.xml new file mode 100644 index 000000000..67cdc1819 --- /dev/null +++ b/Properties/m/ModulesInSeries_2SCdldRMz1EQkVMCQbp7gQ/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/m/ModulesInSeries_2SCdldRMz1EQkVMCQbp7gQ/Documentation.md b/Properties/m/ModulesInSeries_2SCdldRMz1EQkVMCQbp7gQ/Documentation.md new file mode 100644 index 000000000..6b08df1bd --- /dev/null +++ b/Properties/m/ModulesInSeries_2SCdldRMz1EQkVMCQbp7gQ/Documentation.md @@ -0,0 +1 @@ +The number of modules in series, where the total number of modules equals the number in parallel multiplied by the number in series. diff --git a/Properties/n/NominalDiameter_0A8c8X4yP2xOKuafrNBsaG/DocProperty.xml b/Properties/n/NominalDiameter_0A8c8X4yP2xOKuafrNBsaG/DocProperty.xml new file mode 100644 index 000000000..9f1ea9532 --- /dev/null +++ b/Properties/n/NominalDiameter_0A8c8X4yP2xOKuafrNBsaG/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/n/NominalDiameter_0A8c8X4yP2xOKuafrNBsaG/Documentation.md b/Properties/n/NominalDiameter_0A8c8X4yP2xOKuafrNBsaG/Documentation.md new file mode 100644 index 000000000..a242307b3 --- /dev/null +++ b/Properties/n/NominalDiameter_0A8c8X4yP2xOKuafrNBsaG/Documentation.md @@ -0,0 +1 @@ +The nominal diameter defining the cross-section size of the prestressed part of the tendon. diff --git a/Properties/n/NominalDiameter_18BXd89sj1xRbNqTu43bvX/DocProperty.xml b/Properties/n/NominalDiameter_18BXd89sj1xRbNqTu43bvX/DocProperty.xml new file mode 100644 index 000000000..acc7732ba --- /dev/null +++ b/Properties/n/NominalDiameter_18BXd89sj1xRbNqTu43bvX/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/n/NominalDiameter_18BXd89sj1xRbNqTu43bvX/Documentation.md b/Properties/n/NominalDiameter_18BXd89sj1xRbNqTu43bvX/Documentation.md new file mode 100644 index 000000000..97d048dee --- /dev/null +++ b/Properties/n/NominalDiameter_18BXd89sj1xRbNqTu43bvX/Documentation.md @@ -0,0 +1 @@ +The nominal diameter describing the cross-section size of the fastener type. diff --git a/Properties/n/NominalDiameter_3chH1GISj16wMEb$kUhUKU/DocProperty.xml b/Properties/n/NominalDiameter_3chH1GISj16wMEb$kUhUKU/DocProperty.xml new file mode 100644 index 000000000..f0c89298e --- /dev/null +++ b/Properties/n/NominalDiameter_3chH1GISj16wMEb$kUhUKU/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/n/NominalDiameter_3chH1GISj16wMEb$kUhUKU/Documentation.md b/Properties/n/NominalDiameter_3chH1GISj16wMEb$kUhUKU/Documentation.md new file mode 100644 index 000000000..4ba400600 --- /dev/null +++ b/Properties/n/NominalDiameter_3chH1GISj16wMEb$kUhUKU/Documentation.md @@ -0,0 +1 @@ +The nominal diameter defining the cross-section size of the reinforcing bar. diff --git a/Properties/n/NominalLength_1zu$08e7f1bBfiI$1wPJDE/DocProperty.xml b/Properties/n/NominalLength_1zu$08e7f1bBfiI$1wPJDE/DocProperty.xml new file mode 100644 index 000000000..784fb9558 --- /dev/null +++ b/Properties/n/NominalLength_1zu$08e7f1bBfiI$1wPJDE/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/n/NominalLength_1zu$08e7f1bBfiI$1wPJDE/Documentation.md b/Properties/n/NominalLength_1zu$08e7f1bBfiI$1wPJDE/Documentation.md new file mode 100644 index 000000000..02012e98a --- /dev/null +++ b/Properties/n/NominalLength_1zu$08e7f1bBfiI$1wPJDE/Documentation.md @@ -0,0 +1 @@ +The nominal length describing the longitudinal dimensions of the fastener type. diff --git a/Properties/p/Pressure_1FGUp2JnjDm9WSf7MzUIVG/DocProperty.xml b/Properties/p/Pressure_1FGUp2JnjDm9WSf7MzUIVG/DocProperty.xml new file mode 100644 index 000000000..92d9dda13 --- /dev/null +++ b/Properties/p/Pressure_1FGUp2JnjDm9WSf7MzUIVG/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/p/Pressure_1FGUp2JnjDm9WSf7MzUIVG/Documentation.md b/Properties/p/Pressure_1FGUp2JnjDm9WSf7MzUIVG/Documentation.md new file mode 100644 index 000000000..8d00a7a34 --- /dev/null +++ b/Properties/p/Pressure_1FGUp2JnjDm9WSf7MzUIVG/Documentation.md @@ -0,0 +1 @@ +The pressure of the substance in the tank. diff --git a/Properties/r/RadiativeFraction_1NpylN_VP5vxDPzrJD433R/DocProperty.xml b/Properties/r/RadiativeFraction_1NpylN_VP5vxDPzrJD433R/DocProperty.xml new file mode 100644 index 000000000..7e5d950e5 --- /dev/null +++ b/Properties/r/RadiativeFraction_1NpylN_VP5vxDPzrJD433R/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/r/RadiativeFraction_1NpylN_VP5vxDPzrJD433R/Documentation.md b/Properties/r/RadiativeFraction_1NpylN_VP5vxDPzrJD433R/Documentation.md new file mode 100644 index 000000000..8dc33f81f --- /dev/null +++ b/Properties/r/RadiativeFraction_1NpylN_VP5vxDPzrJD433R/Documentation.md @@ -0,0 +1 @@ +The fraction of energy converted to heat. diff --git a/Properties/r/RadiativeFraction_1yXe9WHHj80uzFn9Zy3ZgR/DocProperty.xml b/Properties/r/RadiativeFraction_1yXe9WHHj80uzFn9Zy3ZgR/DocProperty.xml new file mode 100644 index 000000000..c5fb6ebba --- /dev/null +++ b/Properties/r/RadiativeFraction_1yXe9WHHj80uzFn9Zy3ZgR/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/r/RadiativeFraction_1yXe9WHHj80uzFn9Zy3ZgR/Documentation.md b/Properties/r/RadiativeFraction_1yXe9WHHj80uzFn9Zy3ZgR/Documentation.md new file mode 100644 index 000000000..8dc33f81f --- /dev/null +++ b/Properties/r/RadiativeFraction_1yXe9WHHj80uzFn9Zy3ZgR/Documentation.md @@ -0,0 +1 @@ +The fraction of energy converted to heat. diff --git a/Properties/r/Reference_0Jgg8uKTf3neyMWuiNJaPs/DocProperty.xml b/Properties/r/Reference_0Jgg8uKTf3neyMWuiNJaPs/DocProperty.xml new file mode 100644 index 000000000..aefbad110 --- /dev/null +++ b/Properties/r/Reference_0Jgg8uKTf3neyMWuiNJaPs/DocProperty.xml @@ -0,0 +1,10 @@ + + + + + + 当プロジェクトにおけるこの指定型式のためのリファレンスID。（たとえは、'A-1'型) + + + + diff --git a/Properties/r/Reference_0Jgg8uKTf3neyMWuiNJaPs/Documentation.md b/Properties/r/Reference_0Jgg8uKTf3neyMWuiNJaPs/Documentation.md new file mode 100644 index 000000000..2208d22d9 --- /dev/null +++ b/Properties/r/Reference_0Jgg8uKTf3neyMWuiNJaPs/Documentation.md @@ -0,0 +1 @@ +Reference ID for this specified type in this project (e.g. type 'A-1'). diff --git a/Properties/r/Reference_1s$wXlplz2OAWsqC1oj_Ci/DocProperty.xml b/Properties/r/Reference_1s$wXlplz2OAWsqC1oj_Ci/DocProperty.xml new file mode 100644 index 000000000..fac2e6586 --- /dev/null +++ b/Properties/r/Reference_1s$wXlplz2OAWsqC1oj_Ci/DocProperty.xml @@ -0,0 +1,10 @@ + + + + + + 当プロジェクトにおけるこの指定型式のためのリファレンスID。（たとえは、'A-1'型) + + + + diff --git a/Properties/r/Reference_1s$wXlplz2OAWsqC1oj_Ci/Documentation.md b/Properties/r/Reference_1s$wXlplz2OAWsqC1oj_Ci/Documentation.md new file mode 100644 index 000000000..2208d22d9 --- /dev/null +++ b/Properties/r/Reference_1s$wXlplz2OAWsqC1oj_Ci/Documentation.md @@ -0,0 +1 @@ +Reference ID for this specified type in this project (e.g. type 'A-1'). diff --git a/Properties/r/Reference_2rbnE3HtHD6hMy4aEGfmky/DocProperty.xml b/Properties/r/Reference_2rbnE3HtHD6hMy4aEGfmky/DocProperty.xml new file mode 100644 index 000000000..ffb5d2f37 --- /dev/null +++ b/Properties/r/Reference_2rbnE3HtHD6hMy4aEGfmky/DocProperty.xml @@ -0,0 +1,10 @@ + + + + + + 当プロジェクトにおけるこの指定型式のためのリファレンスID。（たとえは、'A-1'型) + + + + diff --git a/Properties/r/Reference_2rbnE3HtHD6hMy4aEGfmky/Documentation.md b/Properties/r/Reference_2rbnE3HtHD6hMy4aEGfmky/Documentation.md new file mode 100644 index 000000000..2208d22d9 --- /dev/null +++ b/Properties/r/Reference_2rbnE3HtHD6hMy4aEGfmky/Documentation.md @@ -0,0 +1 @@ +Reference ID for this specified type in this project (e.g. type 'A-1'). diff --git a/Properties/r/Reference_3PnSsV2xH5FxPu61GHLOnT/DocProperty.xml b/Properties/r/Reference_3PnSsV2xH5FxPu61GHLOnT/DocProperty.xml new file mode 100644 index 000000000..0020dfd37 --- /dev/null +++ b/Properties/r/Reference_3PnSsV2xH5FxPu61GHLOnT/DocProperty.xml @@ -0,0 +1,10 @@ + + + + + + 当プロジェクトにおけるこの指定型式のためのリファレンスID。（たとえは、'A-1'型) + + + + diff --git a/Properties/r/Reference_3PnSsV2xH5FxPu61GHLOnT/Documentation.md b/Properties/r/Reference_3PnSsV2xH5FxPu61GHLOnT/Documentation.md new file mode 100644 index 000000000..2208d22d9 --- /dev/null +++ b/Properties/r/Reference_3PnSsV2xH5FxPu61GHLOnT/Documentation.md @@ -0,0 +1 @@ +Reference ID for this specified type in this project (e.g. type 'A-1'). diff --git a/Properties/s/SheathDiameter_2bINAwQGv0JRbqIZPSxDEp/DocProperty.xml b/Properties/s/SheathDiameter_2bINAwQGv0JRbqIZPSxDEp/DocProperty.xml new file mode 100644 index 000000000..5478d57a1 --- /dev/null +++ b/Properties/s/SheathDiameter_2bINAwQGv0JRbqIZPSxDEp/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/s/SheathDiameter_2bINAwQGv0JRbqIZPSxDEp/Documentation.md b/Properties/s/SheathDiameter_2bINAwQGv0JRbqIZPSxDEp/Documentation.md new file mode 100644 index 000000000..a98ff4b5d --- /dev/null +++ b/Properties/s/SheathDiameter_2bINAwQGv0JRbqIZPSxDEp/Documentation.md @@ -0,0 +1 @@ +Diameter of the sheeth (duct) around the tendon, if there is one with this type of tendon. diff --git a/Properties/s/Status_0Ps5H$cmr3GAgf1o7xNvqx/DocProperty.xml b/Properties/s/Status_0Ps5H$cmr3GAgf1o7xNvqx/DocProperty.xml new file mode 100644 index 000000000..bd70dec08 --- /dev/null +++ b/Properties/s/Status_0Ps5H$cmr3GAgf1o7xNvqx/DocProperty.xml @@ -0,0 +1,13 @@ + + + + + + 要素（主にリノベーションまたは改修プロジェクトにおいて）の状態。 状態は、「新規(New)」－新しく追加される要素。「既存」－要素は存在し、かつ残りもの。「破壊」－要素は存在したが、廃棄されるもの。「一時的」－一時的に存在する要素（一時的にサポートしている構造のようなもの）。 + + + + + + + diff --git a/Properties/s/Status_0Ps5H$cmr3GAgf1o7xNvqx/Documentation.md b/Properties/s/Status_0Ps5H$cmr3GAgf1o7xNvqx/Documentation.md new file mode 100644 index 000000000..1aefa4ee0 --- /dev/null +++ b/Properties/s/Status_0Ps5H$cmr3GAgf1o7xNvqx/Documentation.md @@ -0,0 +1 @@ +Status of the element, predominately used in renovation or retrofitting projects. The status can be assigned to as "New" - element designed as new addition, "Existing" - element exists and remains, "Demolish" - element existed but is to be demolished, "Temporary" - element will exists only temporary (like a temporary support structure). diff --git a/Properties/s/Status_0w6CEEvBH8_82OWPi$yp0J/DocProperty.xml b/Properties/s/Status_0w6CEEvBH8_82OWPi$yp0J/DocProperty.xml new file mode 100644 index 000000000..941914702 --- /dev/null +++ b/Properties/s/Status_0w6CEEvBH8_82OWPi$yp0J/DocProperty.xml @@ -0,0 +1,13 @@ + + + + + + 要素（主にリノベーションまたは改修プロジェクトにおいて）の状態。 状態は、「新規(New)」－新しく追加される要素。「既存」－要素は存在し、かつ残りもの。「破壊」－要素は存在したが、廃棄されるもの。「一時的」－一時的に存在する要素（一時的にサポートしている構造のようなもの）。 + + + + + + + diff --git a/Properties/s/Status_0w6CEEvBH8_82OWPi$yp0J/Documentation.md b/Properties/s/Status_0w6CEEvBH8_82OWPi$yp0J/Documentation.md new file mode 100644 index 000000000..1aefa4ee0 --- /dev/null +++ b/Properties/s/Status_0w6CEEvBH8_82OWPi$yp0J/Documentation.md @@ -0,0 +1 @@ +Status of the element, predominately used in renovation or retrofitting projects. The status can be assigned to as "New" - element designed as new addition, "Existing" - element exists and remains, "Demolish" - element existed but is to be demolished, "Temporary" - element will exists only temporary (like a temporary support structure). diff --git a/Properties/s/Status_1zU_Y7TWrFux4mAMFtlCsA/DocProperty.xml b/Properties/s/Status_1zU_Y7TWrFux4mAMFtlCsA/DocProperty.xml new file mode 100644 index 000000000..10fc86a0c --- /dev/null +++ b/Properties/s/Status_1zU_Y7TWrFux4mAMFtlCsA/DocProperty.xml @@ -0,0 +1,13 @@ + + + + + + 要素（主にリノベーションまたは改修プロジェクトにおいて）の状態。 状態は、「新規(New)」－新しく追加される要素。「既存」－要素は存在し、かつ残りもの。「破壊」－要素は存在したが、廃棄されるもの。「一時的」－一時的に存在する要素（一時的にサポートしている構造のようなもの）。 + + + + + + + diff --git a/Properties/s/Status_1zU_Y7TWrFux4mAMFtlCsA/Documentation.md b/Properties/s/Status_1zU_Y7TWrFux4mAMFtlCsA/Documentation.md new file mode 100644 index 000000000..1aefa4ee0 --- /dev/null +++ b/Properties/s/Status_1zU_Y7TWrFux4mAMFtlCsA/Documentation.md @@ -0,0 +1 @@ +Status of the element, predominately used in renovation or retrofitting projects. The status can be assigned to as "New" - element designed as new addition, "Existing" - element exists and remains, "Demolish" - element existed but is to be demolished, "Temporary" - element will exists only temporary (like a temporary support structure). diff --git a/Properties/s/Status_2gyMFQ3PL8sfxliEzsgytX/DocProperty.xml b/Properties/s/Status_2gyMFQ3PL8sfxliEzsgytX/DocProperty.xml new file mode 100644 index 000000000..14760a8b3 --- /dev/null +++ b/Properties/s/Status_2gyMFQ3PL8sfxliEzsgytX/DocProperty.xml @@ -0,0 +1,13 @@ + + + + + + 要素（主にリノベーションまたは改修プロジェクトにおいて）の状態。 状態は、「新規(New)」－新しく追加される要素。「既存」－要素は存在し、かつ残りもの。「破壊」－要素は存在したが、廃棄されるもの。「一時的」－一時的に存在する要素（一時的にサポートしている構造のようなもの）。 + + + + + + + diff --git a/Properties/s/Status_2gyMFQ3PL8sfxliEzsgytX/Documentation.md b/Properties/s/Status_2gyMFQ3PL8sfxliEzsgytX/Documentation.md new file mode 100644 index 000000000..1aefa4ee0 --- /dev/null +++ b/Properties/s/Status_2gyMFQ3PL8sfxliEzsgytX/Documentation.md @@ -0,0 +1 @@ +Status of the element, predominately used in renovation or retrofitting projects. The status can be assigned to as "New" - element designed as new addition, "Existing" - element exists and remains, "Demolish" - element existed but is to be demolished, "Temporary" - element will exists only temporary (like a temporary support structure). diff --git a/Properties/t/Temperature_1xwFoGmszAiv4oRrZSViTy/DocProperty.xml b/Properties/t/Temperature_1xwFoGmszAiv4oRrZSViTy/DocProperty.xml new file mode 100644 index 000000000..7df54228a --- /dev/null +++ b/Properties/t/Temperature_1xwFoGmszAiv4oRrZSViTy/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/t/Temperature_1xwFoGmszAiv4oRrZSViTy/Documentation.md b/Properties/t/Temperature_1xwFoGmszAiv4oRrZSViTy/Documentation.md new file mode 100644 index 000000000..5aae5b209 --- /dev/null +++ b/Properties/t/Temperature_1xwFoGmszAiv4oRrZSViTy/Documentation.md @@ -0,0 +1 @@ +The temperature of the substance in the tank. diff --git a/Properties/t/TransverseBarBendingParameters_0$taXa9srEXB9I1d3ai9u4/DocProperty.xml b/Properties/t/TransverseBarBendingParameters_0$taXa9srEXB9I1d3ai9u4/DocProperty.xml new file mode 100644 index 000000000..90fa0a170 --- /dev/null +++ b/Properties/t/TransverseBarBendingParameters_0$taXa9srEXB9I1d3ai9u4/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/t/TransverseBarBendingParameters_0$taXa9srEXB9I1d3ai9u4/Documentation.md b/Properties/t/TransverseBarBendingParameters_0$taXa9srEXB9I1d3ai9u4/Documentation.md new file mode 100644 index 000000000..4de74b343 --- /dev/null +++ b/Properties/t/TransverseBarBendingParameters_0$taXa9srEXB9I1d3ai9u4/Documentation.md @@ -0,0 +1 @@ +If this mesh type is bent rather than planar, this attribute provides bending shape parameters. Their meaning is defined by the bending shape code and the respective standard. diff --git a/Properties/t/TransverseBarBendingShapeCode_0OepHgUSb8ygLobAS7j8QC/DocProperty.xml b/Properties/t/TransverseBarBendingShapeCode_0OepHgUSb8ygLobAS7j8QC/DocProperty.xml new file mode 100644 index 000000000..2e08c0e3a --- /dev/null +++ b/Properties/t/TransverseBarBendingShapeCode_0OepHgUSb8ygLobAS7j8QC/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/t/TransverseBarBendingShapeCode_0OepHgUSb8ygLobAS7j8QC/Documentation.md b/Properties/t/TransverseBarBendingShapeCode_0OepHgUSb8ygLobAS7j8QC/Documentation.md new file mode 100644 index 000000000..59aba4dcc --- /dev/null +++ b/Properties/t/TransverseBarBendingShapeCode_0OepHgUSb8ygLobAS7j8QC/Documentation.md @@ -0,0 +1 @@ +Shape code per a standard like ACI 315, ISO 3766, or a similar standard. It is presumed that a single standard for defining the bar bending is used throughout the project and that this standard is referenced from the _IfcProject_ object through the _IfcDocumentReference_ mechanism. diff --git a/Properties/t/TransverseBarNominalDiameter_2pXxXg8PH4zRbXzhVTDrAk/DocProperty.xml b/Properties/t/TransverseBarNominalDiameter_2pXxXg8PH4zRbXzhVTDrAk/DocProperty.xml new file mode 100644 index 000000000..677747a32 --- /dev/null +++ b/Properties/t/TransverseBarNominalDiameter_2pXxXg8PH4zRbXzhVTDrAk/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/t/TransverseBarSpacing_1VnCDpQAj5Y9$nQc__Xtmu/DocProperty.xml b/Properties/t/TransverseBarSpacing_1VnCDpQAj5Y9$nQc__Xtmu/DocProperty.xml new file mode 100644 index 000000000..4861ef8b2 --- /dev/null +++ b/Properties/t/TransverseBarSpacing_1VnCDpQAj5Y9$nQc__Xtmu/DocProperty.xml @@ -0,0 +1,3 @@ + + + diff --git a/Properties/t/TransverseBarSurface_39sLs5TpTDjh1uwTSuL$X8/DocProperty.xml b/Properties/t/TransverseBarSurface_39sLs5TpTDjh1uwTSuL$X8/DocProperty.xml new file mode 100644 index 000000000..82131ca41 --- /dev/null +++ b/Properties/t/TransverseBarSurface_39sLs5TpTDjh1uwTSuL$X8/DocProperty.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/Properties/t/TransverseBarSurface_39sLs5TpTDjh1uwTSuL$X8/Documentation.md b/Properties/t/TransverseBarSurface_39sLs5TpTDjh1uwTSuL$X8/Documentation.md new file mode 100644 index 000000000..9ff08f4db --- /dev/null +++ b/Properties/t/TransverseBarSurface_39sLs5TpTDjh1uwTSuL$X8/Documentation.md @@ -0,0 +1 @@ +Indicator for whether the bar surface is plain or textured. diff --git a/PropertyConstants/n/NONE_00rsh4T2j4PfKgc4o7A7X8.xml b/PropertyConstants/n/NONE_00rsh4T2j4PfKgc4o7A7X8.xml index 7e31a3df9..85a9dc199 100644 --- a/PropertyConstants/n/NONE_00rsh4T2j4PfKgc4o7A7X8.xml +++ b/PropertyConstants/n/NONE_00rsh4T2j4PfKgc4o7A7X8.xml @@ -1,7 +1,9 @@  - + + No end-style has been applied + @@ -18,14 +20,12 @@ No end-style has been applied - No end-style has been applied + There is no pump base, such as an inline pump - - There is no pump base, such as an inline pump - + diff --git a/PropertyConstants/n/NOTDEFINED_0jPqDBAQ13AQB5eFaJZXjR.xml b/PropertyConstants/n/NOTDEFINED_0jPqDBAQ13AQB5eFaJZXjR.xml index 428439745..4310a1f50 100644 --- a/PropertyConstants/n/NOTDEFINED_0jPqDBAQ13AQB5eFaJZXjR.xml +++ b/PropertyConstants/n/NOTDEFINED_0jPqDBAQ13AQB5eFaJZXjR.xml @@ -1,6 +1,7 @@  + @@ -8,7 +9,6 @@ - diff --git a/PropertyConstants/n/NOTKNOWN_0_n254Fb10hBW_0_XIj7Qe.xml b/PropertyConstants/n/NOTKNOWN_0_n254Fb10hBW_0_XIj7Qe.xml index bf770f06c..e99d1b94b 100644 --- a/PropertyConstants/n/NOTKNOWN_0_n254Fb10hBW_0_XIj7Qe.xml +++ b/PropertyConstants/n/NOTKNOWN_0_n254Fb10hBW_0_XIj7Qe.xml @@ -259,10 +259,10 @@ Value is unknown. + Value is unknown. - Value is unknown. diff --git a/PropertyConstants/p/PLAIN_0EphPNrOH0wQPf1nfRslNx.xml b/PropertyConstants/p/PLAIN_0EphPNrOH0wQPf1nfRslNx.xml new file mode 100644 index 000000000..8082e1352 --- /dev/null +++ b/PropertyConstants/p/PLAIN_0EphPNrOH0wQPf1nfRslNx.xml @@ -0,0 +1,3 @@ + + + diff --git a/PropertyConstants/t/TEXTURED_3iVpG874jBxRYyIQnG1zEe.xml b/PropertyConstants/t/TEXTURED_3iVpG874jBxRYyIQnG1zEe.xml new file mode 100644 index 000000000..0abc8bb25 --- /dev/null +++ b/PropertyConstants/t/TEXTURED_3iVpG874jBxRYyIQnG1zEe.xml @@ -0,0 +1,3 @@ + + + diff --git a/PropertyEnumerations/a/PEnum_AirToAirHeatTransferHeatTransferType.xml b/PropertyEnumerations/h/PEnum_HeatTransferType.xml similarity index 77% rename from PropertyEnumerations/a/PEnum_AirToAirHeatTransferHeatTransferType.xml rename to PropertyEnumerations/h/PEnum_HeatTransferType.xml index 41eadcddb..de5b57734 100644 --- a/PropertyEnumerations/a/PEnum_AirToAirHeatTransferHeatTransferType.xml +++ b/PropertyEnumerations/h/PEnum_HeatTransferType.xml @@ -1,5 +1,5 @@  - + diff --git a/PropertyEnumerations/r/PEnum_ReinforcementBarSurface.xml b/PropertyEnumerations/r/PEnum_ReinforcementBarSurface.xml new file mode 100644 index 000000000..d0d683ec8 --- /dev/null +++ b/PropertyEnumerations/r/PEnum_ReinforcementBarSurface.xml @@ -0,0 +1,12 @@ + + + Enumeration indicating whether the bar has a plain or textured (ribbed) surface. + + + + + + + + + diff --git a/Publications/IFC4 Add2 DTV/DocPublication.xml b/Publications/IFC4 Add2 TC1 DTV/DocPublication.xml similarity index 96% rename from Publications/IFC4 Add2 DTV/DocPublication.xml rename to Publications/IFC4 Add2 TC1 DTV/DocPublication.xml index ee2fb85a9..282613641 100644 --- a/Publications/IFC4 Add2 DTV/DocPublication.xml +++ b/Publications/IFC4 Add2 TC1 DTV/DocPublication.xml @@ -1,6 +1,7 @@  - + + diff --git a/Publications/IFC4 Add2 RV/Documentation.md b/Publications/IFC4 Add2 TC1 DTV/Documentation.md similarity index 88% rename from Publications/IFC4 Add2 RV/Documentation.md rename to Publications/IFC4 Add2 TC1 DTV/Documentation.md index ed63aabcc..06c7fa94f 100644 --- a/Publications/IFC4 Add2 RV/Documentation.md +++ b/Publications/IFC4 Add2 TC1 DTV/Documentation.md @@ -11,9 +11,9 @@

- Industry Foundation Classes


+ Industry Foundation Classes 4.0.2.1


- Version 4 - Addendum 2 - Reference View + Design Transfer View

@@ -21,7 +21,7 @@

- © buildingSMART 1996-2016 - This document is owned and copyrighted by buildingSMART International Limited
+ © buildingSMART 1996-2017 - This document is owned and copyrighted by buildingSMART International Limited
By using the IFC4 specification you agree to the following copyright notice

diff --git a/Publications/IFC4 Add2 RV/DocPublication.xml b/Publications/IFC4 Add2 TC1 RV/DocPublication.xml similarity index 97% rename from Publications/IFC4 Add2 RV/DocPublication.xml rename to Publications/IFC4 Add2 TC1 RV/DocPublication.xml index 619876a85..a29f8b1bd 100644 --- a/Publications/IFC4 Add2 RV/DocPublication.xml +++ b/Publications/IFC4 Add2 TC1 RV/DocPublication.xml @@ -1,5 +1,5 @@  - + diff --git a/Publications/IFC4 Add2/Documentation.md b/Publications/IFC4 Add2 TC1 RV/Documentation.md similarity index 89% rename from Publications/IFC4 Add2/Documentation.md rename to Publications/IFC4 Add2 TC1 RV/Documentation.md index a85690b36..450ad98fa 100644 --- a/Publications/IFC4 Add2/Documentation.md +++ b/Publications/IFC4 Add2 TC1 RV/Documentation.md @@ -11,9 +11,9 @@

- Industry Foundation Classes


+ Industry Foundation Classes 4.0.2.1


- Version 4 - Addendum 2 + Reference View

@@ -21,7 +21,7 @@

- © buildingSMART 1996-2016 - This document is owned and copyrighted by buildingSMART International Limited
+ © buildingSMART 1996-2017 - This document is owned and copyrighted by buildingSMART International Limited
By using the IFC4 specification you agree to the following copyright notice

diff --git a/Publications/IFC4 Add2/DocPublication.xml b/Publications/IFC4 Add2 TC1/DocPublication.xml similarity index 97% rename from Publications/IFC4 Add2/DocPublication.xml rename to Publications/IFC4 Add2 TC1/DocPublication.xml index 3e14c4321..82f773248 100644 --- a/Publications/IFC4 Add2/DocPublication.xml +++ b/Publications/IFC4 Add2 TC1/DocPublication.xml @@ -1,5 +1,5 @@  - + diff --git a/Publications/IFC4 Add2 DTV/Documentation.md b/Publications/IFC4 Add2 TC1/Documentation.md similarity index 87% rename from Publications/IFC4 Add2 DTV/Documentation.md rename to Publications/IFC4 Add2 TC1/Documentation.md index 87d90db31..17b5d730b 100644 --- a/Publications/IFC4 Add2 DTV/Documentation.md +++ b/Publications/IFC4 Add2 TC1/Documentation.md @@ -10,10 +10,10 @@

- - Industry Foundation Classes


- Version 4 - Addendum 2 - Design Transfer View + Industry Foundation Classes 4.0.2.1


+ + Version 4.0 - Addendum 2 - Technical Corrigendum 1

@@ -21,7 +21,7 @@

- © buildingSMART 1996-2016 - This document is owned and copyrighted by buildingSMART International Limited
+ © buildingSMART 1996-2017 - This document is owned and copyrighted by buildingSMART International Limited
By using the IFC4 specification you agree to the following copyright notice

diff --git a/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcObjectDefinition/DocEntity.xml b/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcObjectDefinition/DocEntity.xml index 6a8b5c5a0..fa19d9cf8 100644 --- a/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcObjectDefinition/DocEntity.xml +++ b/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcObjectDefinition/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcProject/DocEntity.xml b/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcProject/DocEntity.xml index c2a2d9adf..a0f210244 100644 --- a/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcProject/DocEntity.xml +++ b/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcProject/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcProxy/DocEntity.xml b/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcProxy/DocEntity.xml index cb5ca98fb..cc93a9c26 100644 --- a/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcProxy/DocEntity.xml +++ b/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcProxy/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcRelAssigns/DocEntity.xml b/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcRelAssigns/DocEntity.xml index 5d23bbbc8..f702239d4 100644 --- a/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcRelAssigns/DocEntity.xml +++ b/Sections/Core data schemas/Schemas/IfcKernel/Entities/IfcRelAssigns/DocEntity.xml @@ -23,7 +23,7 @@ - + Particular type of the assignment relationship. It can constrain the applicable object types, used within the role of _RelatedObjects_. { .change-ifc2x4} > IFC4 CHANGE&nbsp; The attribute is deprecated and shall no longer be used. A NIL value should always be assigned. diff --git a/Sections/Core data schemas/Schemas/IfcKernel/Types/IfcObjectTypeEnum/DocEnumeration.xml b/Sections/Core data schemas/Schemas/IfcKernel/Types/IfcObjectTypeEnum/DocEnumeration.xml index ac8002701..874eef74c 100644 --- a/Sections/Core data schemas/Schemas/IfcKernel/Types/IfcObjectTypeEnum/DocEnumeration.xml +++ b/Sections/Core data schemas/Schemas/IfcKernel/Types/IfcObjectTypeEnum/DocEnumeration.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcDistributionElement/DocEntity.xml b/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcDistributionElement/DocEntity.xml index 6998e7d23..bda1c4b30 100644 --- a/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcDistributionElement/DocEntity.xml +++ b/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcDistributionElement/DocEntity.xml @@ -1,5 +1,5 @@  - + @@ -11,7 +11,7 @@ - + Reference to the element to port connection relationship. The relationship then refers to the port which is contained in this element. { .change-ifc2x4} diff --git a/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcOpeningElement/Documentation.md b/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcOpeningElement/Documentation.md index 749dc0e15..7fcba08c8 100644 --- a/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcOpeningElement/Documentation.md +++ b/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcOpeningElement/Documentation.md @@ -1,11 +1,12 @@ The opening element stands for opening, recess or chase, all reflecting voids. It represents a void within any element that has physical manifestation. Openings can be inserted into walls, slabs, beams, columns, or other elements. -The IFC specification provides two entities for opening elements: +There are two main representations for opening elements: -* _IfcOpeningStandardCase_ is used for all openings that have a constant profile along a linear extrusion. They are placed relative to the voided elements and the extrusion direction is perpendicular to the plane of the element (horizontally for walls, vertically for slabs). Only a single extrusion body is allowed. It cuts through the whole thickness of the voided element, i.e. it reflects a true opening. +* Openings that have a constant profile along a linear extrusion. They are placed relative to the voided elements and the extrusion direction is perpendicular to the plane of the element (horizontally for walls, vertically for slabs). Only a single extrusion body is allowed. It cuts through the whole thickness of the voided element, i.e. it reflects a true opening. +>> NOTE  The entity _IfcOpeningStandardCase_ has been deprecated. * _IfcOpeningElement_ is used for all other occurrences of openings and in particular also for niches or recesses. -> NOTE  View definitions or implementer agreements may restrict the types of elements which can be voided by an _IfcOpeningElement_ or _IfcOpeningStandardCase_ +> NOTE  Model View Definitions may restrict the types of elements which can be voided by an _IfcOpeningElement_ There are two different types of opening elements: diff --git a/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcOpeningStandardCase/DocEntity.xml b/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcOpeningStandardCase/DocEntity.xml index 21a800394..c2865473b 100644 --- a/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcOpeningStandardCase/DocEntity.xml +++ b/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcOpeningStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcPort/DocEntity.xml b/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcPort/DocEntity.xml index ed7b3ed50..993049d37 100644 --- a/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcPort/DocEntity.xml +++ b/Sections/Core data schemas/Schemas/IfcProductExtension/Entities/IfcPort/DocEntity.xml @@ -7,7 +7,7 @@ - + Reference to the element to port connection relationship. The relationship then refers to the element in which this port is contained. { .change-ifc2x4} > IFC4 CHANGE&nbsp; The cardinality has been changed from 1:1 to 0:1. IFC4 DEPRECATION&nbsp; The inverse relationship is deprecated for fixed ports due to deprecation of _IfcRelConnectsPortToElement_ for this usage. Use inverse relationship _Nests_ instead. diff --git a/Sections/Core data schemas/Schemas/IfcProductExtension/PropertySets/Pset_LandRegistration/Documentation.md b/Sections/Core data schemas/Schemas/IfcProductExtension/PropertySets/Pset_LandRegistration/Documentation.md index e9882da86..4f3d1b11d 100644 --- a/Sections/Core data schemas/Schemas/IfcProductExtension/PropertySets/Pset_LandRegistration/Documentation.md +++ b/Sections/Core data schemas/Schemas/IfcProductExtension/PropertySets/Pset_LandRegistration/Documentation.md @@ -1 +1,3 @@ -Specifies the identity of land within a statutory registration system. NOTE: The property LandTitleID is to be used in preference to deprecated attribute LandTitleNumber in IfcSite. +Specifies the identity of land within a statutory registration system. + +
diff --git a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorLiningProperties/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorLiningProperties/DocEntity.xml index 00d1c1930..81c733f9a 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorLiningProperties/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorLiningProperties/DocEntity.xml @@ -96,10 +96,10 @@ If the _TransomThickness_ is set to zero (and the _TransomOffset_ set to a posit - + Pointer to the shape aspect, if given. The shape aspect reflects the part of the door shape, which represents the door lining. -{ .change-ifc2x4} -> IFC4 CHANGE&nbsp; The attribute is deprecated and shall no longer be used, i.e. the value shall be NIL ($). +{ .deprecated} +> DEPRECATION&nbsp; The attribute is deprecated and shall no longer be used, i.e. the value shall be NIL ($). diff --git a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorPanelProperties/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorPanelProperties/DocEntity.xml index 6c6eda5ad..903cb46b5 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorPanelProperties/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorPanelProperties/DocEntity.xml @@ -39,7 +39,7 @@ - + Pointer to the shape aspect, if given. The shape aspect reflects the part of the door shape, which represents the door panel. { .deprecated} > DEPRECATION&nbsp; The attribute is deprecated and shall no longer be used, i.e. the value shall be NIL ($). diff --git a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorStyle/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorStyle/DocEntity.xml index c660a7f01..df13ce56f 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorStyle/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcDoorStyle/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowLiningProperties/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowLiningProperties/DocEntity.xml index 8e0803f4d..5d11e7ceb 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowLiningProperties/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowLiningProperties/DocEntity.xml @@ -82,10 +82,10 @@ If the _MullionThickness_ is set to zero (and the _MullionOffset_ set to a posit - + Optional link to a shape aspect definition, which points to the part of the geometric representation of the window style, which is used to represent the lining. -{ .change-ifc2x4} -> IFC4 CHANGE The attribute is deprecated and shall no longer be used, i.e. the value shall be NIL ($). +{ .deprecated} +> DEPRECATION&nbsp; The attribute is deprecated and shall no longer be used, i.e. the value shall be NIL ($). diff --git a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowPanelProperties/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowPanelProperties/DocEntity.xml index 9b518b43b..f05aea315 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowPanelProperties/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowPanelProperties/DocEntity.xml @@ -39,7 +39,7 @@ - + Optional link to a shape aspect definition, which points to the part of the geometric representation of the window style, which is used to represent the panel. { .deprecated} > DEPRECATION&nbsp; The attribute is deprecated and shall no longer be used, i.e. the value shall be NIL ($). diff --git a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowStyle/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowStyle/DocEntity.xml index cf7301a12..bbf9cf2e2 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowStyle/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcArchitectureDomain/Entities/IfcWindowStyle/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDevicePHistory/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDevicePHistory/DocPropertySet.xml new file mode 100644 index 000000000..ea0d072da --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDevicePHistory/DocPropertySet.xml @@ -0,0 +1,7 @@ + + + + + + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDevicePHistory/Documentation.md b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDevicePHistory/Documentation.md new file mode 100644 index 000000000..7d834e996 --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDevicePHistory/Documentation.md @@ -0,0 +1 @@ +Electric flow storage device performance history common attributes. diff --git a/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDeviceTypeCommon/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDeviceTypeCommon/DocPropertySet.xml index 06ffd2b59..d0d3e1b52 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDeviceTypeCommon/DocPropertySet.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_ElectricFlowStorageDeviceTypeCommon/DocPropertySet.xml @@ -25,6 +25,10 @@ + + + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_SolarDeviceTypeCommon/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_SolarDeviceTypeCommon/DocPropertySet.xml index e0bd933d7..0d01d05f1 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_SolarDeviceTypeCommon/DocPropertySet.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_SolarDeviceTypeCommon/DocPropertySet.xml @@ -9,6 +9,8 @@ + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_TransformerTypeCommon/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_TransformerTypeCommon/DocPropertySet.xml index 1e8dde48e..07e42b71c 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_TransformerTypeCommon/DocPropertySet.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcElectricalDomain/PropertySets/Pset_TransformerTypeCommon/DocPropertySet.xml @@ -25,6 +25,8 @@ + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_AirToAirHeatRecoveryTypeCommon/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_AirToAirHeatRecoveryTypeCommon/DocPropertySet.xml index 83756eb4c..2ee81a1a8 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_AirToAirHeatRecoveryTypeCommon/DocPropertySet.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_AirToAirHeatRecoveryTypeCommon/DocPropertySet.xml @@ -9,7 +9,7 @@ - + diff --git a/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_SpaceThermalPHistory/Documentation.md b/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_SpaceThermalPHistory/Documentation.md index 0266060ad..72eee5502 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_SpaceThermalPHistory/Documentation.md +++ b/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_SpaceThermalPHistory/Documentation.md @@ -1 +1 @@ -Thermal and air flow conditions of a space or zone. HISTORY: New property set in IFC 2x2. +Thermal and air flow conditions of a space or zone. diff --git a/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_TankPHistory/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_TankPHistory/DocPropertySet.xml new file mode 100644 index 000000000..b7c7a01f2 --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_TankPHistory/DocPropertySet.xml @@ -0,0 +1,9 @@ + + + + + + + + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_TankPHistory/Documentation.md b/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_TankPHistory/Documentation.md new file mode 100644 index 000000000..73d7f84ec --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcHvacDomain/PropertySets/Pset_TankPHistory/Documentation.md @@ -0,0 +1 @@ +Tank performance history common attributes. diff --git a/Sections/Domain specific data schemas/Schemas/IfcPlumbingFireProtectionDomain/Types/IfcSanitaryTerminalTypeEnum/Documentation.md b/Sections/Domain specific data schemas/Schemas/IfcPlumbingFireProtectionDomain/Types/IfcSanitaryTerminalTypeEnum/Documentation.md index 267556dae..da9ae524c 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcPlumbingFireProtectionDomain/Types/IfcSanitaryTerminalTypeEnum/Documentation.md +++ b/Sections/Domain specific data schemas/Schemas/IfcPlumbingFireProtectionDomain/Types/IfcSanitaryTerminalTypeEnum/Documentation.md @@ -1,5 +1,6 @@ The _IfcSanitaryTerminalTypeEnum_ defines the range of different types of sanitary terminal that can be specified. -> NOTE  The value WCSEAT has been deprecated and should no longer be used; toilet seats should be represented by IfcDiscreteAccessory with ObjectType 'WC Seat'. +{ .deprecated} +> DEPRECATION  The value WCSEAT has been deprecated and should no longer be used; toilet seats should be represented by _IfcDiscreteAccessory_ with ObjectType 'WC Seat'. > HISTORY  New type in IFC2x2. diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcPile/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcPile/DocEntity.xml index 66143e209..32c76c49b 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcPile/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcPile/DocEntity.xml @@ -18,7 +18,7 @@ - + Deprecated. { .change-ifc2x4} diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcementDefinitionProperties/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcementDefinitionProperties/DocEntity.xml index f4296e18a..4edb7fab1 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcementDefinitionProperties/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcementDefinitionProperties/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingBar/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingBar/DocEntity.xml index 67d1207f0..888e6e668 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingBar/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingBar/DocEntity.xml @@ -7,7 +7,7 @@ - + Deprecated. { .change-ifc2x4} @@ -18,7 +18,7 @@ - + The effective cross-section area of the reinforcing bar or group of bars. { .change-ifc2x4} @@ -29,7 +29,7 @@ - + Deprecated. { .change-ifc2x4} @@ -51,7 +51,7 @@ - + Deprecated. { .change-ifc2x4} diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingBarType/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingBarType/DocEntity.xml index 3d3a8ff0d..2f369fde3 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingBarType/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingBarType/DocEntity.xml @@ -1,5 +1,5 @@  - + @@ -15,7 +15,7 @@ - + The nominal diameter defining the cross-section size of the reinforcing bar. @@ -23,7 +23,7 @@ - + The effective cross-section area of the reinforcing bar. @@ -31,7 +31,7 @@ - + The total length of the reinforcing bar. The total length of bended bars are calculated according to local standards with corrections for the bends. @@ -39,7 +39,7 @@ - + Indicator for whether the bar surface is plain or textured. @@ -47,7 +47,7 @@ - + Shape code per a standard like ACI 315, ISO 3766, or a similar standard. It is presumed that a single standard for defining the bar bending is used throughout the project and that this standard is referenced from the _IfcProject_ object through the _IfcDocumentReference_ mechanism. @@ -55,7 +55,7 @@ - + Bending shape parameters. Their meaning is defined by the bending shape code and the respective standard. @@ -70,7 +70,7 @@ (PredefinedType <> IfcReinforcingBarTypeEnum.USERDEFINED) OR ((PredefinedType = IfcReinforcingBarTypeEnum.USERDEFINED) AND EXISTS(SELF\IfcElementType.ElementType)) - + Bending parameters must be accompanied by a shape code. NOT EXISTS(BendingParameters) OR EXISTS(BendingShapeCode) diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingElement/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingElement/DocEntity.xml index bc63b147c..e15830ac6 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingElement/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingElement/DocEntity.xml @@ -1,5 +1,5 @@  - + @@ -13,10 +13,8 @@ - - Deprecated. - -{ .change-ifc2x4} + + { .change-ifc2x4} > IFC4 CHANGE&nbsp; Attribute deprecated. Use material association at _IfcReinforcingElementType_ instead. diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingMesh/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingMesh/DocEntity.xml index ae2c9ed82..4d95ac681 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingMesh/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingMesh/DocEntity.xml @@ -1,5 +1,5 @@  - + @@ -7,7 +7,7 @@ - + Deprecated. { .change-ifc2x4} @@ -18,7 +18,7 @@ - + Deprecated. { .change-ifc2x4} @@ -29,7 +29,7 @@ - + Deprecated. { .change-ifc2x4} @@ -40,7 +40,7 @@ - + Deprecated. { .change-ifc2x4} @@ -51,7 +51,7 @@ - + Deprecated. { .change-ifc2x4} @@ -62,7 +62,7 @@ - + Deprecated. { .change-ifc2x4} @@ -73,7 +73,7 @@ - + Deprecated. { .change-ifc2x4} @@ -84,7 +84,7 @@ - + Deprecated. { .change-ifc2x4} diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingMeshType/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingMeshType/DocEntity.xml index 0f5468b9b..3b36d22a2 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingMeshType/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcReinforcingMeshType/DocEntity.xml @@ -15,7 +15,7 @@ - + The overall length of the mesh measured in its longitudinal direction. @@ -23,7 +23,7 @@ - + The overall width of the mesh measured in its transversal direction. @@ -31,7 +31,7 @@ - + The nominal diameter denoting the cross-section size of the longitudinal bars. @@ -39,7 +39,7 @@ - + The nominal diameter denoting the cross-section size of the transverse bars. @@ -47,7 +47,7 @@ - + The effective cross-section area of the longitudinal bars of the mesh. @@ -55,7 +55,7 @@ - + The effective cross-section area of the transverse bars of the mesh. @@ -63,7 +63,7 @@ - + The spacing between the longitudinal bars. Note: an even distribution of bars is presumed; other cases are handled by classification or property sets. @@ -71,7 +71,7 @@ - + The spacing between the transverse bars. Note: an even distribution of bars is presumed; other cases are handled by classification or property sets. @@ -79,7 +79,7 @@ - + If this mesh type is bent rather than planar, this attribute provides a shape code per a standard like ACI 315, ISO 3766, or a similar standard. It is presumed that a single standard for defining the mesh bending is used throughout the project and that this standard is referenced from the _IfcProject_ object through the _IfcDocumentReference_ mechanism. @@ -87,7 +87,7 @@ - + If this mesh type is bent rather than planar, this attribute provides bending shape parameters. Their meaning is defined by the bending shape code and the respective standard. @@ -102,7 +102,7 @@ (PredefinedType <> IfcReinforcingMeshTypeEnum.USERDEFINED) OR ((PredefinedType = IfcReinforcingMeshTypeEnum.USERDEFINED) AND EXISTS(SELF\IfcElementType.ElementType)) - + Bending parameters must be accompanied by a shape code. NOT EXISTS(BendingParameters) OR EXISTS(BendingShapeCode) diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcTendon/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcTendon/DocEntity.xml index 50b1d0870..e57e357f7 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcTendon/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcTendon/DocEntity.xml @@ -18,7 +18,7 @@ - + The nominal diameter defining the cross-section size of the tendon. { .change-ifc2x4} @@ -29,7 +29,7 @@ - + The effective cross-section area of the tendon. { .change-ifc2x4} @@ -40,7 +40,7 @@ - + The maximum allowed tension force that can be applied on the tendon. @@ -48,7 +48,7 @@ - + The prestress to be applied on the tendon. @@ -56,7 +56,7 @@ - + The friction coefficient between tendon and tendon sheet while the tendon is unbonded. @@ -64,7 +64,7 @@ - + The deformation of an anchor or slippage of tendons when the prestressing device is released. @@ -72,7 +72,7 @@ - + The smallest curvature radius calculated on the whole effective length of the tendon where the tension properties are still valid. diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcTendonType/DocEntity.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcTendonType/DocEntity.xml index 2df0281df..2c9ae006c 100644 --- a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcTendonType/DocEntity.xml +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/Entities/IfcTendonType/DocEntity.xml @@ -15,7 +15,7 @@ - + The nominal diameter defining the cross-section size of the prestressed part of the tendon. @@ -23,7 +23,7 @@ - + The effective cross-section area of the prestressed part of the tendon. @@ -31,7 +31,7 @@ - + Diameter of the sheeth (duct) around the tendon, if there is one with this type of tendon. diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingBarCommon/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingBarCommon/DocPropertySet.xml new file mode 100644 index 000000000..8311fb49c --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingBarCommon/DocPropertySet.xml @@ -0,0 +1,14 @@ + + + + + + + + + + + + + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingBarCommon/Documentation.md b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingBarCommon/Documentation.md new file mode 100644 index 000000000..01a66dc5a --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingBarCommon/Documentation.md @@ -0,0 +1 @@ +Properties common to the definition of all occurrences of IfcReinforcingBar. diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingMeshCommon/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingMeshCommon/DocPropertySet.xml new file mode 100644 index 000000000..0883d68bd --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingMeshCommon/DocPropertySet.xml @@ -0,0 +1,18 @@ + + + + + + + + + + + + + + + + + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingMeshCommon/Documentation.md b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingMeshCommon/Documentation.md new file mode 100644 index 000000000..79643935c --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_ReinforcingMeshCommon/Documentation.md @@ -0,0 +1 @@ +Properties common to the definition of all occurrences of IfcReinforcingMesh. diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonAnchorCommon/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonAnchorCommon/DocPropertySet.xml new file mode 100644 index 000000000..7ac4b57e9 --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonAnchorCommon/DocPropertySet.xml @@ -0,0 +1,8 @@ + + + + + + + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonAnchorCommon/Documentation.md b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonAnchorCommon/Documentation.md new file mode 100644 index 000000000..b037c46a6 --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonAnchorCommon/Documentation.md @@ -0,0 +1 @@ +Properties common to the definition of all occurrences of IfcTendonAnchor. diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonCommon/DocPropertySet.xml b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonCommon/DocPropertySet.xml new file mode 100644 index 000000000..941a69c41 --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonCommon/DocPropertySet.xml @@ -0,0 +1,10 @@ + + + + + + + + + + diff --git a/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonCommon/Documentation.md b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonCommon/Documentation.md new file mode 100644 index 000000000..b8d7df569 --- /dev/null +++ b/Sections/Domain specific data schemas/Schemas/IfcStructuralElementsDomain/PropertySets/Pset_TendonCommon/Documentation.md @@ -0,0 +1 @@ +Properties common to the definition of all occurrences of IfcTendon. diff --git a/Sections/Resource definition data schemas/Schemas/IfcExternalReferenceResource/DocSchema.xml b/Sections/Resource definition data schemas/Schemas/IfcExternalReferenceResource/DocSchema.xml index 5d20db741..055224291 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcExternalReferenceResource/DocSchema.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcExternalReferenceResource/DocSchema.xml @@ -134,9 +134,6 @@ - - - diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcFaceBasedSurfaceModel/DocEntity.xml b/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcFaceBasedSurfaceModel/DocEntity.xml index ef3e1689a..b1728ff2a 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcFaceBasedSurfaceModel/DocEntity.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcFaceBasedSurfaceModel/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcFaceBasedSurfaceModel/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcFaceBasedSurfaceModel/Documentation.md index 0f990727f..12a7b7fa2 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcFaceBasedSurfaceModel/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcFaceBasedSurfaceModel/Documentation.md @@ -16,4 +16,4 @@ Informal Propositions: 2. The fbsm faces have dimensionality 2. { .deprecated} -> IFC4 CHANGE  The entity has been deprecated and shall not be used. The entity _IfcFacetedBrep_ shall be used instead. +> IFC4 CHANGE  The entity has been deprecated and shall not be used. The entity _IfcShellBasedSurfaceModel_ for open shells and _IfcFacetedBrep_ for closed shells shall be used instead. diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcTriangulatedFaceSet/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcTriangulatedFaceSet/Documentation.md index 11a6586e0..a0c548124 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcTriangulatedFaceSet/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometricModelResource/Entities/IfcTriangulatedFaceSet/Documentation.md @@ -39,7 +39,7 @@ Figure 4 shows the use of _IfcTriangulatedFaceSet_ without annotation. The diagr IfcTriangulatedFaceSet_Example-01 -

Figure 168 shows an IfcTriangulatedFaceSet represented by

+

Figure 2 shows an IfcTriangulatedFaceSet represented by

CoordIndex: ((1,6,5), (1,2,6), (6,2,7), (7,2,3), (7,8,6), (6,8,5), (5,8,1), (1,8,4), (4,2,1), (2,4,3), (4,8,7), (7,3,4))
IfcCartesianPointList3D: ((0.,0.,0.), (1.,0.,0.), (1.,1.,0.), (0.,1.,0.), (0.,0.,2.), (1.,0.,2.), (1.,1.,2.), (0.,1.,2.)) diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcCircle/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcCircle/Documentation.md index 2a2de6b5d..06636ae94 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcCircle/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcCircle/Documentation.md @@ -1,11 +1,13 @@ An _IfcCircle_ is a curve consisting of a set of points having equal distance from the center. -> NOTE  A circular arc segment is defined by using the _IfcTrimmedCurve_ with _BasisCurve_ being an _IfcCircle_. +> NOTE  A circular arc segment is defined by using the _IfcTrimmedCurve_ with _BasisCurve_ being an _IfcCircle_ or alternatively as a circular arc defined by three points within an _IfcIndexedPolyCurve_. Figure 1 illustrates the definition of _IfcCircle_ within a three-dimensional position coordinate system placed within the object coordinate system of an element. !["axis1 placement"](../../../../../../figures/ifccircle-layout1.gif "Figure 1 — Circle layout") +The _IfcCircle_ ia parameterized using numeric values in correspondence to the plane angle unit provided within the _IfcUnitAssignment_. If the plane angle unit is 'Degree' the parametric range of a circle is 0 ≤ _u_ ≤ 360, if the plane angle unit is radians, the parametric range is 0 ≤ _u_ ≤ 2π. +   { .extDef} @@ -24,8 +26,7 @@ Figure 1 illustrates the definition of _IfcCircle_ within a three-dimensional po >> >>> ![formula](../../../../../../figures/ifccircle-math1.gif) >> -> The parameterization range is 0 ≤ _u_ ≤ 2π (0 ≤ _u_ ≤ 360 degree). -> In the placement coordinate system defined above, the circle is the equation _C_ = 0, where +> The parameterization range is 0 ≤ _u_ ≤ 360 degree, _u_ is an angular parameter and when a numerical value is specified it shall use the current units for plane angle measure. In the placement coordinate system defined above, the circle is the equation _C_ = 0, where > >> >>> ![formula](../../../../../../figures/ifccircle-math2.gif) diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcIndexedPolyCurve/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcIndexedPolyCurve/Documentation.md index c4ffe3ea7..4996f2c0c 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcIndexedPolyCurve/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcIndexedPolyCurve/Documentation.md @@ -5,11 +5,11 @@ In the case that the list of _Segments_ is provided, it is interpreted as such: * Segment of type _IfcLineIndex_: The first index is the start point of the poly line segment, the last index is the end point of the poly line segment. If more than two indices are included, then all intermediate indices define intermediate points of the polyline connected in the order of appearance of the indices; * Segment of type _IfcArcIndex_: The first index is the start point of the circular arc, the second index is a point on arc, the third index is the end point of the circular arc. The three points shall not be co-linear. In case that this informal proposition is not maintained, the arc segment shall be treated as a polyline segment. -> EXAMPLE  Figure 2 illustrates a bounded open _IfcIndexedPolyCurve_ having straight and arc segments. In this example, the straight segments only have two points and one edge, however more then two indices into the Cartesian point list can be includes, defining a multi edge polyline segment. +> EXAMPLE  Figure 2 illustrates a bounded open _IfcIndexedPolyCurve_ having straight and arc segments. In this example, the straight segments only have two points and one edge, however more then two indices into the Cartesian point list can be includes, defining a multi edge polyline segment. The parametric length of the total poly curve is the sum of the parametric length of its segments, the parametric length of the arc segments are shown in radians, which applies, if the plane angle measure of the data set is Radians. In case that the plane angle measure is Degree, the parametric length of the arc segments has degree values with 90. being the parametric length of a quarter circle. !["poly curve with arcs examples"](../../../../../../figures/ifcindexedpolycurve-fig1.png "Figure 2 — Bounded open _IfcIndexedPolyCurve_ with straight and arc segments") -> EXAMPLE  Figure 2 illustrates a bounded open _IfcIndexedPolyCurve_ having only straight segments. In this example, no list of _Segments_ is provided, hence the points are drawn in the order of their appearance in the _IfcCartesianPointList_. +> EXAMPLE  Figure 2 illustrates a bounded open _IfcIndexedPolyCurve_ having only straight segments. In this example, no list of _Segments_ is provided, hence the points are drawn in the order of their appearance in the _IfcCartesianPointList_. The parametric length of the total poly curve is the sum of the parametric length of its segments, with each line segment having the parametric length of 1.0. !["poly curve examples"](../../../../../../figures/ifcindexedpolycurve-fig2.png "Figure 2 — Bounded open _IfcIndexedPolyCurve_ with only straight segments") diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcLine/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcLine/Documentation.md index f24e7bc02..935e500f8 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcLine/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcLine/Documentation.md @@ -2,9 +2,7 @@ > NOTE  A line segment is defined using either the _IfcPolyline_ with two _Points_, or the _IfcTrimmedCurve_ with _BasisCurve_ being an _IfcLine_. -> EXAMPLE  Figure 1 illustrates an unbounded _IfcLine_ and a bounded _IfcTrimmedCurve_. A bounded line starting at 0.,0. and ending at 0.,2. can be defined by: - -> 1. _IfcLine_ with _IfcVector_._Magnitude_: 2.0 AND _IfcTrimmedCurve_ with _Trim1_: 0. and _Trim2_: 1. (and trimming preference being parameter); +> EXAMPLE  Figure 1 illustrates an unbounded _IfcLine_ and a bounded line. The bounded line starting at 0.,0. and ending at 0.,2. can be defined by: > 1. _IfcLine_ with _IfcVector_._Magnitude_: 2.0 AND _IfcTrimmedCurve_ with _Trim1_: 0. and _Trim2_: 1. (and trimming preference being parameter); > 2. _IfcLine_ with _IfcVector_._Magnitude_: 1.0 AND _IfcTrimmedCurve_ with _Trim1_: 0. and _Trim2_: 2. (and trimming preference being parameter); > 3. _IfcLine_ AND _IfcTrimmedCurve_ with _Trim1_::_IfcCartesianPoint_ [0.,0.] and _Trim2_::_IfcCartesianPoint_ [0.,2.] (and trimming preference being Cartesian) - the _IfcVector_._Magnitude_ has no effect; > 4. _IfcPolyline_ with _Points[1]_ being 0.,0. and _Points[2]_ being 0.,2. @@ -12,6 +10,8 @@ !["line examples"](../../../../../../figures/ifcline-fig1.png "Figure 1 — Unbounded _IfcLine_ and bounded _IfcTrimmedCurve_") +  + { .extDef} > NOTE  Definition according to ISO/CD 10303-42:1992 > A line is an unbounded curve with constant tangent direction. A line is defined by a point and a direction. The positive direction of the line is in the direction of the dir vector. The curve is parameterized as follows: diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcPolyline/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcPolyline/Documentation.md index c09c69daa..6f263756b 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcPolyline/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcPolyline/Documentation.md @@ -1,15 +1,15 @@ The _IfcPolyline_ is a bounded curve with only linear segments defined by a list of Cartesian points. If the first and the last Cartesian point in the list are identical, then the polyline is a closed curve, otherwise it is an open curve. -> EXAMPLE  Figure 1 illustrates a bounded _IfcPolyline_ and shows the parametric length of each segment and of the total polyline. +> EXAMPLE  Figure 1 illustrates a bounded _IfcPolyline_ and shows the parametric length of each segment and of the total polyline. The parametric length of the entire polyline is _n_ - 1, where _n_ is the number of _Points_. !["polyline examples"](../../../../../../figures/ifcpolyline-fig1.png "Figure 1 — Bounded _IfcPolyline_ with parametric length") { .extDef} > NOTE  Definition according to ISO/CD 10303-42:1992 -> A polyline is a bounded curve of _n_ - 1 linear segments, defined by a list of _n_ points, P~1~, P~2~ ... P~n~. The _i_th segment of the curve is parameterized as follows: +> A polyline is a bounded curve of _n_ - 1 linear segments, defined by a list of _n_ points, P~1~, P~2~ ... P~n~. The _i_^th^ segment of the curve is parameterized as follows: { .extDef} >> ![Image](../../../../../../figures/ifcpolyline-math1.gif)    _for_ 1 ≤ _i_ ≤ _n_ - 1 -> where _i_ - 1 ≤ _u_ ≤ _i_ and with parametric range of 0 <≤ _u_ ≤ _n_ - 1. +> where _i_ - 1 ≤ _u_ ≤ _i_ and with parametric range of 0 ≤ _u_ ≤ _n_ - 1. > NOTE  Entity adapted from **polyline** in ISO 10303-42. diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcTrimmedCurve/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcTrimmedCurve/Documentation.md index 03e0bdc22..5926342af 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcTrimmedCurve/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Entities/IfcTrimmedCurve/Documentation.md @@ -4,7 +4,7 @@ !["curve parameterization"](../../../../../../figures/ifctrimmedcurve_parameterization.png "Figure 1 — Trimmed curve parameterization") -Figure 1 shows the four arcs (dashed blue and green lines with arrow showing different orientations) that can be defined by the same _BasisCurve_ (of type _IfcCircle_) and the same trimming points (given by Cartesian points and parameter values) by using different assignments to _Trim1_ and _Trim2_ and _SenseAgreement_. +> EXAMPLE  Figure 1 shows the four arcs (dashed blue and green lines with arrow showing different orientations) that can be defined by the same _BasisCurve_ of type _IfcCircle_ and the same trimming points (given by Cartesian points and parameter values) by using different assignments to _Trim1_ and _Trim2_ and _SenseAgreement_. The trim 1 and trim 2 values for TrimmingPreference=.PARAMETER. are shown as degree values, which applies if the plane area measure is 'Degree', in case of plane area measure 'Radians' those would be ½π and π. > NOTE  Since the _BasisCurve_ is closed (type _IfcCircle_), the exception of the informal proposition IP3 applies, i.e. the sense flag is not required to be consistent with the parameter values of _Trim1_ and _Trim1_, so the rule (sense = parameter 1 < parameter 2) may not be fulfilled. diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Functions/IfcSurfaceWeightsPositive/Expression.txt b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Functions/IfcSurfaceWeightsPositive/Expression.txt index e829e5ea2..0cff98394 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Functions/IfcSurfaceWeightsPositive/Expression.txt +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Functions/IfcSurfaceWeightsPositive/Expression.txt @@ -3,11 +3,12 @@ LOCAL Result : BOOLEAN := TRUE; + Weights : ARRAY [ 0 : B\IfcBSplineSurface.UUpper ] OF ARRAY [ 0 : B\IfcBSplineSurface.VUpper ] OF REAL := B.Weights; END_LOCAL; REPEAT i := 0 TO B\IfcBSplineSurface.UUpper; REPEAT j := 0 TO B\IfcBSplineSurface.VUpper; - IF (B.Weights[i][j] <= 0.0) THEN + IF (Weights[i][j] <= 0.0) THEN Result := FALSE; RETURN(Result); END_IF; diff --git a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Types/IfcCurveOnSurface/DocSelect.xml b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Types/IfcCurveOnSurface/DocSelect.xml index 6d5bdef30..a07bb0c8a 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Types/IfcCurveOnSurface/DocSelect.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcGeometryResource/Types/IfcCurveOnSurface/DocSelect.xml @@ -4,7 +4,7 @@ - + @@ -13,7 +13,6 @@ - diff --git a/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/DocSchema.xml b/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/DocSchema.xml index f541315c2..35b5c47c9 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/DocSchema.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/DocSchema.xml @@ -105,9 +105,6 @@ - - - diff --git a/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialClassificationRelationship/DocEntity.xml b/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialClassificationRelationship/DocEntity.xml index 078e01850..0a45a8e6a 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialClassificationRelationship/DocEntity.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialClassificationRelationship/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialLayer/DocEntity.xml b/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialLayer/DocEntity.xml index f0afbb2d9..e9c4f9ab2 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialLayer/DocEntity.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialLayer/DocEntity.xml @@ -62,8 +62,7 @@ Category of the material layer, e.g. the role it has in the layer set it belongs to (such as 'load bearing', 'thermal insulation' etc.). The list of keywords might be extended by model view definitions, however the following keywords shall apply in general: * 'LoadBearing' &mdash; for all material layers having a load bearing function. * 'Insulation' &mdash; for all material layers having an insolating function. -* 'Inner finish' &mdash; for the material layer being the inner finish. -* 'Outer finish' &mdash; for the material layer being the outer finish. +* 'Finish' &mdash; for the material layer being the inner or outer finish. diff --git a/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialList/DocEntity.xml b/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialList/DocEntity.xml index ffe34b971..2dc29a3f2 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialList/DocEntity.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcMaterialResource/Entities/IfcMaterialList/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Entities/IfcUnitAssignment/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Entities/IfcUnitAssignment/Documentation.md index 292ea9944..96da648b1 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Entities/IfcUnitAssignment/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Entities/IfcUnitAssignment/Documentation.md @@ -2,4 +2,6 @@ > NOTE  A _IfcProject_ has a unit assignment which establishes a set of units which will be used globally within the project, if not otherwise defined. Other objects may have local unit assignments if there is a requirement for them to make use of units which do not fall within the project unit assignment. +All measures used in the geometric representation items are directly defined by the _IfcUnitAssignment_. The minimum set of units that shall be declared by the unit assignment has to include length unit and plane angle units if the IFC data set includes shape representations. + > HISTORY  New entity in IFC1.5.1. diff --git a/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Types/IfcCountMeasure/DocDefined.xml b/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Types/IfcCountMeasure/DocDefined.xml index 3155fd4fb..9880030a6 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Types/IfcCountMeasure/DocDefined.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Types/IfcCountMeasure/DocDefined.xml @@ -5,6 +5,7 @@ + diff --git a/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Types/IfcNumericMeasure/DocDefined.xml b/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Types/IfcNumericMeasure/DocDefined.xml index 34a710172..90e7d5a8b 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Types/IfcNumericMeasure/DocDefined.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcMeasureResource/Types/IfcNumericMeasure/DocDefined.xml @@ -5,6 +5,7 @@ + diff --git a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/DocSchema.xml b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/DocSchema.xml index 26618d0c6..3738b3c82 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/DocSchema.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/DocSchema.xml @@ -280,10 +280,6 @@ - - - - diff --git a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Entities/IfcFillAreaStyle/Documentation.md b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Entities/IfcFillAreaStyle/Documentation.md index c1f7c15db..1dc95017d 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Entities/IfcFillAreaStyle/Documentation.md +++ b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Entities/IfcFillAreaStyle/Documentation.md @@ -40,6 +40,3 @@ An _IfcFillAreaStyle_ can be assigned to _IfcFillArea_ via the _IfcPresentationS > NOTE  Corresponding ISO 10303 name: fill_area_style. Please refer to ISO/IS 10303-46:1994 for the final definition of the formal standard. > HISTORY  New entity in IFC2x2. - -{ .deprecated} -> DEPRECATION  The use of IfcFillAreaStyleTiles is deprecated, as its definition might change is future releases. diff --git a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Entities/IfcPresentationStyleAssignment/DocEntity.xml b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Entities/IfcPresentationStyleAssignment/DocEntity.xml index cc48065a5..140f19f5d 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Entities/IfcPresentationStyleAssignment/DocEntity.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Entities/IfcPresentationStyleAssignment/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcNullStyle/DocEnumeration.xml b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcNullStyle/DocEnumeration.xml index 9c1a13d55..fb4531b9a 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcNullStyle/DocEnumeration.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcNullStyle/DocEnumeration.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcPresentationStyleSelect/DocSelect.xml b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcPresentationStyleSelect/DocSelect.xml index 505734295..3477fb6f9 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcPresentationStyleSelect/DocSelect.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcPresentationStyleSelect/DocSelect.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcStyleAssignmentSelect/DocSelect.xml b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcStyleAssignmentSelect/DocSelect.xml index 718ce4497..6d338819c 100644 --- a/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcStyleAssignmentSelect/DocSelect.xml +++ b/Sections/Resource definition data schemas/Schemas/IfcPresentationAppearanceResource/Types/IfcStyleAssignmentSelect/DocSelect.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcBeam/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcBeam/Documentation.md index 0235a7a72..3c2772cb2 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcBeam/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcBeam/Documentation.md @@ -7,9 +7,10 @@ > NOTE  For any other longitudinal structural member, not constrained to be predominately horizontal nor vertical, or where this semantic information is irrelevant, the entity _IfcMember_ should be used. -There are two entities for beam occurrences: +There are two main representations for beam occurrences: + +* _IfcBeam_ with _IfcMaterialProfileSetUsage_ is used for all occurrences of beams, that have a profile defined that is swept along a directrix. The profile might be changed uniformly by a taper definition along the directrix. The profile parameter and its cardinal point of insertion can be fully described by the _IfcMaterialProfileSetUsage_. These beams are always represented geometricly by an 'Axis' and a 'SweptSolid' or 'AdvancedSweptSolid' shape representation (or by a 'Clipping' geometry based on the swept solid), if a 3D geometric representation is assigned. +>> NOTE  The entity _IfcBeamStandardCase_ has been deprecated, _IfcBeam_ with _IfcMaterialProfileSetUsage_ is used instead. +* _IfcBeam_ without _IfcMaterialProfileSetUsage_ is used for all other occurrences of beams, particularly for beams with non-uniformly changing profile sizes along the sweep, or beams having only 'AdvancedBrep', 'Brep', or 'SurfaceModel' geometry, or if a more parametric representation is not intended. -* _IfcBeamStandardCase_ used for all occurrences of beams, that have a profile defined that is swept along a directrix. The profile might be changed uniformly by a taper definition along the directrix. The profile parameter and its cardinal point of insertion can be fully described by the _IfcMaterialProfileSetUsage_. These beams are always represented geometricly by an 'Axis' and a 'SweptSolid' or 'AdvancedSweptSolid' shape representation (or by a 'Clipping' geometry based on the swept solid), if a 3D geometric representation is assigned. In addition they have to have a corresponding _IfcMaterialProfileSetUsage_ assigned. ->> NOTE  Model view definitions and implementer agreements may further constrain the applicable geometry types, for example, by excluding tapering from an _IfcBeamStandardCase_ implementation.* _IfcBeam_ used for all other occurrences of beams, particularly for beams with non-uniformly changing profile sizes along the sweep, or beams having only 'AdvancedBrep', 'Brep', 'SurfaceModel', or 'Tessellation' geometry. ->> NOTE  Model view definitions and implementer agreements may impose the use of _IfcBeam_ in all cases by excluding _IfcBeamStandardCase_ from scope of the model view. > HISTORY  New entity in IFC1.0 diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcBeamStandardCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcBeamStandardCase/DocEntity.xml index 208adfcd7..abe8370c8 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcBeamStandardCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcBeamStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcColumn/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcColumn/Documentation.md index e2d1858c1..07ad77d48 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcColumn/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcColumn/Documentation.md @@ -8,10 +8,10 @@ > NOTE  For any longitudial structural member, not constrained to be predominately horizontal nor vertical, or where this semantic information is irrelevant, the entity _IfcMember_ exists. -The IFC specification provides two entities for column occurrences: +There are two main representations for column occurrences: -* _IfcColumnStandardCase_ used for all occurrences of columns, tthat have a profile defined that is swept along a directrix. The profile might be changed uniformly by a taper definition along the directrix. The profile parameter and its cardinal point of insertion can be fully described by the _IfcMaterialProfileSetUsage_. These beams are always represented geometricly by an 'Axis' and a 'SweptSolid' or 'AdvancedSweptSolid' shape representation (or by a 'Clipping' geometry based on the swept solid), if a 3D geometric representation is assigned. In addition they have to have a corresponding _IfcMaterialProfileSetUsage_ assigned. ->> NOTE  View definitions and implementer agreements may further constrain the applicable geometry types, for example by excluding tapering from an _IfcColumnStandardCase_ implementation. -* _IfcColumn_ used for all other occurrences of columns, particularly for columns with changing profile sizes along the extrusion, or columns defined by non-linear extrusion, or columns having only 'Brep', or 'SurfaceModel' geometry. +* _IfcColumn_ with _IfcMaterialProfileSetUsage_ is used for all occurrences of columns, that have a profile defined that is swept along a directrix. The profile might be changed uniformly by a taper definition along the directrix. The profile parameter and its cardinal point of insertion can be fully described by the _IfcMaterialProfileSetUsage_. These columns are always represented geometricly by an 'Axis' and a 'SweptSolid' or 'AdvancedSweptSolid' shape representation (or by a 'Clipping' geometry based on the swept solid), if a 3D geometric representation is assigned. +>> NOTE  The entity _IfcColumnStandardCase_ has been deprecated, _IfcColumn_ with _IfcMaterialProfileSetUsage_ is used instead. +* _IfcColumn_ is used for all other occurrences of columns, particularly for columns with changing profile sizes along the extrusion, or columns defined by non-linear extrusion, or columns having only 'Brep', or 'SurfaceModel' geometry, or if a more parametric representation is not intended. > HISTORY  New entity in IFC1.0 diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcColumnStandardCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcColumnStandardCase/DocEntity.xml index 55a05b7ff..42da07fc2 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcColumnStandardCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcColumnStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoor/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoor/Documentation.md index 6e03bb303..a19140056 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoor/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoor/Documentation.md @@ -6,19 +6,19 @@ The _IfcDoor_ defines a particular occurrence of a door inserted in the spatial context of a project. A door can: * be inserted as a filler in an opening using the _IfcRelFillsElement_ relationship, then the _IfcDoor_ has an inverse attribute _FillsVoids_ provided; ->> NOTE  View definitions or implementer agreements may restrict the relationship to only include one door into one opening +>> NOTE  Model View Definitions may restrict the relationship to only include one door into one opening * be part of an element assembly, in general an _IfcCurtainWall_, using the _IfcRelAggregates_ relationship, then the _IfcDoor_ has an inverse attribute _Decomposes_ is provided; * be a "free standing" door, then the _IfcDoor_ has no inverse attributes _FillsVoids_ or _Decomposes_ provided. -This specification provides two entities for door occurrences: +There are two main representations for door occurrences: -* _IfcDoorStandardCase_ used for all occurrences of doors, that have a 'Profile' shape representation defined to which a set of shape parameters for lining and framing properties apply. Additionally it requires the provision of an _IfcDoorType_ that references one _IfcDoorLiningProperties_ and on to many _IfcDoorPanelProperties_; ->> NOTE  see _IfcDoorStandardCase_ for all specific constraints imposed by this subtype. -* _IfcDoor_ used for all other occurrences of doors, particularly for doors having only 'Brep', or 'SurfaceModel' geometry without applying shape parameters. +* _IfcDoor_ with a shape representation having RepresentationIdenfifier='Profile' is used for all occurrences of doors, that have a 'Profile' shape representation defined to which a set of shape parameters for lining and framing properties apply. Additionally it requires the provision of an _IfcDoorType_ that references one _IfcDoorLiningProperties_ and one to many _IfcDoorPanelProperties_; +>> NOTE  The entity _IfcDoorStandardCase_ has been deprecated. +* _IfcDoor_ with other shape representations an no assiged _IfcDoorLiningProperties_ and _IfcDoorPanelProperties_ is used for all other occurrences of doors, particularly for doors having only 'Brep', or 'SurfaceModel' geometry without applying shape parameters. -The actual parameters of the door and/or its shape are defined by the _IfcDoor_ as the occurrence definition (or project instance), or by the _IfcDoorType_ as the specific definition (or project type). The following parameters are given: +The actual parameters of the door and/or its shape are defined by the _IfcDoor_ as the object occurrence definition, or by the _IfcDoorType_ as the object type definition. The following parameters are provided: -* at the _IfcDoor_ or _IfcDoorStandardCase_ for occurrence specific parameters. The _IfcDoor_ specifies: +* at the _IfcDoor_ for occurrence specific parameters. The _IfcDoor_ specifies: * * the door width and height * the door opening direction (by the y-axis of the _ObjectPlacement_)* at the _IfcDoorType_, to which the _IfcDoor_ is related by the inverse relationship _IsTypedBy_ pointing to _IfcRelDefinesByType_, for type parameters common to all occurrences of the same type. @@ -38,10 +38,8 @@ The geometric representation of _IfcDoor_ is given by the _IfcProductDefinitionS The geometric representation of _IfcDoor_ is defined using the following (potentially multiple) _IfcShapeRepresentation_'s for its _IfcProductDefinitionShape_: -* **Profile**: A 'Curve3D' consisting of a single losed curve defining the outer boundary of the door (lining). The door parametric representation uses this profile in order to apply the door lining and panel parameter. If not provided, the profile of the _IfcOpeningElement_ is taken. +* **Profile**: A 'Curve3D' consisting of a single losed curve defining the outer boundary of the door (lining). The door parametric representation uses this profile in order to apply the door lining and panel parameter. If not provided, the profile of the _IfcOpeningElement_ is taken. * **FootPrint**: A 'GeometricCurveSet', or 'Annotation2D' representation defining the 2D shape of the door * **Body**: A 'SweptSolid', 'SurfaceModel', or 'Brep' representation defining the 3D shape of the door. -In addition the parametric representation of a (limited) door shape is available by applying the parameters from _IfcDoorType_ referencing _IfcDoorLiningProperties_ and _IfcDoorPanelProperties_. The purpose of the parameter is described at those entities and below (door opening operation by door type). - -The overall size of the _IfcDoor_ to be used to apply the lining or panel parameter provided by the _IfcDoorType_ is determined by the IfcShapeRepresentation with the RepresentationIdentifier = 'Profile'. +In addition the parametric representation of a (limited) door shape is available by applying the parameters from _IfcDoorType_ referencing _IfcDoorLiningProperties_ and _IfcDoorPanelProperties_. The purpose of the parameter is described at those entities and below (door opening operation by door type). The overall size of the _IfcDoor_ to be used to apply the lining or panel parameter provided by the _IfcDoorType_ is determined by the IfcShapeRepresentation with the RepresentationIdentifier = 'Profile'. diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoorStandardCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoorStandardCase/DocEntity.xml index 39fb7588d..9ab563bbd 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoorStandardCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoorStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoorType/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoorType/Documentation.md index 948a140b4..df3952709 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoorType/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcDoorType/Documentation.md @@ -14,35 +14,3 @@ It is used to define a door specification, or door style (i.e. the specific prod Occurrences of the _IfcDoorType_ within building models are represented by instances of _IfcDoor_ or _IfcDoorStandardCase_. > HISTORY  New entity in IFC4. The entity _IfcDoorType_ replaces the previous definition _IfcDoorStyle_ (which is deprecated in IFC4). - -{ .use-head} -Operation type use definition - -The _IfcDoorTypeOperationEnum_ defines the general layout of the door type and its symbolic presentation. Depending on the enumerator, the appropriate instances of _IfcDoorLiningProperties_ and _IfcDoorPanelProperties_ are attached in the list of _HasPropertySets_. The _IfcDoorTypeOperationEnum_ mainly determines the hinge side (left hung, or right hung), the operation (swinging, sliding, folding, etc.) and the number of panels. - -> NOTE  There are different definitions in various countries on what a left opening or left hung or left swing door is (same for right). Therefore the IFC definition may derivate from the local standard and may need to be mapped appropriately. - -See geometry use definitions at _IfcDoorTypeOperationEnum_ for the correct usage of opening symbols for different operation types. - -{ .use-head} -Material Use Definition - -The material of the _IfcDoorType_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. - -The following keywords for _IfcMaterialConstituentSet.MaterialConstituents[n].Name_ shall be used: - -* 'Lining' - to indicate that the material constituent applies to to the door lining -* 'Framing' - to indicate that the material constituent applies to to the door framing, if not provided, the 'Lining' material information applied to frams as well -* 'Glazing' - to indicate that the material constituent applies to to the glazing as well - -If the fall back single _IfcMaterial_ is referenced, it applies to the lining and framing of the door. - -{ .use-head} -Geometry Use Definitions: - -The _IfcDoorType_ may define the common shape of door occurrences. The common shape can be defined by - -* applying shape parameters defined within the associated _IfcDoorLiningProperties_ and _IfcDoorPanelProperties_ applied to the 'Profile' geometric representation. It is only applicable if the _IfcDoorType_ has only occurrences of type _IfcDoorStandardCase_ (See geometric use definition of _IfcDoorStandardCase_ for further information). -* applying the _RepresentationMaps_ attribute to refer to a list of _IfcRepresentationMap_'s, that allow for multiple geometric representations (e.g. with _IfcShapeRepresentation_'s having an _RepresentationIdentifier_ 'Box', 'Profile', 'FootPrint', or 'Body') ->> NOTE  The product shape representations are defined as _RepresentationMaps_ (attribute of the supertype _IfcTypeProduct_), which get assigned by an element occurrence instance through the _IfcShapeRepresentation.Item[n]_ being an _IfcMappedItem_. See _IfcTypeProduct_ for further information. ->> NOTE  The values of attributes _RepresentationIdentifier_ and _RepresentationType_ of _IfcShapeRepresentation_ are restricted in the same way as those for _IfcDoor_ and _IfcDoorStandardCase_ diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcMember/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcMember/Documentation.md index a60baa777..82c774bda 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcMember/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcMember/Documentation.md @@ -2,10 +2,10 @@ > NOTE  The representation of a member in a structural analysis model is provided by _IfcStructuralCurveMember_ being part of an _IfcStructuralAnalysisModel_. -The IFC specification provides two entities for member occurrences: +There are two main representations for member occurrences: -* _IfcMemberStandardCase_ used for all occurrences of members, that have a profile defined that is swept along a directrix. The profile might be changed uniformly by a taper definition along the directrix. The profile parameter and its cardinal point of insertion can be fully described by the _IfcMaterialProfileSetUsage_. These beams are always represented geometricly by an 'Axis' and a 'SweptSolid' or 'AdvancedSweptSolid' shape representation (or by a 'Clipping' geometry based on the swept solid), if a 3D geometric representation is assigned. In addition they have to have a corresponding _IfcMaterialProfileSetUsage_ assigned. ->> NOTE  View definitions and implementer agreements may further constrain the applicable geometry types, such as by excluding tapering from an _IfcMemberStandardCase_ implementation. -* _IfcMember_ used for all other occurrences of members, particularly for members with changing profile sizes along the extrusion, or members defined by non-linear extrusion, or members having only 'Brep', or 'SurfaceModel' geometry. +* _IfcMember_ with _IfcMaterialProfileSetUsage_ is used for all occurrences of members, that have a profile defined that is swept along a directrix. The profile might be changed uniformly by a taper definition along the directrix. The profile parameter and its cardinal point of insertion can be fully described by the _IfcMaterialProfileSetUsage_. These beams are always represented geometricly by an 'Axis' and a 'SweptSolid' or 'AdvancedSweptSolid' shape representation (or by a 'Clipping' geometry based on the swept solid), if a 3D geometric representation is assigned. In addition they have to have a corresponding _IfcMaterialProfileSetUsage_ assigned. +>> NOTE  The entity _IfcMemberStandardCase_ has been deprecated, _IfcMember_ with _IfcMaterialProfileSetUsage_ is used instead. +* _IfcMember_ without _IfcMaterialProfileSetUsage_ is used for all other occurrences of members, particularly for members with changing profile sizes along the extrusion, or members defined by non-linear extrusion, or members having only 'Brep', or 'SurfaceModel' geometry, or if a more parametric representation is not intended. > HISTORY  New entity in IFC2x2 Addendum 1. diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcMemberStandardCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcMemberStandardCase/DocEntity.xml index 1ddbd6f1f..084d7283c 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcMemberStandardCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcMemberStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcPlate/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcPlate/Documentation.md index bebadc652..df002568a 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcPlate/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcPlate/Documentation.md @@ -9,13 +9,12 @@ Plates are normally made of steel, other metallic material, or by glass panels. > NOTE  The representation of a plate in a structural analysis model is provided by _IfcStructuralSurfaceMember_ being part of an _IfcStructuralAnalysisModel_. -An instance _IfcPlate_ should preferably get its geometric representation and material assignment through the type definition by _IfcPlateType_ assigned using the _IfcRelDefinesByType_ relationship. This allows identical plates in a construction to be represented by the same instance of _IfcPlateType_. +An instance _IfcPlate_ should preferably get its geometric representation and material assignment through the type definition by _IfcPlateType_ assigned using the _IfcRelDefinesByType_ relationship. This allows identical plates in a construction to be represented by the same instance of _IfcPlateType_. The position number of a plate as often used in steel construction is assigned through the attribute _IfcElement.Tag_ -A plate may have openings, such as voids or recesses. They are defined by an _IfcOpeningElement_ attached to the plate using the inverse relationship _HasOpenings_ pointing to _IfcRelVoidsElement_. The position number of a plate as often used in steel construction is assigned through the attribute _IfcElement.Tag_ +There are two main representations for plate occurrences: -The IFC specification provides two entities for plate occurrences: - -* _IfcPlateStandardCase_ used for all occurrences of plates, that are prismatic and where the thickness parameter can be fully described by the _IfcMaterialLayerSetUsage_. These plates are always represented geometrically by a 'SweptSolid' geometry (or by a 'Clipping' geometry based on 'SweptSolid'), if a 3D geometric representation is assigned. In addition they have to have a corresponding _IfcMaterialLayerSetUsage_ assigned. -* _IfcPlate_ used for all other occurrences of plates, particularly for plates with changing thickness, or plates with non planar surfaces, and plates having only 'SurfaceModel' or 'Brep' geometry. +* _IfcPlate_ with _IfcMaterialLayerSetUsage_ is used for all occurrences of plates, that are prismatic and where the thickness parameter can be fully described by the _IfcMaterialLayerSetUsage_. These plates are always represented geometrically by a 'SweptSolid' geometry (or by a 'Clipping' geometry based on 'SweptSolid'), if a 3D geometric representation is assigned. +>> NOTE  The entity _IfcPlateStandardCase_ has been deprecated, _IfcPlate_ with _IfcMaterialLayerSetUsage_ is used instead. +* _IfcPlate_ without _IfcMaterialLayerSetUsage_ is used for all other occurrences of plates, particularly for plates with changing thickness, or plates with non planar surfaces, and plates having only 'SurfaceModel' or 'Brep' geometry or if a more parametric representation is not intended. > HISTORY  New entity in IFC2x2 diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcPlateStandardCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcPlateStandardCase/DocEntity.xml index 39874ee59..d3a0d9251 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcPlateStandardCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcPlateStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcRelCoversBldgElements/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcRelCoversBldgElements/DocEntity.xml index 30bd5b1b7..e678245dd 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcRelCoversBldgElements/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcRelCoversBldgElements/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcRelCoversSpaces/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcRelCoversSpaces/DocEntity.xml index 8894ea437..b9a336ab3 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcRelCoversSpaces/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcRelCoversSpaces/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlab/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlab/Documentation.md index 389e69a3d..add896e37 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlab/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlab/Documentation.md @@ -10,12 +10,12 @@ Only the core or constructional part of this construction is considered to be a > NOTE  An arbitrary planar element to which this semantic information is not applicable or irrelevant shall be modeled as _IfcPlate_. -A slab may have openings, such as floor openings, or recesses. They are defined by an _IfcOpeningElement_ attached to the slab using the inverse relationship _HasOpenings_ pointing to _IfcRelVoidsElement_. +There are two main representations for slab occurrences: -There are three entities for slab occurrences: +* _IfcSlab_ with _IfcMaterialLayerSetUsage_ is used for all occurrences of slabs, that are prismatic and where the thickness parameter can be fully described by the _IfcMaterialLayerSetUsage_. These slabs are always represented geometrically by a 'SweptSolid' geometry (or by a 'Clipping' geometry based on 'SweptSolid'), if a 3D geometric representation is assigned. +>> NOTE  The entity _IfcSlabStandardCase_ has been deprecated, _IfcSlab_ with _IfcMaterialLayerSetUsage_ is used instead. +* _IfcSlab_ without _IfcMaterialLayerSetUsage_ is used for all other occurrences of slabs, particularly for slabs with changing thickness, or slabs with non planar surfaces, and slabs having only 'SweptSolid' or 'Brep' geometry, or if a more parametric representation is not intended. -* _IfcSlabStandardCase_ used for all occurrences of slabs, that are prismatic and where the thickness parameter can be fully described by the _IfcMaterialLayerSetUsage_. These slabs are always represented geometrically by a 'SweptSolid' geometry (or by a 'Clipping' geometry based on 'SweptSolid'), if a 3D geometric representation is assigned. In addition they have to have a corresponding _IfcMaterialLayerSetUsage_ assigned. -* _IfcSlabElementedCase_ used for occurrences of slabs which are aggregated from subordinate elements, following specific decomposition rules expressed by the mandatory use of _IfcRelAggregates_ relationship. -* _IfcSlab_ used for all other occurrences of slabs, particularly for slabs with changing thickness, or slabs with non planar surfaces, and slabs having only 'SweptSolid' or 'Brep' geometry. +> NOTE  The entity _IfcSlabElementedCase_ has been deprecated, _IfcSlab>_ with _IfcRelAggregates_ is used to describe occurrences of slabs which are aggregated from subordinate elements,. > HISTORY  New entity in IFC2.0; it is a merger of the two previous entities IfcFloor, IfcRoofSlab, introduced in IFC1.0 diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlabElementedCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlabElementedCase/DocEntity.xml index e4282b143..9f50271cf 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlabElementedCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlabElementedCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlabStandardCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlabStandardCase/DocEntity.xml index b26d19d62..0d695a8b7 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlabStandardCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcSlabStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcStairFlight/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcStairFlight/DocEntity.xml index 85728ed69..3afa8aa23 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcStairFlight/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcStairFlight/DocEntity.xml @@ -7,7 +7,7 @@ - + Number of the risers included in the stair flight { .change-ifc2x4} > IFC4 CHANGE The attribute has been deprecated it shall only be exposed with a NIL value. Use _Pset_StairFlightCommon.NumberOfRisers_ instead. @@ -18,7 +18,7 @@ - + Number of treads included in the stair flight. { .change-ifc2x4} > IFC4 CHANGE The attribute has been deprecated it shall only be exposed with a NIL value. Use _Pset_StairFlightCommon.NumberOfTreads_ instead. @@ -29,7 +29,7 @@ - + Vertical distance from tread to tread. The riser height is supposed to be equal for all stairs in a stair flight. { .change-ifc2x4} @@ -41,7 +41,7 @@ - + Horizontal distance from the front to the back of the tread. The tread length is supposed to be equal for all steps of the stair flight. { .change-ifc2x4} diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWall/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWall/Documentation.md index 8cd938968..5f334c37a 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWall/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWall/Documentation.md @@ -7,14 +7,12 @@ > NOTE  An arbitrary planar element to which this semantic information is not applicable (is not predominantly vertical), shall be modeled as _IfcPlate_. -A wall may have openings, such as wall openings, openings used for windows or doors, or niches and recesses. They are defined by an _IfcOpeningElement_ attached to the wall using the inverse relationship _HasOpenings_ pointing to _IfcRelVoidsElement_. +There are two main representations for for wall occurrences: -> NOTE  Walls with openings that have already been modeled within the enclosing geometry may use the relationship _IfcRelConnectsElements_ to associate the wall with embedded elements such as doors and windows. +* _IfcWall_ with _IfcMaterialLayerSetUsage_ is used for all occurrences of walls, that have a non-changing thickness along the wall path and where the thickness parameter can be fully described by a material layer set. These walls are always represented geometrically by an 'Axis' and a 'SweptSolid' shape representation (or by a 'Clipping' geometry based on 'SweptSolid'), if a 3D geometric representation is assigned. +>> NOTE  The entity _IfcWallStandardCase_ has been deprecated, _IfcWall_ with _IfcMaterialLayerSetUsage_ is used instead. +* _IfcWall_ without _IfcMaterialLayerSetUsage_ is used for all other occurrences of wall, particularly for walls with changing thickness along the wall path (e.g. polygonal walls), or walls with a non-rectangular cross sections (e.g. L-shaped retaining walls), and walls having an extrusion axis that is unequal to the global Z axis of the project (i.e. non-vertical walls), or walls having only 'Brep', or 'SurfaceModel' geometry, or if a more parametric representation is not intended. -There are three entities for wall occurrences: - -* _IfcWallStandardCase_  used for all occurrences of walls, that have a non-changing thickness along the wall path and where the thickness parameter can be fully described by a material layer set. These walls are always represented geometrically by an 'Axis' and a 'SweptSolid' shape representation (or by a 'Clipping' geometry based on 'SweptSolid'), if a 3D geometric representation is assigned. In addition they have to have a corresponding _IfcMaterialProfileSetUsage_ assigned. -* _IfcWallElementedCase_ used for occurrences of walls which are aggregated from subordinate elements, following specific decomposition rules expressed by the mandatory use of _IfcRelAggregates_ relationship. -* _IfcWall_  used for all other occurrences of wall, particularly for walls with changing thickness along the wall path (e.g. polygonal walls), or walls with a non-rectangular cross sections (e.g. L-shaped retaining walls), and walls having an extrusion axis that is unequal to the global Z axis of the project (i.e. non-vertical walls), or walls having only 'Brep', or 'SurfaceModel' geometry. +> NOTE  The entity _IfcWallbElementedCase_ has been deprecated, _IfcWall>_ with _IfcRelAggregates_ is used to describe occurrences of wall which are aggregated from subordinate elements, such as wall panels. > HISTORY  New entity in IFC1.0 diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWallElementedCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWallElementedCase/DocEntity.xml index 07918c1dd..830036195 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWallElementedCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWallElementedCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWallStandardCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWallStandardCase/DocEntity.xml index 29a0117f3..454381170 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWallStandardCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWallStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindow/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindow/Documentation.md index b2174940b..19106d8bd 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindow/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindow/Documentation.md @@ -6,31 +6,31 @@ The _IfcWindow_ defines a particular occurrence of a window inserted in the spatial context of a project. A window can: -* be inserted into an _IfcOpeningElement_ using the _IfcRelFillsElement_ relationship, then the _IfcWindow_ has an inverse attribute _FillsVoids_ provided, +* be inserted into an _IfcOpeningElement_ using the _IfcRelFillsElement_ relationship, then the _IfcWindow_ has an inverse attribute _FillsVoids_ provided, +>> NOTE  Model View Definitions or implementer agreements may restrict the relationship to only include one window (or door) into one opening. * be part of an element assembly, often an _IfcCurtainWall_, using the _IfcRelAggregates_ relationship, then the inverse attribute _Decomposes_ is provided. * or be a "free standing" window, then the _IfcWindow_ has no inverse attributes _FillsVoids_ or _Decomposes_ provided. -> NOTE  View definitions or implementer agreements may restrict the relationship to only include one window (or door) into one opening. +There are two main representations for window occurrences: -There are two entities for window occurrences: - -* _IfcWindowStandardCase_ used for all occurrences of windows, that have a 'Profile' shape representation defined to which a set of shape parameters for lining and framing properties apply. Additionally it requires the provision of an _IfcWindowType_ that references one _IfcWindowLiningProperties_ and on to many _IfcWindowPanelProperties_. +* _IfcWindow_ with a shape representation having RepresentationIdenfifier='Profile' is used for all occurrences of windows, that have a 'Profile' shape representation defined to which a set of shape parameters for lining and framing properties apply. Additionally it requires the provision of an _IfcWindowType_ that references one _IfcWindowLiningProperties_ and on to many _IfcWindowPanelProperties_. +>> NOTE  The entity _IfcWindowStandardCase_ has been deprecated. * _IfcWindow_ used for all other occurrences of windows, particularly for windows having only 'Brep', or 'SurfaceModel' geometry without applying shape parameters. -The actual parameter of the window and/or its shape is defined at the _IfcWindow_ as the occurrence definition (or project instance), or by the _IfcWindowType_ as the specific definition (or project type). The following parameters are given: +The actual parameter of the window and/or its shape is defined at the _IfcWindow_ as the object occurrence definition, or by the _IfcWindowType_ as the object type definition . The following parameters are provided: -* at the _IfcWindow_ or _IfcWindowStandardCase_ for occurrence specific parameters. The _IfcWindow_ specifies: +* at the _IfcWindow_ for occurrence specific parameters. The _IfcWindow_ specifies: * * the window width and height * the window opening direction (by the y-axis of the _ObjectPlacement_) -* at the _IfcWindowType_ to which the _IfcWindow_ is related by the inverse relationship _IsDefinedBy_ pointing to _IfcRelDefinesByType_, for type parameters common to all occurrences of the same type. +* at the _IfcWindowType_ to which the _IfcWindow_ is related by the inverse relationship _IsTypedBy_ pointing to _IfcRelDefinesByType_, for type parameters common to all occurrences of the same type. * * the partitioning type (single panel, double panel, tripel panel, more panels) * the operation type (swing, tilt and turn, pivot revolve, fixed case ment, etc.) * the window panel hinge side (by using two different styles for right and left opening windows) * the construction material type * the particular attributes for the lining by the _IfcWindowLiningProperties_ - * the particular attributes for the panels by the  _IfcWindowPanelProperties_ + * the particular attributes for the panels by the _IfcWindowPanelProperties_ > HISTORY  New entity in IFC1.0. diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowStandardCase/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowStandardCase/DocEntity.xml index 067294956..4e001656a 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowStandardCase/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowStandardCase/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowType/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowType/DocEntity.xml index 62b81e1e2..afbcc051f 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowType/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowType/DocEntity.xml @@ -1,5 +1,5 @@  - + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowType/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowType/Documentation.md index cf9986d58..3d9b66ce8 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowType/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Entities/IfcWindowType/Documentation.md @@ -14,26 +14,6 @@ Occurrences of the _IfcWindowType_ within building models are represented by ins > HISTORY  New entity in IFC4. The entity _IfcWindowType_ replaces the previous definition _IfcWindowStyle_ (which is deprecated in IFC4). -{ .use-head} -Partitioning type use definition - -The _IfcWindowTypePartitioningEnum_ defines the general layout of the window type and its symbolic presentation. Depending on the enumerator, the appropriate instances of _IfcWindowLiningProperties_ and _IfcWindowPanelProperties_ are attached in the list of _HasPropertySets_. The _IfcWindowTypePartitioningEnum_ mainly determines the way of partitioning the window into individual window panels and thereby number and position of window panels. - -See geometry use definitions at _IfcWindowTypePartitioningEnum_ for the correct usage of panel partitioning and _IfcWindowPanelProperties_ for the opening symbols for different panel operation types. - -{ .use-head} -Material Use Definition - -The material of the _IfcWindowType_ is defined by the _IfcMaterialConstituentSet_ or as fall back by _IfcMaterial_ and attached by the _IfcRelAssociatesMaterial_._RelatingMaterial_. It is accessible by the inverse _HasAssociations_ relationship. - -The following keywords for _IfcMaterialConstituentSet.MaterialConstituents[n].Name_ shall be used: - -* 'Lining' - to indicate that the material constituent applies to to the window lining -* 'Framing' - to indicate that the material constituent applies to to the window panels, if not provided, the 'Lining' material information applied to panels as well -* 'Glazing' - to indicate that the material constituent applies to to the glazing part - -If the fall back single _IfcMaterial_ is referenced, it applies to the lining and framing of the window. - { .use-head} Geometry Use Definitions: diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Types/IfcWallTypeEnum/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Types/IfcWallTypeEnum/Documentation.md index 6a0bd17e6..bb7572e38 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Types/IfcWallTypeEnum/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedBldgElements/Types/IfcWallTypeEnum/Documentation.md @@ -10,6 +10,10 @@ { .change-ifc2x4} > IFC4 CHANGE  New enumerators MOVABLE, PARAPET, PARTITIONING, and SOLIDWALL have been added. -> IFC4 DEPRECATION  The enumerators STANDARD, POLYGONAL and ELEMENTEDWALL are deprecated and shall no longer be used. +> +> + +{ .deprecated} +> IFC4 DEPRECATION  The enumerator POLYGONAL is deprecated and shall no longer be used. > NOTE  The potentially misleading term _SHEAR_ shall not impose a particular resistance against shear forces, but a particular shape. diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastener/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastener/DocEntity.xml index 750e1be82..b9278662d 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastener/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastener/DocEntity.xml @@ -1,16 +1,14 @@  - + - + The nominal diameter describing the cross-section size of the fastener type. - -{ .change-ifc2x4} -> IFC4 CHANGE&nbsp; Deprecated; the respective attribute of _IfcMechanicalFastenerType_ should be used instead. +> Deprecated in IFC4 @@ -19,11 +17,9 @@ - + The nominal length describing the longitudinal dimensions of the fastener type. - -{ .change-ifc2x4} -> IFC4 CHANGE&nbsp; Deprecated; the respective attribute of _IfcMechanicalFastenerType_ should be used instead. +> Deprecated in IFC4 diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastener/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastener/Documentation.md index 7b2b10824..597521ed4 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastener/Documentation.md +++ b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastener/Documentation.md @@ -3,4 +3,4 @@ > HISTORY  New entity in IFC2x2 { .change-ifc2x4} -> IFC4 CHANGE  Supertype changed from _IfcFastener_ to _IfcElementComponent_. Attribute _PredefinedType_ added. Attributes _NominalDiameter_ and _NominalLength_ deprecated. +> IFC4 CHANGE  Supertype changed from _IfcFastener_ to _IfcElementComponent_. Attribute _PredefinedType_ added. Attributes _NominalDiameter_ and _NominalLength_ are deprecated. diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastenerType/DocEntity.xml b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastenerType/DocEntity.xml index d4996ed4d..019a60d37 100644 --- a/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastenerType/DocEntity.xml +++ b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/Entities/IfcMechanicalFastenerType/DocEntity.xml @@ -1,5 +1,5 @@  - + @@ -14,7 +14,7 @@ - + The nominal diameter describing the cross-section size of the fastener type. @@ -22,7 +22,7 @@ - + The nominal length describing the longitudinal dimensions of the fastener type. diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/PropertySets/Pset_MechanicalFastenerCommon/DocPropertySet.xml b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/PropertySets/Pset_MechanicalFastenerCommon/DocPropertySet.xml new file mode 100644 index 000000000..b39a05180 --- /dev/null +++ b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/PropertySets/Pset_MechanicalFastenerCommon/DocPropertySet.xml @@ -0,0 +1,8 @@ + + + + + + + + diff --git a/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/PropertySets/Pset_MechanicalFastenerCommon/Documentation.md b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/PropertySets/Pset_MechanicalFastenerCommon/Documentation.md new file mode 100644 index 000000000..0a28a204d --- /dev/null +++ b/Sections/Shared element data schemas/Schemas/IfcSharedComponentElements/PropertySets/Pset_MechanicalFastenerCommon/Documentation.md @@ -0,0 +1 @@ +Properties related to mechanical fasteners. diff --git a/Templates/Object Association/DocTemplateDefinition.xml b/Templates/Association/DocTemplateDefinition.xml similarity index 82% rename from Templates/Object Association/DocTemplateDefinition.xml rename to Templates/Association/DocTemplateDefinition.xml index c65bace67..4cda6614d 100644 --- a/Templates/Object Association/DocTemplateDefinition.xml +++ b/Templates/Association/DocTemplateDefinition.xml @@ -1,5 +1,5 @@  - + The concept _Approval Association_ describes how object or object types can have associated approvals indicating who is required to approve the data, the status of whether it has been approved, and the date/time of such approval. Approvals may require multiple parties fulfilling various roles. @@ -37,51 +37,43 @@ - - The concept _Classification Association_ describes how objects and object types can be further described by associating references to external sources of information. The source of information can be: + + Objects, type objects, properties, and some resource schema entities can be further described by associating references to external sources of information. The source of information can be: * a classification system; * a dictionary server; * any external catalogue that classifies the object further; -* any service that combine the above features. +* a service that combine the above features. -An individual item within the external source of information can be selected. It then applies the inherent meaning of the item to the _IfcObject_ or _IfcTypeObject_. - -> NOTE&nbsp; The classification system or dictionary server that is used within the project itself can also be indicated at the level of _IfcProject_ or _IfcProjectLibrary_ either as an external source, or copied with all relevant classification items into the project data. Use the concept _Project Classification Information_ to utilize this functionality. - -The main attributes to be provided for a _Classification Association_ are: - -* _Identification_: holds the key provided for a specific references to classification items (or tables) -* _Name_: allows for a human interpretable designation of a classification notation +An individual item within the external source of information can be selected. It then applies the inherent meaning of the item to the object or property. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="Name[Value]='Beam'"/> + <TemplateRule Parameters="Identification[Value]='QRO 200x16'"/> + <TemplateRule Parameters="ClassificationName[Value]='EN 10210-2'"/> +</TemplateRules> + + + + + + + - + - - - - - - - - - - - - - - - - + @@ -91,43 +83,18 @@ The main attributes to be provided for a _Classification Association_ are: - + - - - - - - - - - - - - - - - - - - - - - - - - - - + - + @@ -140,15 +107,22 @@ The main attributes to be provided for a _Classification Association_ are: - - The concept _Constraint Association_ describes how object or object types may have associated constraints indicating a qualitative objective or a quantitative metric to be met. + + { .std} +Any object or property may have associated constraints indicating a qualitative objective or a quantitative metric to be met. +{ .std} Constraints based on metrics are measurable, such that the status of a metric being valid is computer-interpretable. Metric constraints are based on simple conditional logic such as greater than a particular value or included within a specified list or table. Constraints may be combine multiple metrics using boolean logic such as AND, OR, XOR, or NOT. + + + + + @@ -157,108 +131,15 @@ Constraints based on metrics are measurable, such that the status of a metric be - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -268,6 +149,96 @@ Constraints based on metrics are measurable, such that the status of a metric be + + + The constraint model may be used to indicate mappings between data in the IFC model and external documents. This concept template may also be used by software applications to translate data to/from spreadsheets without necessarily instantiating constraint relationships within an IFC data set. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The concept _Document Association_ describes how objects or object types can have associated documents indicating external files. Documents may be referenced in their entirety such as to capture product brochures, data sheets, multimedia content, or thumbnail images. Contents within documents may be referenced from any object, and may be used to synchronize information in other files such as work schedules for project management applications. @@ -393,6 +364,13 @@ Materials can have representations for surface styles indicating colors, texture Material constituents are associated with products or product types where materials are placed arbitrarily (unlike 1D material profiles or 2D material layers). The mapping of materials to geometry may be accomplished using _IfcShapeAspect_. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="MaterialName[Value]='PVC' AND ConstituentName[Value]='Beschichtung'"/> +</TemplateRules> + + @@ -577,6 +555,16 @@ The material of those standard case elements is defined by _IfcMaterialLayerSetU Material layer sets are associated with products or product types to indicate a parametric specification of layers having specified thickness filling a boundary defined on the product, or the occurrences of the product type. Examples of such products or product types are slabs, walls, and plates. + + + <TemplateRules operator="and"> +<TemplateRule Parameters="HasLayer[Size]=3"/> +<TemplateRule Parameters="LayerName[Value]='reinforced concrete' AND LayerThickness[Value]=250 AND Category[Value]='Load Bearing'"/> +<TemplateRule Parameters="LayerName[Value]='thermal insulation' AND LayerThickness[Value]=100 AND Category[Value]='Insulation'"/> +<TemplateRule Parameters="LayerName[Value]='metal sheet' AND LayerThickness[Value]=3 AND Category[Value]='Outer finish'"/> +</TemplateRules> + + @@ -754,6 +742,13 @@ The material of those standard case elements is defined by _IfcMaterialProfileSe Material profile sets are associated with products or product types where materials are placed in cross-sections of specified dimensions following a path defined at occurrences of the type. Examples of such products are beams, columns, members, reinforcing, footings, piles, pipe segments, duct segments, and cable segments. > EXAMPLE&nbsp; Material profile sets can be provided at the _IfcColumnType_, defining the common material information for all occurrences of the same column type. It is then accessible by the inverse _IsTypedBy_ relationship at _IfcColumn_ pointing to _IfcColumnType_ having the _HasAssociations_ inverse relationship to _IfcRelAssociatesMaterial_ with _RelatingMaterial_ refering to the _IfcMaterialProfileSet_>. If an individual material association is provide at the _IfcColumn_ and the _IfcColumnType_, then the material directly assigned to _IfcColumn_ overrides the material assigned to _IfcColumnType_. + + + <TemplateRules operator="and"> +<TemplateRule Parameters="MaterialName[Value]='Steel' AND ProfileName[Value]='IPE 120' AND Category[Value]='Load Bearing'"/> +</TemplateRules> + + @@ -811,7 +806,7 @@ The material of those standard case elements is defined by _IfcMaterialProfileSe - + @@ -840,6 +835,13 @@ The material of those standard case elements is defined by _IfcMaterialProfileSe Materials are directly associated with products and product types to indicate a uniform material for the entire object. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="MaterialName[Value]='steel'"/> +</TemplateRules> + + diff --git a/Templates/Object Assignment/DocTemplateDefinition.xml b/Templates/Object Assignment/DocTemplateDefinition.xml index bc8d35464..e4b9476a5 100644 --- a/Templates/Object Assignment/DocTemplateDefinition.xml +++ b/Templates/Object Assignment/DocTemplateDefinition.xml @@ -24,7 +24,7 @@ The grouping relationship does not apply any other meaning then grouping objects under some aspect. It is non-hierarchical, meaning that objects can be assigned to many groups, and it does not interfere with other relationship concepts, such as _Element Decomposition_. - + @@ -35,16 +35,32 @@ The grouping relationship does not apply any other meaning then grouping objects - + The _Component to Distribution System_ assignment + + + <TemplateRules operator="and"> + <!-- Check assignement to IfcDistributionSystem --> + <TemplateRule Parameters="IsAssigned[Size]>0 AND SystemName[Value]='WWS_1'"/> +</TemplateRules> + + - + - + + + + + + + + + @@ -55,14 +71,30 @@ The grouping relationship does not apply any other meaning then grouping objects The _Port to Distribution System_ assignment + + + <TemplateRules operator="and"> + <!-- Check assignement to IfcDistributionSystem --> + <TemplateRule Parameters="IsAssigned[Size]>0 AND SystemName[Value]='WWS_1'"/> +</TemplateRules> + + - + - + + + + + + + + + @@ -102,6 +134,13 @@ The _Group Assignment_ concept establish a given object as being the group colle > NOTE&nbsp; The _IfcGroup_ maybe not yet have a grouping relationship established, it then identifies an empty group. > EXAMPLE&nbsp; An air handler belonging to an air conditioning system is an example of such group assignment. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="IsGrouped[Size]>1 AND RelatedObjects[Size]>4"/> +</TemplateRules> + + diff --git a/Templates/Object Association/Documentation.md b/Templates/Object Association/Documentation.md deleted file mode 100644 index d96275aa8..000000000 --- a/Templates/Object Association/Documentation.md +++ /dev/null @@ -1 +0,0 @@ -The concept of an _Object Association_ provides the means to associate sources of information (most notably a classification, library, document, approval, contraint, or material) to objects definitions. The information associated may reside internally or externally in regard of the project data. diff --git a/Templates/Object Attributes/DocTemplateDefinition.xml b/Templates/Object Attributes/DocTemplateDefinition.xml index fcc0e4aae..3c8dbe86e 100644 --- a/Templates/Object Attributes/DocTemplateDefinition.xml +++ b/Templates/Object Attributes/DocTemplateDefinition.xml @@ -16,6 +16,21 @@ Doors may be further described by their size and operation type. + + + <TemplateRules operator="and"> + <TemplateRules operator="or"> + <TemplateRule Parameters="OperationType[Value]='SINGLE_SWING_LEFT'"/> + <TemplateRules operator="and"> + <TemplateRule Parameters="OperationType[Exits]=FALSE"/> + <TemplateRule Parameters="TypeOperationType[Value]='SINGLE_SWING_LEFT' "/> + </TemplateRules> + </TemplateRules> + <TemplateRule Parameters="OverallHeight[Value]=2.20"/> + <TemplateRule Parameters="OverallWidth[Value]=1.10"/> +</TemplateRules> + + @@ -52,7 +67,7 @@ - + @@ -114,269 +129,23 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Windows may be further described by their size and partitioning type. + + + <TemplateRules operator="and"> + <TemplateRules operator="or"> + <TemplateRule Parameters="PartitioningType[Value]='DOUBLE_PANEL_VERTICAL'"/> + <TemplateRules operator="and"> + <TemplateRule Parameters="PartitioningType[Exits]=FALSE"/> + <TemplateRule Parameters="TypePartitioningType[Value]='DOUBLE_PANEL_VERTICAL'"/> + </TemplateRules> + </TemplateRules> + <TemplateRule Parameters="OverallHeight[Value]=2.50"/> + <TemplateRule Parameters="OverallWidth[Value]=1.75"/> +</TemplateRules> + + @@ -470,6 +239,15 @@ Grids may be used to provide a layout reference for building elements. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="UAxes[Size]=5"/> + <TemplateRule Parameters="VAxes[Size]=5"/> + <TemplateRule Parameters="WAxes[Size]=5"/> +</TemplateRules> + + @@ -548,6 +326,19 @@ A building may be located according to a postal address, and may indicate a baseline elevation and land elevation. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="Name[Value]='AEC3 Office'"/> + <TemplateRule Parameters="LongName[Value]='AEC3 Office Building Munich'"/> + <TemplateRule Parameters="HasAdress[Size]=1"/> + <TemplateRule Parameters="AddressLines[Value]='Joseph-Wild-Str.13'"/> + <TemplateRule Parameters="Town[Value]='München'"/> + <TemplateRule Parameters="PostalCode[Value]='81829'"/> + <TemplateRule Parameters="Country[Value]='D'"/> +</TemplateRules> + + @@ -636,6 +427,18 @@ A site may be located according to latitute, longitute, elevation, land title designation, and/or postal address. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="Name[Value]='SiteName'"/> + <TemplateRule Parameters="LongName[Value]='LongSiteName'"/> + <TemplateRule Parameters="Latitude[Value]=-33.85"/> + <TemplateRule Parameters="Longitude[Value]=151.2"/> + <TemplateRule Parameters="Elevation[Value]=58"/> + <TemplateRule Parameters="HasAddress[Size]>0"/> +</TemplateRules> + + @@ -734,6 +537,16 @@ Space may be further described by their elevation including floor coverings. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="Name[Value]='OF-02.012'"/> + <TemplateRule Parameters="LongName[Value]='Office 2.12'"/> + <TemplateRule Parameters="TypeName[Value]='OF-02'"/> + <TemplateRule Parameters="TypeLongName[Value]='Office OF-02'"/> +</TemplateRules> + + @@ -820,6 +633,15 @@ A building storey may be indicate the elevation of the top surface of the floor slab, excluding any floor coverings. For storeys with raised or sunken areas, the elevation should reflect the largest area of the slab. For split-level buildings, each level should have it's own _IfcBuildingStorey_. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="Name[Value]='OG2'"/> + <TemplateRule Parameters="LongName[Value]='Obergeschoss 2'"/> + <TemplateRule Parameters="Elevation[Value]=10.0"/> +</TemplateRules> + + @@ -845,6 +667,17 @@ + + Systems may be further identified via the _LongName_ attribute. This value should generally correspond to readable names for systems. While the _Name_ attribute generally provides a coded or abbreviated identifie, like "HW", the _LongName_ provides a functional name for the system such as "Hot water system". + + + + + + + + + @@ -858,6 +691,24 @@ The main attributes to be provided for a _Object Occurrence Predefined Type_ are If the object is typed by an _IfcTypeObject_, then the _PredefinedType_ at the _IfcObject_ occurrence shall only be used if the _PredefinedType_ at _IfcTypeObject_ is set to _NOTDEFINED_. + + + <TemplateRules operator="and"> + <TemplateRules operator="or"> + <!-- Other checking type attribute on object or occurrence --> + <TemplateRule Parameters="PredefinedType[Value]='USERDEFINED' AND UserDefinedType[Value]='Aussteifung'"/> + <TemplateRules operator="and"> + <TemplateRules operator="nor"> + <TemplateRule Parameters="PredefinedType[Value]='USERDEFINED' OR UserDefinedType[Value]='Aussteifung'"/> + </TemplateRules> + <TemplateRules operator="or"> + <TemplateRule Parameters="TypePredefinedType[Value]='USERDEFINED' AND TypeUserdefinedType[Value]='Aussteifung'"/> + </TemplateRules> + </TemplateRules> + </TemplateRules> +</TemplateRules> + + @@ -901,7 +752,11 @@ The main attributes to be provided for a _Object Occurrence Predefined Type_ are - + + + + + @@ -1048,7 +903,11 @@ The main attributes to be provided for a _Object Occurrence Predefined Type_ are - + + + + + @@ -1115,6 +974,13 @@ Specific subtypes introduce additional attributes for _User Identity_. * Spatial objects may be further identified via the _LongName_ attribute. This value should generally correspond to building signage describing floor levels or rooms. While the _Name_ attribute generally provides a coded or abbreviated identifier, the _LongName_ provides a functional name for the location such as "Reception Area". See concept template _Spatial Element Occurrence Attributes_ * Physical elements may be further identified via the _Tag_ attribute. This is a human readable identifier such as an element or item number While there is no restriction on usage of such tags, it is recommended the _Tag_ is unique within it's containing scope. See concept template _Element Occurrence Attributes_ + + + <TemplateRules operator="and"> + <TemplateRule Parameters="ObjectName[Value]='Beam_01'"/> +</TemplateRules> + + diff --git a/Templates/Object Attributes/Documentation.md b/Templates/Object Attributes/Documentation.md index 2d8321db7..da1572f06 100644 --- a/Templates/Object Attributes/Documentation.md +++ b/Templates/Object Attributes/Documentation.md @@ -5,8 +5,8 @@ Resource-level instances (not deriving from _IfcRoot_) do not have any identity, The distinction between rooted and non-rooted (resource-level) entities achieves several goals: { .ref} -* File size may be reduced by interning (sharing) non-rooted data instances; -* Database retrieval may be more efficient by storing non-rooted data local to rooted data instances; -* Storage size may be reduced by avoiding IFC-GUID storage for items not requiring direct retrieval; -* Comparisons of differences may be done at a higher level where the context of such change is apparent; +* File size may be reduced by interning (sharing) non-rooted data instances; +* Database retrieval may be more efficient by storing non-rooted data local to rooted data instances; +* Storage size may be reduced by avoiding IFC-GUID storage for items not requiring direct retrieval; +* Comparisons of differences may be done at a higher level where the context of such change is apparent; * Implementations may treat non-rooted data instances as immutable for efficiency or simplified usage. diff --git a/Templates/Object Composition/DocTemplateDefinition.xml b/Templates/Object Composition/DocTemplateDefinition.xml index 8abe86de6..0fa5a2602 100644 --- a/Templates/Object Composition/DocTemplateDefinition.xml +++ b/Templates/Object Composition/DocTemplateDefinition.xml @@ -24,6 +24,13 @@ The part may also provide, in addition to the aggregate, more specifically the f The part should not be contained in the spatial hierarchy, i.e. the concept _Spatial Containment_ shall not be used at the level of parts. The part is contained in the spatial structure by the spatial containment of its composite. > EXAMPLE&nbsp; An _IfcBeam_ may be aggregated into an element assembly using the objectified relationship _IfcRelAggregates_, refering to it by its inverse attribute SELF\IfcObjectDefinition.Decomposes. Any subtype of _IfcElement_ can be an element assembly, with _IfcElementAssembly_ as a special focus subtype. In this case it should not be additionally contained in the spatial hierarchy, i.e. _SELF\IfcElement.ContainedInStructure_ should be NIL. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="Decomposes[Exists]=TRUE AND RelatingObject[Type]='IfcWallStandardCase' AND ElementName[Value]='Facade'"/> +</TemplateRules> + + @@ -62,6 +69,14 @@ By default the following constraints apply to an element being decomposed by _El * the composite shall not have an own _Material_ assignment, material is assigned to the parts. > NOTE&nbsp; Use the sub template _Element Decomposition Required_ if any instance of the element is required to represent a composite with declared parts. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="IsDecomposedBy[Exists]=TRUE AND RelatedObjects[Size]=2"/> + <TemplateRule Parameters="RelatedObjects[Type]='IfcSlab' OR RelatedObjects[Type]='IfcRailing'"/> +</TemplateRules> + + @@ -96,6 +111,14 @@ The order of spatial structure elements being included in the concept for builin In addition a more general hierarchical tree of spatial elements can be created by using _IfcSpatialZone_, from high to low: _IfcProject_, _IfcSite_, and _IfcSpatialZone_ with _IfcSite_ being an optional level. > NOTE&nbsp; The more general hiearchical tree has been introduced as an intermediate solution and stub for further extensions to support infrastructure works. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="RelatingObject[Type]='IfcProject' AND ProjectName[Value]='Green Architecture Sydney' "/> + <!-- <TemplateRule Parameters="RelatingObject[Type]='IfcSite' AND SpatialElementName[Value]='LOT-1002'"/> --> +</TemplateRules> + + @@ -131,16 +154,24 @@ The order of spatial structure elements being included in the concept for builin In addition a more general hierarchical tree of spatial elements can be created by using _IfcSpatialZone_, from low to high: _IfcSpatialZone_, _IfcSite_, and _IfcProject_, with _IfcSite_ being an optional level. > NOTE&nbsp; The more general hiearchical tree has been introduced as an intermediate solution and stub for further extensions to support infrastructure works. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="RelatedObjects[Size]=4 AND RelatedObjects[Type]='IfcBuildingStorey'"/> + <TemplateRule Parameters="SpatialElementName[Value]='UG' OR SpatialElementName[Value]='EG' OR SpatialElementName[Value]='OG1' OR SpatialElementName[Value]='DG'"/> +</TemplateRules> + + - + - + @@ -188,6 +219,13 @@ In addition a more general hierarchical tree of spatial elements can be created The 'Body' representation of an element does not account for voids, for which CSG operations are required to produce the resulting shape. The 'Mesh' representation of an element does account for voids, such that no additional operations are required. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="HasOpenings[Size]=1 AND HasFillings[Size]=1 AND RelatedFillings[Size]=1 AND ElementName[Type]='IfcDoor'"/> +</TemplateRules> + + @@ -311,6 +349,15 @@ A general rule for using nesting as opposed to aggregation is based on the conte Ports indicate possible connections to other objects according to specified system types, flow direction, and connection properties. Ports are typically connected between devices via cables, pipes, or ducts. Ports may have placement defined indicating the position and outward orientation of the port relative to the product or product type. Ports may also have material profile sets defined indicating the flow area and connection enclosure. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="PortName[Value]='P1'"/> + <TemplateRule Parameters="Flow[Value]='SINK' OR Flow[Value]='SOURCE'"/> + <TemplateRule Parameters="SystemType[Value]='ELECTRICAL' OR SystemType[Value]='WATERSUPPLY' OR SystemType[Value]='WASTEWATER'"/> +</TemplateRules> + + @@ -367,7 +414,6 @@ Ports may have placement defined indicating the position and outward orientation - diff --git a/Templates/Object Connectivity/DocTemplateDefinition.xml b/Templates/Object Connectivity/DocTemplateDefinition.xml index e5725672c..5ad23641e 100644 --- a/Templates/Object Connectivity/DocTemplateDefinition.xml +++ b/Templates/Object Connectivity/DocTemplateDefinition.xml @@ -21,57 +21,37 @@ Elements may be connected to other elements, where the _RelatingElement_ is of equal or higher priority, is generally constructed first, and/or anchors the _RelatedElement_. - - - - Elements based on an 'Axis' representation such as walls, beams, and columns use a path connectivity relationship to indicate parameters for the connection, indicating which side takes precedence for material layers or profiles. - + - - - - - - - - - - - - - - + - - - - - - - - - + + + + + + @@ -82,12 +62,12 @@ - + - + @@ -96,41 +76,35 @@ - + Ports on distribution elements, such as ducts and airoutlets, or pipes and sanitary elements are connected with each other using the _Port Connectivity_. The port connection determines the direction of flow between the connected ports belonging to the distribution elements. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="ConnectedToPort[Size]=1 AND ConnectedFromPort[Size]=0"/> +</TemplateRules> + + - + - + - - - - - - + - - - - - - - - - + @@ -434,7 +408,7 @@ - + @@ -541,7 +515,15 @@ - + + + + + + + + + @@ -588,6 +570,13 @@ Any subtype of _IfcElement_ may participate in two different containment relatio * The subtypes of _IfcElement_ are placed within the project spatial hierarchy using the objectified relationship _IfcRelContainedInSpatialStructure_, refering to it by its inverse attribute _SELF\IfcElement.ContainedInStructure_. Subtypes of _IfcSpatialElement_ are valid spatial containers. * The subtypes of _IfcElement_ may be aggregated into an element assembly using the objectified relationship _IfcRelAggregates_, refering to it by its inverse attribute _SELF\IfcObjectDefinition.Decomposes_. Any subtype of _IfcElement_ can be an element assembly, with _IfcElementAssembly_ as a special focus subtype. In this case it should not be additionally contained in the project spatial hierarchy, i.e. _SELF\IfcElement.ContainedInStructure_ should be _NIL_. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="RelatingStructure[Type]='IfcBuildingStorey' AND SpatialElementName[Value]='Ground Floor'"/> +</TemplateRules> + + @@ -595,7 +584,15 @@ Any subtype of _IfcElement_ may participate in two different containment relatio - + + + + + + + + + diff --git a/Templates/Object Definition/DocTemplateDefinition.xml b/Templates/Object Definition/DocTemplateDefinition.xml index 93f7ed65c..135c3cbcb 100644 --- a/Templates/Object Definition/DocTemplateDefinition.xml +++ b/Templates/Object Definition/DocTemplateDefinition.xml @@ -1,5 +1,5 @@  - + Object occurrences can be defined by a particular object type, using the _Object Typing_ concept. A pair of entities are defined for most semantic objects - an object occurrence entity and a corresponding object type entity. @@ -25,16 +25,28 @@ Many object occurrence and object type entities have an attribute named _Predefi > EXAMPLE&nbsp; For scenarios of object types having part compositions, such parts may be reflected at object occurrences having separate state. For example, a _wall type_ may define a particular arrangement of studs, a _wall occurrence_ may reflect the same arrangement of studs, and studs within the wall occurrence may participate in specific relationships that do not exist at the type such as being connected to an electrical junction box. > NOTE&nbsp; If the object type has aggregated elements, such objects are reflected at the object occurrence using the _IfcRelDefinesByObject_ relationship. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="RelatingType[Type]='IfcBeamType' AND TypeName[Value]='IPE 120'"/> +</TemplateRules> + + - + - + - + + + + + + @@ -46,10 +58,10 @@ Many object occurrence and object type entities have an attribute named _Predefi - + The concept template _Property Sets_ describes how sets of properties (usually defined by a name, value, unit triple) are associated to objects or object types. - + The concept template _Property Sets for Objects_ describes how an object occurrence can be related to a single or multiple property sets. A property set contains a single or multiple properties. The data types of an individual property are single value, enumerated value, bounded value, table value, reference value, list value, and combination of property occurrences. Property sets can also be related to an object type, see concept _Property Sets for Types_. They then define the common properties for all occurrences of the same type. If the same property (by name) is provided by the same property set (by name), then the properties directly assigned to the object occurrence override the properties assigned to the object type. @@ -68,7 +80,7 @@ Property sets can also be related to an object type, see concept _Property Sets - + @@ -91,7 +103,7 @@ Property sets can also be related to an object type, see concept _Property Sets - + @@ -103,17 +115,17 @@ Property sets can also be related to an object type, see concept _Property Sets - + - + - + @@ -124,7 +136,7 @@ Property sets can also be related to an object type, see concept _Property Sets - + @@ -160,7 +172,7 @@ Property sets can also be related to an object type, see concept _Property Sets - + @@ -183,7 +195,7 @@ Property sets can also be related to an object type, see concept _Property Sets - + @@ -219,6 +231,45 @@ Property sets can also be related to an object type, see concept _Property Sets + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -231,7 +282,21 @@ Property sets can also be related to an object type, see concept _Property Sets - + + The concept template _Property Sets with Override_ extends the concept template _Property Sets for Objects_ by allowing a property to be either provided at the individual object, or at the object type. If the same property (by name) is provided by the same property set (by name), then the property directly assigned to the object occurrence overrides the property assigned to the object type. + + + <TemplateRules operator="or"> + <TemplateRule Parameters="PsetName[Value]='Pset_BeamCommon' AND PropertyName[Value]='FireRating' AND Value[Value]='F30'"/> + <TemplateRules operator="and"> + <TemplateRule Parameters="TypePsetName[Value]='Pset_BeamCommon' AND TypePropertyName[Value]='FireRating' AND TypeValue[Value]='F30'"/> + <TemplateRules operator="nor"> + <TemplateRule Parameters="PsetName[Value]='Pset_BeamCommon' AND PropertyName[Value]='FireRating' AND Value[Exists]=TRUE"/> + </TemplateRules> + </TemplateRules> +</TemplateRules> + + @@ -275,31 +340,36 @@ Property sets can also be related to an object type, see concept _Property Sets - + - + - + - + - + + + + + + @@ -318,7 +388,7 @@ Property sets can also be related to an object type, see concept _Property Sets - + For performance history, properties are in the form of time series, for tracking data at points in time. @@ -373,7 +443,7 @@ Property sets can also be related to an object type, see concept _Property Sets - + The concept template _Property Sets for Objects_ describes how an object type can be related to a single or multiple property sets. A property set contains a single or multiple properties. The data types of an individual property are single value, enumerated value, bounded value, table value, reference value, list value, and combination of property occurrences. The property values assigned to an object type apply equally to all occurrences of this object type, see concept _Object Typing_, unless it is overriden by a property with same name within a property set with the same name at an individual object occurrence. @@ -420,10 +490,17 @@ The property values assigned to an object type apply equally to all occurrences - + Any specialization of object can be related to multiple quantity set occurrences. A quantity set contains multiple quantity occurrences. The data type of quantity occurrence values are count, length, area, volume, weight, time, or a combination of quantities. Each quantity is defined by its name, value, and optionally a description and a formula. The quantity set is expressed by instances of _IfcElementQuantity_, where the _Name_ attribute determines the common designator of the quantity set. This specification contains a number of predefined quantity sets, a template definition is provided for each of them. The name of the template has to be used as the value of the _Name_ attribute. The _MethodOfMeasurement_ attribute specifies the method, by which the values of the individual quantities are calculated. For the quantity set templates included in this specification, the value of _MethodOfMeasurement_ shall be "BaseQuantities". + + + <TemplateRules operator="and"> + <TemplateRule Parameters="QsetName[Value]='Qto_BeamBaseQuantities' AND QuantityName[Value]='Length' AND LengthValue[Value]=2000"/> +</TemplateRules> + + @@ -452,7 +529,7 @@ The quantity set is expressed by instances of _IfcElementQuantity_, where the _N - + @@ -480,7 +557,7 @@ The quantity set is expressed by instances of _IfcElementQuantity_, where the _N - + @@ -508,7 +585,7 @@ The quantity set is expressed by instances of _IfcElementQuantity_, where the _N - + @@ -536,7 +613,7 @@ The quantity set is expressed by instances of _IfcElementQuantity_, where the _N - + @@ -564,7 +641,7 @@ The quantity set is expressed by instances of _IfcElementQuantity_, where the _N - + @@ -592,7 +669,7 @@ The quantity set is expressed by instances of _IfcElementQuantity_, where the _N - + diff --git a/Templates/Partial Templates/DocTemplateDefinition.xml b/Templates/Partial Templates/DocTemplateDefinition.xml index 149f8e792..5f285840f 100644 --- a/Templates/Partial Templates/DocTemplateDefinition.xml +++ b/Templates/Partial Templates/DocTemplateDefinition.xml @@ -1,5 +1,5 @@  - + @@ -821,6 +821,79 @@ Scaling is supported to correlate the size of a texture with its physical dimens + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3568,7 +3641,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + @@ -3658,7 +3731,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + @@ -3706,7 +3779,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + @@ -3817,7 +3890,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens Presentation layers may be used to organize geometry into groups that may be shown or hidden. Such designation is only for viewing and editing purposes and does not imply any semantic meaning. - + @@ -3832,7 +3905,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + @@ -3844,14 +3917,14 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + Material properties may capture standard or user-defined parameters. - + @@ -3861,9 +3934,38 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -3881,7 +3983,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + Profiles are used to describe cross-sections of swept solid geometry. @@ -4078,24 +4180,14 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + Profile properties may capture standard or user-defined parameters. - - - - - - - - - - - + @@ -4105,9 +4197,38 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -4116,7 +4237,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + @@ -4144,7 +4265,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens - + Properties may contain user-defined data, where data types are open-ended. @@ -4162,41 +4283,7 @@ Scaling is supported to correlate the size of a texture with its physical dimens - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + diff --git a/Templates/Product Shape/DocTemplateDefinition.xml b/Templates/Product Shape/DocTemplateDefinition.xml index e3c8fa7b9..3f8524043 100644 --- a/Templates/Product Shape/DocTemplateDefinition.xml +++ b/Templates/Product Shape/DocTemplateDefinition.xml @@ -63,12 +63,12 @@ The representation identifier of the annotation representation is: - + - + @@ -122,12 +122,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -138,12 +138,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -330,12 +330,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -346,12 +346,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -405,12 +405,12 @@ The representation identifier of the axis representation is: - + - + @@ -461,12 +461,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -477,12 +477,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -532,12 +532,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -548,12 +548,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -603,12 +603,12 @@ The representation identifier of the body representation is: - + - + @@ -663,12 +663,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -732,12 +732,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -759,7 +759,7 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + @@ -781,12 +781,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -821,8 +821,8 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - - The _Body AdvancedSwept DiskSolid PolyCurve Geometry_ is the representation of the 3D shape of a product by swept disk solid models, where the directrix is created by an indexed poly curve. + + The _Body AdvancedSwept Disk Solid PolyCurve Geometry_ is the representation of the 3D shape of a product by swept disk solid models, where the directrix is created by an indexed poly curve. The following attribute values for the _IfcShapeRepresentation_ holding this geometric representation shall be used: @@ -830,6 +830,9 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo * _IfcShapeRepresentation_._RepresentationType_ = 'AdvancedSweptSolid' * _IfcShapeRepresentation_._Items_ = _IfcSweptDiskSolid_, _IfcSweptDiskSolidPolygonal_ * _IfcShapeRepresentation_._Items[1..n].Directrix_ = _IfcIndexedPolyCurve_ + + + @@ -851,12 +854,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -886,7 +889,7 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + @@ -908,12 +911,69 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -981,12 +1041,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1043,12 +1103,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1149,12 +1209,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1184,6 +1244,66 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo + + The _Body SurfaceModel Geometry_ is the representation of the 3D shape of a product by geometric items representing a solid. It comprises the existing concept templates "Body Tessellation Geometry", "Body SweptSolid Geometry", and "Mapped Solid Geometry". It is used if no particular geomertric item is requested, but any valid geometric item can be used to provide the "Body Geometry". + +The following attribute values for the _IfcShapeRepresentation_ holding this geometric representation shall be used: + +* _IfcShapeRepresentation_._RepresentationIdentifier_ = 'Body' +* _IfcShapeRepresentation_._RepresentationType_ = 'Tessellation', 'SweptSolid', 'MappedRepresentation' +* _IfcShapeRepresentation_._Items_ = _IfcTessellateditem_, _IfcExtrudedAreaSolid_, _IfcRevolvedAreaSolid_, _'IfcMappedItem'_ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The _Body SurfaceModel Geometry_ is the representation of the 3D shape of a product by surface models. @@ -1213,12 +1333,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1273,12 +1393,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1507,6 +1627,9 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo * _IfcShapeRepresentation_._Items[1..n].SweptArea_ = _IfcArbitraryClosedProfileDef_, _IfcArbitraryProfileDefWithVoids_ * _IfcShapeRepresentation_._Items[1..n].SweptArea.OuterCurve_ = _IfcIndexedPolyCurve_ * _IfcShapeRepresentation_._Items[1..n].SweptArea.InnerCurves_ = _IfcIndexedPolyCurve_ + + + @@ -1563,6 +1686,9 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo * _IfcShapeRepresentation_._RepresentationIdentifier_ = 'Body' * _IfcShapeRepresentation_._RepresentationType_ = 'Tessellation' * _IfcShapeRepresentation_._Items_ = _IfcTessellatedFaceSet_ + + + @@ -1584,12 +1710,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1602,7 +1728,7 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + @@ -1636,6 +1762,9 @@ The representation identifier and type and the only allowed single representatio * _IfcShapeRepresentation_._Items_ = _IfcBoundingBox_ > NOTE&nbsp; The specification does not determine the method by which the bounding box has to be created. If such a method need to be prescribed the definition has to be established by model view definitions or implementer agreements. + + + @@ -1652,12 +1781,12 @@ The representation identifier and type and the only allowed single representatio - + - + @@ -1668,12 +1797,12 @@ The representation identifier and type and the only allowed single representatio - + - + @@ -1754,6 +1883,9 @@ The representation identifier and type and the only allowed single representatio * _IfcShapeRepresentation_._RepresentationIdentifier_ = 'CoG' * _IfcShapeRepresentation_._RepresentationType_ : 'BoundingBox' * _IfcShapeRepresentation_._Items_ = _IfcCartesianPoint_ + + + @@ -1812,12 +1944,12 @@ The representation identifier of the foot print representation is: - + - + @@ -1871,12 +2003,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1892,12 +2024,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1944,12 +2076,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1965,12 +2097,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -1998,6 +2130,9 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo This specialization of the footprint representation uses indexed curves to represent boundaries. + + + @@ -2009,12 +2144,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -2030,12 +2165,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -2285,6 +2420,27 @@ The representation identifier of the mapped geometry representation is any of th + + + + + + + + + + + + + + + + + + + + + @@ -2367,12 +2523,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -2424,12 +2580,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -2453,14 +2609,17 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - - The _Reference SweptSolid Geometry_ is the reference representation of the 3D shape of a product by swept solid models, only allowing for the basic extruded area solids and revolved area solids. Being a reference representation it is normally not displayed and it is not used in a voiding relationship. + + The _Reference Geometry General_ is the reference representation of the 3D shape of a product by using either of the existing concept templates "Reference Tessellation Geometry", "Reference SweptSolid Geometry". It is used if no particular geomertric item is requested, but any valid geometric item can be used to provide the "Reference Geometry". Being a reference representation it is normally not displayed and it is not used in a voiding relationship. The following attribute values for the _IfcShapeRepresentation_ holding this geometric representation shall be used: * _IfcShapeRepresentation_._RepresentationIdentifier_ = 'Reference' -* _IfcShapeRepresentation_._RepresentationType_ = 'SweptSolid' -* _IfcShapeRepresentation_._Items_ = _IfcExtrudedAreaSolid_, _IfcRevolvedAreaSolid_ +* _IfcShapeRepresentation_._RepresentationType_ = 'Tessellation', 'SweptSolid' +* _IfcShapeRepresentation_._Items_ = _IfcTessellatedFaceSet_, _IfcExtrudedAreaSolid_ + + + @@ -2488,23 +2647,79 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + The _Reference SweptSolid Geometry_ is the reference representation of the 3D shape of a product by swept solid models, only allowing for the basic extruded area solids and revolved area solids. Being a reference representation it is normally not displayed and it is not used in a voiding relationship. + +The following attribute values for the _IfcShapeRepresentation_ holding this geometric representation shall be used: + +* _IfcShapeRepresentation_._RepresentationIdentifier_ = 'Reference' +* _IfcShapeRepresentation_._RepresentationType_ = 'SweptSolid' +* _IfcShapeRepresentation_._Items_ = _IfcExtrudedAreaSolid_ + + + + + + + + + + + + + + + + + + + - - - - - - - - + + + + + + - + @@ -2528,6 +2743,9 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo * _IfcShapeRepresentation_._Items[1..n].SweptArea_ = _IfcArbitraryClosedProfileDef_, _IfcArbitraryProfileDefWithVoids_ * _IfcShapeRepresentation_._Items[1..n].SweptArea.OuterCurve_ = _IfcIndexedPolyCurve_ * _IfcShapeRepresentation_._Items[1..n].SweptArea.InnerCurves_ = _IfcIndexedPolyCurve_ + + + @@ -2564,11 +2782,9 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - - @@ -2593,6 +2809,9 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo * _IfcShapeRepresentation_._RepresentationIdentifier_ = 'Reference' * _IfcShapeRepresentation_._RepresentationType_ = 'Tessellation' * _IfcShapeRepresentation_._Items_ = _IfcTessellatedFaceSet_ + + + @@ -2616,12 +2835,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -2736,12 +2955,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -2794,12 +3013,12 @@ The following attribute values for the _IfcShapeRepresentation_ holding this geo - + - + @@ -3014,6 +3233,135 @@ The representation identifier and type and the only allowed single representatio + + The surface colour of the geometry. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + <templaterules operator="and"> + <templaterule parameters="Name[Value]='RC-Beams'"></templaterule> +</templaterules> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Product occurrences are placed in a right handed Cartesian coordinate system. The _Product Placement_ is used to establish an object coordinate system that maby be placed relative to a parent object coordinate system, and ultimately to the project coordinate system. @@ -3107,6 +3455,13 @@ Placement follows aggregation and containment relationships as follows: * for distribution elements, positioning is relative to the containing spatial structure, however may be constrained by port connections. For example, a electrical junction box may fill an opening within a wall, and the junction box may contain ports for contained outlets or switches; the placement of such connected elements is contrained relative to connected port of the junction box. As another example, an air terminal may fill a ceiling covering which is placed relative to a space; the placement of a connecting duct fitting may be constrained relative to the air terminal. If a containing spatial structure contains a grid, then placement may also be based relative to grid coordinates. In certain use cases, an absolute placement may be used by omiting the _IfcObjectPlacement_. In this case, the shape representation is defined within the world coordinate system. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="HasPlacement[Exists]=TRUE AND RelativeToElement[Type]='IfcBuildingStorey' AND SpatialElementName='Ground Floor'"/> +</TemplateRules> + + @@ -3117,9 +3472,34 @@ If a containing spatial structure contains a grid, then placement may also be ba - + - + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Templates/Product Type Shape/DocTemplateDefinition.xml b/Templates/Product Type Shape/DocTemplateDefinition.xml index c2f9549d9..45394d9fc 100644 --- a/Templates/Product Type Shape/DocTemplateDefinition.xml +++ b/Templates/Product Type Shape/DocTemplateDefinition.xml @@ -398,6 +398,108 @@ If an element type is defined parametrically (such as a flow segment type defini + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -591,12 +693,12 @@ If an element type is defined parametrically (such as a flow segment type defini - + - + @@ -607,12 +709,12 @@ If an element type is defined parametrically (such as a flow segment type defini - + - + diff --git a/Templates/Project Context/DocTemplateDefinition.xml b/Templates/Project Context/DocTemplateDefinition.xml index a04fc21e2..fb6ec6195 100644 --- a/Templates/Project Context/DocTemplateDefinition.xml +++ b/Templates/Project Context/DocTemplateDefinition.xml @@ -18,116 +18,17 @@ - - Adding a geospatial coordinate reference, using an recognized coordinate reference system, to the geometric representation context. It allows to position the project coordinate system on earth (normally using eastings, northings, elevation about datum, and orientation). - -> HISTORY&nbsp; New concept template enabled by schema enhancements in IFC4. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Projects may define classification structures, which may be used to classify objects contained within the same project, or other referencing projects (incorporating the current project as _IfcProjectLibrary_). The classification information can either be provided as an external classification reference, only refering to an _IfcClassification_, that holds the classification name, edition and a resource location, or to an _IfcClassification_ containing the _IfcClassificationReference_'s as the classification notations, and thereby allowing to include the classification system structure within the exchange structure. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="ClassificationSource[Value]='DIN' AND ClassificationName[Value]='DIN 276'"/> +</TemplateRules> + + @@ -356,6 +257,13 @@ The classification information can either be provided as an external classificat Declaration of object types, such as element types utilized by the element occurrences within this project, within the context of the project. It provides a directory of all object types independently if and where they are used by object occurrences. > HISTORY&nbsp; New concept template enabled by schema enhancements in IFC4. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="RelatedTypes[Type]='IfcBeamType' AND RelatedTypes[Size]=3"/> +</TemplateRules> + + @@ -450,6 +358,126 @@ The classification information can either be provided as an external classificat + + Adding a geospatial coordinate reference, using an recognized coordinate reference system, to the geometric representation context. It allows to position the project coordinate system on earth (normally using eastings, northings, elevation about datum, and orientation). + +> HISTORY&nbsp; New concept template enabled by schema enhancements in IFC4. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="HasGlobalPosition[Exists]=TRUE"/> + <TemplateRule Parameters="CRSName[Value]=EPSG:5555"/> + <!-- Other checking parameters: Eastings[Value], Northings[Value], OrthogonalHeight[Value], XaxisAbscissa[Value], XAxisOrdinate[Value] --> +</TemplateRules> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Projects may define libraries holding revisions of the project such as model servers or databases. Multiple libraries may be referenced to indicate multiple revisions, multiple branches, and/or multiple servers. @@ -617,7 +645,7 @@ application/step | IFC-SPF - + @@ -690,12 +718,12 @@ application/step | IFC-SPF - + - + @@ -734,7 +762,7 @@ application/step | IFC-SPF - + @@ -791,6 +819,13 @@ application/step | IFC-SPF The main geometric representation context that is created for 3D representations, it can be further refined using geometric representation sub contexts for specific 3D contexts. > NOTE&nbsp; The 3D shape representations with the representation identifier "Body" are linked to the 3D geometric representation subset with context identifier "Body" and context type "Model". + + + <TemplateRules operator="and"> + <TemplateRule Parameters="ContextIdentifier[Value]='Model' AND ContextType[Value]='Body' AND SubContextIdentifier[Value]='Model'"/> +</TemplateRules> + + @@ -808,12 +843,12 @@ application/step | IFC-SPF - + - + @@ -852,7 +887,7 @@ application/step | IFC-SPF - + @@ -911,9 +946,9 @@ application/step | IFC-SPF The project context includes the definition of the default units within the IFC data set. They are declared once for the context of the whole data set. Default units are those units that apply: -* to all geometric representation items within the geometric representation contexts; -* to all attributes with a defined datatype indicating a measure datatype; -* to all properties and quantities with a defined datatype indicating a measure datatype and with no local unit definitions provided. +* to all geometric representation items within the geometric representation contexts; +* to all attributes with a defined datatype indicating a measure datatype; +* to all properties and quantities with a defined datatype indicating a measure datatype and with no local unit definitions provided. Default units are defined as either: @@ -923,6 +958,16 @@ Default units are defined as either: * Monetary unit as a special case of a unit to hold the currency name > EXAMPLE&nbsp; Meter is an SI unit without prefix, milli meter is an SI unit with prefix, inch and foot are conversion based units to be declared with a converstion factor to the SI unit (here meter), heat flux density (W/m2) is a derived unit with the unit elements Power (W) and Area (m2), and Euro is a monetary unit. + + + <TemplateRules operator="and"> + <TemplateRule Parameters="HasUnits[Exists]=TRUE"/> + <TemplateRule Parameters="SIUnitType[Value]='LENGTHUNIT' AND SIUnitName[Value]='METRE'"/> + <TemplateRule Parameters="ConversionUnitType[Value]='PLANEANGLEUNIT' AND ConversionUnitName[Value]='degree'"/> + <TemplateRule Parameters="DerivedUnitType[Value]='MASSDENSITYUNIT'"/> +</TemplateRules> + + diff --git a/figures/examples/ifcwallelementedcase-solid.png b/figures/examples/ifcwallelementedcase-solid.png index 10b29b827..2d3512436 100644 Binary files a/figures/examples/ifcwallelementedcase-solid.png and b/figures/examples/ifcwallelementedcase-solid.png differ diff --git a/figures/examples/ifcwallelementedcase-trans.png b/figures/examples/ifcwallelementedcase-trans.png index 5ec95ecbb..c2b9e1f4b 100644 Binary files a/figures/examples/ifcwallelementedcase-trans.png and b/figures/examples/ifcwallelementedcase-trans.png differ diff --git a/figures/ifcadvancedbrep_01.png b/figures/ifcadvancedbrep_01.png index 6aafe7a16..75f5e17ce 100644 Binary files a/figures/ifcadvancedbrep_01.png and b/figures/ifcadvancedbrep_01.png differ diff --git a/figures/ifcbeam-01.png b/figures/ifcbeam-01.png new file mode 100644 index 000000000..0ea09c721 Binary files /dev/null and b/figures/ifcbeam-01.png differ diff --git a/figures/ifcbeam-02.png b/figures/ifcbeam-02.png new file mode 100644 index 000000000..c8bd72b0f Binary files /dev/null and b/figures/ifcbeam-02.png differ diff --git a/figures/ifcbeam_cardinalpoint.png b/figures/ifcbeam_cardinalpoint.png new file mode 100644 index 000000000..3097ac005 Binary files /dev/null and b/figures/ifcbeam_cardinalpoint.png differ diff --git a/figures/ifccolumn-01.png b/figures/ifccolumn-01.png new file mode 100644 index 000000000..860dac7a5 Binary files /dev/null and b/figures/ifccolumn-01.png differ diff --git a/figures/ifccolumn-02.png b/figures/ifccolumn-02.png new file mode 100644 index 000000000..89f3e35a6 Binary files /dev/null and b/figures/ifccolumn-02.png differ diff --git a/figures/ifccolumn_cardinalpoint.png b/figures/ifccolumn_cardinalpoint.png new file mode 100644 index 000000000..bfc3cbb55 Binary files /dev/null and b/figures/ifccolumn_cardinalpoint.png differ diff --git a/figures/ifcgeometricrepresentationcontext_truenorth.png b/figures/ifcgeometricrepresentationcontext_truenorth.png index cba7d1aca..ff72031cb 100644 Binary files a/figures/ifcgeometricrepresentationcontext_truenorth.png and b/figures/ifcgeometricrepresentationcontext_truenorth.png differ diff --git a/figures/ifcindexedcolourmap-fig1.png b/figures/ifcindexedcolourmap-fig1.png index 39e2e77c3..8865638bd 100644 Binary files a/figures/ifcindexedcolourmap-fig1.png and b/figures/ifcindexedcolourmap-fig1.png differ diff --git a/figures/ifcindexedpolycurve-fig1.png b/figures/ifcindexedpolycurve-fig1.png index 5ccd880da..634e99fec 100644 Binary files a/figures/ifcindexedpolycurve-fig1.png and b/figures/ifcindexedpolycurve-fig1.png differ diff --git a/figures/ifcindexedpolycurve-fig2.png b/figures/ifcindexedpolycurve-fig2.png index 8ee8b9db4..a833115da 100644 Binary files a/figures/ifcindexedpolycurve-fig2.png and b/figures/ifcindexedpolycurve-fig2.png differ diff --git a/figures/ifcindexedpolygonalface_01.png b/figures/ifcindexedpolygonalface_01.png index 954c29883..00bdf84e2 100644 Binary files a/figures/ifcindexedpolygonalface_01.png and b/figures/ifcindexedpolygonalface_01.png differ diff --git a/figures/ifcmember-01.png b/figures/ifcmember-01.png new file mode 100644 index 000000000..04b197551 Binary files /dev/null and b/figures/ifcmember-01.png differ diff --git a/figures/ifcmember-02.png b/figures/ifcmember-02.png new file mode 100644 index 000000000..5ac58bc91 Binary files /dev/null and b/figures/ifcmember-02.png differ diff --git a/figures/ifcmember_sweptsolid-01.png b/figures/ifcmember_sweptsolid-01.png deleted file mode 100644 index bdc20651b..000000000 Binary files a/figures/ifcmember_sweptsolid-01.png and /dev/null differ diff --git a/figures/ifcplate_materialusage-01.png b/figures/ifcplate_materialusage-01.png new file mode 100644 index 000000000..27cc8512d Binary files /dev/null and b/figures/ifcplate_materialusage-01.png differ diff --git a/figures/ifcpolyline-fig1.png b/figures/ifcpolyline-fig1.png index b511e8c0d..6d9d8de1a 100644 Binary files a/figures/ifcpolyline-fig1.png and b/figures/ifcpolyline-fig1.png differ diff --git a/figures/ifcslabelementedcase-floor.png b/figures/ifcslabelementedcase-floor.png deleted file mode 100644 index 26b4a7225..000000000 Binary files a/figures/ifcslabelementedcase-floor.png and /dev/null differ diff --git a/figures/ifcsurface-math1.png b/figures/ifcsurface-math1.png new file mode 100644 index 000000000..9379b6ccb Binary files /dev/null and b/figures/ifcsurface-math1.png differ diff --git a/figures/ifcsurface-math2.png b/figures/ifcsurface-math2.png new file mode 100644 index 000000000..9f22db6ce Binary files /dev/null and b/figures/ifcsurface-math2.png differ diff --git a/figures/ifcsweptdisksolid-layout1.png b/figures/ifcsweptdisksolid-layout1.png index e77d4986d..0bc234ab0 100644 Binary files a/figures/ifcsweptdisksolid-layout1.png and b/figures/ifcsweptdisksolid-layout1.png differ diff --git a/figures/ifctriangulatedfaceset_01.png b/figures/ifctriangulatedfaceset_01.png index 5462b114a..ad602e0b2 100644 Binary files a/figures/ifctriangulatedfaceset_01.png and b/figures/ifctriangulatedfaceset_01.png differ diff --git a/figures/ifcwall_materialusage-01.png b/figures/ifcwall_materialusage-01.png new file mode 100644 index 000000000..32b730fec Binary files /dev/null and b/figures/ifcwall_materialusage-01.png differ diff --git a/img/IFC4_layered_architecture.png b/img/IFC4_layered_architecture.png index 3157a8076..44c5753d0 100644 Binary files a/img/IFC4_layered_architecture.png and b/img/IFC4_layered_architecture.png differ