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.
Just recently came across this issue that unit modules were meant to be linked into a block file, but due to the large amount of small variations within the units, the designers wanted to have a base module to link into the unit file as well, such as:
Module A is linked to the Units file onto different stories. In the Units file, small variations are added to the base A, which eventually results in Unit A1, A2, etc. Similarly with Unit type B, C and so on. Eventually the Unit file was linked story-by story into the Block file.
Though from attribute management point of view such amount of hotlinks is not easy to manage, the designers preferred this solution to deal with the frequent design changes of the 30+ unit types. At the end of the linking process the problem was, that since the Units file already contained more than 20 hotlinks, the total number of links significantly increased in the master file, which caused slowness in general, for scheduling, for updating the links and so on. If the Units file could have been a single file without previously added links it would have been much easier to handle. To overcome this issue, a tiny, but very powerful function of the Publisher was activated: Break nested Hotlinks and Xrefs.
Whenever publishing modules – in this case every story that contains one unit type was published as a separate module -, using the embedding function under Options… allows us to get rid of the excess links. At the same time the designers could still use the Units file for doing their work, but the process was not hindered later either.
As an additional benefit, the published modules only need to be linked once into the further files (typical stories or directly into the block), whenever there is an update, they just publish again with a click and update the links.
Setting up the Project Altitude properly and displaying its values for BIM Submission in Singapore requires a bit of insight of the Reference Levels function of ARCHICAD which the local practice might not be fully aware of.
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 🙂
ARCHICAD Meshes can be created in many different ways – by creating level ridges based on external drawings, by importing point clouds and modeling the terrain based on it or importing text files with the coordinates and then let ARCHICAD automatically build the terrain.
The first scenario is ideal as it will provide us with the contours that mark points at the same elevation, but other creation methods do not provide that natively. Using add-ons with more comprehensive earthwork-related functions can be an option, but for such a simple request we also have a solution within ARCHICAD.
Some users like to have their own 2D representations created with lines and fills for the default window with a little bit GDL scripting, let us look at how we can achieve that and how to control it with ARCHICAD’s Model View Option (MVO).