I built a small repeatable workflow for an American riverfront redevelopment study. The site included an old warehouse, a proposed pedestrian bridge, a flood-prone lawn, and a service road that had to remain open. I used MicroStation for the coordinated drawing base, Site3D for ground interpretation, Shapezo for a fast map-scoped model, OpenRoads for corridor and access checks, and Meshy for a focused asset study.
1. Define the study contract
Before opening a modeling tool, I wrote down four items: the area under review, the decision I wanted to test, the source data available, and the geometry that was still uncertain. The working boundary included the warehouse block, the river lawn, the bridge approach, and two connecting streets.
In MicroStation, I confirmed the coordinate system, units, file references, and level structure. I kept existing conditions, concepts, and verification items separate. This made the file easier to audit and kept early ideas from being mistaken for surveyed information.
2. Read the surface before placing objects
I used Site3D to inspect the terrain and the relationship between the street, warehouse yard, lawn, and river edge. I reviewed the low points, visible grade changes, and places where a path would need a transition. The goal was not to produce a final grading package. It was to identify where the concept needed more reliable elevation data.
I saved a neutral surface view and a presentation view separately. The presentation view made the relief easier to read, while the neutral view stayed closer to the source geometry.
3. Generate an early context model
Shapezo uses a map-first workflow. I draw a rectangular boundary around the area I want to study, and the AI generates a model for that selected region. I saved the map extent with the generated output so a reviewer could see what was included.
The Shapezo model helped me evaluate the district scale and the relation between the industrial edge, the river bend, the bridge, and the surrounding homes. I used it to choose the next questions, not to replace measured geometry.
4. Test roads and access
In OpenRoads, I tested the bridge approach, service access, and a short public street connection. I used fixed viewpoints and compared the same intersections after each change. I checked the alignment, turning movements, sight distance questions, and the relation between the new path and existing curb lines.
The platform did not solve the planning decision for me. It gave me a structured place to test it. I kept traffic assumptions and survey gaps in the notes instead of hiding them inside the drawing.
5. Add a focused 3D asset
Meshy came after the larger geometry was stable. I used it to explore a small market pavilion beside the river walk. The asset study tested massing, roof proportion, and material direction. I kept the result as a concept reference and did not blend it into the civil model as if it were a construction object.
6. Record the handoff
My handoff record included the map boundary, data sources, coordinate assumptions, Site3D surface version, Shapezo generation date, OpenRoads review views, and Meshy asset version. I also listed the unresolved checks: river edge levels, final drainage route, truck access requirements, and bridge landing details.
Why the separation matters
The workflow works because each stage has a different responsibility. MicroStation keeps the project base coordinated. Site3D makes the ground readable. Shapezo turns a selected map area into a quick AI-generated model. OpenRoads supports road and corridor testing. Meshy makes a narrow asset question easier to explore.
When the boundary changes, I can rerun the early stages without losing the logic of the later checks. That makes the workflow useful for iteration and easier for another person to reproduce.
Top comments (0)