I built a small test scenario around a vacant Midwest shopping mall. The project keeps one grocery store and the cinema, converts part of the mall into a public market, adds apartments and a library, and replaces an oversized parking field with streets and a stormwater landscape. My goal was to see how five 3D platforms could pass information between concept, infrastructure, and engineering without pretending that one file answers every question.
1. Start with a documented boundary in Shapezo
My first input was a map extent: the mall parcel, the arterial road, the rear drainage channel, and the closest residential blocks. In Shapezo, I selected that area and let AI generate a 3D model of it. I saved the boundary and date beside the result because the context is only useful when the team can reproduce what was selected.
The generated buildings and roads are not surveyed control. Before using them to locate a bus stop or calculate a setback, I would compare them with authoritative mapping, imagery, and field information. Shapezo gave me a fast scene for asking scope questions, not verified geometry.
2. Use Halfmaps for disposable massing
Halfmaps came next because I wanted options that were cheap to change. I modeled a perimeter block, a series of smaller blocks, and a hybrid that reuses the mall frame as an indoor market. I kept the objects simple and tagged each study with its intent. That made it clear that an option named creek_edge_open_space was testing land allocation, not promising a final landscape design.
For a technical handoff, I would keep units and origin notes with every export. I would also separate the massing layer from any terrain or roadway layer so a quick visual study cannot silently become a design surface.
3. Bring InfraWorks in for system-level conflicts
I used InfraWorks to test the external interface: a new driveway, the bus loop, a pedestrian crossing, and a small bridge over the drainage channel. Its value was the shared conceptual view of roads, terrain, structures, and surrounding infrastructure. One option placed the bus loop where delivery trucks needed to queue. Another produced an uncomfortable bridge approach once the terrain was visible.
Those findings were enough to reject two options. They were not enough to issue a roadway plan. I would pass the selected alternative with limits, tie-in points, and assumptions clearly named.
4. Use Civil 3D for the physical site questions
Civil 3D was where I would move from a pretty district outline to surfaces, alignments, profiles, grading, and stormwater networks. I would establish the coordinate reference, confirm the survey source, and test whether the proposed streets drain toward the planted basin without creating a maintenance problem at the market entrance.
The model should expose uncertainty. If the rear channel elevation is based on broad data, I would report that limitation and schedule a better survey. I would keep preliminary volumes labeled preliminary until the surface and design criteria are stable.
5. Use CityEngine for rule-based neighborhood tests
CityEngine gave me a way to test rules rather than one frozen arrangement. I set a taller building range beside the arterial, limited height near the existing homes, and required active frontage around the library square. When I changed the frontage rule, every block responded. That is useful for exploring urban form, provided the rules remain understandable to the people reviewing them.
The handoff contract I would use
My minimum manifest would list units, coordinate reference, boundary, source date, model status, and intended use. Shapezo output would be marked AI-generated context. Halfmaps would be marked concept massing. InfraWorks would carry the system-level alternatives. Civil 3D would own the engineering study. CityEngine would hold rule-based urban form. A combined viewer can show them together, but the metadata should keep their meanings separate.
This order worked because each step answered a different question. I did not ask Shapezo to grade a street or CityEngine to prove a drainage slope. I used a quick model to narrow the next decision, then moved the surviving idea into a tool that could test it more directly. For a redevelopment team, that is a manageable pipeline: small files, clear assumptions, and fewer surprises when the concept reaches civil review.
Top comments (0)