# Export \[STG]

## Export File

After updating the model parameters, you can also update all exported files in your project folder. The 'Export' function enables users to specify the root directory and file names, automatically overriding previous files.

![](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20230317-223340.png?api=v2)

**Type\[Project Inputs/ 3D Model / 2D Drawings / Finite Element Model]:** This parameter is used to export different types of data to various file formats.

* If the user selects “Project Inputs”, workflow inputs can be exported to an Excel file.
* If the user chooses the “3D model”, they can export it to file formats such as Object (.obj), IFC v4.3 (.ifc), GL Transmission Format(.gltf) and AutoCAD (.dxf).
* If the user selects “2D drawings”, they have the option to export in Microstation (.dgn) or AutoCAD (.dxf) format.
* If the user selects a finite element model, they can choose to export it in SAP2000 (.s2k), CSIBRIDGE (.b2k), LARSA 4D (.lar), or Midas Civil (.mct) format.

**Object:** This parameter is activated only when "2D Drawings" is selected as the Type. Once enabled, the user must select the specific 2D drawing they wish to export. To select the 2D drawing, click the three-dot button within the Object parameter. In the user interface that appears, click the Select Drawing button, then choose the drawing to be exported.

![image-20250918-121515.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-121515.png?api=v2)

![image-20250918-121601.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-121601.png?api=v2)

![image-20250918-121515.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-121515.png?api=v2)

![image-20250918-121621.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-121621.png?api=v2)

**File Format:** This parameter is used to select the file format based on the chosen Type (Project Inputs, 3D Model, 2D Drawings, or Finite Element Model). To select the desired file format, click the three-dot icon within the parameter.

![image-20250918-123202.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-123202.png?api=v2)

**File Name\[Set Project Directory On Local Disk/Set File Name On Local Disk/Sync to Local Disk]:** The file name and file path can only be set through the 'Set File Name On Local Disk...' action accessed via the three-dot cell menu. The file path will be stored in the project, while the project directory will be stored in your browser's cache. This enables different users who access the same project to specify the location of the root project directory and immediately use export settings such as file names/paths.

![](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20230317-222444.png?api=v2)

**Set Project Directory On Local Disk:** The full path of the file will be the combination of the project directory and the file path. Users can choose the project directory through the '3-dot' spreadsheet cell actions.

**Sync to Local Disk:** Users can select specific rows and synchronize them by using the 'Sync to Local Disk' feature.

**Full Path \[Set Project Directory On Local Disk/Set File Name On Local Disk/Sync to Local Disk]:**

## DGN Export Settings

DGN Export Settings is a group of input parameters that allows users to configure export options when MicroStation is selected as the file format.

**Seed File:** In MicroStation, a seed file is a template file used as the starting point when creating a new drawing file (DGN). This file defines the initial settings and configuration for the new drawing.

A seed file ensures that fundamental settings are predefined before drafting begins. For example, it may include:

* Drawing units (meters, millimeters, inches, etc.)
* Drawing scale
* Level (layer) structure
* View settings
* Drawing limits
* Global origin (the starting point of the coordinate system)
* Line types and line weights
* Cell (block) definitions

By establishing these settings in advance, the seed file helps maintain consistency across drawings—particularly important in large-scale projects involving multiple team members.

The seed file can be selected by clicking the three-dot icon within the parameter.

![image-20250918-140055.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-140055.png?api=v2)

**Annotation Scale:** This parameter becomes active when the Export File Type is set to '2D Drawings' and the File Format is selected as 'Microstation (\*.dgn).'

In MicroStation, DGN Annotation Scale refers to the setting that controls the display scale of annotations such as text, dimensions, symbols, and other annotation elements within a DGN file.

\- *Scaling Annotations:* When working with drawings at different scales, it ensures that annotations (like texts, dimension lines, and notes) remain readable and consistent. In other words, when the drawing is zoomed in or out, annotation sizes are automatically adjusted accordingly.\
\- *Different View Scales:* If your drawing will be viewed or printed at various scales (e.g., 1:100, 1:50), the annotation scale ensures that annotations appear at the appropriate size for each scale.\
\- *Consistency of Fonts and Dimensions:* When annotation scale is enabled, texts and dimensions maintain a fixed size on the drawing, independent of the actual drawing scale.

