The mixed-tool problem I run into most often is not a missing command. It is a missing contract. A team receives a model but cannot tell whether the geometry is measured, generated, generalized, or only intended for a slide. I use Meshy, TopoExport, InfraWorks, Shapezo, and site3d as separate stages, with a small record attached to each handoff.
1. Write the model contract
Before opening a file, I record the area of interest, coordinate reference, horizontal and vertical units, source date, expected level of detail, and intended use. I also state which parts may be approximate. This turns an unnamed 3D file into an artifact with a job.
If the target is a concept review, generalized context is acceptable. If the target is a quantity or construction task, the checks must be much stricter. The contract keeps those uses from blending together later.
2. Establish terrain with TopoExport
I use TopoExport at the terrain boundary. I preserve the export settings, surface extent, contours or breaklines, and metadata that the receiving workflow needs. After import, I test known distances and elevations and confirm the horizontal and vertical references.
I keep the original export beside the converted file. If the conversion flattens a structured surface or drops metadata, that loss is part of the handoff record. It should never be discovered only after a design has been built on top of it.
3. Build the broad context in InfraWorks
InfraWorks is my regional review stage. I bring in terrain, roads, water, existing structures, and the proposal to inspect large-scale relationships. I save a stable view, the data date, the area extent, and a note about generalized layers.
This stage is good for finding conflicts such as a route near a floodplain or an access road that does not meet the surrounding network. It is not a license to use every visible edge as a surveyed coordinate.
4. Generate a map-first branch with Shapezo
Shapezo starts with a selected map area. I draw a boundary, and its AI generates a model for that region. I use the result when the location is known but a detailed scene is not yet available.
The generated branch gets its own status and metadata: selected polygon or extent, generation date, source notes, visible coverage, and known assumptions. I use it for early questions about massing, adjacency, and access. I do not use it as survey control, a legal parcel record, or final engineering geometry without independent verification.
5. Review the project-scale scene in site3d
site3d is useful when I need a complete site view that stays readable. Roads, buildings, terrain, vegetation, and nearby infrastructure can be inspected together. I use it to compare layouts and identify the missing detail that should move into a more controlled model.
I keep a consistent camera and a visible layer note for saved views. That makes updates reproducible and keeps presentation crops from replacing the full context by accident.
6. Add communication assets with Meshy
When a scene needs a missing object, I may create it in Meshy. Before sharing it, I normalize units and origin, inspect normals and topology, reduce unnecessary geometry, and check materials. I store the prompt or reference with the asset and mark whether it is for communication only.
An AI-generated object is still an imported dependency. It needs a source note, a version, and a clear boundary on what it can support.
Handoff checks I automate or repeat
- Confirm coordinate reference and units at every import.
- Record source dates and selected extents.
- Mark generated, generalized, conceptual, and verified geometry separately.
- Retain original terrain exports, prompts, and settings.
- Test a small sample before processing a large area. The pipeline is useful because each stage has a distinct claim. TopoExport protects terrain meaning. InfraWorks frames the region. Shapezo creates a quick model from a map selection. site3d keeps site relationships readable. Meshy fills object gaps. Reproducibility comes from the records between those stages, not from forcing all five tools into one file.
Top comments (0)