Import & export formats
IFC structural models and SAF workbooks in and out, DXF as a reference drawing, result tables as CSV or xlsx, and an OOFEM input deck.
Results & reports 5 min read
Besides its own project file, Elementarium reads IFC, SAF and DXF, and writes IFC, SAF, an OOFEM input deck, result tables, PNG images and the PDF report. None needs a plugin.
| Format | Direction | What it carries |
|---|---|---|
.elproj | In and out, every plan | The whole project, lossless |
IFC (.ifc) | In and out | The structural analysis view: model, loading and, between Elementarium projects, everything else |
SAF 2.2 (.xlsx) | In and out | The analysis model and its loading |
| DXF | In | A reference underlay to snap against — no members, nodes or loads |
| OOFEM input deck | Out | The analysis, with its solver settings, for an independent solve |
CSV, .xlsx, clipboard | Out | Result tables, with their filters; the clipboard on every plan |
| PNG | Out, every plan | A capture of a viewer, with its legend |
| Out | The report |
The project file
File › Save as (Ctrl S) writes the project to an .elproj file and File › Open
(Ctrl O) reads one back. It is not a translation: the file is the project's own document,
so everything the project holds comes back exactly — geometry, loads, load groups and
combinations, analysis setups, design checks, drawings, report configuration and project
settings, including anything a later version of the app has added that this one has
never heard of. IFC and SAF go through an intermediate model, and another program receives only what that
format can express; this file does not.
Opening a file replaces the content of the current project. The project itself, its URL and the people it is shared with stay, which is the same contract the IFC and SAF imports have. To keep both, create a new project first and open the file into that.
The file works on every plan, so it is the copy of a milestone that lives outside the project and its version history, the way to hand a model to someone outside the project, and the way to keep a model after a subscription ends.
IFC — the structural analysis view
IFC is the format BIM and detailing tools write. Elementarium reads the structural analysis view of an IFC2X3, IFC4 or IFC4X3 file — nodes, members, plates, supports, releases, load cases, combinations and loads — in whatever units the file declares, and writes the project back as an IFC4 structural analysis view. Between Elementarium projects, everything the app models survives the round trip: what standard IFC cannot express travels in an Elementarium property set. Other programs ignore that set and receive the standard part, including the loads it produces. Imported entities keep their GlobalIds through edits, so an export goes back with the identities it came in with.
A file that holds only the architectural model (IfcBeam, IfcColumn and IfcSlab
solids) is not imported. See IFC structural models for the mapping,
the tolerances and what IFC cannot say.
SAF — models in and out
The Structural Analysis Format is an open, spreadsheet-based
interchange format: an .xlsx workbook with one worksheet per object type. Elementarium
reads and writes SAF 2.2, which is what SCIA Engineer, RFEM and others speak.
What travels:
| Carried | Detail |
|---|---|
| Geometry | Nodes and members, with interior nodes preserved |
| Members | Section, material, local axis orientation, end releases, analysis eccentricity |
| Surfaces | Plates with their openings, and what is attached to them |
| Constraints | Rigid arms |
| Libraries | Materials and cross-sections |
| Loading | Load groups, load cases, combinations, and the loads themselves |
Axes are carried, not converted. SAF states which way is up in its global coordinate system field, and so does an Elementarium project. The geometry is imported untouched and the file's vertical becomes the project setting — no rotation, no sign flips, and a round trip gives back the coordinates that went in. The one case that cannot be taken is a file with X vertical, which leaves nothing for the viewer's plane to be built on; the import stops rather than guessing.
DXF — a drawing to work against
A DXF is imported as a reference underlay, not as a model. Nothing in it becomes a member, a node or a load; it gives you accurate geometry to snap against while you draw.
- Units, plane and placement are yours to set.
- Blocks stay as inserts rather than being exploded.
- Object snap finds endpoints, intersections, centres, midpoints, quadrants and insertion points from the entity definitions, not from the rendered curves.
OOFEM input deck
An analysis exports as an OOFEM input file: nodes, elements, materials, cross-sections, boundary conditions and the solver settings the analysis was configured with. The settings matter: an analysis in Elementarium is its solver settings, so exporting one without them would hand OOFEM a different problem.
Load cases become solution steps. OOFEM has no load case; it has a step and a load-time function on every load record, which is enough to carry the whole set in one file:
| Elementarium | OOFEM |
|---|---|
| Pure load case | A step that scales itself by 1 |
| Combination | A step carrying its γ factors |
| Envelope combination | One step per permutation |
Two options:
| Option | Effect | Why it is optional |
|---|---|---|
| Annotate | Writes an # <Elementarium id> comment above each record, so you can find a member | Doubles the line count |
| ParaView output | Adds a vtkxml export module, so the run also produces .vtu files for ParaView | Off by default: OOFEM writes one file per solution step next to the input |
Result tables — CSV, xlsx and the clipboard
Any result table exports with its filters applied, in three forms:
| Format | For |
|---|---|
| CSV | Anything that reads text |
.xlsx | A spreadsheet — real numbers in the cells, so you can sum and chart them |
| Clipboard | Paste straight into whatever is already open |
CSV and the clipboard carry formatted text at the table's own decimal places; the spreadsheet carries the numbers themselves.
The report
The calculation package goes out as PDF. See Exporting a report.
Earlier versions
Exports write the current model. To export an earlier state, open it from version history and Restore as new project, then export that. The original project is not touched.
Something wrong or unclear on this page? Tell us, and it gets corrected.