In summary, The DGN Annotation Scale helps keep annotation elements consistent and readable across different drawing scales. This prevents annotations from appearing too large or too small when working on the project or printing the drawing.

The annotation scale can be selected by clicking the three-dot icon within the parameter.

![image-20250918-141830.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-141830.png?api=v2)

![image-20250918-141908.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-141908.png?api=v2)

**3D Element Type \[Mesh / Smart Solid]:** This parameter becomes active when the Export File Type is set to '3D Model' and the File Format is selected as 'Microstation (\*.dgn).'

In MicroStation, the term 3D Element Type refers to the type of 3D element within a model or design. Specifically, it can refer to two types of elements:\
\- Mesh:\
A Mesh is a structure made up of many small triangles or polygons that form a surface or object in a 3D model. It is commonly used for modeling complex, organic, or free-form shapes. Mesh elements consist of vertices (points), edges, and faces (surfaces). Meshes are mostly used for surface modeling and do not contain volume information (they are considered hollow).\
\- Smart Solid:\
A Smart Solid is a 3D element created using MicroStation’s solid modeling capabilities. These elements contain not only surfaces but also volume information. Solid models are more suitable for engineering, analysis, and manufacturing processes because they represent real solid properties. Smart Solids can be parametric and editable, meaning shape changes can be made in a controlled and precise manner.

**Include Quantities \[YES/NO]:** This parameter becomes active when the Export File Type is set to '3D Model' and the File Format is selected as 'Microstation (\*.dgn).'

The "Include Quantities" option typically refers to whether dimensional data (quantities) such as volume, area, or length should be automatically included or calculated during modeling or when generating reports.\
Usage Scenarios:\
\- *Sectioning and Reporting:* When taking sections of structural elements, this option determines whether volume, area, or length data are included in the report. For example, if you want to include the volume of a concrete object in the report, you should enable the “Include Quantities” option.\
\- *Exporting / Data Transfer:* When exporting the model (e.g., to IFC, Excel, or other formats), this setting determines whether quantity data should be included in the exported file.

Note: If this option is not enabled, the model will contain only geometry, and quantity data (such as volume or area) will not be calculated or exported.

**Export Roadway Alignment \[YES/NO]:** This parameter becomes active when the Export File Type is set to '3D Model' and the File Format is selected as 'Microstation (\*.dgn).'\
Exporting roadway alignment from OpenBrIM refers to extracting the road alignment data created or stored within OpenBrIM for use in another program.

## IFC Export Settings

The IFC Export Settings consist of a set of input parameters that allow users to configure export options when IFC v4.3 (\*.ifc) is selected as the file format.

**IFC Export Schema \[None / DEFAULT / AASHTO IDM]:** This parameter becomes active when the Export File Type is set to '3D Model' and the File Format is selected as 'IFC v4.3 (\*.ifc).'

The term "IFC Export Schema" refers to a setting that determines which schema (or standard) will be used when exporting a project in the IFC (Industry Foundation Classes) format.\
\&#xNAN;*- None:* When "None" is selected, no specific IFC schema is applied. Typically, a default or standard IFC structure is exported. In some software applications, this option implies that no customized schema will be used, and the export will conform to the general IFC standard in a non-specialized manner.\
\&#xNAN;*- Default:* The "Default" option generally uses the software's built-in IFC export settings. That is, the export will be carried out in accordance with the default IFC standard supported by the application. While this schema may vary across different programs, it typically corresponds to the widely used IFC 2x3 or IFC4 formats. It represents the program’s native IFC schema, suitable for general-purpose use.\
\&#xNAN;*- AASHTO IDM:* This refers to an IDM (Information Delivery Manual) schema developed by the American Association of State Highway and Transportation Officials (AASHTO). An IDM defines the data structures and workflows required for information exchange. This particular schema is used to export IFC files according to specific standards and rules, especially for transportation and infrastructure projects. Selecting the AASHTO IDM schema ensures that the file is prepared in accordance with the specialized information structures required in the field of transportation engineering.

