Skip to content

IFC

Use this dialog to define a project base point for IFC models, i.e., map coordinates for the origin point in the BIM project, and set various settings for export to IFC.

Where do I find the dialog?

On the toolbar select the icon for Settings Gemini Terrain - Project - IFC.

Using the dialog

You can enter values manually or snap them in the map. Note that 3D snapping must be active for height to be included (toolbar at the bottom left).

The program uses the project base point when inserting IFC files that are not georeferenced but have relative coordinates based on this point. Before you insert the IFC model with Add you must enter the project base point in Settings Gemini Terrain - Project - General to ensure correct placement (otherwise, it may be placed relative to 0,0).

Note

If the IFC origin is not specified, the origin for all terrain models is used. Normally, this is 0,0 and has no significance.

A = Project base point

IFC models with only an internal origin in the model must be placed manually with dynamic placement, or georeferenced with the function Georeference model... that you find on the context menu of models.

Georeferenced IFC models

When you insert a georeferenced IFC model, a dialog appears with the georeference information (IfcProjectedCRS and IfcMapConversion):

  • IfcProjectedCRS.Name = EPSG code (specifies the combination of geodetic datum, projection, and height datum)
  • IfcMapConversion.Eastings = EAST coordinate
  • IfcMapConversion.Northings = NORTH coordinate
  • IfcMapConversion.OrthogonalHeight = HEIGHT

The project base point in Settings Gemini Terrain - Project - General is not used if the IFC model is georeferenced. The file will then be placed according to the georeference information, where IfcMapConversion can be 0,0,0 or have a project base point.

Export to IFC

You can enter Name of project (IfcProject) in this dialog. If the field is blank, the program will use the project name and description in the general properties dialog.

The project base point is also used when exporting data (File - Export - IFC). The values for the project base point are subtracted from the object coordinates when exporting to IFC.

Without a defined IFC origin (0,0,0), you get map coordinates in the file. You can optionally check Export map coordinates if you want this even when the project base point is defined.

Furthermore, you can also enter Name of exported construction site (IfcSite). Gemini-map is the default name (for backward compatibility).

You can also configure how different attributes from the schema should be exported.

Export description as part of attribute values

Normally, descriptions for attribute values (such as S_FCODE) are placed in a description/specification field separate from the actual value.

However, most IFC viewers ignore the description field and only show the user the code.

With this option, you can decide whether the description should be added to the value during export.

Export of geometry attributes in application layer

Here you can choose whether geometry attributes should be included and what name the PSet should have. The default name is Ter_Qto_Geometry. This is used to avoid conflict with standard IFC PSet. Common fields are for example Length, Area, and Volume.

Export of root-level attributes

Here you can choose whether attributes at root level (that do not belong to a group in the schema) should be included and what the PSet should be called. The default name is Attributter.

Export of groups in the schema

Here you can choose whether groups in the schema should be included or not. You can also specify a prefix for the PSet groups. The default value is an empty string (no prefix). The prefix is used to avoid name conflicts with standard IFC PSet.

Note

PSet stands for Property Set in IFC and is used to organize properties in logical groups.

Contract post number

Warning

This function is disabled from version 19.0.1.

Use these settings to link relevant parts of the contract with attributes as they appear in Gemini Terrain, to display relevant contract posts in Gemini 3D Field. In the example, the fields Location and Process must be filled in, but this will vary between contracts. The program will prompt for the relevant post number parts.

Example

The example below shows how such a link can look. Here, we want to extract ISY Location and ISY Process code. Since these are under the property ISY Description you must use the syntax shown in the second image.

The result in Gemini 3D Field is that the contract appears as a separate tab for IFC elements:

Note

The method described also works for DWG files.