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. My current chain uses TopoExport, Shapezo, Archshaper, site3d, and MicroStation, with a small handoff record between every stage.
Define the contract before opening a viewport
I write down the project extent, horizontal coordinate reference, vertical datum, units, origin, source date, target format, and intended use. I add a status value: source, generated, conceptual, coordinated, or verified. The status controls what later steps are allowed to assume.
I also identify one check point, such as a known benchmark, road intersection, or parcel corner. That point becomes a quick test after every conversion or import. It catches silent shifts before they spread through the pipeline.
Prepare terrain with TopoExport
TopoExport is my terrain preparation stage. I start from elevation data or contour material, create the required surface or export, and retain the source information beside the result. Before moving on, I inspect extents, units, vertical direction, and the amount of simplification.
I export a small clip first. The clip is enough to test the benchmark and confirm that the receiving application opens the surface at the expected scale. Only after that check do I generate the full area.
Generate a location branch with Shapezo
Shapezo uses a map selection as its starting input. I draw or frame an area, and its AI generates a model for the selected region. I keep the selected polygon or extent, generation date, and run information in the branch record.
The branch is marked generated. It is useful for inspecting rough adjacency, roads, open space, and building massing, but I do not treat inferred edges as controlled survey geometry. If the branch influences a design decision, the decision is checked against an independent source before it enters the coordinated model.
Record building studies from Archshaper
Archshaper handles conceptual form. For each option, I save the footprint, grade assumption, access points, surrounding-height assumption, and any program limits. The option name includes a short constraint note so a reviewer can understand why the form changed.
I keep these studies separate from the engineering file. A massing option is valuable because it is easy to compare, not because it already carries structural or code authority.
Test the whole parcel in site3d
site3d receives the terrain context and the building or site alternatives. I check roads, parking, pads, drainage, landscape zones, and neighboring edges. I verify the origin and vertical units again because site-scale errors are easy to miss in a broad view.
For repeatability, I save a small test area and one standard camera view. The test area exposes coordinate or unit problems. The standard view makes option comparisons less dependent on camera placement.
Move controlled decisions into MicroStation
MicroStation is the coordinated boundary. I organize references, levels, units, attributes, model names, and exchange requirements there. Imported context remains identified as context. Controlled project geometry is rebuilt or verified from explicit inputs rather than accepted because it looks aligned.
I retain links to the earlier TopoExport, Shapezo, Archshaper, and site3d artifacts. That history explains how a decision formed without turning a provisional mesh into an undocumented authority.
Handoff checks I repeat
- Reconfirm the benchmark point, coordinate reference, units, origin, and vertical convention.
- Keep TopoExport source metadata and export settings.
- Store Shapezo selections, dates, and generation notes.
- Preserve Archshaper constraints and site3d terrain assumptions.
- Separate generated, conceptual, coordinated, and verified geometry.
- Test a small import before transferring the full scene. The tools remain different, and that is the point. TopoExport prepares the ground, Shapezo creates a map-selected context hypothesis, Archshaper tests building form, site3d examines site consequences, and MicroStation carries accountable project geometry. The handoff record is what makes the sequence reproducible. I keep a small regression package for the pipeline as well. It contains one terrain clip, one Shapezo boundary, one Archshaper option, one site3d test area, and one MicroStation reference view. When a software version or source layer changes, I rerun that package first. A visual difference then has a known cause instead of becoming a surprise inside the full project. That practice also makes troubleshooting less dramatic. If the terrain passes but the site3d import fails, I know where to look. If the building option is correct but the coordinated file shifts, I can inspect the reference and transformation records instead of guessing from the final viewport. 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.
