A Reproducible Terrain-to-BIM Workflow with TopoExport, Shapezo, Archshaper, site3d, and MicroStation

Description and use

A step-by-step workflow that ensures reproducible transfer from terrain data to BIM, with coordinate and unit checks at every stage.

Problem

Ensuring reliable, reproducible transfer of terrain, context, and building concepts across multiple software tools without silent coordinate or unit shifts.

Outcome

The workflow produces a reproducible, auditable BIM model with clear provenance, reducing errors and simplifying troubleshooting.

Workflow

• Define project contract and benchmark point before opening any viewport
• Prepare terrain with TopoExport: create surface, inspect extents, units, and simplification, export a small clip for testing
• Generate a location branch with Shapezo: select area, run AI generation, record polygon, date, and run info
• Record building studies with Archshaper: save footprint, grade, access points, constraints, and option names
• Test the whole parcel in site3d: import terrain and building alternatives, verify roads, parking, drainage, origin, units, and save a small test area with a standard camera view
• Move controlled decisions into MicroStation: organize references, levels, units, attributes, rebuild or verify geometry, link to earlier artifacts
• Repeat handoff checks: reconfirm benchmark, coordinate reference, units, origin, keep source metadata, store selections and constraints, separate geometry states, test small import before full transfer
• Maintain a small regression package for the pipeline to rerun when software or source layers change

Evidence

I get more reliable results when I treat each tool as a pipeline stage instead of exporting a finished-looking scene and hoping the next application interprets it correctly.

Source

I keep the test package small enough to run after a normal edit. That makes it part of the workflow rather than a special event saved for the end of a project.

Source