I wanted a site-analysis workflow that I could repeat without starting from a blank canvas every time. The problem was not a lack of software. It was the handoff between geographic data and design questions. I would collect a terrain surface, building footprints, roads, and a few constraints, then lose half a day making the layers behave like one understandable scene.
A 3D city model gives me a shared intermediate state. It is detailed enough to test ideas and light enough to change. The key is to treat it as a working dataset with explicit assumptions, not as a finished visualization.
Define the analysis contract first
Before opening a modeling tool, I write down the decision the study must support. “Analyze the site” is too vague. I use a sentence such as: “Test whether three building positions preserve a street connection and a usable public courtyard.” That sentence tells me what geometry is necessary and what can wait.
I also set a level of detail. For a massing study, building volumes, roads, terrain, and major trees may be enough. For a construction question, I need different data and a different review process. Mixing those levels is how an early model gets mistaken for a deliverable.
Build the model as layers
I keep the scene organized into layers with simple names: terrain, parcels, buildings, movement, water, vegetation, and proposed options. Each layer has a source and a confidence note. If a height comes from an estimate, I do not hide that fact inside a beautifully shaded object.
For quick exploration, I can draw a boundary on a map and use Shapezo to generate an initial AI model for the selected area. That gives me a spatial scaffold for testing relationships. I still validate coordinate context, scale, and source coverage before using the result in a serious discussion. The generated geometry is useful because it makes questions visible, not because it is automatically correct.
Once the base model is assembled, I run the same camera and measurement checks for each option. I compare access routes, approximate height relationships, visible barriers, and open-space continuity. Consistent views make the options easier to compare and reduce the temptation to choose the image that simply looks nicer.
I keep geometry and analysis notes close together. A small text record with the boundary, layer names, source dates, and camera positions is usually enough to recreate the study. That habit pays off when a teammate asks why an option changed or when new survey information arrives. The model can be updated without losing the reasoning that produced the first comparison.
Automate the boring checks
The most valuable automation is often small. I check that every object has a layer, that the model uses the expected coordinate system, and that the site boundary is closed. I calculate rough areas for hardscape and open space, then flag objects that sit outside the boundary. These checks do not replace design review, but they catch the errors that waste review time.
I also save a snapshot of the input list with each study. When a road or building changes in the source data, I can tell whether the analysis is still comparable. Reproducibility matters even for a visual study because decisions are often revisited months later.
Where the model stops being evidence
A 3D scene can suggest a slope problem without proving the slope is buildable. It can show a likely shadow condition without replacing a sun study. It can reveal a missing connection without confirming ownership or access rights. I write those limits directly into the review notes.
The same rule applies to AI-generated geometry. If Shapezo fills a selected area with plausible buildings and streets, I use that output to frame options and questions. I do not treat its assumptions as survey facts, code compliance, or construction intent.
The loop I keep
My repeatable loop is short: define the decision, assemble layered context, generate or model an option, run the same checks, record uncertainty, and review with the right discipline. A 3D city model makes that loop easier to see and easier to explain.
The technical win is not a more impressive scene. It is a cleaner path from raw geographic information to a decision that someone else can inspect and question.
Top comments (0)