Decided to re-visit coordinate settings for projects that requires IFC exchange between ARCHICAD and Revit in this blog. In my previous blogs the focus was only on Latitude(Lat) and Longitude(Long). I received some requests to handle Northing and Easting (UTM) as well. To address that I tested the settings of both ARCHICAD and Revit and share the result via this blog.
Before going into how to do the settings we need to understand how both tools work and various coordinate systems available for us to use.
Forward migration is usually relatively smooth with ARCHICAD nowadays, but if it’s paired with some hotlinking and IFC export then the new features might cause some confusion.
Two of the latest additions to ARCHICAD are the introduction of Classification Systems and the improved IFC Translator settings, which both provide a lot of opportunities and smart management functions for the user, but during migration+hotlinking+IFC export they will need some extra cautiousness, otherwise the user might get unexpected results. Even though this might not be a mainstream case, we just had a few support issues in Singapore because of this, so let me give a generic explanation, hoping to clear up the confusion as much as possible 🙂
Recently came accross a situation where the Design Architect need to exchange ARCHICAD model with their project partners. The Main Contractor was using REVIT for their BIM process. So, there was a need for conversion of ARCHICAD model to REVIT model via IFC.
The project has large topography as it was a infrastructure project and all of them were created using Mesh object in ARCHICAD. When the topography was transferred to REVIT via IFC that becomes as a Model In-Place element which can not be edited easily. The Main Contractor requested for Toposurface which can be edited further in REVIT. This article covers the solution on how to re-create an editable Toposurface in REVIT using the data exported from ARCHICAD.
This post is a follow-up of previous post Project Base Files for Coordination. In case the Structural team decided to use Tekla Structures for their BIM authoring then they need a Project Base File in Tekla with setup based on Architectural file.
Architectural Project Base File
Setup the Architectural Project Base File in ARCHICAD and export as IFC file as discussed in the post Project Base Files for Coordination.
This post is to follow up on a request for explanation of each step on the post Project Base Files for Coordination. Let me write this post to further explain the steps.
Why there is a need for Project Base Files?
As mentioned in the post Project Base Files (PBF) are project specific templates in various tools used for BIM authoring.
- PBF consists of Location, Orientation, Grids and Levels. These information can be based on national standards or agreed settings by the entire project team through BIM Execution Plan (BEP).
- This is to make sure everyone (BIM Authors) start with the right foot.
- This will ease the co-ordination process when the models from different BIM authors (disciplines or trades) are merged together.
- This is to represent the real world condition of the entire building (including all disciplines) virtually.
This post is to follow up on the previously published ‘Syncing Zone Cover Fills and Floor Finishes’ article where we mapped the Cover Fill value of the Zones to a custom made IFC property and made it appear in the Zone Stamp, this way saving some time, but most importantly reducing the risk of human errors when the user has to manually update the Floor Finish parameter of the Zones.
We also faced a minor (?) problem: since the naming convention of the Fills is diverse, not all Fills can be used right away to be displayed with their names as Floor Finishes. For example all ‘Pavement xx’ fills should only show ‘Pavement’, instead of showing the full name, including the version number.
Splitting the IFC Mapping rules is a way to solve this problem. A similar case where rule splitting was involved for the Zone Names has already been presented on this blog by Chidam, this post intends to give some detailed explanation on the rule splitting particularly, so it is easier to embrace it. IFC Mapping is NOT ONLY for model exchange purposes!