DEV Community

Cover image for Shapezo vs. Site3D: A Clear Modeling Boundary
MapToModel
MapToModel

Posted on

Shapezo vs. Site3D: A Clear Modeling Boundary

Shapezo and Site3D sit on opposite sides of a useful site-modeling boundary. Shapezo captures contextual design intent: massing, public edges, landscape, circulation, and relationships to surrounding American buildings. Site3D develops focused terrain and site logic: grades, pads, parking, access, retaining conditions, and drainage concepts.

Treat intent and ground logic as different states

A Shapezo study is a spatial hypothesis. It can reveal whether a civic entrance belongs to a terrace or whether a campus edge connects to a green, but approximate geometry should not be treated as survey authority.

Site3D is useful when the project needs direct control of site geometry. Its model should still carry units, coordinate origin, surface extents, vertical assumptions, breaklines, and export expectations. Do not let a focused site model become authoritative by accident.

Context is a dependency, not decoration

The grading decision changes the architectural experience. A finished floor affects the entry. A retaining wall changes the public edge. A drainage channel may become a landscape feature or a barrier.

Shapezo provides the scene in which those relationships can be discussed. Site3D provides a focused environment in which ground consequences can be tested. Keeping both views available is more reliable than treating context as a static background.

A minimal exchange contract

  • project_id and option_id for traceability.
  • units, coordinate_reference, and vertical_datum for predictable placement.
  • surface_extent and breakline_policy for terrain scope.
  • design_invariants for public access, setbacks, tree protection, or water edges.
  • validation_state such as concept, checked, or approved-for-coordination.
  • owner and next_check so unresolved questions have a destination.

The exact schema can vary. The model should still explain what is authoritative, what is derived, and what remains provisional.

A repeatable handoff

  1. Establish the site story and design invariants in Shapezo.
  2. Document coordinates, units, sources, and approximate level of development.
  3. Rebuild or validate the ground logic in Site3D.
  4. Test grades, pads, access, parking, retaining conditions, and drainage.
  5. Run an exchange test before the model becomes the basis for detailed civil work.

Engineering risks to keep visible

The main Shapezo risk is intent being mistaken for measured geometry. The main Site3D risk is exchange uncertainty being discovered after downstream production begins. Both risks shrink when the receiving team knows the assumptions and the next check.

For generated or approximate surfaces, keep a source log and confidence note. Rebuild any object that becomes structurally, quantitatively, or legally significant.

Decision rule

Use Shapezo when the dominant uncertainty is design intent and context. Use Site3D when the dominant uncertainty is terrain and site coordination. Use both when the project needs a memorable place and a dependable ground model.

Top comments (0)