Skip to content
This repository has been archived by the owner on Mar 31, 2024. It is now read-only.

Describe how representation ContextIdentifier should be used #10

Merged
merged 1 commit into from
Sep 27, 2019
Merged

Describe how representation ContextIdentifier should be used #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions ...resentationResource/Entities/IfcGeometricRepresentationContext/Documentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@

The use of one instance of _IfcGeometricRepresentationContext_ to represent the model (3D) view is mandatory, the use of a second instance of _IfcGeometricRepresentationContext_ to represent the plan (2D) view is optional (but needs to be given, if there are scale dependent plan views), the additional scale or view dependent contexts need to be handled by using the subtype _IfcGeometricRepresentationSubContext_ pointing to the model view (or the plan view) as the _ParentContext_. See Figure 2 for an example using geometric representation contexts for 3D and 2D with assigned sub contexts.

> NOTE  The inherited attribute _ContextIdentifier_ shall have a value that matches _IfcShapeRepresentation.RepresentationIdentifier_. For example 'Body', 'Annotation', or 'Axis'.
> NOTE  The inherited attribute _ContextType_ shall have one of the following recognized values: 'Model', 'Plan', 'NotDefined'.

 
Expand Down