![image-20250918-160710.png](https://openbrim.atlassian.net/wiki/download/attachments/2126774316/image-20250918-160710.png?api=v2)

**Include Property Sets \[YES/NO]:** This parameter becomes active when the Export File Type is set to '3D Model' and the File Format is selected as 'IFC v4.3 (\*.ifc).'

The "Include Property Set" option in an IFC export determines whether or not property sets (Psets) — collections of metadata attached to objects — will be included in the exported IFC file.\
In the IFC format, an object (e.g., a wall, door, or column) is not just geometry. It can carry important non-geometric data, such as:

* Material information
* Fire resistance
* Manufacturer
* Load-bearing capacity
* Thermal properties
* Custom notes or identifiers

These pieces of information are grouped into Property Sets (Psets).

*If "Include Property Set" is Enabled:*

* All property sets (Psets) will be included in the IFC file.
* The exported model contains both geometry and rich metadata.
* This is essential for BIM workflows, where the model is expected to carry usable, sharable information between disciplines and software platforms.

*If "Include Property Set" is Disabled:*

* Only basic object information (usually just geometry) is exported.
* Detailed data like material, fire rating, or manufacturer will not be included.
* The IFC file size is smaller but lacks important data for BIM use.

**Include Quantities \[YES/NO]:** This parameter becomes active when the Export File Type is set to '3D Model' and the File Format is selected as 'IFC v4.3 (\*.ifc).'

The “Include Quantities” option in IFC export determines whether quantity data (measurable values) related to objects will be included in the exported IFC file. In an IFC model, not only the geometry and properties of objects are stored, but also quantitative measurements like area, volume, length, weight, etc.

If “Include Quantities” is enabled:

* Quantity data (quantity sets) related to objects are included in the IFC file.
* For example, length, thickness, and area of a wall; glass area or frame length of a window, etc.
* These quantities are essential for takeoff, cost estimation, and analysis workflows.
* It plays a critical role in BIM processes involving measurements and calculations.

If “Include Quantities” is disabled:

* These numerical quantity details are excluded from the IFC file.
* Only geometry and other properties (property sets) are retained.
* The file is simpler but lacks quantity information needed for takeoff or detailed analysis.

**Base Units \[SI/US]:** This parameter becomes active when the Export File Type is set to '3D Model' and the File Format is selected as 'IFC v4.3 (\*.ifc).'\
The "Base Units" option refers to the unit system used for measurements in the exported model. This setting is important to ensure that the dimensions and data are interpreted correctly in other software that reads the IFC file.

* *SI (International System of Units – Metric)*\
  Based on meters, kilograms, seconds, etc.\
  Standard in most countries including Europe, Asia, and many others.\
  Examples: Length = meter (m), mass = kilogram (kg), area = square meters (m²)
* *US (Imperial / US Customary Units)*\
  Based on feet, inches, pounds, etc.\
  Commonly used in the United States.\
  Examples: Length = foot (ft), mass = pound (lb), area = square feet (ft²)

When exporting an IFC file, the units used in your model must match the units defined in the IFC export. Otherwise:\
\- Lengths, areas, and volumes may be misinterpreted.\
\- Data exchange between BIM software could result in scale issues.\
\- The model may appear incorrectly sized or positioned in the target software

**Set Coordinate System \[YES/NO]:** This parameter becomes active when the Export File Type is set to '3D Model' and the File Format is selected as 'IFC v4.3 (\*.ifc).'\
The "Set Coordinate System" refers to how the coordinate system of the model is defined and applied during export. This setting is crucial for ensuring that BIM models can be shared consistently and accurately across different platforms and disciplines.

The "Set Coordinate System" option determines whether the model is positioned and exported according to:\
\- Global coordinates (e.g., local coordinate system, EPSG codes, geographic references),\
\- Real-world project location (e.g., aligning to survey points or project base points),\
\- How the origin point of the project (project base point or survey point) is set.

Correctly configuring this setting allows:\
\- The model to be aligned with real-world geographic coordinates (important for GIS integration),\
\- Different discipline models (architectural, structural, MEP) to be accurately overlaid and coordinated,\
\- Reduced errors in site-related works such as construction layout, excavation, and site planning.