| Latest revision |
Your text |
| Line 15: |
Line 15: |
| | You can find the command in Blender under Scene > Building Information Modeling > System Setup. | | You can find the command in Blender under Scene > Building Information Modeling > System Setup. |
| | This will create a basic spatial tree. It will create a tree of collections with the structure IfcProject > IfcSite > IfcBuilding > IfcStorey This is merely for convenience instead of having to create it all by yourself, since all IFC exports require a valid spatial tree. You can see the tree of collections in the outliner when this is done. | | This will create a basic spatial tree. It will create a tree of collections with the structure IfcProject > IfcSite > IfcBuilding > IfcStorey This is merely for convenience instead of having to create it all by yourself, since all IFC exports require a valid spatial tree. You can see the tree of collections in the outliner when this is done. |
| − | [[File:BlenderBIM QuickProjectSetup 01.JPG|frame|center|Quick Project Setup, Schema and Data directories]] | + | [[File:BlenderBIM_QPS.jpg|frame|Quick Project Setup, Schema and Data directories]] |
| − | | |
| − | ==Standard project structure==
| |
| − | The standard project structure, as proposed by Building Smart (the developer of IFC) and currently default in the BlenderBIM add-on, is following:
| |
| − | *site as IfcSite
| |
| − | *building as IfcBuilding
| |
| − | *storey as IfcBuildingStorey
| |
| − | *space as IfcSpace
| |
| − | A project can include any number of sites, a site any number of buildings and so on.
| |
| − | The abstract spaces, converted to their respective IFC counterparts on export, are represented by a hierarchy of collections. Any objects outside a IfcSite collection will be ignored on export.
| |
| − | | |
| − | Empty axes objects, with names identical to those of their container collections, are automatically placed in the project structure created by the Quick project setup command and they serve several purposes:
| |
| − | | |
| − | They hold the IFC properties for the spatial elements. IFC spatial elements (e.g. sites, buildings, elements) can store properties (attributes / psets / qtos / etc). In Blender, if you click on an object, you can see the object panel and manipulate it via the UI. However, for a collection, there is no UI panel associated with the collection. So for convenience, an object is provided that people can click on.
| |
| − | | |
| − | They define the IFC placement of the spatial element. IFC spatial elements almost always have a placement. E.g. a building storey has an elevation value (e.g. a Z coordinate). Blender collections do not have physical locations. Therefore, at the very least, an empty is required, so you can set the placement.
| |
| − | | |
| − | They serve as a placeholder for IFC representations of the spatial element. IFC spatial elements may have representations. E.g. a building or site can actually have geometry associated with it. Therefore, we need an object. In this case, we need more than an empty - we need an actual mesh object.
| |
| − | | |
| − | Note that the name of the Representation object (empty axes or anything else you use) has to be kept identical to the name of the collection it belongs to. So if you rename a storey for example, the empty must be renamed as well.
| |
| − | {{BlenderBIM_Add-on_Documentation}}
| |
| − | [[Category:Blender]] [[Category:BlenderBIM Add-on]]
| |
