Create IFCTunnelDep2.2.ifc #120
Conversation
Forgot to add the extra context to the project.
Add GUID for IfcRelPositions
IfcSite also aggregated to IfcProject
Separate IfcRelAggregates for IfcProject-IfcSite and IfcProject-IfcAlignment
IfcReferent.PredefinedType=.STATION. everywhere
IfcLinearPlacement.PlacementRelTo = IfcAlignment.ObjectPlacement
Co-authored-by: Stefan Jaud <[email protected]>
…/larswik/IFC-Tunnel-Deployment into Lars-example-file-for-sprint-2.2
| #93= IFCCARTESIANPOINT((0.0,0.0,0.0)); | ||
| #94= IFCPRODUCTDEFINITIONSHAPE($,$,(#95)); | ||
| #95= IFCSHAPEREPRESENTATION(#41,'Axis','Segment',(#96)); | ||
| #96= IFCCURVESEGMENT(.CONTSAMEGRADIENTSAMECURVATURE.,#97,IFCPARAMETERVALUE(-92.0),IFCNONNEGATIVELENGTHMEASURE(92.0),#100); |
There was a problem hiding this comment.
@SergejMuhic I can't remember: what was the conclusion on mixing IfcParameterValue with IfcNonNegativeLengthMeasure?
There was a problem hiding this comment.
@SergejMuhic I can't remember: what was the conclusion on mixing
IfcParameterValuewithIfcNonNegativeLengthMeasure?
Don't know? @SergejMuhic ?
There was a problem hiding this comment.
Implementer agreement, sort of.
|
Added a text to the Description attribute of IfcAlignment, IfcAlignmentHorizontal and IfcAlignmentVertical regarding the incorrect use of IfcNonNegativeLengthMeasure and IfcParameterValue in the geometric representations. Reports error for sprint 2.3 of course, but since this is 2.2, can we approve this file now? |
File
Manually edited the example file from sprint 2.1 with the following updates:
Covered Concept Templates - Usages Included
All concept templates up to and including sprint 2.2
Miscellaneous