Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


It is possible to import ArchiCAD Zones with any associated information from an ArchiCAD model directly into the dRofus database. 

This feature can be used to load data into a dRofus Project from an existing ArchiCAD model. This function is also used to dynamically add Zones being created in ArchiCAD into dRofus. For example, after having placed all of the dRofus Rooms in the ArchiCAD model, you might later add all the additional ArchiCAD created Zones (such as Corridors) into dRofus.

What data is imported?

Like all other operations in the ArchiCAD Add-On this process also relies upon the active Room Attribute Configuration. By default it will use the Configuration you have defined as Default, but you can also create a customised Configuration for importing Zones. If so, make sure you select the correct Attribute Configuration by clicking on the active Attribute Configuration to use within the "Import Rooms to dRofus" dialog (highlighted below):



When importing Zones to dRofus the directions of all the mapped attributes within the Attribute Configuration will be reversed in order to write data FROM ArchiCAD TO dRofus. For example, if you have defined that "Notes" on a Room should go from dRofus to ArchiCAD in the active Attribute Configuration, when you carry out the ArchiCAD Zones import, it will actually push the values the other way - i.e., from ArchiCAD to dRofus. However, note that it will not update any Attributes that are read-only in dRofus (such as system or calculated attributes). These attributes will be displayed in half tone within the Attribute Configuration editor to indicate which ones cannot be updated.

Where should the Zones be imported to in dRofus?

Every Zone that is to be imported in to dRofus must be located somewhere within the pre-defined Function Structure. So before importing Zones into dRofus you must decide which Function and / or Sub-Function to import to. 

You need to identify the Zone properties within ArchiCAD which contain Functions / Sub Functions information. In the following example, for Zones on LEVEL 9, the ArchiCAD IFC property called "Building" is used to define the 1st Function tier, "Level" as the 2nd Function tier and "Department" as the 3rd Function tier (highlighted below):




In order to view the IFC properties for Zones within the "Import Rooms to dRofus" dialog, you will need to select at least one Zone (that contains all the required IFC properties) prior to bringing up the "Import Rooms to dRofus" dialog:



Within the "Import Rooms to dRofus" dialog, you select the Zone properties that contain the Function / Sub Function definitions. You can then specify whether the values within each property contain the Name value, Number value, or both. The default is that it contains the Name only.

If the Zone property contains only the name of the Function, it will create a new Function in dRofus with that name (if it doesn't already exist) and auto-generate a number for that Function during import.

If the Zone property contains only the number of the Function, it will create a new Function in dRofus with that number (if it doesn't already exist) and leave its name empty.


An example of using Name only against the 3 levels of Functions is as follows:



There is a filter to indicate which Zone(s) to consider for importing in to dRofus as Rooms:

Checkboxes to include only specific Zone(s) and / or lowest (identified) Function(s)



Using the "Name only" option for all the 3 Function tiers, and after clicking on "Import Rooms", 1 x 2nd tier Function called "LEVEL 9" and 3 x 3rd tier Functions called "Balcony", "T&E" and "Unit" along with the 13 Room instances have now been created within dRofus as follows:

Note that the Function "LEVEL 9" has acquired "12" as its Number. This can be easily changed within the "Properties" panel on the right-hand side:



Info

If you have not yet decided the Functions / Sub-Functions (within the pre-defined Function Structure) in to which you'd like your Zones to be imported in to, you could just import the Zones into a temporary Function in dRofus, and then later move them to the desired Functions / Sub-Functions within the dRofus Client.

If the active Room or Space Attribute Configuration has been mapped with dRofus' "Room Name" --> ArchiCAD's "Zone Name" - "Room Name"s of the new Rooms created in dRofus will be blank and "Zone Name"s of the Zones within the model will be blanked out.
If the active Room or Space Attribute Configuration has been mapped with ArchiCAD's "Zone Name" --> dRofus' "Room Name" AND the "Disable edit room names" within dRofus Client is checked by the Project Administrator - an error message saying "Changing the list of predefined Room Names is not allowed" will appear, followed by another message saying no Rooms have been imported / created within dRofus.
If the active Room or Space Attribute Configuration has no mapping of Names between dRofus and Revit - "Room Name"s of the new Rooms created in dRofus will be blank while "Zone Name"s of the Zones within the model will remain unchanged.

  • No labels