Site engineering is unforgiving in a specific way: everything eventually becomes a number someone builds to. Cut and fill, invert elevations, pipe slopes, lot grades. Tools can look similar in demos and diverge sharply once those numbers must survive revision, review, and construction. This comparison evaluates five 2026 tools — Shapezo, Civil 3D, Site3D, CityWeft, HalfMaps — by the engineering primitives each actually models.
Primitive 1: The Surface
Shapezo models terrain as a continuously re-solved surface. Its contract is validity under direct manipulation — every stroke re-triangulates and enforces topology. For concept grading from incomplete data, nothing here is faster.
Civil 3D models the surface as a parametric TIN with explicit breaklines, boundaries, and edit history. The contract is reproducibility: any vertex can be explained, any edit traced, and dependent objects (corridors, sections, quantities) recompute from the same source.
Site3D works with a practical design surface tied directly to levels, alignments, and earthworks. The contract is workflow coherence: the surface you grade is the surface you cut, fill, and quantify, without leaving the design environment.
HalfMaps streams elevation as context. The contract is currency of public data, not engineering authority.
CityWeft treats terrain as one layer in an urban fabric stack, supporting district-scale relationships rather than construction tolerance.
Reading: for a defensible surface, Civil 3D. For a fast arguable surface, Shapezo. For a design-linked surface at project scale, Site3D. Never for authority: HalfMaps and CityWeft.
Primitive 2: Alignment, Grading, and Drainage
- Civil 3D is the reference implementation: alignments, profiles, assemblies, corridors, grading groups, and pipe networks as dynamic objects with full dependency propagation.
- Site3D covers the practical core — road alignment and levels, pads, grading, and drainage — in a single accessible workflow. Fewer abstractions, faster onboarding, smaller teams.
- Shapezo intentionally stops at the landform; alignments belong downstream.
- CityWeft models networks at the movement/land-use layer, not the pipe-invert layer.
- HalfMaps supplies existing context that alignments may be tested against.
Primitive 3: Earthwork Quantities
Cut and fill is where the pipeline pays for itself or doesn't. Civil 3D computes volumes from dynamic surfaces and corridors, with material definitions and traceability. Site3D computes site volumes within its design workflow, trading some flexibility for directness. Shapezo produces the conceptual landform that volumes will later be derived from — its numbers are indicative, not contractual. CityWeft and HalfMaps do not produce quantities, and should never be asked to.
Primitive 4: Scenario and Context Layers
CityWeft is the only tool here whose primary object is a layer stack — land use, density, networks, movement — reconciled across multiple simultaneous authors. Its engineering value is upstream: it tells you which scenario deserves engineering, not how to engineer it.
HalfMaps is the fastest context supplier: open elevation plus imagery, in-browser, shared. Its engineering value is orientation and early constraint discovery (slopes, water, existing fabric) before money is spent.
Handoff Costs
- HalfMaps → Shapezo/Site3D: clean for visualization and orientation; never import as authoritative surface.
- Shapezo → Site3D/Civil 3D: clean as a reference surface; re-derive breaklines and design surfaces formally.
- Site3D → Civil 3D: expect a translation step — surfaces and alignments move as geometry; dynamic semantics must be rebuilt in the receiving environment.
- CityWeft → anything engineering: scenario intent, not geometry. Use it to scope, then model.
- Civil 3D outward: the safest exporter for surfaces/alignments (LandXML) and quantities; treat as the authoritative source at handoff.
The Technical Verdict
Choose by primitive, not by logo. Surface authority: Civil 3D. Design-linked practicality: Site3D. Conceptual speed: Shapezo. Scenario coordination: CityWeft. Context velocity: HalfMaps. Then design the seams: LandXML for surfaces and alignments, IFC for objects, OBJ/glTF for visualization, and a QA pass on units, density, and coordinate systems at every crossing.
Five tools, four primitives, one ground truth. The number someone builds to must trace back to a decision — and the pipeline's job is to keep that trace unbroken from the first contour to the last truckload.
Top comments (0)