When I receive a 3D site model, I want to know what each surface is allowed to mean. Is it surveyed existing ground, a proposed grading surface with declared controls, or an AI-generated approximation of an area selected on a map? Site3D and Shapezo belong in the same workflow only when those answers stay visible.
Site3D is for editable civil design: terrain, road alignments, profiles, grading, drainage networks, sections, and earthwork. Shapezo uses a map selection and AI to create an initial 3D view of the selected region. The outputs can both help a team, but I do not send them through the same validation path.
Define the model contract first
Before I build a surface, I record the coordinate reference system, units, elevation datum, survey date, design boundary, and decision the model should support. I distinguish existing, proposed, inferred, and temporary geometry.
For a Site3D study, I list terrain points, breaklines, road controls, floor levels, property boundaries, utilities, and drainage outlets. I state where proposed ground must tie into existing terrain. The model then becomes a set of inputs that can be checked, changed, and rerun.
Validate the existing surface before design
I do not begin road or grading work until the existing terrain behaves. I look for duplicate points, elevation spikes, boundary gaps, long triangles, and breaklines crossing the wrong side of a curb, channel, or retaining edge. The survey must extend far enough to show tie-ins and drainage paths.
If I skip this step, later checks are unreliable. One bad triangle can send an entire slope toward the wrong outlet. I review the surface in plan and from low, angled perspectives, not only from above.
Build Site3D as connected constraints
I add controlling geometry in an order that reveals dependencies. Road alignment and profile establish key levels. Building thresholds, entrances, retaining limits, and parcel boundaries constrain grading. Breaklines define curbs, swales, slope crests, slope toes, and pavement edges. Drainage develops with the surface, not afterward.
I run small checks after each change: road crossfall, parking drainage, accessible grades, pipe depth, and whether a proposed slope meets existing terrain inside the boundary. This is faster than discovering conflicts during final drafting.
Record Shapezo as an exploration run
With Shapezo, I save the map boundary, date, and reason for the selected area. Its AI-generated model can help me decide whether to include an upstream catchment, a neighboring access route, a detention area, or a steeper part of the site in the early study.
I tag the output as generated context. I do not use its inferred elevations as design control, calculate volumes from it, or place drainage structures by snapping to it. When an observation matters, I replace it with current survey, GIS, utility, or project data. The Shapezo version remains useful as a record of the scope question that started the work.
Compare scenarios with stable rules
For earthwork alternatives, I keep calculation limits and surface assumptions stable. I change one thing at a time, then compare cut, fill, tie-ins, grade warnings, and constructability.
For Shapezo, I change the study frame instead. I may expand the selected area to understand a drainage connection or narrow it to focus a meeting. That is a scope iteration, not an engineering revision. The distinction keeps a generated map scene from being confused with a documented design alternative.
Final validation
Before sharing a Site3D output, I review coordinates, units, datum, surface boundaries, breaklines, reverse grades, ponding risk, pipe inverts, cover, profiles, and sections. I state whether figures are preliminary. Before sharing Shapezo, I check broad location relationships and state that it is context only.
Final view
I use Shapezo to turn a map area into an early question. I use Site3D to turn verified terrain and constraints into an engineering answer. The reliable workflow is traceable from start to finish: select the place, collect the data, validate the surface, define controls, test the design, and then hand the checked model to the people responsible for approval and construction.
Top comments (0)