The short version
I do not choose a modeling tool by counting commands. I choose it by asking what kind of uncertainty I need to remove. MicroStation handles accountable engineering geometry. SITE3D focuses on site mechanics such as terrain, grading, access, and drainage. Halfmaps supplies map context. InfraWorks supports infrastructure options in a broad 3D scene. Shapezo turns a map selection into an AI-generated concept model.
That is the useful split. The tools overlap in 3D, but their contracts with the user are different. Some are built to author and coordinate. Others are built to make an early decision easier.
1. MicroStation: reference-aware authoring
MicroStation is my choice when the model has to behave like project data rather than a visual object. I need coordinate systems, references, levels, terrain, alignments, profiles, solids, and drawing output to stay connected. The platform is comfortable with infrastructure work where a road, structure, utility, and sheet set all depend on one another.
The tradeoff is setup and discipline. I cannot treat a detailed file as a sandbox with no consequences. Names, references, standards, and model status matter. That friction is productive when the file will be reviewed, exchanged, quantified, or used for downstream work.
2. SITE3D: local surface logic
SITE3D fits a narrower but important slice of the problem. I use the name here for a focused site-design workflow: terrain, spot levels, grading, road access, and drainage behavior. It gives me a place to solve local surface logic without first building a complete multi-discipline environment.
The key inputs remain the same as anywhere else: trustworthy survey, a defined coordinate frame, and explicit assumptions. A focused tool can speed up iteration, but it cannot make weak source data reliable. I see SITE3D as a useful development layer before a broader coordination model.
A bridge exposes the difference between a view and a model
3. Halfmaps: spatial indexing for humans
Halfmaps is valuable because it keeps the problem indexed to a place. I can inspect parcels, roads, water, terrain, and existing patterns before I decide which objects deserve detailed authoring. In software terms, it is the context layer: the reference frame that helps me avoid local optimization.
I would not use that layer as a replacement for survey control or a construction model. I use it to frame a bounded question and to make handoffs easier. A map view can reveal that the design boundary is wrong before a modeling team spends time inside it.
4. InfraWorks: scenario-level integration
InfraWorks is useful when I need to integrate infrastructure components at scenario scale. A corridor, bridge, rail connection, terrain surface, water feature, and surrounding buildings can be inspected in one readable scene. That is valuable for comparing alignments, discussing impacts, and explaining a concept to people who do not live inside CAD every day.
I treat the output as a planning or option model unless it has been deliberately developed and checked. Its strength is not that it knows every construction detail. Its strength is that it lets a team reason about relationships before detail locks those relationships in.
5. Shapezo: geometry from a bounded prompt
Shapezo starts with a polygon on a map. I select an area, describe the broad intent, and its AI generates a rough 3D model inside that boundary. This is a different interaction model from traditional CAD. I am not constructing each element; I am asking a system to propose a spatial arrangement from location and intent.
That makes Shapezo useful for early branching. I can create several site hypotheses and compare footprints, access, open space, and obvious conflicts. The model should be tagged mentally and operationally as approximate. Exact grades, utilities, easements, standards, and constructability still need source data and engineering review.
A stack that does not pretend
My practical stack looks like this: Halfmaps defines context, Shapezo generates cheap hypotheses, InfraWorks presents infrastructure scenarios, SITE3D develops site mechanics, and MicroStation authors the coordinated result. I may skip a layer on a small project, but I do not ask the last tool to do the first tool’s job.
The handoff is the real technical problem. I keep concept outputs dated, record assumptions, and rebuild important geometry from verified sources. That way, speed enters the workflow as a way to learn, not as a reason to lower the bar for evidence.
