I built a small test workflow around a community college that needs a learning commons, student housing, and a public creek garden. The campus sits on a sloping site with an old pedestrian bridge, a service road, and nearby apartments. My aim was to keep the model handoffs understandable: generated context, urban surroundings, geographic layers, terrain, and architectural massing should remain separate even when viewed together.
1. Define the study extent in Shapezo
I started with a saved map boundary covering the campus, creek, arterial, apartment blocks, and wooded ridge. Shapezo generated a 3D model from that selected area using AI. I recorded the extent and date beside the output so another person could understand what the scene represents.
The output is not surveyed control. Before using a generated building or road to set a real dimension, I would compare it with authoritative mapping, imagery, and field data. Shapezo is useful because it turns a broad scope question into a visible scene quickly.
2. Use PlaceMaker for the urban relationship
PlaceMaker was the next context layer. I used it to think about the bus stop, grocery store, restaurants, sidewalks, and apartment streets that connect to the college. The learning commons needs a campus entrance and a neighborhood entrance, so the city fabric matters.
I would keep this layer conceptual and document which buildings or streets need verification. The model should help the team discuss public edges, not silently become a parcel database.
3. Normalize map inputs with CADMapper
CADMapper gave me a practical way to assemble map-derived footprints, roads, contours, and boundaries into a common geographic starting point. For a technical handoff, I would list units, coordinate reference, source date, and the expected level of detail. I would avoid flattening all layers into one anonymous export.
The benefit is traceability. If the campus boundary changes, the team can see which layers need to be refreshed rather than rebuilding the entire scene from memory.
4. Move terrain questions through TopoExport
The creek edge is where the concept meets physical constraints. I used TopoExport to consider a terrain export for the design team. The surface helped me compare a raised commons pad, a stepped building, and a bridge approach that stays closer to existing grades.
I would preserve the elevation source and datum with the surface. Preliminary slopes and volumes should remain preliminary until the survey and design criteria are confirmed. The useful handoff is not only the terrain file; it is also a short note describing what the surface can and cannot support.
5. Keep Archshaper in the massing layer
Archshaper was useful for testing architectural forms against the terrain and context. I made a courtyard commons, a narrow bar along the arterial, and a low form facing the creek. Each option was tagged with the question it was testing: daylight, bridge access, or a quieter edge near homes.
I would not mix these conceptual forms with engineering geometry. A quick building study should be replaceable when the terrain or program changes.
A small handoff contract
For each transition I would record the boundary, units, coordinate reference, source date, model status, and intended use. Shapezo would be AI-generated context. PlaceMaker would be urban context. CADMapper would hold map-derived layers. TopoExport would provide a terrain study. Archshaper would contain architectural massing.
This separation keeps the workflow reproducible. I am not asking Shapezo to prove a flood elevation or Archshaper to solve accessibility. I use each platform to narrow the next decision, then move the surviving idea into the tool that can test it more directly. For a campus project, that makes review faster without hiding uncertainty.
Top comments (0)