archive-org.com » ORG » B » BUILDINGSMART-TECH.ORG

Total: 393

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • #CV-2x3-142 — Welcome to buildingSMART-Tech.org
    the spatial structure Description An IFC exchange file conforming to the coordination view shall have minimum of one instance of IfcBuilding within the spatial structure either directly assigned to IfcProject if no IfcSite is present or assigned to IfcSite Previous CV 2x3 141 Next CV 2x3 143 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 142 IFC Impl Guide IFC Header Guide IFC4

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-142 (2016-02-11)
    Open archived version from archive


  • #CV-2x3-143 — Welcome to buildingSMART-Tech.org
    2x3 143 based on IFC2x3 effects extended coordination view date 23 May 2007 initiator ISG meeting in Espoo summary agreement on having the containment tree and the relative placement tree identical for spatial elements Description The spatial containment of IfcSpatialStructureElement forms a tree and the local relative placement of IfcSpatialStructureElement forms another tree both trees should be identical i e if an IfcBuildingStorey is contained in 201 IFCBUILDING then the IfcBuildingStorey ObjectPlacement PlacementRelTo shall point to the same instance 201 IFCBUILDING Figure the containment and local placement trees Added 2010 in official buildingSMART certification 2 0 program the uppermost spatial structure element either an IfcSite or an IfcBuilding that is directly assigned to the IfcProject through Decomoses RelatingObject shall have no relative placement the placement of the uppermost spatial structure element is provided by IfcLocalPlacement with PlacementRelTo NIL Previous CV 2x3 142 Next CV 2x3 144 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 143 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents frequently asked questions Implementations Search Advanced Search IFC Dev Blog IFC Dev Blog More Registration This site contains content which is only available to

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-143 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-144 — Welcome to buildingSMART-Tech.org
    element and no own geometry number CV 2x3 144 based on IFC2x3 effects extended coordination view date 26 Feb 2008 initiator ISG meeting in Prague summary roofs are aggregates and shall have at least one contained element and no own geometry Description update 2012 02 06 This implementer agreement has been withdrawn with immediate effect The IFC2x3 Coordination View 2 0 compliant applications shall support the import of IfcRoof with own geometric representation and without components This is to unify the requirements e g to equally apply to also IfcCurtainWall IfcStair IfcRamp etc Outdated agreement The IfcRoof should only be exported as an aggregate without having an own geometric representation As a minimum one contained element shall be included having the geometric representation This would normally be an IfcSlab with PredefinedType ROOF Previous CV 2x3 143 Next CV 2x3 145 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 144 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community accompanying documents frequently asked questions Implementations Search Advanced Search IFC Dev Blog IFC Dev Blog More Registration This site contains content which is only available to registered users To get access to

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-144 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-145 — Welcome to buildingSMART-Tech.org
    to an IfcExtrudedSolid and an IfcPolygonalBoundedHalfSpace or IfcBoxedHalfSpace Axis representation RepresentationIdentifier Axis RepresentationType Curve2D Body representation RepresentationIdentifier Body RepresentationType Clipping There are two options default the Body representation is based on an foot print profile with true arc segments IfcCompositeCurve with arc segments based on IfcTrimmedCurve referring to a BasisCurve of type IfcCircle The clipping boundary of the IfcPolygonalBoundedHalfSpace should then also be based on an IfcCompositeCurve with arc segments based on IfcTrimmedCurve referring to a BasisCurve of type IfcCircle The geometry of both the foot print of the wall and the clipping boundary could should be identical for the overlapping part of the curve or the clipping boundary is larger then the clipped body in all directions but the critical clipping edge fall back the Body representation is based on an foot print profile with either true arc segments or by a faceted polyline The clipping boundary has to be larger then the clipped body in all directions but the critical clipping edge NOTE It is illegal to send a Body with a footprint being a faceted polyline AND a clipping boundary being another faceted polyline both deemed to represent the same arc It would lead in wrong clippings

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-145 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-146 — Welcome to buildingSMART-Tech.org
    vertex defined only once and shared by edges Description For each IfcClosedShell and IfcOpenShell used e g in IfcFacetedBrep or in IfcShellBasedSurfaceModel each vertex shall only be exported once Edges shall share identical vertices Previous CV 2x3 145 Next CV 2x3 147 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3 146 IFC Impl Guide IFC Header Guide IFC4 impl guidance Implementer s community

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-146 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-147 — Welcome to buildingSMART-Tech.org
    following agreement is made for distinguishing the display of surfaces as single sided or double sided if no IfcSurfaceStyle is assigned to the IfcShallBasedSurfaceModel or the included IfcOpenShell or IfcClosedShell then the surfaces default to double sided surfaces for visualization if an IfcSurfaceStyle is assigned to the IfcShallBasedSurfaceModel or the included IfcOpenShell or IfcClosedShell then the surfaces are treated according to the value of IfcSurfaceStyle Side Values being POSITIVE or NEGATIVE determine a single sided surface the value BOTH determines a double sided surface NOTE 1 for correct visualization of single sided surfaces the face orientation is essential Single sided surfaces shall only be exported if the sending system can ensure correct orientation of faces NOTE 2 it is illegal to export surfaces of an IfcOpenShell or an IfcClosedShell twice one for each orientation inside or outside For IfcFacetedBrep s the face orientation always has to point away from the solid Therefore face normals have to be correct and consistent for all faces of the IfcFacetedBrep This implementer agreement extends and clarifies the agreement CV 2x3 135 Previous CV 2x3 146 Next CV 2x3 148 Implementation get involved first steps and tools IFC2x3 impl guidance IFC Impl Agreements CV 2x3

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-147 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-148 — Welcome to buildingSMART-Tech.org
    input latitude longitude and elevation within the geodetic system WGS84 address given as country city zip code address lines in some countries a region may be provided additionally true north as 2D direction indicating the derivation of the positive y axis of the project coordinate system to the north direction The information is exported into IfcSite RefLatitude IfcSite RefLongitude as degrees minutes second micro seconds IfcSite RefElevation as length measure IfcBuilding BuildingAddress IfcPostalAddress see note 1 added 13 07 2011 IfcGeometricRepresentationContext TrueNorth NOTE 1 added 13 07 2011 the following agreement is made regarding the provision of address the address if available shall always be exported as IfcBuilding BuildingAddress within the Coordination View V2 0 the address shall not be exported as IfcSite SiteAddress Example to 1 109 IFCSITE 30kooSTG92lR6dcl7curCu 33 Site 01 108 Example Site ELEMENT 48 7 58 800000 11 34 34 540000 500 34 to 2 35 IFCPOSTALADDRESS Any Street 12 Munich Bavaria 80000 Germany 36 IFCBUILDING 1VP6n5Llf2YvEbkIyrqQcE 33 Building 01 25 Example Building ELEMENT 500 34 35 to 3 20 IFCDIRECTION 0 7071 0 7071 27 IFCGEOMETRICREPRESENTATIONCONTEXT Model 3 1 E 006 26 20 28 IFCGEOMETRICREPRESENTATIONCONTEXT Plan 3 1 E 006 26 20 Previous CV 2x3

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-148 (2016-02-11)
    Open archived version from archive

  • #CV-2x3-149 — Welcome to buildingSMART-Tech.org
    ROOFING NOTDEFINED has been added as a requirement to the extended coordination view For export of IfcCovering the relationship IfcRelContainedInSpatialStructure is mandatory to assign the IfcCovering to the spatial structure of the project Optionally the relationships IfcRelCoversSpaces or IfcRelCoversBldgElements may be asserted There are no requirements for maintaining these relationships for round trip Previous CV 2x3 148 Next CV 2x3 150 Implementation get involved first steps and tools IFC2x3 impl

    Original URL path: http://www.buildingsmart-tech.org/implementation/ifc-implementation/ifc-impl-agreements/cv-2x3-149 (2016-02-11)
    Open archived version from archive



  •