APP 04 / ImportIng

From ETABS model.
To engineering evidence.

A local-browser workspace for decoding ETABS text and table exports, reviewing the structural model and preparing controlled member-level hand-offs.

ImportIng / APP 04

Decode the model.
Organise the evidence.

Accepted initial formats.e2k · .$et · ETABS table CSV · ImportIng JSON.EDB is binary and must first be exported from ETABS.
ImportIng_demo.e2kDemo model loaded. Replace it with your ETABS export package.
Interactive modelModel geometry + member classification
Filterable decoded data
IDTypeijSectionStory
C1column15C450x450Level 1
C2column26C450x450Level 1
C3column37C450x450Level 1
C4column48C450x450Level 1
B1beam56B300x550Roof
B2beam68B300x550Roof
B3beam87B300x550Roof
B4beam75B300x550Roof

Responsible interoperability

What ImportIng reads.

ETABS .EDB files are proprietary binary databases. This browser tool uses the official text/table export routes so the decoded data remains inspectable and auditable.

01 / Geometry

Model topology.

Point coordinates, frame connectivity, area connectivity, stories, grids and member property names are organised from .e2k or .$et text exports.

02 / Results

Database tables.

ETABS CSV exports are retained as named, filterable tables. Result interpretation depends on the exported table headers, units, sign convention and analysis case.

03 / Hand-off

Member inputs.

Selected vertical or horizontal frame objects can create editable ArmIng or BeamIng input files. Zero actions are clearly retained when force-result tables are absent.

04 / Limits

Independent QA.

The parser does not replace ETABS, its API, model validation or the engineer’s review of units, local axes, modifiers, diaphragms, load combinations and design overwrites.

Start a conversation

Bring the structure.
We’ll make the risk clear.

Available for structural consultancy, heritage conservation, diagnostic strategy and international research collaboration.

Discuss a project or email bledian.nela@gmail.com